From: andrew@lunn.ch (Andrew Lunn)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 1/3] arm: kirkwood: affect pins to their devices on OpenBlocks A6
Date: Wed, 6 Mar 2013 19:21:31 +0100 [thread overview]
Message-ID: <20130306182131.GF3904@lunn.ch> (raw)
In-Reply-To: <1362587021-32762-2-git-send-email-thomas.petazzoni@free-electrons.com>
On Wed, Mar 06, 2013 at 05:23:39PM +0100, Thomas Petazzoni wrote:
> The pinctrl configuration done for the Kirkwood-based OpenBlocks A6
> board was somewhat strange: all pins for all devices were selected
> through "hogs", i.e as pins of the pinctrl device. Even though it
> works, it isn't the proper way of doing things: pins should preferably
> be associated to whatever device they belong to.
Hi Thomas
Being able to add pinctrl nodes to the device is new. I think it was
added in 3.8. Before then each device driver had to explicitly request
its pins and most didn't, so hogs was the way to do it. Now the core
driver code gets the pins. So i would not say it is odd, just
outdated. It would be nice to change the comment to reflect this.
> Therefore, this patch moves the selection of pin muxing of the
> relevant pins to the UART nodes, the I2C node, the NAND node and the
> gpio-leds node.
For gpio-leds, see the comment i just made for the next patch.
Otherwise this look O.K.
Andrew
>
> Signed-off-by: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
> ---
> arch/arm/boot/dts/kirkwood-openblocks_a6.dts | 19 +++++++++++++------
> 1 file changed, 13 insertions(+), 6 deletions(-)
>
> diff --git a/arch/arm/boot/dts/kirkwood-openblocks_a6.dts b/arch/arm/boot/dts/kirkwood-openblocks_a6.dts
> index ede7fe0d..087681d 100644
> --- a/arch/arm/boot/dts/kirkwood-openblocks_a6.dts
> +++ b/arch/arm/boot/dts/kirkwood-openblocks_a6.dts
> @@ -19,17 +19,23 @@
> ocp at f1000000 {
> serial at 12000 {
> clock-frequency = <200000000>;
> + pinctrl-0 = <&pmx_uart0>;
> + pinctrl-names = "default";
> status = "ok";
> };
>
> serial at 12100 {
> clock-frequency = <200000000>;
> + pinctrl-0 = <&pmx_uart1>;
> + pinctrl-names = "default";
> status = "ok";
> };
>
> nand at 3000000 {
> chip-delay = <25>;
> status = "okay";
> + pinctrl-0 = <&pmx_nand>;
> + pinctrl-names = "default";
>
> partition at 0 {
> label = "uboot";
> @@ -69,6 +75,8 @@
>
> i2c at 11100 {
> status = "okay";
> + pinctrl-0 = <&pmx_twsi1>;
> + pinctrl-names = "default";
>
> s35390a: s35390a at 30 {
> compatible = "s35390a";
> @@ -77,16 +85,12 @@
> };
>
> pinctrl: pinctrl at 10000 {
> - pinctrl-0 = < &pmx_nand &pmx_uart0
> - &pmx_uart1 &pmx_twsi1
> - &pmx_dip_sw0 &pmx_dip_sw1
> + pinctrl-0 = <&pmx_dip_sw0 &pmx_dip_sw1
> &pmx_dip_sw2 &pmx_dip_sw3
> &pmx_gpio_0 &pmx_gpio_1
> &pmx_gpio_2 &pmx_gpio_3
> &pmx_gpio_4 &pmx_gpio_5
> - &pmx_gpio_6 &pmx_gpio_7
> - &pmx_led_red &pmx_led_green
> - &pmx_led_yellow >;
> + &pmx_gpio_6 &pmx_gpio_7>;
> pinctrl-names = "default";
>
> pmx_uart0: pmx-uart0 {
> @@ -195,6 +199,9 @@
>
> gpio-leds {
> compatible = "gpio-leds";
> + pinctrl-0 = <&pmx_led_red &pmx_led_green
> + &pmx_led_yellow>;
> + pinctrl-names = "default";
>
> led-red {
> label = "obsa6:red:stat";
> --
> 1.7.9.5
>
next prev parent reply other threads:[~2013-03-06 18:21 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-03-06 16:23 [PATCH for 3.10] Misc small improvements to Kirkwood-based OpenBlocks A6 platform Thomas Petazzoni
2013-03-06 16:23 ` [PATCH 1/3] arm: kirkwood: affect pins to their devices on OpenBlocks A6 Thomas Petazzoni
2013-03-06 18:21 ` Andrew Lunn [this message]
2013-03-06 19:07 ` Thomas Petazzoni
2013-03-06 16:23 ` [PATCH 2/3] arm: kirkwood: factor pinmux descriptors for " Thomas Petazzoni
2013-03-06 18:16 ` Andrew Lunn
2013-03-06 19:16 ` Thomas Petazzoni
2013-03-07 6:22 ` Andrew Lunn
2013-03-07 8:08 ` Thomas Petazzoni
2013-03-07 9:24 ` Andrew Lunn
2013-03-22 15:44 ` Thomas Petazzoni
2013-03-26 19:48 ` Andrew Lunn
2013-03-06 16:23 ` [PATCH 3/3] arm: kirkwood: add support for Init button on " Thomas Petazzoni
2013-03-06 18:24 ` Andrew Lunn
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=20130306182131.GF3904@lunn.ch \
--to=andrew@lunn.ch \
--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 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).