linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: jorik@kippendief.biz
To: wens@csie.org, maxime.ripard@free-electrons.com
Cc: mark.rutland@arm.com, robh+dt@kernel.org,
	devicetree@vger.kernel.org, linux-arm-kernel@lists.infradead.org,
	linux-kernel@vger.kernel.org, Jorik Jonker <jorik@kippendief.biz>
Subject: [PATCH v4 5/8] dts: sun8i-h3: add pinmux definitions for UART2-3
Date: Wed,  7 Sep 2016 09:58:58 +0200	[thread overview]
Message-ID: <1473235141-12768-6-git-send-email-jorik@kippendief.biz> (raw)
In-Reply-To: <1473235141-12768-1-git-send-email-jorik@kippendief.biz>

From: Jorik Jonker <jorik@kippendief.biz>

These are the pinmux definitions for uarts2-3 on H3. These are the only
pins for these UARTS, but one could choose to use reduce them to only
RX/TX.

Signed-off-by: Jorik Jonker <jorik@kippendief.biz>
---
 arch/arm/boot/dts/sun8i-h3.dtsi | 14 ++++++++++++++
 1 file changed, 14 insertions(+)

diff --git a/arch/arm/boot/dts/sun8i-h3.dtsi b/arch/arm/boot/dts/sun8i-h3.dtsi
index 685755c..5cde54c 100644
--- a/arch/arm/boot/dts/sun8i-h3.dtsi
+++ b/arch/arm/boot/dts/sun8i-h3.dtsi
@@ -373,6 +373,20 @@
 				allwinner,drive = <SUN4I_PINCTRL_10_MA>;
 				allwinner,pull = <SUN4I_PINCTRL_NO_PULL>;
 			};
+
+			uart2_rts_cts_pins: uart2_rts_cts {
+				allwinner,pins = "PA0", "PA1", "PA2", "PA3";
+				allwinner,function = "uart2";
+				allwinner,drive = <SUN4I_PINCTRL_10_MA>;
+				allwinner,pull = <SUN4I_PINCTRL_NO_PULL>;
+			};
+
+			uart3_rts_cts_pins: uart3_rts_cts {
+				allwinner,pins = "PA13", "PA14", "PA15", "PA16";
+				allwinner,function = "uart3";
+				allwinner,drive = <SUN4I_PINCTRL_10_MA>;
+				allwinner,pull = <SUN4I_PINCTRL_NO_PULL>;
+			};
 		};
 
 		timer@01c20c00 {
-- 
2.7.4

  parent reply	other threads:[~2016-09-07  8:00 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-09-07  7:58 [PATCH v4 0/8] dts: sun8i-h3: complete UART I2C definitions for H3 jorik
2016-09-07  7:58 ` [PATCH v4 1/8] dts: sun8i-h3: drop _a and address suffix from uart0 pinmux jorik
2016-09-08  6:17   ` Maxime Ripard
2016-09-07  7:58 ` [PATCH v4 2/8] dts: sun8i-h3: clarify uart1 pinmux definition name jorik
2016-09-08  6:18   ` Maxime Ripard
2016-09-07  7:58 ` [PATCH v4 3/8] dts: sun8i-h3: move uart0 pinmux/peripheral assocation to DSTI jorik
2016-09-08  6:22   ` Maxime Ripard
2016-09-07  7:58 ` [PATCH v4 4/8] dts: sun8i-h3: move uart1 " jorik
2016-09-07  8:54   ` Chen-Yu Tsai
2016-09-08  6:23   ` Maxime Ripard
2016-09-08  8:02     ` Jorik Jonker
2016-09-08  9:01       ` Maxime Ripard
2016-09-08  9:51         ` Jorik Jonker
2016-09-12  9:47           ` Maxime Ripard
2016-09-07  7:58 ` jorik [this message]
2016-09-07  7:58 ` [PATCH v4 6/8] dts: sun8i-h3: associate pinmux/peripherals for UART2-3 jorik
2016-09-07  7:59 ` [PATCH v4 7/8] dts: sun8i-h3: add pinmux definitions for I2C0-2 jorik
2016-09-07  7:59 ` [PATCH v4 8/8] dts: sun8i-h3: add I2C0-2 peripherals to H3 SOC jorik

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=1473235141-12768-6-git-send-email-jorik@kippendief.biz \
    --to=jorik@kippendief.biz \
    --cc=devicetree@vger.kernel.org \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mark.rutland@arm.com \
    --cc=maxime.ripard@free-electrons.com \
    --cc=robh+dt@kernel.org \
    --cc=wens@csie.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).