From: megous@megous.com
To: maxime.ripard@free-electrons.com, wens@csie.org, robh@kernel.org,
johan@kernel.org, mark.rutland@arm.com
Cc: Ondrej Jirman <megous@megous.com>,
devicetree@vger.kernel.org, linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org, linux-sunxi@googlegroups.com
Subject: [PATCH 3/7] ARM: dts: sun8i: a83t: Add nodes for UART2-UART4
Date: Wed, 27 Mar 2019 01:18:39 +0100 [thread overview]
Message-ID: <20190327001843.2420-4-megous@megous.com> (raw)
In-Reply-To: <20190327001843.2420-1-megous@megous.com>
From: Ondrej Jirman <megous@megous.com>
A83T has 5 UART interfaces, but only the first two have their nodes
defined in sun8i-a83t.dtsi. Add nodes for the missing interfaces.
Signed-off-by: Ondrej Jirman <megous@megous.com>
---
arch/arm/boot/dts/sun8i-a83t.dtsi | 33 +++++++++++++++++++++++++++++++
1 file changed, 33 insertions(+)
diff --git a/arch/arm/boot/dts/sun8i-a83t.dtsi b/arch/arm/boot/dts/sun8i-a83t.dtsi
index fcb7ef5ce2df..e5c39eef1c29 100644
--- a/arch/arm/boot/dts/sun8i-a83t.dtsi
+++ b/arch/arm/boot/dts/sun8i-a83t.dtsi
@@ -873,6 +873,39 @@
status = "disabled";
};
+ uart2: serial@1c28800 {
+ compatible = "snps,dw-apb-uart";
+ reg = <0x01c28800 0x400>;
+ interrupts = <GIC_SPI 2 IRQ_TYPE_LEVEL_HIGH>;
+ reg-shift = <2>;
+ reg-io-width = <4>;
+ clocks = <&ccu CLK_BUS_UART2>;
+ resets = <&ccu RST_BUS_UART2>;
+ status = "disabled";
+ };
+
+ uart3: serial@1c28c00 {
+ compatible = "snps,dw-apb-uart";
+ reg = <0x01c28c00 0x400>;
+ interrupts = <GIC_SPI 3 IRQ_TYPE_LEVEL_HIGH>;
+ reg-shift = <2>;
+ reg-io-width = <4>;
+ clocks = <&ccu CLK_BUS_UART3>;
+ resets = <&ccu RST_BUS_UART3>;
+ status = "disabled";
+ };
+
+ uart4: serial@1c29000 {
+ compatible = "snps,dw-apb-uart";
+ reg = <0x01c29000 0x400>;
+ interrupts = <GIC_SPI 4 IRQ_TYPE_LEVEL_HIGH>;
+ reg-shift = <2>;
+ reg-io-width = <4>;
+ clocks = <&ccu CLK_BUS_UART4>;
+ resets = <&ccu RST_BUS_UART4>;
+ status = "disabled";
+ };
+
i2c0: i2c@1c2ac00 {
compatible = "allwinner,sun8i-a83t-i2c",
"allwinner,sun6i-a31-i2c";
--
2.21.0
next prev parent reply other threads:[~2019-03-27 0:27 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-03-27 0:18 [PATCH 0/7] Add bluetooth, gps and accelerometer to TBS A711 megous
2019-03-27 0:18 ` [PATCH 1/7] ARM: dts: sun8i: tbs-a711: Enable bluetooth megous
2019-04-01 8:00 ` Maxime Ripard
2019-03-27 0:18 ` [PATCH 2/7] ARM: dts: sun8i: tbs-a711: Add node for BMA250 accelerometer megous
2019-04-01 6:30 ` Maxime Ripard
2019-04-01 11:34 ` Ondřej Jirman
2019-03-27 0:18 ` megous [this message]
2019-04-01 8:00 ` [PATCH 3/7] ARM: dts: sun8i: a83t: Add nodes for UART2-UART4 Maxime Ripard
2019-03-27 0:18 ` [PATCH 4/7] ARM: dts: sun8i: a83t: Add UART2 PB pins megous
2019-03-28 8:01 ` [linux-sunxi] " Chen-Yu Tsai
2019-03-27 0:18 ` [PATCH 5/7] gnss: Add u-blox,neo-6m compatible megous
2019-03-27 0:18 ` [PATCH 6/7] dt-bindings: " megous
2019-03-31 6:42 ` Rob Herring
2019-03-27 0:18 ` [PATCH 7/7] ARM: dts: sun8i: tbs-a711: Enable UART2 (for NEO-6M GPS module) megous
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=20190327001843.2420-4-megous@megous.com \
--to=megous@megous.com \
--cc=devicetree@vger.kernel.org \
--cc=johan@kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-sunxi@googlegroups.com \
--cc=mark.rutland@arm.com \
--cc=maxime.ripard@free-electrons.com \
--cc=robh@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).