From: Krzysztof Kozlowski <krzk@kernel.org>
To: T Pratham <t-pratham@ti.com>
Cc: Herbert Xu <herbert@gondor.apana.org.au>,
"David S. Miller" <davem@davemloft.net>,
Rob Herring <robh@kernel.org>,
Krzysztof Kozlowski <krzk+dt@kernel.org>,
Conor Dooley <conor+dt@kernel.org>,
Catalin Marinas <catalin.marinas@arm.com>,
Will Deacon <will@kernel.org>,
linux-crypto@vger.kernel.org, devicetree@vger.kernel.org,
linux-kernel@vger.kernel.org,
linux-arm-kernel@lists.infradead.org,
Vignesh Raghavendra <vigneshr@ti.com>,
Praneeth Bajjuri <praneeth@ti.com>,
Kamlesh Gurudasani <kamlesh@ti.com>,
Manorit Chawdhry <m-chawdhry@ti.com>
Subject: Re: [PATCH RFC 1/3] dt-bindings: crypto: Add binding for TI DTHE V2 driver
Date: Sun, 9 Feb 2025 13:27:49 +0100 [thread overview]
Message-ID: <20250209-sincere-honored-vole-dda3c7@krzk-bin> (raw)
In-Reply-To: <20250206-dthe-v2-aes-v1-1-1e86cf683928@ti.com>
On Thu, Feb 06, 2025 at 02:44:30PM +0530, T Pratham wrote:
> Add new DT binding for Texas Instruments DTHE V2 crypto driver.
This was never tested so only limited review.
Subject and commit msg: Bindings are for hardware, not driver. Rephrase
to accurately describe the hardware.
>
> DTHE V2 is introduced as a part of TI AM62L SoC and can currently be
> only found in it.
>
> Signed-off-by: T Pratham <t-pratham@ti.com>
> ---
> PS: Please note that the dmas option in dt-bindings is subject to change in
> future as dma driver is not finalized yet. Any updated changes will be
> sent in the next version of the patch.
>
> .../devicetree/bindings/crypto/ti,dthev2.yaml | 50 ++++++++++++++++++++++
> MAINTAINERS | 6 +++
> 2 files changed, 56 insertions(+)
>
> diff --git a/Documentation/devicetree/bindings/crypto/ti,dthev2.yaml b/Documentation/devicetree/bindings/crypto/ti,dthev2.yaml
> new file mode 100644
> index 0000000000000000000000000000000000000000..9c871fe191ae0a3341d047d4565ec1e1bf1f21ef
> --- /dev/null
> +++ b/Documentation/devicetree/bindings/crypto/ti,dthev2.yaml
Filename matching compatible.
> @@ -0,0 +1,50 @@
> +# SPDX-License-Identifier: (GPL-2.0-only OR BSD-2-Clause)
> +%YAML 1.2
> +---
> +$id: http://devicetree.org/schemas/crypto/ti,dthev2.yaml#
> +$schema: http://devicetree.org/meta-schemas/core.yaml#
> +
> +title: K3 SoC DTHE V2 crypto module
> +
> +maintainers:
> + - T Pratham <t-pratham@ti.com>
> +
> +properties:
> + compatible:
> + enum:
> + - ti,dthe-v2
NAK, SoC-based compatible instead.
> +
> + reg:
> + maxItems: 1
> +
> + dmas:
> + items:
> + - description: 'AES Engine RX DMA Channel'
> + - description: 'AES Engine TX DMA Channel'
> + - description: 'SHA Engine TX DMA Channel'
> +
> + dma-names:
> + items:
> + - const: rx
> + - const: tx1
> + - const: tx2
> +
> +
Drop stray blank line
> +required:
> + - compatible
> + - reg
> + - dmas
> + - dma-names
> +
> +additionalProperties: false
> +
> +examples:
> + - |
> +
Drop stray blank line
> + crypto: crypto@40800000 {
Drop label
> + compatible = "ti,dthe-v2";
> + reg = <0x00 0x40800000 0x00 0x10000>;
> +
> + dmas = <&main_bcdma 0 0xc701 0>, <&main_bcdma 0 0x4700 0>, <&main_bcdma 0 0xc700 0>;
Wrap according to coding style.
Best regards,
Krzysztof
next prev parent reply other threads:[~2025-02-09 12:41 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-02-06 9:14 [PATCH RFC 0/3] Add support for Texas Instruments DTHE V2 crypto accelerator T Pratham
2025-02-06 9:14 ` [PATCH RFC 1/3] dt-bindings: crypto: Add binding for TI DTHE V2 driver T Pratham
2025-02-06 10:24 ` Rob Herring (Arm)
2025-02-09 12:27 ` Krzysztof Kozlowski [this message]
2025-02-06 9:14 ` [PATCH RFC 2/3] crypto: ti: Add driver for DTHE V2 AES Engine (ECB, CBC) T Pratham
2025-02-06 9:14 ` [PATCH RFC DONOTMERGE 3/3] arm64: defconfig: enable DTHE V2 module T Pratham
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=20250209-sincere-honored-vole-dda3c7@krzk-bin \
--to=krzk@kernel.org \
--cc=catalin.marinas@arm.com \
--cc=conor+dt@kernel.org \
--cc=davem@davemloft.net \
--cc=devicetree@vger.kernel.org \
--cc=herbert@gondor.apana.org.au \
--cc=kamlesh@ti.com \
--cc=krzk+dt@kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-crypto@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=m-chawdhry@ti.com \
--cc=praneeth@ti.com \
--cc=robh@kernel.org \
--cc=t-pratham@ti.com \
--cc=vigneshr@ti.com \
--cc=will@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