From: Krzysztof Kozlowski <krzysztof.kozlowski@canonical.com>
To: Tudor Ambarus <tudor.ambarus@microchip.com>,
nicolas.ferre@microchip.com, claudiu.beznea@microchip.com,
alexandre.belloni@bootlin.com
Cc: robh+dt@kernel.org, linux-arm-kernel@lists.infradead.org,
devicetree@vger.kernel.org, linux-kernel@vger.kernel.org,
kavyasree.kotagiri@microchip.com
Subject: Re: [PATCH] ARM: dts: at91: Use the generic "crypto" node name for the crypto IPs
Date: Tue, 8 Feb 2022 12:55:32 +0100 [thread overview]
Message-ID: <d995fee3-c2ad-55d2-86a0-c8a27e459ff0@canonical.com> (raw)
In-Reply-To: <20220208111225.234685-1-tudor.ambarus@microchip.com>
On 08/02/2022 12:12, Tudor Ambarus wrote:
> The DT specification recommeds that:
> "The name of a node should be somewhat generic, reflecting the function of
> the device and not its precise programming model. If appropriate, the name
> should be one of the following choices:"
> "crypto" being the recommendation for the crypto nodes. Follow the DT
> recommendation and use the generic "crypto" node name for the at91 crypto
> IPs. While at this, add labels to the crypto nodes where they missed, for
> easier reference purposes.
>
> Signed-off-by: Tudor Ambarus <tudor.ambarus@microchip.com>
> ---
> arch/arm/boot/dts/sam9x60.dtsi | 6 +++---
> arch/arm/boot/dts/sama5d2.dtsi | 6 +++---
> arch/arm/boot/dts/sama5d3.dtsi | 6 +++---
> arch/arm/boot/dts/sama5d4.dtsi | 6 +++---
> 4 files changed, 12 insertions(+), 12 deletions(-)
>
Acked-by: Krzysztof Kozlowski <krzysztof.kozlowski@canonical.com>
Best regards,
Krzysztof
next prev parent reply other threads:[~2022-02-08 11:55 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-02-08 11:12 [PATCH] ARM: dts: at91: Use the generic "crypto" node name for the crypto IPs Tudor Ambarus
2022-02-08 11:55 ` Krzysztof Kozlowski [this message]
2022-02-24 15:23 ` Nicolas Ferre
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=d995fee3-c2ad-55d2-86a0-c8a27e459ff0@canonical.com \
--to=krzysztof.kozlowski@canonical.com \
--cc=alexandre.belloni@bootlin.com \
--cc=claudiu.beznea@microchip.com \
--cc=devicetree@vger.kernel.org \
--cc=kavyasree.kotagiri@microchip.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=nicolas.ferre@microchip.com \
--cc=robh+dt@kernel.org \
--cc=tudor.ambarus@microchip.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;
as well as URLs for NNTP newsgroup(s).