devicetree.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Jayesh Choudhary <j-choudhary@ti.com>
To: <linux-crypto@vger.kernel.org>
Cc: <devicetree@vger.kernel.org>, <linux-kernel@vger.kernel.org>,
	<herbert@gondor.apana.org.au>, <davem@davemloft.net>,
	<krzysztof.kozlowski+dt@linaro.org>, <j-choudhary@ti.com>,
	<robh+dt@kernel.org>
Subject: [PATCH 1/2] dt-bindings: crypto: ti,sa2ul: Add a new compatible for AM62
Date: Tue, 12 Apr 2022 13:00:15 +0530	[thread overview]
Message-ID: <20220412073016.6014-2-j-choudhary@ti.com> (raw)
In-Reply-To: <20220412073016.6014-1-j-choudhary@ti.com>

Add the AM62 version of sa3ul to the compatible list.

Signed-off-by: Jayesh Choudhary <j-choudhary@ti.com>
---
 Documentation/devicetree/bindings/crypto/ti,sa2ul.yaml | 1 +
 1 file changed, 1 insertion(+)

diff --git a/Documentation/devicetree/bindings/crypto/ti,sa2ul.yaml b/Documentation/devicetree/bindings/crypto/ti,sa2ul.yaml
index a410d2cedde6..02f47c2e7998 100644
--- a/Documentation/devicetree/bindings/crypto/ti,sa2ul.yaml
+++ b/Documentation/devicetree/bindings/crypto/ti,sa2ul.yaml
@@ -15,6 +15,7 @@ properties:
       - ti,j721e-sa2ul
       - ti,am654-sa2ul
       - ti,am64-sa2ul
+      - ti,am62-sa3ul
 
   reg:
     maxItems: 1
-- 
2.17.1


  reply	other threads:[~2022-04-12  8:07 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-04-12  7:30 [PATCH 0/2] New compatible for sa3ul for AM62x Jayesh Choudhary
2022-04-12  7:30 ` Jayesh Choudhary [this message]
2022-04-12 12:03   ` [PATCH 1/2] dt-bindings: crypto: ti,sa2ul: Add a new compatible for AM62 Krzysztof Kozlowski
2022-04-13  8:33     ` Jayesh Choudhary
2022-04-13 15:48   ` Krzysztof Kozlowski
2022-04-12  7:30 ` [PATCH 2/2] crypto: sa2ul: Add the " Jayesh Choudhary
2022-04-21  9:59 ` [PATCH 0/2] New compatible for sa3ul for AM62x Herbert Xu

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=20220412073016.6014-2-j-choudhary@ti.com \
    --to=j-choudhary@ti.com \
    --cc=davem@davemloft.net \
    --cc=devicetree@vger.kernel.org \
    --cc=herbert@gondor.apana.org.au \
    --cc=krzysztof.kozlowski+dt@linaro.org \
    --cc=linux-crypto@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=robh+dt@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;
as well as URLs for NNTP newsgroup(s).