mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Krzysztof Kozlowski <krzk@kernel.org>
To: Alex Ousherovitch <aousherovitch@rambus.com>,
	Conor Dooley <conor+dt@kernel.org>,
	"David S. Miller" <davem@davemloft.net>,
	Herbert Xu <herbert@gondor.apana.org.au>,
	Jonathan Corbet <corbet@lwn.net>,
	Krzysztof Kozlowski <krzk+dt@kernel.org>,
	Rob Herring <robh@kernel.org>,
	Saravanakrishnan Krishnamoorthy <skrishnamoorthy@rambus.com>
Cc: devicetree@vger.kernel.org,
	Joel Wittenauer <Joel.Wittenauer@cryptography.com>,
	linux-crypto@vger.kernel.org, linux-doc@vger.kernel.org,
	linux-kernel@vger.kernel.org,
	Shuah Khan <skhan@linuxfoundation.org>,
	Thi Nguyen <thin@rambus.com>
Subject: Re: [PATCH 2/5] crypto: cmh - add core platform driver
Date: Wed, 14 Oct 2026 08:01:09 +0200	[thread overview]
Message-ID: <1190d520-fbf3-410e-b9db-f940370d0533@kernel.org> (raw)
In-Reply-To: <20261013174847.2192609-3-aousherovitch@rambus.com>

On 13/10/2026 19:48, Alex Ousherovitch wrote:
> Add the Rambus CryptoManager Hub (CMH) hardware crypto accelerator
> core platform driver.  This patch provides:
> 
> - Platform driver registration and probe/remove lifecycle
> - Hardware configuration and core discovery
> - Mailbox Queue Interface (MQI) for VCQ command submission
> - Transaction manager with async completion and backlog support
> - Result handler with threaded-IRQ completion
> - DMA buffer management
> - Debugfs instrumentation (when CONFIG_CRYPTO_DEV_CMH_DEBUG=y)
> - Sysfs attributes (fw_version, hw_version, boot_status,
>   mbx_available, mbx_count)
> - Kconfig and Makefile integration
> 
> No crypto algorithms are registered yet -- those follow in
> subsequent patches.
> 

Implement feedback you already received on v1, v2, v3, v4 and v5.

Best regards,
Krzysztof

  reply	other threads:[~2026-10-14  6:01 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-10-13 17:48 [PATCH 0/5] crypto: cmh - add Rambus CryptoManager Hub core driver and AES Alex Ousherovitch
2026-10-13 17:48 ` [PATCH 1/5] dt-bindings: crypto: add Rambus CryptoManager Hub Alex Ousherovitch
2026-10-14  5:58   ` Krzysztof Kozlowski
2026-10-14  5:59   ` Krzysztof Kozlowski
2026-10-14  6:59     ` Ousherovitch, Alex
2026-10-13 17:48 ` [PATCH 2/5] crypto: cmh - add core platform driver Alex Ousherovitch
2026-10-14  6:01   ` Krzysztof Kozlowski [this message]
2026-10-13 17:48 ` [PATCH 3/5] crypto: cmh - add key/datastore infrastructure Alex Ousherovitch
2026-10-13 17:48 ` [PATCH 4/5] crypto: cmh - add AES skcipher/aead/cmac Alex Ousherovitch
2026-10-13 17:48 ` [PATCH 5/5] MAINTAINERS: add Rambus CryptoManager Hub (CMH) Alex Ousherovitch
2026-10-13 17:57 ` [PATCH 0/5] crypto: cmh - add Rambus CryptoManager Hub core driver and AES Conor Dooley
2026-10-13 18:35   ` Ousherovitch, Alex
2026-10-14  5:58 ` Krzysztof Kozlowski

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=1190d520-fbf3-410e-b9db-f940370d0533@kernel.org \
    --to=krzk@kernel.org \
    --cc=Joel.Wittenauer@cryptography.com \
    --cc=aousherovitch@rambus.com \
    --cc=conor+dt@kernel.org \
    --cc=corbet@lwn.net \
    --cc=davem@davemloft.net \
    --cc=devicetree@vger.kernel.org \
    --cc=herbert@gondor.apana.org.au \
    --cc=krzk+dt@kernel.org \
    --cc=linux-crypto@vger.kernel.org \
    --cc=linux-doc@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=robh@kernel.org \
    --cc=skhan@linuxfoundation.org \
    --cc=skrishnamoorthy@rambus.com \
    --cc=thin@rambus.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox

all inboxes | Powered by JetHome®