From: Matt Porter <mporter@ti.com> To: Linux OMAP List <linux-omap@vger.kernel.org> Cc: Linux ARM Kernel List <linux-arm-kernel@lists.infradead.org>, Devicetree Discuss <devicetree-discuss@lists.ozlabs.org>, Linux Kernel Mailing List <linux-kernel@vger.kernel.org>, Benoit Cousson <b-cousson@ti.com>, Tony Lindgren <tony@atomide.com>, Vaibhav Hiremath <hvaibhav@ti.com>, AnilKumar <anilkumar@ti.com> Subject: [PATCH v2 2/2] ARM: dts: AM33XX: adjust leds to use the corrected gpio label Date: Mon, 10 Sep 2012 15:45:12 -0400 [thread overview] Message-ID: <1347306312-31533-3-git-send-email-mporter@ti.com> (raw) In-Reply-To: <1347306312-31533-1-git-send-email-mporter@ti.com> With the am33xx.dtsi now using gpio labels that match the AM33xx documentation, we need to refer to GPIO1 by the "gpio1" label. Signed-off-by: Matt Porter <mporter@ti.com> --- arch/arm/boot/dts/am335x-bone.dts | 8 ++++---- 1 file changed, 4 insertions(+), 4 deletions(-) diff --git a/arch/arm/boot/dts/am335x-bone.dts b/arch/arm/boot/dts/am335x-bone.dts index b0a7409..fa0c9d5 100644 --- a/arch/arm/boot/dts/am335x-bone.dts +++ b/arch/arm/boot/dts/am335x-bone.dts @@ -41,27 +41,27 @@ heartbeat { label = "beaglebone:green:usr0"; - gpios = <&gpio2 21 0>; + gpios = <&gpio1 21 0>; linux,default-trigger = "heartbeat"; default-state = "off"; }; mmc { label = "beaglebone:green:usr1"; - gpios = <&gpio2 22 0>; + gpios = <&gpio1 22 0>; linux,default-trigger = "mmc0"; default-state = "off"; }; led2 { label = "beaglebone:green:usr2"; - gpios = <&gpio2 23 0>; + gpios = <&gpio1 23 0>; default-state = "off"; }; led3 { label = "beaglebone:green:usr3"; - gpios = <&gpio2 24 0>; + gpios = <&gpio1 24 0>; default-state = "off"; }; }; -- 1.7.9.5
WARNING: multiple messages have this Message-ID (diff)
From: mporter@ti.com (Matt Porter) To: linux-arm-kernel@lists.infradead.org Subject: [PATCH v2 2/2] ARM: dts: AM33XX: adjust leds to use the corrected gpio label Date: Mon, 10 Sep 2012 15:45:12 -0400 [thread overview] Message-ID: <1347306312-31533-3-git-send-email-mporter@ti.com> (raw) In-Reply-To: <1347306312-31533-1-git-send-email-mporter@ti.com> With the am33xx.dtsi now using gpio labels that match the AM33xx documentation, we need to refer to GPIO1 by the "gpio1" label. Signed-off-by: Matt Porter <mporter@ti.com> --- arch/arm/boot/dts/am335x-bone.dts | 8 ++++---- 1 file changed, 4 insertions(+), 4 deletions(-) diff --git a/arch/arm/boot/dts/am335x-bone.dts b/arch/arm/boot/dts/am335x-bone.dts index b0a7409..fa0c9d5 100644 --- a/arch/arm/boot/dts/am335x-bone.dts +++ b/arch/arm/boot/dts/am335x-bone.dts @@ -41,27 +41,27 @@ heartbeat { label = "beaglebone:green:usr0"; - gpios = <&gpio2 21 0>; + gpios = <&gpio1 21 0>; linux,default-trigger = "heartbeat"; default-state = "off"; }; mmc { label = "beaglebone:green:usr1"; - gpios = <&gpio2 22 0>; + gpios = <&gpio1 22 0>; linux,default-trigger = "mmc0"; default-state = "off"; }; led2 { label = "beaglebone:green:usr2"; - gpios = <&gpio2 23 0>; + gpios = <&gpio1 23 0>; default-state = "off"; }; led3 { label = "beaglebone:green:usr3"; - gpios = <&gpio2 24 0>; + gpios = <&gpio1 24 0>; default-state = "off"; }; }; -- 1.7.9.5
next prev parent reply other threads:[~2012-09-10 19:44 UTC|newest] Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top 2012-09-10 19:45 [PATCH v2 0/2] ARM: dts: AM33xx: Correct gpio labels to match docs Matt Porter 2012-09-10 19:45 ` Matt Porter 2012-09-10 19:45 ` Matt Porter 2012-09-10 19:45 ` [PATCH v2 1/2] ARM: dts: AM33XX: fix gpio node numbering to match hardware Matt Porter 2012-09-10 19:45 ` Matt Porter 2012-09-10 19:45 ` Matt Porter 2012-09-10 19:45 ` Matt Porter [this message] 2012-09-10 19:45 ` [PATCH v2 2/2] ARM: dts: AM33XX: adjust leds to use the corrected gpio label Matt Porter 2012-09-11 6:38 ` [PATCH v2 0/2] ARM: dts: AM33xx: Correct gpio labels to match docs Hiremath, Vaibhav 2012-09-11 6:38 ` Hiremath, Vaibhav 2012-09-11 6:38 ` Hiremath, Vaibhav
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=1347306312-31533-3-git-send-email-mporter@ti.com \ --to=mporter@ti.com \ --cc=anilkumar@ti.com \ --cc=b-cousson@ti.com \ --cc=devicetree-discuss@lists.ozlabs.org \ --cc=hvaibhav@ti.com \ --cc=linux-arm-kernel@lists.infradead.org \ --cc=linux-kernel@vger.kernel.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: linkBe 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.