From: Javier Martinez Canillas <javier@dowhile0.org>
To: Jon Hunter <jon-hunter@ti.com>
Cc: Tony Lindgren <tony@atomide.com>,
Benoit Cousson <b-cousson@ti.com>,
device-tree <devicetree-discuss@lists.ozlabs.org>,
linux-omap <linux-omap@vger.kernel.org>,
linux-arm <linux-arm-kernel@lists.infradead.org>
Subject: Re: [PATCH 5/9] ARM: dts: Add GPMC node for OMAP2, OMAP4 and OMAP5
Date: Fri, 8 Mar 2013 21:25:00 +0100 [thread overview]
Message-ID: <CABxcv==OKX4z8x7ztqDJ5CozNmTQ5UaD43mTLWfQuqUt-y7xcQ@mail.gmail.com> (raw)
In-Reply-To: <1362763654-9660-6-git-send-email-jon-hunter@ti.com>
On Fri, Mar 8, 2013 at 6:27 PM, Jon Hunter <jon-hunter@ti.com> wrote:
> Add the device-tree node for GPMC on OMAP2, OMAP4 and OMAP5 devices.
>
> Signed-off-by: Jon Hunter <jon-hunter@ti.com>
> ---
> arch/arm/boot/dts/omap2420.dtsi | 11 +++++++++++
> arch/arm/boot/dts/omap2430.dtsi | 11 +++++++++++
> arch/arm/boot/dts/omap4.dtsi | 11 +++++++++++
> arch/arm/boot/dts/omap5.dtsi | 11 +++++++++++
> 4 files changed, 44 insertions(+)
>
> diff --git a/arch/arm/boot/dts/omap2420.dtsi b/arch/arm/boot/dts/omap2420.dtsi
> index af65609..d4ce6c2 100644
> --- a/arch/arm/boot/dts/omap2420.dtsi
> +++ b/arch/arm/boot/dts/omap2420.dtsi
> @@ -29,6 +29,17 @@
> pinctrl-single,function-mask = <0x3f>;
> };
>
> + gpmc: gpmc@6800a000 {
> + compatible = "ti,omap2420-gpmc";
> + reg = <0x6800a000 0x1000>;
> + #address-cells = <2>;
> + #size-cells = <1>;
> + interrupts = <20>;
> + gpmc,num-cs = <8>;
> + gpmc,num-waitpins = <4>;
> + ti,hwmods = "gpmc";
> + };
> +
> mcbsp1: mcbsp@48074000 {
> compatible = "ti,omap2420-mcbsp";
> reg = <0x48074000 0xff>;
> diff --git a/arch/arm/boot/dts/omap2430.dtsi b/arch/arm/boot/dts/omap2430.dtsi
> index c392445..832f184 100644
> --- a/arch/arm/boot/dts/omap2430.dtsi
> +++ b/arch/arm/boot/dts/omap2430.dtsi
> @@ -29,6 +29,17 @@
> pinctrl-single,function-mask = <0x3f>;
> };
>
> + gpmc: gpmc@6e000000 {
> + compatible = "ti,omap2430-gpmc";
> + reg = <0x6e000000 0x1000>;
> + #address-cells = <2>;
> + #size-cells = <1>;
> + interrupts = <20>;
> + gpmc,num-cs = <8>;
> + gpmc,num-waitpins = <4>;
> + ti,hwmods = "gpmc";
> + };
> +
> mcbsp1: mcbsp@48074000 {
> compatible = "ti,omap2430-mcbsp";
> reg = <0x48074000 0xff>;
> diff --git a/arch/arm/boot/dts/omap4.dtsi b/arch/arm/boot/dts/omap4.dtsi
> index 827f6f3..726ef11 100644
> --- a/arch/arm/boot/dts/omap4.dtsi
> +++ b/arch/arm/boot/dts/omap4.dtsi
> @@ -196,6 +196,17 @@
> #interrupt-cells = <1>;
> };
>
> + gpmc: gpmc@50000000 {
> + compatible = "ti,omap4430-gpmc";
> + reg = <0x50000000 0x1000>;
Hi Jon,
By looking at the GPMC Register Summary from both the OMAP4460 and OMAP OMAP35x
Technical Reference Manuals I see that the GPMC register address space
is only 720 bytes length. From base address + 0x0 to base address +
0x02d0.
So shouldn't the regs property be <0x50000000 0x2d0> instead?
Of course are only a few kilobytes but still I wonder if it makes
sense to map them when they are not going to be used.
Best regards,
Javier
next prev parent reply other threads:[~2013-03-08 20:25 UTC|newest]
Thread overview: 37+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-03-08 17:27 [PATCH 0/9] ARM: dts: Various OMAP2+ device-tree updates Jon Hunter
2013-03-08 17:27 ` [PATCH 1/9] ARM: OMAP2+: Prepare for device-tree PMU support Jon Hunter
2013-03-08 17:27 ` [PATCH 2/9] ARM: dts: OMAP2+: Add PMU nodes Jon Hunter
2013-03-08 17:27 ` [PATCH 3/9] ARM: dts: OMAP2+: Add SDMA controller bindings and nodes Jon Hunter
2013-03-08 17:27 ` [PATCH 4/9] ARM: dts: OMAP3: Add support for OMAP3430 SDP board Jon Hunter
2013-03-09 2:25 ` Anil Kumar
2013-03-11 17:53 ` Jon Hunter
2013-03-12 2:42 ` Kumar, Anil
2013-03-12 8:50 ` Javier Martinez Canillas
2013-03-13 2:50 ` Kumar, Anil
2013-03-12 21:27 ` Jon Hunter
2013-03-13 2:59 ` Kumar, Anil
2013-03-11 2:45 ` Anil Kumar
2013-03-11 17:54 ` Jon Hunter
2013-03-08 17:27 ` [PATCH 5/9] ARM: dts: Add GPMC node for OMAP2, OMAP4 and OMAP5 Jon Hunter
2013-03-08 20:25 ` Javier Martinez Canillas [this message]
2013-03-08 21:41 ` Jon Hunter
2013-03-09 1:25 ` Javier Martinez Canillas
2013-03-09 12:42 ` Ezequiel Garcia
2013-03-11 17:56 ` Jon Hunter
2013-03-14 15:45 ` Benoit Cousson
2013-03-14 15:50 ` Jon Hunter
2013-03-14 15:57 ` Ezequiel Garcia
2013-03-14 15:58 ` Benoit Cousson
2013-03-14 16:00 ` Jon Hunter
2013-03-14 16:03 ` Benoit Cousson
2013-03-08 17:27 ` [PATCH 6/9] ARM: dts: Add OMAP3430 SDP flash memory bindings Jon Hunter
2013-03-08 17:27 ` [PATCH 7/9] ARM: dts: Add OMAP2 gpio bindings Jon Hunter
2013-03-08 17:27 ` [PATCH 8/9] ARM: dts: OMAP3+: Correct gpio #interrupts-cells property Jon Hunter
2013-03-08 17:27 ` [PATCH 9/9] ARM: dts: OMAP3: Add reg and interrupt properties for gpio Jon Hunter
2013-03-14 14:57 ` [PATCH 0/9] ARM: dts: Various OMAP2+ device-tree updates Benoit Cousson
2013-03-14 15:45 ` Florian Vaussard
2013-03-14 15:59 ` Jon Hunter
2013-03-14 16:06 ` Benoit Cousson
2013-03-14 16:02 ` Javier Martinez Canillas
2013-03-14 16:04 ` Jon Hunter
2013-03-14 16:08 ` Benoit Cousson
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='CABxcv==OKX4z8x7ztqDJ5CozNmTQ5UaD43mTLWfQuqUt-y7xcQ@mail.gmail.com' \
--to=javier@dowhile0.org \
--cc=b-cousson@ti.com \
--cc=devicetree-discuss@lists.ozlabs.org \
--cc=jon-hunter@ti.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-omap@vger.kernel.org \
--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).