linux-omap.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Dan Murphy <dmurphy@ti.com>
To: Sricharan R <r.sricharan@ti.com>
Cc: linux-omap@vger.kernel.org, linux-arm-kernel@lists.infradead.org,
	tony@atomide.com, rnayak@ti.com, b-cousson@ti.com
Subject: Re: [PATCH 3/4] ARM: dts: omap5-uevm: Add LED support for uEVM blue LED
Date: Wed, 5 Jun 2013 12:04:15 -0500	[thread overview]
Message-ID: <51AF6F8F.4000702@ti.com> (raw)
In-Reply-To: <1370414770-1485-4-git-send-email-r.sricharan@ti.com>

Sricharan

Thanks for sending this up in the series.

On 06/05/2013 01:46 AM, Sricharan R wrote:
> From: Dan Murphy <dmurphy@ti.com>
>
> Add support for blue LED 1 off of GPIO 153.
> Make the LED a heartbeat LED
> Configure the MUX for GPIO output.
>
> Cc: Dan Murphy <dmurphy@ti.com>
> Signed-off-by: Dan Murphy <dmurphy@ti.com>
> [Sricharan R <r.sricharan@ti.com>: Replaced constants with preprocessor macros]
> Signed-off-by: Sricharan R <r.sricharan@ti.com>
> ---
>  arch/arm/boot/dts/omap5-uevm.dts |   17 +++++++++++++++++
>  1 file changed, 17 insertions(+)
>
> diff --git a/arch/arm/boot/dts/omap5-uevm.dts b/arch/arm/boot/dts/omap5-uevm.dts
> index cf862df..a2aed5b 100644
> --- a/arch/arm/boot/dts/omap5-uevm.dts
> +++ b/arch/arm/boot/dts/omap5-uevm.dts
> @@ -66,6 +66,16 @@
>  		device = <&hsusb2_phy>;
>  		clock-frequency = <19200000>; /* 19.2 MHz */
>  	};
> +
> +	leds {
> +		compatible = "gpio-leds";
> +		led@1 {
> +			label = "omap5:blue:usr1";
> +			gpios = <&gpio5 25 GPIO_ACTIVE_HIGH>; /* gpio5_153 D1 LED */
> +			linux,default-trigger = "heartbeat";
> +			default-state = "off";
> +		};
> +	};
>  };
>  
>  &omap5_pmx_core {
> @@ -77,6 +87,7 @@
>  			&mcbsp1_pins
>  			&mcbsp2_pins
>  			&usbhost_pins
> +			&led_gpio_pins
>  	>;
>  
>  	twl6040_pins: pinmux_twl6040_pins {
> @@ -175,6 +186,12 @@
>  			0x6e (PIN_OUTPUT | MUX_MODE6) /* gpio3_79 OUTPUT | MODE 6 ETH_NRESET */
>  		>;
>  	};
> +
> +	led_gpio_pins: pinmux_led_gpio_pins {
> +		pinctrl-single,pins = <
> +			0x196 (PIN_OUTPUT | MUX_MODE6) /* uart3_cts_rctx.gpio5_153 OUTPUT | MODE6 */
Same comment from Florian.  We can drop the OUTPUT | MODE6 in the comment.
> +		>;
> +	};
>  };
>  
>  &omap5_pmx_wkup {


-- 
------------------
Dan Murphy


  reply	other threads:[~2013-06-05 17:04 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-06-05  6:46 [PATCH 0/4] ARM: dts: omap5: Cleanup and updates for DT files Sricharan R
2013-06-05  6:46 ` [PATCH 1/4] ARM: dts: omap5: Rename omap5-evm to omap5-uevm Sricharan R
2013-06-05  6:50   ` Sricharan R
2013-06-05  6:46 ` [PATCH 2/4] ARM: dts: omap5-uevm: Add USB Host support Sricharan R
2013-06-05  7:59   ` Florian Vaussard
2013-06-05  9:12     ` Sricharan R
2013-06-05 12:15       ` Florian Vaussard
2013-06-05 10:32   ` Roger Quadros
2013-06-05 11:50     ` Sricharan R
2013-06-05 13:57   ` Nishanth Menon
2013-06-06 17:51     ` Sricharan R
2013-06-06 18:46       ` Nishanth Menon
2013-06-07  6:08         ` Sricharan R
2013-06-05  6:46 ` [PATCH 3/4] ARM: dts: omap5-uevm: Add LED support for uEVM blue LED Sricharan R
2013-06-05 17:04   ` Dan Murphy [this message]
2013-06-06 17:52     ` Sricharan R
2013-06-05  6:46 ` [PATCH 4/4] ARM: dts: omap5-uevm: Add uart pinctrl data Sricharan R

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=51AF6F8F.4000702@ti.com \
    --to=dmurphy@ti.com \
    --cc=b-cousson@ti.com \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-omap@vger.kernel.org \
    --cc=r.sricharan@ti.com \
    --cc=rnayak@ti.com \
    --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).