From: viresh.kumar@st.com (Viresh Kumar)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH v4] ARM: SPEAr600: Add device-tree support to SPEAr600 boards
Date: Fri, 16 Mar 2012 15:21:53 +0530 [thread overview]
Message-ID: <4F630D39.2090905@st.com> (raw)
In-Reply-To: <1331890216-8361-1-git-send-email-sr@denx.de>
On 3/16/2012 3:00 PM, Stefan Roese wrote:
> This patch adds a generic target for SPEAr600 board that can be
> configured via the device-tree. Currently the following devices
> are supported via the devicetree:
>
> - VIC interrupts
> - PL011 UART
> - PL061 GPIO
> - Synopsys DW I2C
> - Synopsys DW ethernet
>
> Signed-off-by: Stefan Roese <sr@denx.de>
> Cc: Viresh Kumar <viresh.kumar@st.com>
> Cc: Arnd Bergmann <arnd@arndb.de>
> Cc: Jean-Christophe PLAGNIOL-VILLARD <plagnioj@jcrosoft.com>
Acked-by: Viresh Kumar <viresh.kumar@st.com>
I have one query (as part of my learning of DT) to all DT experts:
>
> + /* local/cpu GPIO */
> + gpio0: gpio at f0100000 {
> + #gpio-cells = <2>;
> + compatible = "arm,pl061", "arm,primecell";
> + gpio-controller;
> + reg = <0xf0100000 0x1000>;
> + interrupt-parent = <&vic0>;
> + interrupts = <18>;
> + };
> +
>
Can we add name property here:
name = "gpio0"
So that we don't need to do below stuff.
> diff --git a/arch/arm/mach-spear6xx/clock.c b/arch/arm/mach-spear6xx/clock.c
> @@ -641,8 +641,8 @@ static struct clk_lookup spear_clk_lookups[] = {
> - { .dev_id = "gpio0", .clk = &gpio0_clk},
> - { .dev_id = "gpio1", .clk = &gpio1_clk},
> - { .dev_id = "gpio2", .clk = &gpio2_clk},
> + { .dev_id = "f0100000.gpio", .clk = &gpio0_clk},
> + { .dev_id = "fc980000.gpio", .clk = &gpio1_clk},
I can't find much dts files using this approach. Even i don't know
if setting name will be sufficient?
--
viresh
WARNING: multiple messages have this Message-ID (diff)
From: Viresh Kumar <viresh.kumar-qxv4g6HH51o@public.gmane.org>
To: Stefan Roese <sr-ynQEQJNshbs@public.gmane.org>,
Arnd Bergmann <arnd-r2nGTMty4D4@public.gmane.org>,
Jean-Christophe PLAGNIOL-VILLARD
<plagnioj-sclMFOaUSTBWk0Htik3J/w@public.gmane.org>
Cc: "devicetree-discuss-mnsaURCQ41sdnm+yROfE0A@public.gmane.org"
<devicetree-discuss-mnsaURCQ41sdnm+yROfE0A@public.gmane.org>,
spear-devel <spear-devel-nkJGhpqTU55BDgjK7y7TUQ@public.gmane.org>,
"linux-arm-kernel-IAPFreCvJWM7uuMidbF8XUB+6BGkLq7r@public.gmane.org"
<linux-arm-kernel-IAPFreCvJWM7uuMidbF8XUB+6BGkLq7r@public.gmane.org>
Subject: Re: [PATCH v4] ARM: SPEAr600: Add device-tree support to SPEAr600 boards
Date: Fri, 16 Mar 2012 15:21:53 +0530 [thread overview]
Message-ID: <4F630D39.2090905@st.com> (raw)
In-Reply-To: <1331890216-8361-1-git-send-email-sr-ynQEQJNshbs@public.gmane.org>
On 3/16/2012 3:00 PM, Stefan Roese wrote:
> This patch adds a generic target for SPEAr600 board that can be
> configured via the device-tree. Currently the following devices
> are supported via the devicetree:
>
> - VIC interrupts
> - PL011 UART
> - PL061 GPIO
> - Synopsys DW I2C
> - Synopsys DW ethernet
>
> Signed-off-by: Stefan Roese <sr-ynQEQJNshbs@public.gmane.org>
> Cc: Viresh Kumar <viresh.kumar-qxv4g6HH51o@public.gmane.org>
> Cc: Arnd Bergmann <arnd-r2nGTMty4D4@public.gmane.org>
> Cc: Jean-Christophe PLAGNIOL-VILLARD <plagnioj-sclMFOaUSTBWk0Htik3J/w@public.gmane.org>
Acked-by: Viresh Kumar <viresh.kumar-qxv4g6HH51o@public.gmane.org>
I have one query (as part of my learning of DT) to all DT experts:
>
> + /* local/cpu GPIO */
> + gpio0: gpio@f0100000 {
> + #gpio-cells = <2>;
> + compatible = "arm,pl061", "arm,primecell";
> + gpio-controller;
> + reg = <0xf0100000 0x1000>;
> + interrupt-parent = <&vic0>;
> + interrupts = <18>;
> + };
> +
>
Can we add name property here:
name = "gpio0"
So that we don't need to do below stuff.
> diff --git a/arch/arm/mach-spear6xx/clock.c b/arch/arm/mach-spear6xx/clock.c
> @@ -641,8 +641,8 @@ static struct clk_lookup spear_clk_lookups[] = {
> - { .dev_id = "gpio0", .clk = &gpio0_clk},
> - { .dev_id = "gpio1", .clk = &gpio1_clk},
> - { .dev_id = "gpio2", .clk = &gpio2_clk},
> + { .dev_id = "f0100000.gpio", .clk = &gpio0_clk},
> + { .dev_id = "fc980000.gpio", .clk = &gpio1_clk},
I can't find much dts files using this approach. Even i don't know
if setting name will be sufficient?
--
viresh
next prev parent reply other threads:[~2012-03-16 9:51 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-03-16 9:30 [PATCH v4] ARM: SPEAr600: Add device-tree support to SPEAr600 boards Stefan Roese
2012-03-16 9:30 ` Stefan Roese
2012-03-16 9:51 ` Viresh Kumar [this message]
2012-03-16 9:51 ` Viresh Kumar
2012-03-16 11:51 ` Jean-Christophe PLAGNIOL-VILLARD
2012-03-16 11:51 ` Jean-Christophe PLAGNIOL-VILLARD
2012-03-16 11:50 ` Jean-Christophe PLAGNIOL-VILLARD
2012-03-16 11:50 ` Jean-Christophe PLAGNIOL-VILLARD
2012-03-16 12:09 ` Arnd Bergmann
2012-03-16 12:09 ` Arnd Bergmann
2012-03-16 12:33 ` Stefan Roese
2012-03-16 12:33 ` Stefan Roese
2012-03-16 12:52 ` Arnd Bergmann
2012-03-16 12:52 ` Arnd Bergmann
2012-03-16 12:57 ` Stefan Roese
2012-03-16 12:57 ` Stefan Roese
2012-03-16 12:20 ` Stefan Roese
2012-03-16 12:20 ` Stefan Roese
2012-03-16 12:14 ` Arnd Bergmann
2012-03-16 12:14 ` Arnd Bergmann
2012-03-16 12:34 ` Stefan Roese
2012-03-16 12:34 ` Stefan Roese
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=4F630D39.2090905@st.com \
--to=viresh.kumar@st.com \
--cc=linux-arm-kernel@lists.infradead.org \
/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.