U-Boot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Jagan Teki <jagan@amarulasolutions.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH v3 02/13] rockchip: dts: rk3399: Sync pwm2_pin_pull_down from Linux 5.1-rc2
Date: Thu, 25 Apr 2019 23:04:16 +0530	[thread overview]
Message-ID: <20190425173427.13445-3-jagan@amarulasolutions.com> (raw)
In-Reply-To: <20190425173427.13445-1-jagan@amarulasolutions.com>

To make successful build with dts(i) files syncing from Linux 5.1-rc2
the rk3399.dtsi would require pwm2_pin_pull_down.

So, sync the pwm2_pin_pull_down node from Linux 5.1-rc2.  Since this
node is strictly not part of any commit alone, I have mentioned
Linux 5.1-rc2 tag for future reference of where would this sync
coming from.

Signed-off-by: Jagan Teki <jagan@amarulasolutions.com>
Reviewed-by: Paul Kocialkowski <paul.kocialkowski@bootlin.com>
---
 arch/arm/dts/rk3399.dtsi | 6 ++++++
 1 file changed, 6 insertions(+)

diff --git a/arch/arm/dts/rk3399.dtsi b/arch/arm/dts/rk3399.dtsi
index b53e41b4dc..99471f6287 100644
--- a/arch/arm/dts/rk3399.dtsi
+++ b/arch/arm/dts/rk3399.dtsi
@@ -2495,6 +2495,12 @@
 				rockchip,pins =
 					<1 RK_PC3 RK_FUNC_1 &pcfg_pull_none>;
 			};
+
+
+			pwm2_pin_pull_down: pwm2-pin-pull-down {
+				rockchip,pins =
+					<1 RK_PC3 RK_FUNC_1 &pcfg_pull_down>;
+			};
 		};
 
 		pwm3a {
-- 
2.18.0.321.gffc6fa0e3

  parent reply	other threads:[~2019-04-25 17:34 UTC|newest]

Thread overview: 36+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-04-25 17:34 [U-Boot] [PATCH v3 00/13] rockchip: Add new rk3399 boards Jagan Teki
2019-04-25 17:34 ` [U-Boot] [PATCH v3 01/13] rockchip: dts: rk3399: Sync rk3399-opp from Linux Jagan Teki
2019-04-25 17:34 ` Jagan Teki [this message]
2019-04-25 17:34 ` [U-Boot] [PATCH v3 03/13] rockchip: dts: rk3399: Create initial rk3399-u-boot.dtsi Jagan Teki
2019-04-26 13:21   ` Jagan Teki
2019-04-26 13:33     ` Paul Kocialkowski
2019-04-25 17:34 ` [U-Boot] [PATCH v3 04/13] Kconfig: Add default SPL_FIT_GENERATOR for rockchip Jagan Teki
2019-04-25 17:34 ` [U-Boot] [PATCH v3 05/13] arm: rockchip: rk3399: Move common configs in Kconfig Jagan Teki
2019-04-25 17:34 ` [U-Boot] [PATCH v3 06/13] rockchip: rk3399: Add Orangepi RK3399 support Jagan Teki
2019-04-26 14:17   ` Paul Kocialkowski
2019-04-26 14:27     ` Jagan Teki
2019-04-26 14:34       ` Paul Kocialkowski
2019-04-26 14:45         ` Jagan Teki
2019-04-26 14:54           ` Paul Kocialkowski
2019-04-26 15:01             ` Jagan Teki
2019-04-26 15:12               ` Paul Kocialkowski
2019-04-26 15:18                 ` Jagan Teki
2019-04-26 15:38                   ` Paul Kocialkowski
2019-04-26 15:48                     ` Jagan Teki
2019-04-26 16:08                       ` Paul Kocialkowski
2019-04-26 16:09                         ` Philipp Tomsich
2019-04-26 16:16                         ` Jagan Teki
2019-04-26 16:40                           ` Paul Kocialkowski
2019-04-26 16:53                             ` Jagan Teki
2019-04-26 17:08                               ` Paul Kocialkowski
2019-04-26 17:21                                 ` Jagan Teki
2019-04-26 17:37                                   ` Paul Kocialkowski
2019-04-26 17:42                                     ` Jagan Teki
2019-04-26 18:02                                       ` Paul Kocialkowski
2019-04-25 17:34 ` [U-Boot] [PATCH v3 07/13] rockchip: dts: rk3399: Sync rk3399-nanopi4.dtsi from Linux Jagan Teki
2019-04-25 17:34 ` [U-Boot] [PATCH v3 08/13] rockchip: dts: rk3399: nanopi4: Use CD pin as RK_FUNC_1 Jagan Teki
2019-04-25 17:34 ` [U-Boot] [PATCH v3 09/13] rockchip: rk3399: Add Nanopi M4 board support Jagan Teki
2019-04-25 17:34 ` [U-Boot] [PATCH v3 10/13] rockchip: rk3399: Add Nanopi NEO4 " Jagan Teki
2019-04-25 17:34 ` [U-Boot] [PATCH v3 11/13] rockchip: rk3399: Add Rockpro64 " Jagan Teki
2019-04-25 17:34 ` [U-Boot] [PATCH v3 12/13] rockchip: rk3399: Add Rock PI 4 support Jagan Teki
2019-04-25 17:34 ` [U-Boot] [PATCH v3 13/13] doc: rockchip: Add global doc for rk3399 build/flash Jagan Teki

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=20190425173427.13445-3-jagan@amarulasolutions.com \
    --to=jagan@amarulasolutions.com \
    --cc=u-boot@lists.denx.de \
    /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