From: Sergei Shtylyov <sergei.shtylyov@cogentembedded.com>
To: horms@verge.net.au, linux-renesas-soc@vger.kernel.org,
robh+dt@kernel.org, mark.rutland@arm.com,
devicetree@vger.kernel.org
Cc: linux@arm.linux.org.uk, magnus.damm@gmail.com,
linux-arm-kernel@lists.infradead.org
Subject: [PATCH 3/3] ARM: dts: blanche: add Ethernet pins
Date: Fri, 01 Jul 2016 02:08:55 +0300 [thread overview]
Message-ID: <3303208.PZCWAdujda@wasted.cogentembedded.com> (raw)
In-Reply-To: <2144803.0K8qXzjIFq@wasted.cogentembedded.com>
Add the (previously omitted) pin data for the SMSC LAN89218 Ethernet chip
to the Blanche board's device tree: the chip's IRQ output is connected to
the SoC's IRQ0 pin and its nCS input is connected to the SoC's EX_CS0# pin.
Signed-off-by: Sergei Shtylyov <sergei.shtylyov@cogentembedded.com>
---
arch/arm/boot/dts/r8a7792-blanche.dts | 15 +++++++++++++++
1 file changed, 15 insertions(+)
Index: renesas/arch/arm/boot/dts/r8a7792-blanche.dts
===================================================================
--- renesas.orig/arch/arm/boot/dts/r8a7792-blanche.dts
+++ renesas/arch/arm/boot/dts/r8a7792-blanche.dts
@@ -50,6 +50,9 @@
reg-io-width = <4>;
vddvario-supply = <&d3_3v>;
vdd33a-supply = <&d3_3v>;
+
+ pinctrl-0 = <&lan89218_pins>;
+ pinctrl-names = "default";
};
};
@@ -67,6 +70,18 @@
groups = "scif3_data";
function = "scif3";
};
+
+ lan89218_pins: lan89218 {
+ intc {
+ groups = "intc_irq0";
+ function = "intc";
+ };
+ lbsc {
+ groups = "lbsc_ex_cs0";
+ function = "lbsc";
+ };
+ };
+
};
&scif0 {
prev parent reply other threads:[~2016-06-30 23:08 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-06-30 23:05 [PATCH 0/3] Add R8A7792/Blanche PFC support Sergei Shtylyov
2016-06-30 23:06 ` [PATCH 1/3] ARM: dts: r8a7792: add " Sergei Shtylyov
2016-07-01 8:07 ` Geert Uytterhoeven
2016-07-02 17:07 ` Sergei Shtylyov
2016-06-30 23:08 ` [PATCH 2/3] ARM: dts: blanche: add SCIF0/3 pins Sergei Shtylyov
2016-07-01 8:10 ` Geert Uytterhoeven
2016-06-30 23:08 ` Sergei Shtylyov [this message]
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=3303208.PZCWAdujda@wasted.cogentembedded.com \
--to=sergei.shtylyov@cogentembedded.com \
--cc=devicetree@vger.kernel.org \
--cc=horms@verge.net.au \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-renesas-soc@vger.kernel.org \
--cc=linux@arm.linux.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).