From: Tero Kristo <t-kristo@ti.com>
To: Rob Herring <robh@kernel.org>
Cc: <herbert@gondor.apana.org.au>, <davem@davemloft.net>,
Keerthy <j-keerthy@ti.com>, <devicetree@vger.kernel.org>,
<linux-crypto@vger.kernel.org>
Subject: Re: [PATCHv3 1/7] dt-bindings: crypto: Add TI SA2UL crypto accelerator documentation
Date: Wed, 3 Jun 2020 13:01:26 +0300 [thread overview]
Message-ID: <a75b48ad-ecc0-89bc-f6a2-7149bc3fefb0@ti.com> (raw)
In-Reply-To: <20200528152341.GA103581@bogus>
On 28/05/2020 18:23, Rob Herring wrote:
> On Thu, 14 May 2020 15:50:05 +0300, Tero Kristo wrote:
>> From: Keerthy <j-keerthy@ti.com>
>>
>> The Security Accelerator Ultra Lite (SA2UL) subsystem provides hardware
>> cryptographic acceleration for the following use cases:
>>
>> * Encryption and authentication for secure boot
>> * Encryption and authentication of content in applications
>> requiring DRM (digital rights management) and
>> content/asset protection
>>
>> SA2UL provides support for number of different cryptographic algorithms
>> including SHA1, SHA256, SHA512, AES, 3DES, and various combinations of
>> the previous for AEAD use.
>>
>> Cc: Rob Herring <robh@kernel.org>
>> Cc: devicetree@vger.kernel.org
>> Signed-off-by: Keerthy <j-keerthy@ti.com>
>> [t-kristo@ti.com: converted documentation to yaml]
>> Signed-off-by: Tero Kristo <t-kristo@ti.com>
>> ---
>> v3:
>> - fixed a typo in rng child node regex
>>
>> .../devicetree/bindings/crypto/ti,sa2ul.yaml | 76 +++++++++++++++++++
>> 1 file changed, 76 insertions(+)
>> create mode 100644 Documentation/devicetree/bindings/crypto/ti,sa2ul.yaml
>>
>
> Reviewed-by: Rob Herring <robh@kernel.org>
Thanks Rob,
Herbert, whats the plan with the rest of the series? Do you want me to
re-post it? It shows deferred under crypto patchwork currently.
-Tero
--
Texas Instruments Finland Oy, Porkkalankatu 22, 00180 Helsinki. Y-tunnus/Business ID: 0615521-4. Kotipaikka/Domicile: Helsinki
next prev parent reply other threads:[~2020-06-03 10:01 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-04-24 16:44 [PATCHv2 0/7] crypto: TI SA2UL crypto accelerator support Tero Kristo
2020-04-24 16:44 ` [PATCHv2 1/7] dt-bindings: crypto: Add TI SA2UL crypto accelerator documentation Tero Kristo
2020-05-11 21:53 ` Rob Herring
2020-05-12 4:47 ` Tero Kristo
2020-05-14 12:50 ` [PATCHv3 " Tero Kristo
2020-05-26 13:16 ` Tero Kristo
2020-05-28 15:23 ` Rob Herring
2020-06-03 10:01 ` Tero Kristo [this message]
2020-06-03 12:27 ` Herbert Xu
2020-06-03 12:38 ` Tero Kristo
2020-06-03 12:39 ` Herbert Xu
2020-06-03 12:53 ` Tero Kristo
2020-06-03 12:54 ` Herbert Xu
2020-04-24 16:44 ` [PATCHv2 2/7] crypto: sa2ul: Add crypto driver Tero Kristo
2020-04-24 16:44 ` [PATCHv2 3/7] crypto: sa2ul: add sha1/sha256/sha512 support Tero Kristo
2020-04-24 16:44 ` [PATCHv2 4/7] crypto: sa2ul: Add AEAD algorithm support Tero Kristo
2020-04-24 16:44 ` [PATCHv2 5/7] crypto: sa2ul: add device links to child devices Tero Kristo
2020-04-24 16:44 ` [PATCHv2 6/7] arm64: dts: ti: k3-am6: Add crypto accelarator node Tero Kristo
2020-04-24 16:44 ` [PATCHv2 7/7] arm64: dts: ti: k3-j721e-main: Add crypto accelerator node Tero Kristo
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=a75b48ad-ecc0-89bc-f6a2-7149bc3fefb0@ti.com \
--to=t-kristo@ti.com \
--cc=davem@davemloft.net \
--cc=devicetree@vger.kernel.org \
--cc=herbert@gondor.apana.org.au \
--cc=j-keerthy@ti.com \
--cc=linux-crypto@vger.kernel.org \
--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;
as well as URLs for NNTP newsgroup(s).