linux-crypto.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Tero Kristo <t-kristo@ti.com>
To: Rob Herring <robh@kernel.org>
Cc: <herbert@gondor.apana.org.au>, <davem@davemloft.net>,
	<linux-crypto@vger.kernel.org>, Keerthy <j-keerthy@ti.com>,
	<devicetree@vger.kernel.org>
Subject: Re: [PATCHv2 1/7] dt-bindings: crypto: Add TI SA2UL crypto accelerator documentation
Date: Tue, 12 May 2020 07:47:02 +0300	[thread overview]
Message-ID: <53c7c7db-9357-c2fa-c792-64261489d32c@ti.com> (raw)
In-Reply-To: <20200511215343.GA10123@bogus>

On 12/05/2020 00:53, Rob Herring wrote:
> On Fri, Apr 24, 2020 at 07:44:24PM +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>
>> ---
>>   .../devicetree/bindings/crypto/ti,sa2ul.yaml  | 76 +++++++++++++++++++
>>   1 file changed, 76 insertions(+)
>>   create mode 100644 Documentation/devicetree/bindings/crypto/ti,sa2ul.yaml
>>
>> diff --git a/Documentation/devicetree/bindings/crypto/ti,sa2ul.yaml b/Documentation/devicetree/bindings/crypto/ti,sa2ul.yaml
>> new file mode 100644
>> index 000000000000..27bb3a7e2b87
>> --- /dev/null
>> +++ b/Documentation/devicetree/bindings/crypto/ti,sa2ul.yaml
>> @@ -0,0 +1,76 @@
>> +# SPDX-License-Identifier: (GPL-2.0-only or BSD-2-Clause)
>> +%YAML 1.2
>> +---
>> +$id: http://devicetree.org/schemas/crypto/ti,sa2ul.yaml#
>> +$schema: http://devicetree.org/meta-schemas/core.yaml#
>> +
>> +title: K3 SoC SA2UL crypto module
>> +
>> +maintainers:
>> +  - Tero Kristo <t-kristo@ti.com>
>> +
>> +properties:
>> +  compatible:
>> +    enum:
>> +      - ti,j721e-sa2ul
>> +      - ti,am654-sa2ul
>> +
>> +  reg:
>> +    maxItems: 1
>> +
>> +  power-domains:
>> +    maxItems: 1
>> +
>> +  dmas:
>> +    items:
>> +      - description: TX DMA Channel
>> +      - description: RX DMA Channel #1
>> +      - description: RX DMA Channel #2
>> +
>> +  dma-names:
>> +    items:
>> +      - const: tx
>> +      - const: rx1
>> +      - const: rx2
>> +
>> +  dma-coherent: true
>> +
>> +  "#address-cells":
>> +    const: 2
>> +
>> +  "#size-cells":
>> +    const: 2
>> +
>> +  ranges:
>> +    description:
>> +      Address translation for the possible RNG child node for SA2UL
>> +
>> +patternProperties:
>> +  "^rng@[a-lf0-9]+$":
> 
> a-l?

Ooops, thats a typo right here. Will fix that.

> 
>> +    type: object
>> +    description:
>> +      Child RNG node for SA2UL
> 
> Does this child node have a binding?

Yes, it is here:

Documentation/devicetree/bindings/rng/omap_rng.txt.

It is an old one so not converted to yaml yet though.

-Tero

> 
>> +
>> +required:
>> +  - compatible
>> +  - reg
>> +  - power-domains
>> +  - dmas
>> +  - dma-names
>> +  - dma-coherent
>> +
>> +additionalProperties: false
>> +
>> +examples:
>> +  - |
>> +    #include <dt-bindings/soc/ti,sci_pm_domain.h>
>> +
>> +    main_crypto: crypto@4e00000 {
>> +        compatible = "ti,j721-sa2ul";
>> +        reg = <0x0 0x4e00000 0x0 0x1200>;
>> +        power-domains = <&k3_pds 264 TI_SCI_PD_EXCLUSIVE>;
>> +        dmas = <&main_udmap 0xc000>, <&main_udmap 0x4000>,
>> +               <&main_udmap 0x4001>;
>> +        dma-names = "tx", "rx1", "rx2";
>> +        dma-coherent;
>> +    };
>> -- 
>> 2.17.1
>>
>> --

--
Texas Instruments Finland Oy, Porkkalankatu 22, 00180 Helsinki. Y-tunnus/Business ID: 0615521-4. Kotipaikka/Domicile: Helsinki

  reply	other threads:[~2020-05-12  4:47 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 [this message]
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
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=53c7c7db-9357-c2fa-c792-64261489d32c@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).