From: Andreas Kemnade <andreas@kemnade.info>
To: Bhargav Joshi <j.bhargav.u@gmail.com>
Cc: Aaro Koskinen <aaro.koskinen@iki.fi>,
Kevin Hilman <khilman@baylibre.com>,
Roger Quadros <rogerq@kernel.org>,
Tony Lindgren <tony@atomide.com>, Rob Herring <robh@kernel.org>,
Krzysztof Kozlowski <krzk+dt@kernel.org>,
Conor Dooley <conor+dt@kernel.org>,
Herbert Xu <herbert@gondor.apana.org.au>,
"David S. Miller" <davem@davemloft.net>,
Animesh Agarwal <animeshagarwal28@gmail.com>,
linux-omap@vger.kernel.org, devicetree@vger.kernel.org,
linux-kernel@vger.kernel.org, linux-crypto@vger.kernel.org
Subject: Re: [PATCH 1/2] ARM: dts: ti: omap: dra7: Remove clocks from crypto nodes
Date: Fri, 11 Sep 2026 08:15:47 +0200 [thread overview]
Message-ID: <20260911081547.400ac521@kemnade.info> (raw)
In-Reply-To: <20260911-ti-dra7-omap-sham-fix-v1-1-c430f01b4e13@gmail.com>
On Fri, 11 Sep 2026 03:41:57 +0530
Bhargav Joshi <j.bhargav.u@gmail.com> wrote:
> The omap-sham and omap-aes crypto drivers do not use "clocks" and
> "clock-names" properties. Clock management is handled by the ti-sysc
> interconnect parent wrapper. The dt-bindings for ti,omap-sham and
> ti,omap-aes don't define these clock properties. Having them in the
> child nodes causes dtbs_check warnings.
>
> Remove the "clocks" and "clock-names" properties from the sham and aes
> nodes.
>
> Signed-off-by: Bhargav Joshi <j.bhargav.u@gmail.com>
Reviewed-by: Andreas Kemnade <andreas@kemnade.info>
> ---
> arch/arm/boot/dts/ti/omap/dra7.dtsi | 8 --------
> 1 file changed, 8 deletions(-)
>
> diff --git a/arch/arm/boot/dts/ti/omap/dra7.dtsi b/arch/arm/boot/dts/ti/omap/dra7.dtsi
> index 711ce4c31bb1..0784c6d9cbe4 100644
> --- a/arch/arm/boot/dts/ti/omap/dra7.dtsi
> +++ b/arch/arm/boot/dts/ti/omap/dra7.dtsi
> @@ -1012,8 +1012,6 @@ aes1: aes@0 {
> interrupts = <GIC_SPI 80 IRQ_TYPE_LEVEL_HIGH>;
> dmas = <&edma_xbar 111 0>, <&edma_xbar 110 0>;
> dma-names = "tx", "rx";
> - clocks = <&l3_iclk_div>;
> - clock-names = "fck";
> };
> };
>
> @@ -1043,8 +1041,6 @@ aes2: aes@0 {
> interrupts = <GIC_SPI 59 IRQ_TYPE_LEVEL_HIGH>;
> dmas = <&edma_xbar 114 0>, <&edma_xbar 113 0>;
> dma-names = "tx", "rx";
> - clocks = <&l3_iclk_div>;
> - clock-names = "fck";
> };
> };
>
> @@ -1073,8 +1069,6 @@ sham1: sham@0 {
> interrupts = <GIC_SPI 46 IRQ_TYPE_LEVEL_HIGH>;
> dmas = <&edma_xbar 119 0>;
> dma-names = "rx";
> - clocks = <&l3_iclk_div>;
> - clock-names = "fck";
> };
> };
>
> @@ -1103,8 +1097,6 @@ sham2: sham@0 {
> interrupts = <GIC_SPI 163 IRQ_TYPE_LEVEL_HIGH>;
> dmas = <&edma_xbar 165 0>;
> dma-names = "rx";
> - clocks = <&l3_iclk_div>;
> - clock-names = "fck";
> };
> };
>
>
next prev parent reply other threads:[~2026-09-11 6:17 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-10 22:11 [PATCH 0/2] ARM: dts: ti: Clean up OMAP crypto bindings and dt Bhargav Joshi
2026-09-10 22:11 ` [PATCH 1/2] ARM: dts: ti: omap: dra7: Remove clocks from crypto nodes Bhargav Joshi
2026-09-11 6:15 ` Andreas Kemnade [this message]
2026-09-10 22:11 ` [PATCH 2/2] dt-bindings: crypto: ti,omap-sham: Add OMAP3 compatible and deprecate ti,hwmods Bhargav Joshi
2026-09-11 6:24 ` Andreas Kemnade
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=20260911081547.400ac521@kemnade.info \
--to=andreas@kemnade.info \
--cc=aaro.koskinen@iki.fi \
--cc=animeshagarwal28@gmail.com \
--cc=conor+dt@kernel.org \
--cc=davem@davemloft.net \
--cc=devicetree@vger.kernel.org \
--cc=herbert@gondor.apana.org.au \
--cc=j.bhargav.u@gmail.com \
--cc=khilman@baylibre.com \
--cc=krzk+dt@kernel.org \
--cc=linux-crypto@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-omap@vger.kernel.org \
--cc=robh@kernel.org \
--cc=rogerq@kernel.org \
--cc=tony@atomide.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