From: Nishanth Menon <nm@ti.com>
To: Dan Murphy <dmurphy@ti.com>
Cc: linux@arm.linux.org.uk, b-cousson@ti.com, tony@atomide.com,
devicetree-discuss@lists.ozlabs.org,
linux-kernel@vger.kernel.org, linux-omap@vger.kernel.org,
linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH v5] ARM:dts:omap4-panda: Update the LED support for the panda DTS
Date: Fri, 17 May 2013 08:34:18 -0500 [thread overview]
Message-ID: <20130517133418.GA5068@kahuna> (raw)
In-Reply-To: <1368796883-5501-1-git-send-email-dmurphy@ti.com>
On 08:21-20130517, Dan Murphy wrote:
[...]
May be others with better DT experience can help here..
but here is a trick to reduce dts file changes:
> diff --git a/arch/arm/boot/dts/omap4-panda-es.dts b/arch/arm/boot/dts/omap4-panda-es.dts
> index f1d8c21..08d2e38 100644
> --- a/arch/arm/boot/dts/omap4-panda-es.dts
> +++ b/arch/arm/boot/dts/omap4-panda-es.dts
> @@ -34,3 +34,37 @@
> 0x5e 0x100 /* hdmi_sda.hdmi_sda INPUT | MODE 0 */
> >;
> };
> +
> +&omap4_pmx_core {
> + led_gpio_pins: gpio_led_pmx {
> + pinctrl-single,pins = <
> + 0xb6 0x3 /* gpio_110 OUTPUT | MODE 3 */
> + >;
> + };
> +};
> +
> +&led_wkgpio_pins {
> + pinctrl-single,pins = <
> + 0x1c 0x3 /* gpio_wk8 OUTPUT | MODE 3 */
> + >;
> +};
> +
> +&leds {
> + compatible = "gpio-leds";
> + pinctrl-names = "default";
Normally, override will either add (if new param) OR replace (if same param)
So the above two are superfluous.
> + pinctrl-0 = <
> + &led_gpio_pins
> + &led_wkgpio_pins
> + >;
These are needed
> +
> + heartbeat {
> + label = "pandaboard::status1";
can drop this
> + gpios = <&gpio4 14 0>;
needed
> + linux,default-trigger = "heartbeat";
can be dropped
> + };
> + mmc {
> + label = "pandaboard::status2";
could be dropped
> + gpios = <&gpio1 8 0>;
needed
> + linux,default-trigger = "mmc0";
could be dropped.
--
Regards,
Nishanth Menon
prev parent reply other threads:[~2013-05-17 13:34 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-05-17 13:21 [PATCH v5] ARM:dts:omap4-panda: Update the LED support for the panda DTS Dan Murphy
2013-05-17 13:34 ` Nishanth Menon [this message]
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=20130517133418.GA5068@kahuna \
--to=nm@ti.com \
--cc=b-cousson@ti.com \
--cc=devicetree-discuss@lists.ozlabs.org \
--cc=dmurphy@ti.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-omap@vger.kernel.org \
--cc=linux@arm.linux.org.uk \
--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).