From: Bhuvanchandra DV <bhuvanchandra.dv@toradex.com>
To: shawnguo@kernel.org
Cc: linux-arm-kernel@lists.infradead.org, devicetree@vger.kernel.org,
kernel@pengutronix.de, stefan@agner.ch,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] ARM: dts: vf-colibri-eval-v3: Use enable-gpios for BL_ON
Date: Wed, 27 Jan 2016 23:53:41 +0530 [thread overview]
Message-ID: <56A90B2D.70006@toradex.com> (raw)
In-Reply-To: <1452322793-26020-1-git-send-email-bhuvanchandra.dv@toradex.com>
Ping!
On 01/09/2016 12:29 PM, Bhuvanchandra DV wrote:
> Use pwm-backlight driver 'enable-gpios' property for backlight on/off
> control.
>
> Signed-off-by: Bhuvanchandra DV <bhuvanchandra.dv@toradex.com>
> ---
> arch/arm/boot/dts/vf-colibri.dtsi | 9 +++++++++
> 1 file changed, 9 insertions(+)
>
> diff --git a/arch/arm/boot/dts/vf-colibri.dtsi b/arch/arm/boot/dts/vf-colibri.dtsi
> index e5949b9..1c0da05 100644
> --- a/arch/arm/boot/dts/vf-colibri.dtsi
> +++ b/arch/arm/boot/dts/vf-colibri.dtsi
> @@ -10,7 +10,10 @@
> / {
> bl: backlight {
> compatible = "pwm-backlight";
> + pinctrl-names = "default";
> + pinctrl-0 = <&pinctrl_gpio_bl_on>;
> pwms = <&pwm0 0 5000000 0>;
> + enable-gpios = <&gpio1 13 GPIO_ACTIVE_HIGH>;
> status = "disabled";
> };
> };
> @@ -169,6 +172,12 @@
> >;
> };
>
> + pinctrl_gpio_bl_on: gpio_bl_on {
> + fsl,pins = <
> + VF610_PAD_PTC0__GPIO_45 0x22ef
> + >;
> + };
> +
> pinctrl_i2c0: i2c0grp {
> fsl,pins = <
> VF610_PAD_PTB14__I2C0_SCL 0x37ff
>
--
Best regards,
Bhuvan
next prev parent reply other threads:[~2016-01-27 18:23 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-01-09 6:59 [PATCH] ARM: dts: vf-colibri-eval-v3: Use enable-gpios for BL_ON Bhuvanchandra DV
2016-01-27 18:23 ` Bhuvanchandra DV [this message]
[not found] ` <1452322793-26020-1-git-send-email-bhuvanchandra.dv-2KBjVHiyJgBBDgjK7y7TUQ@public.gmane.org>
2016-01-28 8:39 ` Shawn Guo
2016-01-28 22:28 ` Stefan Agner
2016-02-01 11:19 ` Shawn Guo
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=56A90B2D.70006@toradex.com \
--to=bhuvanchandra.dv@toradex.com \
--cc=devicetree@vger.kernel.org \
--cc=kernel@pengutronix.de \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=shawnguo@kernel.org \
--cc=stefan@agner.ch \
/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).