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: magnus.damm@gmail.com, linux@arm.linux.org.uk,
linux-arm-kernel@lists.infradead.org
Subject: [PATCH v4 7/7] ARM: dts: sk-rzg1m: add Ether support
Date: Fri, 21 Oct 2016 23:48:58 +0300 [thread overview]
Message-ID: <1646335.vYatMAFDPt@wasted.cogentembedded.com> (raw)
In-Reply-To: <2719479.geOc9vqcRS@wasted.cogentembedded.com>
Define the SK-RZG1M board dependent part of the Ether device node.
Enable DHCP and NFS root for the kernel booting.
Based on the original (and large) patch by Dmitry Shifrin
<dmitry.shifrin@cogentembedded.com>.
Signed-off-by: Sergei Shtylyov <sergei.shtylyov@cogentembedded.com>
Reviewed-by: Geert Uytterhoeven <geert+renesas@glider.be>
---
Changes in version 4:
- added Geert's tag.
Changes in version 2:
- new patch.
arch/arm/boot/dts/r8a7743-sk-rzg1m.dts | 15 ++++++++++++++-
1 file changed, 14 insertions(+), 1 deletion(-)
Index: renesas/arch/arm/boot/dts/r8a7743-sk-rzg1m.dts
===================================================================
--- renesas.orig/arch/arm/boot/dts/r8a7743-sk-rzg1m.dts
+++ renesas/arch/arm/boot/dts/r8a7743-sk-rzg1m.dts
@@ -20,7 +20,7 @@
};
chosen {
- bootargs = "ignore_loglevel";
+ bootargs = "ignore_loglevel rw root=/dev/nfs ip=dhcp";
stdout-path = "serial0:115200n8";
};
@@ -42,3 +42,16 @@
&scif0 {
status = "okay";
};
+
+ðer {
+ phy-handle = <&phy1>;
+ renesas,ether-link-active-low;
+ status = "okay";
+
+ phy1: ethernet-phy@1 {
+ reg = <1>;
+ interrupt-parent = <&irqc>;
+ interrupts = <0 IRQ_TYPE_LEVEL_LOW>;
+ micrel,led-mode = <1>;
+ };
+};
next prev parent reply other threads:[~2016-10-21 20:48 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-10-21 20:39 [PATCH v4 0/7] Add R8A7743/SK-RZG1M board support Sergei Shtylyov
[not found] ` <2719479.geOc9vqcRS-gHKXc3Y1Z8zGSmamagVegGFoWSdPRAKMAL8bYrjMMd8@public.gmane.org>
2016-10-21 20:40 ` [PATCH v4 1/7] ARM: dts: r8a7743: initial SoC device tree Sergei Shtylyov
2016-10-21 20:41 ` [PATCH v4 2/7] ARM: dts: r8a7743: add SYS-DMAC support Sergei Shtylyov
2016-10-21 20:42 ` [PATCH v4 3/7] ARM: dts: r8a7743: add [H]SCIF{|A|B} support Sergei Shtylyov
2016-10-21 20:46 ` [PATCH v4 5/7] ARM: dts: r8a7743: add IRQC support Sergei Shtylyov
2016-10-21 20:47 ` [PATCH v4 6/7] ARM: dts: sk-rzg1m: initial device tree Sergei Shtylyov
2016-10-21 20:45 ` [PATCH v4 4/7] ARM: dts: r8a7743: add Ether support Sergei Shtylyov
2016-10-21 20:48 ` Sergei Shtylyov [this message]
2016-10-26 12:08 ` [PATCH v4 0/7] Add R8A7743/SK-RZG1M board support Geert Uytterhoeven
[not found] ` <CAMuHMdUNgnYc1O7DATNH1r9SQ72eqtxwFvqcen08Tq+Er3LuvQ-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2016-10-26 13:23 ` Sergei Shtylyov
2016-10-26 13:27 ` Geert Uytterhoeven
[not found] ` <CAMuHMdWQegsEf_C=UGXpQiEAX0YQqy335teuvCZxBY6C=7QozA-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2016-10-27 7:06 ` Simon Horman
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=1646335.vYatMAFDPt@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).