From: Lokesh Vutla <lokeshvutla@ti.com>
To: Russ Dill <Russ.Dill@ti.com>
Cc: devicetree@vger.kernel.org, paul@pwsan.com, tony@atomide.com,
rnayak@ti.com, rob@landley.net, benoit.cousson@linaro.org,
linux-omap@vger.kernel.org, linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH 3/3] ARM: dts: AM33xx: Add RNG node
Date: Wed, 7 Aug 2013 11:47:01 +0530 [thread overview]
Message-ID: <5201E65D.8070906@ti.com> (raw)
In-Reply-To: <CA+Bv8XZ0SqtCJQszrpVcRuksJU+GNBoJD7FaP+NuQrbshnnBpg@mail.gmail.com>
On Tuesday 06 August 2013 11:47 PM, Russ Dill wrote:
> On Tue, Aug 6, 2013 at 1:33 AM, Lokesh Vutla <lokeshvutla@ti.com> wrote:
>> Add the generic AM33xx RNG module's device tree data and
>> enable it for the am335x-evm, am335x-evmsk, and am335x-bone
>> platforms. Also add Documentation file describing the data
>> for the RNG module.
>>
>> Signed-off-by: Lokesh Vutla <lokeshvutla@ti.com>
>> ---
>> .../devicetree/bindings/hwrng/omap_rng.txt | 22 ++++++++++++++++++++
>> arch/arm/boot/dts/am335x-bone.dts | 4 ++++
>> arch/arm/boot/dts/am335x-evm.dts | 4 ++++
>> arch/arm/boot/dts/am335x-evmsk.dts | 4 ++++
>> arch/arm/boot/dts/am33xx.dtsi | 8 +++++++
>> 5 files changed, 42 insertions(+)
>> create mode 100644 Documentation/devicetree/bindings/hwrng/omap_rng.txt
>>
>> diff --git a/Documentation/devicetree/bindings/hwrng/omap_rng.txt b/Documentation/devicetree/bindings/hwrng/omap_rng.txt
>> new file mode 100644
>> index 0000000..6a62acd
>> --- /dev/null
>> +++ b/Documentation/devicetree/bindings/hwrng/omap_rng.txt
>> @@ -0,0 +1,22 @@
>> +OMAP SoC HWRNG Module
>> +
>> +Required properties:
>> +
>> +- compatible : Should contain entries for this and backward compatible
>> + RNG versions:
>> + - "ti,omap2-rng" for OMAP2.
>> + - "ti,omap4-rng" for OMAP4, OMAP5 and AM33XX.
>> + Note that these two versions are incompatible.
>> +- ti,hwmods: Name of the hwmod associated with the RNG module
>> +- reg : Offset and length of the register set for the module
>> +- interrupts : the interrupt number for the RNG module.
>> + Only used for "ti,omap4-rng".
>> +
>> +Example:
>> +/* AM335x */
>> +rng: rng@48310000 {
>> + compatible = "ti,omap4-rng";
>> + ti,hwmods = "rng";
>> + reg = <0x48310000 0x2000>;
>> + interrupts = <111>;
>> +};
>> diff --git a/arch/arm/boot/dts/am335x-bone.dts b/arch/arm/boot/dts/am335x-bone.dts
>> index 444b4ed..46a3887 100644
>> --- a/arch/arm/boot/dts/am335x-bone.dts
>> +++ b/arch/arm/boot/dts/am335x-bone.dts
>> @@ -234,3 +234,7 @@
>> pinctrl-0 = <&davinci_mdio_default>;
>> pinctrl-1 = <&davinci_mdio_sleep>;
>> };
>> +
>> +&rng {
>> + status = "okay";
>> +};
>> diff --git a/arch/arm/boot/dts/am335x-evm.dts b/arch/arm/boot/dts/am335x-evm.dts
>> index 3aee1a4..ebfbebe1 100644
>> --- a/arch/arm/boot/dts/am335x-evm.dts
>> +++ b/arch/arm/boot/dts/am335x-evm.dts
>> @@ -488,3 +488,7 @@
>> ti,adc-channels = <4 5 6 7>;
>> };
>> };
>> +
>> +&rng {
>> + status = "okay";
>> +};
>> diff --git a/arch/arm/boot/dts/am335x-evmsk.dts b/arch/arm/boot/dts/am335x-evmsk.dts
>> index 0c8ad17..6610a05 100644
>> --- a/arch/arm/boot/dts/am335x-evmsk.dts
>> +++ b/arch/arm/boot/dts/am335x-evmsk.dts
>> @@ -402,3 +402,7 @@
>> phy_id = <&davinci_mdio>, <1>;
>> phy-mode = "rgmii-txid";
>> };
>> +
>> +&rng {
>> + status = "okay";
>> +};
>> diff --git a/arch/arm/boot/dts/am33xx.dtsi b/arch/arm/boot/dts/am33xx.dtsi
>> index 38b446b..b1e6205 100644
>> --- a/arch/arm/boot/dts/am33xx.dtsi
>> +++ b/arch/arm/boot/dts/am33xx.dtsi
>> @@ -530,5 +530,13 @@
>> #size-cells = <1>;
>> status = "disabled";
>> };
>> +
>> + rng: rng@48310000 {
>> + compatible = "ti,omap4-rng";
>> + ti,hwmods = "rng";
>> + reg = <0x48310000 0x2000>;
>> + interrupts = <111>;
>> + status = "disabled";
>
> Is there any point in making this default to "disabled"? Are there any
> am335x platforms where the trng doesn't function?
Yes, you are correct. Just followed how aes and sha are done.
ll update and send a v2.
Thanks and regards,
Lokesh
>
>> + };
>> };
>> };
>> --
>> 1.7.9.5
>>
>> --
>> To unsubscribe from this list: send the line "unsubscribe linux-omap" in
>> the body of a message to majordomo@vger.kernel.org
>> More majordomo info at http://vger.kernel.org/majordomo-info.html
next prev parent reply other threads:[~2013-08-07 6:17 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-08-06 8:33 [PATCH 0/3] ARM: AM33xx: Add RNG module data Lokesh Vutla
2013-08-06 8:33 ` [PATCH 1/3] ARM: AM33xx: hwmod: " Lokesh Vutla
2013-08-28 18:48 ` Paul Walmsley
2013-08-29 9:22 ` Lokesh Vutla
2013-08-29 11:30 ` Paul Walmsley
2013-08-29 12:05 ` Lokesh Vutla
2013-08-29 9:34 ` [PATCH V2 " Lokesh Vutla
2013-08-06 8:33 ` [PATCH 2/3] ARM: AM33xx: clock: Add RNG clock data Lokesh Vutla
2013-08-06 8:33 ` [PATCH 3/3] ARM: dts: AM33xx: Add RNG node Lokesh Vutla
2013-08-06 18:17 ` Russ Dill
2013-08-07 6:17 ` Lokesh Vutla [this message]
2013-08-07 6:30 ` [PATCH V2] " Lokesh Vutla
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=5201E65D.8070906@ti.com \
--to=lokeshvutla@ti.com \
--cc=Russ.Dill@ti.com \
--cc=benoit.cousson@linaro.org \
--cc=devicetree@vger.kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-omap@vger.kernel.org \
--cc=paul@pwsan.com \
--cc=rnayak@ti.com \
--cc=rob@landley.net \
--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).