All of lore.kernel.org
 help / color / mirror / Atom feed
From: sashiko-bot@kernel.org
To: "Alex Ousherovitch" <aousherovitch@rambus.com>
Cc: devicetree@vger.kernel.org, robh@kernel.org, conor+dt@kernel.org
Subject: Re: [PATCH 3/5] crypto: cmh - add key/datastore infrastructure
Date: Tue, 13 Oct 2026 17:58:02 +0000	[thread overview]
Message-ID: <sashiko-outbox-170283@kernel.org> (raw)
In-Reply-To: <20261013174847.2192609-4-aousherovitch@rambus.com>

Thank you for your contribution! Sashiko AI review found 1 potential issue(s) to consider:
- [Low] crypto: cmh: missing implementation for QSE and HCQ VCQ builders
--

commit edeafa889ed6c19c029045fbf5064008f9e6f3d7
Author: Alex Ousherovitch <aousherovitch@rambus.com>

crypto: cmh - add key/datastore infrastructure

This commit adds the CMH key and datastore system object layer shared by
the algorithm drivers. It implements context staging, DMA mapping, and
VCQ builder functions.

> diff --git a/drivers/crypto/cmh/include/cmh_sys.h b/drivers/crypto/cmh/include/cmh_sys.h
> new file mode 100644
> index 0000000000000..47c19e2f72a93
> --- /dev/null
> +++ b/drivers/crypto/cmh/include/cmh_sys.h

[ ... ]

> +/* QSE core VCQ builders */
> +void vcq_add_qse_flush(struct vcq_cmd *slot, u32 core_id);

[Severity: Low]
Are the implementations for the QSE and HCQ VCQ builders missing?
They are declared here in the header, but they do not appear to be implemented
in cmh_sys.c or used anywhere in the current tree.

Since these prototypes constitute dead code right now, should their
declarations be deferred until the patches that introduce the QSE and HCQ
drivers?

> +void vcq_add_qse_ml_kem_keygen(struct vcq_cmd *slot, u32 core_id, u32 k, u32 flags,
> +			       u64 seed, u64 z, u64 ek, u64 dk, u32 dk_type,
> +			       bool masked);

[ ... ]

-- 
Sashiko AI review · https://sashiko.dev/#/patchset/20261013174847.2192609-1-aousherovitch@rambus.com?part=3

  reply	other threads:[~2026-10-13 17:58 UTC|newest]

Thread overview: 12+ 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-13 17:57   ` sashiko-bot
2026-10-13 17:48 ` [PATCH 2/5] crypto: cmh - add core platform driver Alex Ousherovitch
2026-10-13 18:13   ` sashiko-bot
2026-10-13 17:48 ` [PATCH 3/5] crypto: cmh - add key/datastore infrastructure Alex Ousherovitch
2026-10-13 17:58   ` sashiko-bot [this message]
2026-10-13 17:48 ` [PATCH 4/5] crypto: cmh - add AES skcipher/aead/cmac Alex Ousherovitch
2026-10-13 18:02   ` sashiko-bot
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

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=sashiko-outbox-170283@kernel.org \
    --to=sashiko-bot@kernel.org \
    --cc=aousherovitch@rambus.com \
    --cc=conor+dt@kernel.org \
    --cc=devicetree@vger.kernel.org \
    --cc=robh@kernel.org \
    --cc=sashiko-reviews@lists.linux.dev \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.