From: tony@atomide.com (Tony Lindgren)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH v7 2/3] arm/dts: AM33XX: Configure pinmuxs for user leds control on Bone
Date: Fri, 7 Sep 2012 10:00:24 -0700 [thread overview]
Message-ID: <20120907170023.GX1303@atomide.com> (raw)
In-Reply-To: <D8A9C7D8-76C8-4B30-A179-F007B336C97B@dominion.thruhere.net>
* Koen Kooi <koen@dominion.thruhere.net> [120907 01:46]:
>
> Op 6 sep. 2012, om 11:38 heeft AnilKumar Ch <anilkumar@ti.com> het volgende geschreven:
>
> > Adds GPIO pinctrl nodes to am3358_pinmux master node to control
> > user leds (USR0, USR1, USR2 and USR3) present on BeagleBone.
> >
> > [koen at dominion.thruhere.net: led0, led1 suggested by koen]
> > Signed-off-by: AnilKumar Ch <anilkumar@ti.com>
>
> Acked-by: Koen Kooi <koen@dominion.thruhere.net>
This one still has the discussion going on about if GPIO pins
should be muxed by the GPIO controller in the "GPIO only" case
for gpio leds driver. But other than that:
Acked-by: Tony Lindgren <tony@atomide.com>
>
> > ---
> > arch/arm/boot/dts/am335x-bone.dts | 43 +++++++++++++++++++++++++++++++++++++
> > 1 file changed, 43 insertions(+)
> >
> > diff --git a/arch/arm/boot/dts/am335x-bone.dts b/arch/arm/boot/dts/am335x-bone.dts
> > index c634f87..b0a7409 100644
> > --- a/arch/arm/boot/dts/am335x-bone.dts
> > +++ b/arch/arm/boot/dts/am335x-bone.dts
> > @@ -18,11 +18,54 @@
> > reg = <0x80000000 0x10000000>; /* 256 MB */
> > };
> >
> > + am33xx_pinmux: pinmux at 44e10800 {
> > + userled_pins: pinmux_userled_pins {
> > + pinctrl-single,pins = <
> > + 0x54 0x7 /* gpmc_a5.gpio1_21, OUTPUT | MODE7 */
> > + 0x58 0x17 /* gpmc_a6.gpio1_22, OUTPUT_PULLUP | MODE7 */
> > + 0x5c 0x7 /* gpmc_a7.gpio1_23, OUTPUT | MODE7 */
> > + 0x60 0x17 /* gpmc_a8.gpio1_24, OUTPUT_PULLUP | MODE7 */
> > + >;
> > + };
> > + };
> > +
> > ocp {
> > uart1: serial at 44e09000 {
> > status = "okay";
> > };
> >
> > + leds {
> > + compatible = "gpio-leds";
> > + pinctrl-names = "default";
> > + pinctrl-0 = <&userled_pins>;
> > +
> > + heartbeat {
> > + label = "beaglebone:green:usr0";
> > + gpios = <&gpio2 21 0>;
> > + linux,default-trigger = "heartbeat";
> > + default-state = "off";
> > + };
> > +
> > + mmc {
> > + label = "beaglebone:green:usr1";
> > + gpios = <&gpio2 22 0>;
> > + linux,default-trigger = "mmc0";
> > + default-state = "off";
> > + };
> > +
> > + led2 {
> > + label = "beaglebone:green:usr2";
> > + gpios = <&gpio2 23 0>;
> > + default-state = "off";
> > + };
> > +
> > + led3 {
> > + label = "beaglebone:green:usr3";
> > + gpios = <&gpio2 24 0>;
> > + default-state = "off";
> > + };
> > + };
> > +
> > i2c1: i2c at 44e0b000 {
> > status = "okay";
> > clock-frequency = <400000>;
> > --
> > 1.7.9.5
> >
> > --
> > To unsubscribe from this list: send the line "unsubscribe linux-omap" in
> > the body of a message to majordomo at vger.kernel.org
> > More majordomo info at http://vger.kernel.org/majordomo-info.html
> >
>
next prev parent reply other threads:[~2012-09-07 17:00 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-09-06 9:38 [PATCH v7 0/3] arm/dts: Add device tree data for AM33XX devices AnilKumar Ch
2012-09-06 9:38 ` [PATCH v7 1/3] arm/dts: AM33XX: Add basic pinctrl device tree data AnilKumar Ch
2012-09-07 16:58 ` Tony Lindgren
2012-09-06 9:38 ` [PATCH v7 2/3] arm/dts: AM33XX: Configure pinmuxs for user leds control on Bone AnilKumar Ch
2012-09-07 8:45 ` Koen Kooi
2012-09-07 17:00 ` Tony Lindgren [this message]
2012-09-06 9:38 ` [PATCH v7 3/3] arm/dts: AM33XX: Add D_CAN device tree data AnilKumar Ch
2012-09-07 5:30 ` [PATCH v7 0/3] arm/dts: Add device tree data for AM33XX devices AnilKumar, Chimata
2012-09-07 8:37 ` Benoit Cousson
2012-09-07 17:01 ` Tony Lindgren
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=20120907170023.GX1303@atomide.com \
--to=tony@atomide.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 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).