From: Lokesh Vutla <lokeshvutla@ti.com>
To: Benoit Cousson <bcousson@baylibre.com>
Cc: paul@pwsan.com, tony@atomide.com, rnayak@ti.com,
linux-omap@vger.kernel.org, linux-arm-kernel@lists.infradead.org,
devicetree@vger.kernel.org
Subject: Re: [RESEND PATCH V2 1/2] ARM: dts: AM33xx: Add RNG node
Date: Wed, 16 Oct 2013 11:42:08 +0530 [thread overview]
Message-ID: <525E2E38.4000304@ti.com> (raw)
In-Reply-To: <525CE564.6010605@baylibre.com>
Hi Benoit,
On Tuesday 15 October 2013 12:19 PM, Benoit Cousson wrote:
> Hi Lokesh,
>
> On 12/10/2013 15:26, Lokesh Vutla wrote:
>> Hi Benoit,
>> On Thursday 29 August 2013 06:22 PM, Lokesh Vutla wrote:
>>> Add the AM33xx RNG module's device tree data.
>>> Also add Documentation file describing the data
>>> for the RNG module.
>> Seems you missed this patch. Please consider this for this merge window.
>
> Indeed I missed it. Sorry :-(
>
>> Patch 2/2 is already taken by Paul.
>> Without this patch AM335x boot will crash as I mentioned in my cover letter.
>>
>> Thanks and regards,
>> Lokesh
>>>
>>> Signed-off-by: Lokesh Vutla <lokeshvutla@ti.com>
>>> ---
>>> Changes since V1:
>>> - Drop "status=disabled" entry in dt node, Since
>>> RNG is present on all AM33xx platforms.
>>>
>>> .../devicetree/bindings/hwrng/omap_rng.txt | 22 ++++++++++++++++++++
>>> arch/arm/boot/dts/am33xx.dtsi | 7 +++++++
>>> 2 files changed, 29 insertions(+)
>>> create mode 100644 Documentation/devicetree/bindings/hwrng/omap_rng.txt
>
> I do not see the acked-by for the binding part. You do need that for any new bindings nowadays.
>
>>>
>>> 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/am33xx.dtsi b/arch/arm/boot/dts/am33xx.dtsi
>>> index 38b446b..26ebe30 100644
>>> --- a/arch/arm/boot/dts/am33xx.dtsi
>>> +++ b/arch/arm/boot/dts/am33xx.dtsi
>>> @@ -530,5 +530,12 @@
>>> #size-cells = <1>;
>>> status = "disabled";
>>> };
>>> +
>>> + rng: rng@48310000 {
>>> + compatible = "ti,omap4-rng";
>>> + ti,hwmods = "rng";
>>> + reg = <0x48310000 0x2000>;
>>> + interrupts = <111>;
>>> + };
>>> };
>>> };
>>>
>>
>
> It looks good to me, but it does not apply on my branch.
Can I take this as your Acked-by: ?
Ok, Ill rebase on top of your tree and post it.
Thanks and Regards,
Lokesh
> Please rebase it and repost with the proper acked-by.
>
> Thanks,
> Benoit
>
>
WARNING: multiple messages have this Message-ID (diff)
From: lokeshvutla@ti.com (Lokesh Vutla)
To: linux-arm-kernel@lists.infradead.org
Subject: [RESEND PATCH V2 1/2] ARM: dts: AM33xx: Add RNG node
Date: Wed, 16 Oct 2013 11:42:08 +0530 [thread overview]
Message-ID: <525E2E38.4000304@ti.com> (raw)
In-Reply-To: <525CE564.6010605@baylibre.com>
Hi Benoit,
On Tuesday 15 October 2013 12:19 PM, Benoit Cousson wrote:
> Hi Lokesh,
>
> On 12/10/2013 15:26, Lokesh Vutla wrote:
>> Hi Benoit,
>> On Thursday 29 August 2013 06:22 PM, Lokesh Vutla wrote:
>>> Add the AM33xx RNG module's device tree data.
>>> Also add Documentation file describing the data
>>> for the RNG module.
>> Seems you missed this patch. Please consider this for this merge window.
>
> Indeed I missed it. Sorry :-(
>
>> Patch 2/2 is already taken by Paul.
>> Without this patch AM335x boot will crash as I mentioned in my cover letter.
>>
>> Thanks and regards,
>> Lokesh
>>>
>>> Signed-off-by: Lokesh Vutla <lokeshvutla@ti.com>
>>> ---
>>> Changes since V1:
>>> - Drop "status=disabled" entry in dt node, Since
>>> RNG is present on all AM33xx platforms.
>>>
>>> .../devicetree/bindings/hwrng/omap_rng.txt | 22 ++++++++++++++++++++
>>> arch/arm/boot/dts/am33xx.dtsi | 7 +++++++
>>> 2 files changed, 29 insertions(+)
>>> create mode 100644 Documentation/devicetree/bindings/hwrng/omap_rng.txt
>
> I do not see the acked-by for the binding part. You do need that for any new bindings nowadays.
>
>>>
>>> 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 at 48310000 {
>>> + compatible = "ti,omap4-rng";
>>> + ti,hwmods = "rng";
>>> + reg = <0x48310000 0x2000>;
>>> + interrupts = <111>;
>>> +};
>>> diff --git a/arch/arm/boot/dts/am33xx.dtsi b/arch/arm/boot/dts/am33xx.dtsi
>>> index 38b446b..26ebe30 100644
>>> --- a/arch/arm/boot/dts/am33xx.dtsi
>>> +++ b/arch/arm/boot/dts/am33xx.dtsi
>>> @@ -530,5 +530,12 @@
>>> #size-cells = <1>;
>>> status = "disabled";
>>> };
>>> +
>>> + rng: rng at 48310000 {
>>> + compatible = "ti,omap4-rng";
>>> + ti,hwmods = "rng";
>>> + reg = <0x48310000 0x2000>;
>>> + interrupts = <111>;
>>> + };
>>> };
>>> };
>>>
>>
>
> It looks good to me, but it does not apply on my branch.
Can I take this as your Acked-by: ?
Ok, Ill rebase on top of your tree and post it.
Thanks and Regards,
Lokesh
> Please rebase it and repost with the proper acked-by.
>
> Thanks,
> Benoit
>
>
next prev parent reply other threads:[~2013-10-16 6:12 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-08-29 12:52 [RESEND PATCH V2 0/2] ARM: AM33xx: Add RNG Moudle data Lokesh Vutla
2013-08-29 12:52 ` Lokesh Vutla
2013-08-29 12:52 ` [RESEND PATCH V2 1/2] ARM: dts: AM33xx: Add RNG node Lokesh Vutla
2013-08-29 12:52 ` Lokesh Vutla
2013-10-12 13:26 ` Lokesh Vutla
2013-10-12 13:26 ` Lokesh Vutla
2013-10-12 21:51 ` Paul Walmsley
2013-10-12 21:51 ` Paul Walmsley
2013-10-15 6:49 ` Benoit Cousson
2013-10-15 6:49 ` Benoit Cousson
2013-10-16 6:12 ` Lokesh Vutla [this message]
2013-10-16 6:12 ` Lokesh Vutla
2013-10-16 11:16 ` Lokesh Vutla
2013-10-16 11:16 ` Lokesh Vutla
2013-10-29 21:00 ` Tony Lindgren
2013-10-29 21:00 ` Tony Lindgren
2013-10-29 23:28 ` Kumar Gala
2013-10-29 23:28 ` Kumar Gala
2013-08-29 12:52 ` [RESEND PATCH V2 2/2] ARM: AM33xx: hwmod: Add RNG module data Lokesh Vutla
2013-08-29 12:52 ` Lokesh Vutla
2013-10-09 15:03 ` Paul Walmsley
2013-10-09 15:03 ` Paul Walmsley
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=525E2E38.4000304@ti.com \
--to=lokeshvutla@ti.com \
--cc=bcousson@baylibre.com \
--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=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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.