From: Conor Dooley <conor@kernel.org>
To: Aleksander Jan Bajkowski <olek2@wp.pl>
Cc: ansuelsmth@gmail.com, herbert@gondor.apana.org.au,
davem@davemloft.net, matthias.bgg@gmail.com,
angelogioacchino.delregno@collabora.com, robh@kernel.org,
krzk+dt@kernel.org, conor+dt@kernel.org, lorenzo@kernel.org,
linux-arm-kernel@lists.infradead.org,
linux-mediatek@lists.infradead.org, linux-crypto@vger.kernel.org,
devicetree@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH 1/2] dt-bindings: crypto: eip93: add clock gate and reset line
Date: Wed, 4 Mar 2026 19:08:59 +0000 [thread overview]
Message-ID: <20260304-hardship-abreast-7a2d58cbe446@spud> (raw)
In-Reply-To: <20260303193923.85242-1-olek2@wp.pl>
[-- Attachment #1: Type: text/plain, Size: 1587 bytes --]
On Tue, Mar 03, 2026 at 08:39:17PM +0100, Aleksander Jan Bajkowski wrote:
> Add the clock gate and reset line, both of which are available
> on the Airoha AN7581. Both properties are optional.
Why are they optional?
>
> Signed-off-by: Aleksander Jan Bajkowski <olek2@wp.pl>
> ---
> .../crypto/inside-secure,safexcel-eip93.yaml | 12 ++++++++++++
> 1 file changed, 12 insertions(+)
>
> diff --git a/Documentation/devicetree/bindings/crypto/inside-secure,safexcel-eip93.yaml b/Documentation/devicetree/bindings/crypto/inside-secure,safexcel-eip93.yaml
> index 997bf9717f9e..058454b679b4 100644
> --- a/Documentation/devicetree/bindings/crypto/inside-secure,safexcel-eip93.yaml
> +++ b/Documentation/devicetree/bindings/crypto/inside-secure,safexcel-eip93.yaml
> @@ -48,6 +48,12 @@ properties:
> interrupts:
> maxItems: 1
>
> + clocks:
> + maxItems: 1
> +
> + resets:
> + maxItems: 1
> +
> required:
> - compatible
> - reg
> @@ -57,11 +63,17 @@ additionalProperties: false
>
> examples:
> - |
> + #include <dt-bindings/clock/en7523-clk.h>
> #include <dt-bindings/interrupt-controller/arm-gic.h>
> + #include <dt-bindings/reset/airoha,en7581-reset.h>
>
> crypto@1e004000 {
> compatible = "airoha,en7581-eip93", "inside-secure,safexcel-eip93ies";
> reg = <0x1fb70000 0x1000>;
>
> + clocks = <&scuclk EN7523_CLK_CRYPTO>;
> +
> interrupts = <GIC_SPI 44 IRQ_TYPE_LEVEL_HIGH>;
> +
> + resets = <&scuclk EN7581_CRYPTO_RST>;
> };
> --
> 2.47.3
>
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 228 bytes --]
next prev parent reply other threads:[~2026-03-04 19:09 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-03-03 19:39 [PATCH 1/2] dt-bindings: crypto: eip93: add clock gate and reset line Aleksander Jan Bajkowski
2026-03-03 19:39 ` [PATCH 2/2] arm64: dts: airoha: en7581: add crypto offload support Aleksander Jan Bajkowski
2026-03-03 20:00 ` Christian Marangi
2026-03-04 20:05 ` Aleksander Jan Bajkowski
2026-03-04 19:08 ` Conor Dooley [this message]
2026-03-04 21:46 ` [PATCH 1/2] dt-bindings: crypto: eip93: add clock gate and reset line Aleksander Jan Bajkowski
2026-03-04 22:29 ` Conor Dooley
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=20260304-hardship-abreast-7a2d58cbe446@spud \
--to=conor@kernel.org \
--cc=angelogioacchino.delregno@collabora.com \
--cc=ansuelsmth@gmail.com \
--cc=conor+dt@kernel.org \
--cc=davem@davemloft.net \
--cc=devicetree@vger.kernel.org \
--cc=herbert@gondor.apana.org.au \
--cc=krzk+dt@kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-crypto@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mediatek@lists.infradead.org \
--cc=lorenzo@kernel.org \
--cc=matthias.bgg@gmail.com \
--cc=olek2@wp.pl \
--cc=robh@kernel.org \
/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