From: Anson Huang <Anson.Huang@nxp.com>
To: shawnguo@kernel.org, s.hauer@pengutronix.de,
kernel@pengutronix.de, fabio.estevam@nxp.com, robh+dt@kernel.org,
mark.rutland@arm.com, linux-arm-kernel@lists.infradead.org,
devicetree@vger.kernel.org, linux-kernel@vger.kernel.org
Cc: Linux-imx@nxp.com
Subject: [PATCH 2/3] ARM: dts: imx6sll-evk: correct lcd regulator GPIO pin
Date: Fri, 13 Jul 2018 15:58:26 +0800 [thread overview]
Message-ID: <1531468707-25737-2-git-send-email-Anson.Huang@nxp.com> (raw)
In-Reply-To: <1531468707-25737-1-git-send-email-Anson.Huang@nxp.com>
On i.MX6SLL EVK board, lcd regulator is controlled
by GPIO4 IO03 using MX6SLL_PAD_KEY_ROW5__GPIO4_IO03 pin,
NOT MX6SLL_PAD_ECSPI1_SCLK__GPIO4_IO08, correct it.
Signed-off-by: Anson Huang <Anson.Huang@nxp.com>
---
arch/arm/boot/dts/imx6sll-evk.dts | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/arch/arm/boot/dts/imx6sll-evk.dts b/arch/arm/boot/dts/imx6sll-evk.dts
index cc5cf5e..41e87e6 100644
--- a/arch/arm/boot/dts/imx6sll-evk.dts
+++ b/arch/arm/boot/dts/imx6sll-evk.dts
@@ -74,7 +74,7 @@
pinctrl-names = "default";
pinctrl-0 = <&pinctrl_reg_lcd>;
regulator-name = "lcd-pwr";
- gpio = <&gpio4 8 GPIO_ACTIVE_HIGH>;
+ gpio = <&gpio4 3 GPIO_ACTIVE_HIGH>;
enable-active-high;
};
@@ -289,7 +289,7 @@
pinctrl_reg_lcd: reglcdgrp {
fsl,pins = <
- MX6SLL_PAD_ECSPI1_SCLK__GPIO4_IO08 0x17059
+ MX6SLL_PAD_KEY_ROW5__GPIO4_IO03 0x17059
>;
};
--
2.7.4
next prev parent reply other threads:[~2018-07-13 8:03 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-07-13 7:58 [PATCH 1/3] ARM: dts: imx6sll-evk: enable PWM1 for backlight driver Anson Huang
2018-07-13 7:58 ` Anson Huang [this message]
2018-07-13 18:00 ` [PATCH 2/3] ARM: dts: imx6sll-evk: correct lcd regulator GPIO pin Fabio Estevam
2018-07-13 7:58 ` [PATCH 3/3] ARM: dts: imx6sll-evk: enable SEIKO 43WVF1G lcdif panel Anson Huang
2018-07-13 18:01 ` Fabio Estevam
2018-07-13 17:58 ` [PATCH 1/3] ARM: dts: imx6sll-evk: enable PWM1 for backlight driver Fabio Estevam
2018-07-17 5:58 ` 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=1531468707-25737-2-git-send-email-Anson.Huang@nxp.com \
--to=anson.huang@nxp.com \
--cc=Linux-imx@nxp.com \
--cc=devicetree@vger.kernel.org \
--cc=fabio.estevam@nxp.com \
--cc=kernel@pengutronix.de \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mark.rutland@arm.com \
--cc=robh+dt@kernel.org \
--cc=s.hauer@pengutronix.de \
--cc=shawnguo@kernel.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).