From: sashiko-bot@kernel.org
To: "Pavitrakumar Managutte" <pavitrakumarm@vayavyalabs.com>
Cc: robh@kernel.org, conor+dt@kernel.org, devicetree@vger.kernel.org
Subject: Re: [PATCH v19 4/4] crypto: spacc - Add SPAcc Kconfig and Makefile
Date: Wed, 29 Jul 2026 10:38:51 +0000 [thread overview]
Message-ID: <20260729103852.282791F000E9@smtp.kernel.org> (raw)
In-Reply-To: <20260729102547.159890-5-pavitrakumarm@vayavyalabs.com>
Thank you for your contribution! Sashiko AI review found 3 potential issue(s) to consider:
- [Medium] Hardware tuning parameters are hardcoded via Kconfig options rather than dynamic configuration mechanisms.
- [Low] Redundant 'default n' and inconsistent indentation in help text.
- [Low] Missing 'depends on HAS_IOMEM' for an MMIO-based driver.
--
--- Patch [4]: [PATCH v19 4/4] crypto: spacc - Add SPAcc Kconfig and Makefile ---
commit 976ac00ba3bdbdaaa6d1e32b6172c60030c0e6b9
Author: Pavitrakumar Managutte <pavitrakumarm@vayavyalabs.com>
crypto: spacc - Add SPAcc Kconfig and Makefile
This commit introduces the Makefile and Kconfig definitions for the new
SPAcc (Security Protocol Accelerator) crypto driver.
> diff --git a/drivers/crypto/dwc-spacc/Kconfig b/drivers/crypto/dwc-spacc/Kconfig
> new file mode 100644
> index 0000000000000..b528c8e47b3b5
> --- /dev/null
> +++ b/drivers/crypto/dwc-spacc/Kconfig
> @@ -0,0 +1,82 @@
> +# SPDX-License-Identifier: GPL-2.0-only
> +
> +config CRYPTO_DEV_SPACC
> + tristate "Support for dwc_spacc Security Protocol Accelerator"
> + depends on HAS_DMA
[Severity: Low]
Does this driver need a dependency on HAS_IOMEM? The Kconfig option
CRYPTO_DEV_SPACC_DEBUG_TRACE_IO notes tracing of MMIO, indicating the driver
uses memory-mapped I/O. Without this dependency, randconfig builds might fail
on architectures that lack MMIO support.
> + select CRYPTO_ENGINE
> + select CRYPTO_HASH if CRYPTO_DEV_SPACC_HASH
[ ... ]
> +config CRYPTO_DEV_SPACC_PRIORITY
> + int "VSPACC priority value"
> + range 0 15
> + default 1
[Severity: Medium]
Would it be better to configure hardware tuning parameters like arbitration
priority and internal counter timeouts dynamically (e.g., via module
parameters or device tree)? Defining them in Kconfig bakes the values into
the kernel image at compile time, which prevents configuring different
SPAcc instances with varying parameters on a multi-platform kernel.
> + help
> + Default arbitration priority weight for this Virtual SPAcc instance.
> + Hardware resets this to 1. Higher values means higher priority.
[ ... ]
> +config CRYPTO_DEV_SPACC_CONFIG_DEBUG
> + bool "Enable SPAcc debug logs"
> + default n
> + help
> + Say y to enable additional debug prints and diagnostics in the
[Severity: Low]
This isn't a bug, but should the 10-space indentation on this line be
replaced with a standard tab and two spaces to match Kconfig styling
guidelines? Also, the 'default n' on the preceding line is redundant
since Kconfig options default to 'n' if no other default is specified.
> + SPAcc driver. Disable this for production builds.
> +
> +endif # CRYPTO_DEV_SPACC
--
Sashiko AI review · https://sashiko.dev/#/patchset/20260729102547.159890-1-pavitrakumarm@vayavyalabs.com?part=4
prev parent reply other threads:[~2026-07-29 10:38 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-07-29 10:25 [PATCH v19 0/4] crypto: spacc - Add SPAcc Crypto Driver Pavitrakumar Managutte
2026-07-29 10:25 ` [PATCH v19 1/4] dt-bindings: crypto: Document support for SPAcc Pavitrakumar Managutte
2026-07-29 10:25 ` [PATCH v19 2/4] crypto: spacc - Add SPAcc ahash support Pavitrakumar Managutte
2026-07-29 10:50 ` sashiko-bot
2026-07-29 10:25 ` [PATCH v19 3/4] crypto: spacc - Add SPAcc AUTODETECT Support Pavitrakumar Managutte
2026-07-29 10:42 ` sashiko-bot
2026-07-29 10:25 ` [PATCH v19 4/4] crypto: spacc - Add SPAcc Kconfig and Makefile Pavitrakumar Managutte
2026-07-29 10:38 ` sashiko-bot [this message]
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=20260729103852.282791F000E9@smtp.kernel.org \
--to=sashiko-bot@kernel.org \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=pavitrakumarm@vayavyalabs.com \
--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.