linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Joel Fernandes <joelf@ti.com>
To: Sergei Shtylyov <sergei.shtylyov@cogentembedded.com>,
	Tony Lindgren <tony@atomide.com>,
	Benoit Cousson <bcousson@baylibre.com>,
	Linux OMAP List <linux-omap@vger.kernel.org>,
	Linux ARM Kernel List <linux-arm-kernel@lists.infradead.org>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH 07/10] ARM: dts: DRA7: Add DT node for DES IP
Date: Mon, 28 Apr 2014 11:38:33 -0500	[thread overview]
Message-ID: <535E8409.10905@ti.com> (raw)
In-Reply-To: <535BE096.2060407@cogentembedded.com>

On 04/26/2014 11:36 AM, Sergei Shtylyov wrote:
> Hello.
> 
> On 26-04-2014 3:02, Joel Fernandes wrote:
> 
>> DRA7xx SoCs have a DES3DES IP. Add DT data for the same.
> 
>> Signed-off-by: Joel Fernandes <joelf@ti.com>
>> ---
>>   arch/arm/boot/dts/dra7.dtsi |   11 +++++++++++
>>   1 file changed, 11 insertions(+)
> 
>> diff --git a/arch/arm/boot/dts/dra7.dtsi b/arch/arm/boot/dts/dra7.dtsi
>> index 1c0f8e1..0533b89 100644
>> --- a/arch/arm/boot/dts/dra7.dtsi
>> +++ b/arch/arm/boot/dts/dra7.dtsi
>> @@ -789,6 +789,17 @@
>>               dma-names = "tx0", "rx0";
>>               status = "disabled";
>>           };
>> +
>> +        des: des@480a5000 {
> 
>    Shouldn't the node name be "crypto@480a5000", according to the ePAPR
> standard?
> 
Actually I'm not a big fan of the standard here in this regard.
"crypto@480a5000" doesn't mean anything and serves no purpose for
anyone. There are quite a few crypto modules and such a name doesn't
help and is confusing at best.

There's no property either in the device tree node itself to describe it
as des, except for the phandle label which is used only at dt
compile-time if I'm right. So makes sense to have the name be more specific.

This is how we have added dts nodes for other crypto modules in the past...

thanks,
 -Joel


  reply	other threads:[~2014-04-28 16:39 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-04-25 23:02 [PATCH 00/10] ARM: OMAP: dts and HWMOD entries for crypto modules Joel Fernandes
2014-04-25 23:02 ` [PATCH 01/10] ARM: OMAP: hwmod: Add SYSC offsets for AES IP Joel Fernandes
2014-04-25 23:02 ` [PATCH 02/10] ARM: DRA7xx: hwmod: Add hwmod data for DES IP Joel Fernandes
2014-04-25 23:02 ` [PATCH 03/10] ARM: DRA7xx: hwmod: Add hwmod data for AES IP Joel Fernandes
2014-04-25 23:02 ` [PATCH 04/10] ARM: DRA7xx: Add hwmod entries for RNG module Joel Fernandes
2014-04-25 23:02 ` [PATCH 05/10] ARM: OMAP4: hwmod: Add hwmod data for AES IP Joel Fernandes
2014-04-25 23:02 ` [PATCH 06/10] ARM: OMAP4: hwmod: add hwmod data for DES IP Joel Fernandes
2014-04-25 23:02 ` [PATCH 07/10] ARM: dts: DRA7: Add DT node " Joel Fernandes
2014-04-26 16:36   ` Sergei Shtylyov
2014-04-28 16:38     ` Joel Fernandes [this message]
2014-04-25 23:02 ` [PATCH 08/10] ARM: dts: DRA7: Add DT node for AES IP Joel Fernandes
2014-04-25 23:02 ` [PATCH 09/10] ARM: dts: OMAP4: clk: Add clk node for DES IP Joel Fernandes
2014-05-14  9:04   ` Tero Kristo
2014-04-25 23:02 ` [PATCH 10/10] ARM: dts: OMAP4: Add clock nodes for AES/DES nodes Joel Fernandes

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=535E8409.10905@ti.com \
    --to=joelf@ti.com \
    --cc=bcousson@baylibre.com \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-omap@vger.kernel.org \
    --cc=sergei.shtylyov@cogentembedded.com \
    --cc=tony@atomide.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).