From: Benoit Cousson <b-cousson@ti.com>
To: Lokesh Vutla <lokeshvutla@ti.com>
Cc: linux-omap@vger.kernel.org, linux-arm-kernel@lists.infradead.org,
devicetree-discuss@lists.ozlabs.org
Subject: Re: [PATCH V2 2/3] ARM: dts: omap5: EMIF device tree data for OMAP5 boards
Date: Mon, 5 Nov 2012 11:55:48 +0100 [thread overview]
Message-ID: <50979B34.8010009@ti.com> (raw)
In-Reply-To: <1349959669-16366-3-git-send-email-lokeshvutla@ti.com>
On 10/11/2012 02:47 PM, Lokesh Vutla wrote:
> Adding EMIF device tree data for OMAP5 boards.
>
> Signed-off-by: Lokesh Vutla <lokeshvutla@ti.com>
> ---
> arch/arm/boot/dts/omap5.dtsi | 24 ++++++++++++++++++++++++
> 1 file changed, 24 insertions(+)
>
> diff --git a/arch/arm/boot/dts/omap5.dtsi b/arch/arm/boot/dts/omap5.dtsi
> index 5db33f4..445aeea 100644
> --- a/arch/arm/boot/dts/omap5.dtsi
> +++ b/arch/arm/boot/dts/omap5.dtsi
> @@ -319,5 +319,29 @@
> ti,buffer-size = <128>;
> ti,hwmods = "mcbsp3";
> };
> +
> + emif1: emif@0x4c000000 {
> + compatible = "ti,emif-4d5";
> + ti,hwmods = "emif1";
> + phy-type = <2>;
> + reg = <0x4c000000 0x3ff>;
Should 0x400. This parameter is the size, not the end address.
> + interrupts = <0 110 0x4>;
> + interrupt-parent = <&gic>;
Please remove the interrupt-parent. It is not needed since DT will use
the parent node to get it. It will avoid duplicating the entry for every
nodes.
> + hw-caps-read-idle-ctrl;
> + hw-caps-ll-interface;
> + hw-caps-temp-alert;
> + };
> +
> + emif2: emif@0x4d000000 {
> + compatible = "ti,emif-4d5";
> + ti,hwmods = "emif2";
> + phy-type = <2>;
Can you just add a comment to give more information. I know this is in
the binding documentation, but some more comment never hurt.
> + reg = <0x4d000000 0x3ff>;
0x400 as well.
> + interrupts = <0 111 0x4>;
> + interrupt-parent = <&gic>;
Ditto.
> + hw-caps-read-idle-ctrl;
> + hw-caps-ll-interface;
> + hw-caps-temp-alert;
> + };
> };
> };
>
Regards,
Benoit
next prev parent reply other threads:[~2012-11-05 10:55 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-10-11 12:47 [PATCH V2 0/3] ARM: dts: omap5: EMIF and LPDDR2 device tree data Lokesh Vutla
2012-10-11 12:47 ` [PATCH V2 1/3] ARM: dts: omap5-evm: Fix size of memory defined for EVM Lokesh Vutla
2012-10-11 12:47 ` [PATCH V2 2/3] ARM: dts: omap5: EMIF device tree data for OMAP5 boards Lokesh Vutla
2012-11-05 10:55 ` Benoit Cousson [this message]
2012-10-11 12:47 ` [PATCH V2 3/3] ARM: dts: omap5-evm: LPDDR2 memory device details for EVM Lokesh Vutla
2012-11-05 11:02 ` Benoit Cousson
2012-11-05 5:58 ` [PATCH V2 0/3] ARM: dts: omap5: EMIF and LPDDR2 device tree data Lokesh Vutla
2012-11-05 10:51 ` Benoit Cousson
2012-11-05 11:03 ` Benoit Cousson
2012-11-05 11:06 ` 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=50979B34.8010009@ti.com \
--to=b-cousson@ti.com \
--cc=devicetree-discuss@lists.ozlabs.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-omap@vger.kernel.org \
--cc=lokeshvutla@ti.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).