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 2/2] dt-bindings: crypto: ti,omap-sham: Add OMAP3 compatible and deprecate ti,hwmods
Date: Fri, 11 Sep 2026 08:24:06 +0200 [thread overview]
Message-ID: <20260911082406.05e2a212@kemnade.info> (raw)
In-Reply-To: <20260911-ti-dra7-omap-sham-fix-v1-2-c430f01b4e13@gmail.com>
On Fri, 11 Sep 2026 03:41:58 +0530
Bhargav Joshi <j.bhargav.u@gmail.com> wrote:
> The OMAP SHAM driver supports OMAP3 SoCs, and "ti,omap3-sham" is
> actively used in existing dts. However, it was previously missing from
> binding. Add "ti,omap3-sham" to the list of valid compatibles.
>
> The legacy "ti,hwmods" property is no longer needed as TI OMAP mirgrated
> to "ti-sysc". Mark it as deprecated and remove it from the required
> properties.
>
> Signed-off-by: Bhargav Joshi <j.bhargav.u@gmail.com>
What about also removing ti,hwmods usage while you are deprecating it?
Regards,
Andreas
> ---
> Documentation/devicetree/bindings/crypto/ti,omap-sham.yaml | 3 ++-
> 1 file changed, 2 insertions(+), 1 deletion(-)
>
> diff --git a/Documentation/devicetree/bindings/crypto/ti,omap-sham.yaml b/Documentation/devicetree/bindings/crypto/ti,omap-sham.yaml
> index d69b50228009..3ef05890e13a 100644
> --- a/Documentation/devicetree/bindings/crypto/ti,omap-sham.yaml
> +++ b/Documentation/devicetree/bindings/crypto/ti,omap-sham.yaml
> @@ -13,6 +13,7 @@ properties:
> compatible:
> enum:
> - ti,omap2-sham
> + - ti,omap3-sham
> - ti,omap4-sham
> - ti,omap5-sham
>
> @@ -32,6 +33,7 @@ properties:
> description: Name of the hwmod associated with the SHAM module
> $ref: /schemas/types.yaml#/definitions/string
> enum: [sham]
> + deprecated: true
>
> dependencies:
> dmas: [dma-names]
> @@ -40,7 +42,6 @@ additionalProperties: false
>
> required:
> - compatible
> - - ti,hwmods
> - reg
> - interrupts
>
>
prev parent reply other threads:[~2026-09-11 6:24 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
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 [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=20260911082406.05e2a212@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