From: Fabrizio Castro <fabrizio.castro@bp.renesas.com>
To: Rob Herring <robh+dt@kernel.org>,
Mark Rutland <mark.rutland@arm.com>,
Russell King <linux@armlinux.org.uk>
Cc: Simon Horman <horms@verge.net.au>,
Magnus Damm <magnus.damm@gmail.com>,
Geert Uytterhoeven <geert@linux-m68k.org>,
devicetree@vger.kernel.org, linux-arm-kernel@lists.infradead.org,
linux-renesas-soc@vger.kernel.org,
Chris Paterson <Chris.Paterson2@renesas.com>,
Biju Das <biju.das@bp.renesas.com>,
Fabrizio Castro <fabrizio.castro@bp.renesas.com>,
Chris Paterson <chris.paterson2@renesas.com>
Subject: [PATCH 2/4] ARM: dts: iwg22d: Add /dev/ttySC5 support
Date: Fri, 13 Oct 2017 14:03:14 +0100 [thread overview]
Message-ID: <1507899796-7941-3-git-send-email-fabrizio.castro@bp.renesas.com> (raw)
In-Reply-To: <1507899796-7941-1-git-send-email-fabrizio.castro@bp.renesas.com>
Signed-off-by: Fabrizio Castro <fabrizio.castro@bp.renesas.com>
Signed-off-by: Chris Paterson <chris.paterson2@renesas.com>
---
arch/arm/boot/dts/r8a7745-iwg22d-sodimm.dts | 14 ++++++++++++++
1 file changed, 14 insertions(+)
diff --git a/arch/arm/boot/dts/r8a7745-iwg22d-sodimm.dts b/arch/arm/boot/dts/r8a7745-iwg22d-sodimm.dts
index edda4f1..5d5bb2f 100644
--- a/arch/arm/boot/dts/r8a7745-iwg22d-sodimm.dts
+++ b/arch/arm/boot/dts/r8a7745-iwg22d-sodimm.dts
@@ -17,6 +17,7 @@
aliases {
serial3 = &scif4;
+ serial5 = &hscif1;
ethernet0 = &avb;
};
@@ -39,7 +40,20 @@
};
};
+&hscif1 {
+ pinctrl-0 = <&hscif1_pins>;
+ pinctrl-names = "default";
+
+ uart-has-rtscts;
+ status = "okay";
+};
+
&pfc {
+ hscif1_pins: hscif1 {
+ groups = "hscif1_data", "hscif1_ctrl";
+ function = "hscif1";
+ };
+
scif4_pins: scif4 {
groups = "scif4_data_b";
function = "scif4";
--
2.7.4
next prev parent reply other threads:[~2017-10-13 13:03 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-10-13 13:03 [PATCH 0/4] ARM: dts: iwg22d: DT architecture rework and UART Fabrizio Castro
2017-10-13 13:03 ` [PATCH 1/4] ARM: dts: iwg22d: Use /dev/ttySC3 as debug console Fabrizio Castro
2017-10-16 8:34 ` Biju Das
[not found] ` <KL1PR06MB1702D289BE9642F285CF9ED1B84F0-k6wCOA2IOKSx7cDWSRonpW0DtJ1/0DrXvxpqHgZTriW3zl9H0oFU5g@public.gmane.org>
2017-10-17 7:59 ` Simon Horman
2017-10-23 11:01 ` Fabrizio Castro
2017-10-13 13:03 ` Fabrizio Castro [this message]
2017-10-17 7:57 ` [PATCH 2/4] ARM: dts: iwg22d: Add /dev/ttySC5 support Simon Horman
2017-10-23 11:04 ` Fabrizio Castro
[not found] ` <1507899796-7941-1-git-send-email-fabrizio.castro-kTT6dE0pTRh9uiUsa/gSgQ@public.gmane.org>
2017-10-13 13:03 ` [PATCH 3/4] ARM: dts: iwg22d-sodimm-dbhd-ca: Add device tree for HDMI DB Fabrizio Castro
2017-10-17 8:02 ` Simon Horman
2017-10-23 11:11 ` Fabrizio Castro
2017-10-13 13:03 ` [PATCH 4/4] ARM: dts: iwg22d-sodimm: sort dt nodes Fabrizio Castro
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=1507899796-7941-3-git-send-email-fabrizio.castro@bp.renesas.com \
--to=fabrizio.castro@bp.renesas.com \
--cc=Chris.Paterson2@renesas.com \
--cc=biju.das@bp.renesas.com \
--cc=devicetree@vger.kernel.org \
--cc=geert@linux-m68k.org \
--cc=horms@verge.net.au \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-renesas-soc@vger.kernel.org \
--cc=linux@armlinux.org.uk \
--cc=magnus.damm@gmail.com \
--cc=mark.rutland@arm.com \
--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;
as well as URLs for NNTP newsgroup(s).