From: Andy Yan <andy.yan@rock-chips.com>
To: heiko@sntech.de, robh+dt@kernel.org, devicetree@vger.kernel.org,
linux-rockchip@lists.infradead.org
Cc: linux-kernel@vger.kernel.org,
linux-arm-kernel@lists.infradead.org,
Andy Yan <andy.yan@rock-chips.com>
Subject: [PATCH 3/4] arm64: dts: rockchip: remove enable-gpio of backlight on rk3399 evb
Date: Thu, 5 Mar 2020 19:39:11 +0800 [thread overview]
Message-ID: <20200305113912.32226-4-andy.yan@rock-chips.com> (raw)
In-Reply-To: <20200305113912.32226-1-andy.yan@rock-chips.com>
There is no enable-gpio for backlight control on rk3399 evb,
actually GPIO1_B5 is for LCD panle enable. So remove it from backlight
dt node.
Signed-off-by: Andy Yan <andy.yan@rock-chips.com>
---
arch/arm64/boot/dts/rockchip/rk3399-evb.dts | 1 -
1 file changed, 1 deletion(-)
diff --git a/arch/arm64/boot/dts/rockchip/rk3399-evb.dts b/arch/arm64/boot/dts/rockchip/rk3399-evb.dts
index af6e23568504..d4e402b40d08 100644
--- a/arch/arm64/boot/dts/rockchip/rk3399-evb.dts
+++ b/arch/arm64/boot/dts/rockchip/rk3399-evb.dts
@@ -48,7 +48,6 @@
240 241 242 243 244 245 246 247
248 249 250 251 252 253 254 255>;
default-brightness-level = <200>;
- enable-gpios = <&gpio1 RK_PB5 GPIO_ACTIVE_HIGH>;
pwms = <&pwm0 0 25000 0>;
};
--
2.17.1
next prev parent reply other threads:[~2020-03-05 11:39 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-03-05 11:39 [PATCH 0/4] Enable eDP display " Andy Yan
2020-03-05 11:39 ` [PATCH 1/4] arm64: dts: rockchip: remove dvs2 pinctrl for pmic " Andy Yan
2020-03-05 21:38 ` Heiko Stübner
2020-03-05 11:39 ` [PATCH 2/4] arm64: dts: rockchip: Add pmic dt tree for " Andy Yan
2020-03-05 23:46 ` Heiko Stuebner
2020-03-05 11:39 ` Andy Yan [this message]
2020-03-05 23:50 ` [PATCH 3/4] arm64: dts: rockchip: remove enable-gpio of backlight on " Heiko Stuebner
2020-03-05 11:39 ` [PATCH 4/4] arm64: dts: rockchip: Enable eDP display " Andy Yan
2020-03-05 23:51 ` Heiko Stuebner
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=20200305113912.32226-4-andy.yan@rock-chips.com \
--to=andy.yan@rock-chips.com \
--cc=devicetree@vger.kernel.org \
--cc=heiko@sntech.de \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-rockchip@lists.infradead.org \
--cc=robh+dt@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
all inboxes | Powered by JetHome®