From: Sergei Shtylyov <sergei.shtylyov@cogentembedded.com>
To: Simon Horman <horms@verge.net.au>,
Rob Herring <robh+dt@kernel.org>,
linux-renesas-soc@vger.kernel.org, devicetree@vger.kernel.org
Cc: Magnus Damm <magnus.damm@gmail.com>, Mark Rutland <mark.rutland@arm.com>
Subject: [PATCH] arm64: dts: renesas: v3msk: specify EtherAVB PHY IRQ
Date: Tue, 8 Jan 2019 22:56:50 +0300 [thread overview]
Message-ID: <f9c6b067-80ba-c3c6-abcb-57d9524972fc@cogentembedded.com> (raw)
In-Reply-To: <038a791d-aa57-9c3d-eaea-09c5704ecb54@cogentembedded.com>
Specify EtherAVB PHY IRQ in the V3M Starter Kit board's device tree, now
that we have the GPIO support (previously phylib had to resort to polling).
Signed-off-by: Sergei Shtylyov <sergei.shtylyov@cogentembedded.com>
---
The patch is against the 'renesas-devel-20190107-v5.0-rc1' tag of Simon
Horman's 'renesas.git' repo...
arch/arm64/boot/dts/renesas/r8a77970-v3msk.dts | 2 ++
1 file changed, 2 insertions(+)
Index: renesas/arch/arm64/boot/dts/renesas/r8a77970-v3msk.dts
===================================================================
--- renesas.orig/arch/arm64/boot/dts/renesas/r8a77970-v3msk.dts
+++ renesas/arch/arm64/boot/dts/renesas/r8a77970-v3msk.dts
@@ -108,6 +108,8 @@
phy0: ethernet-phy@0 {
rxc-skew-ps = <1500>;
reg = <0>;
+ interrupt-parent = <&gpio1>;
+ interrupts = <17 IRQ_TYPE_LEVEL_LOW>;
};
};
next prev parent reply other threads:[~2019-01-08 19:56 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-02-13 11:18 [PATCH v2 0/2] Add R8A77970/Eagle GPIO support Sergei Shtylyov
[not found] ` <038a791d-aa57-9c3d-eaea-09c5704ecb54-M4DtvfQ/ZS1MRgGoP+s0PdBPR1lH4CV8@public.gmane.org>
2018-02-13 11:22 ` [PATCH v2 1/2] arm64: dts: renesas: r8a77970: add " Sergei Shtylyov
[not found] ` <85e2d81e-3de9-4f61-ad8f-e0a0ec8381bc-M4DtvfQ/ZS1MRgGoP+s0PdBPR1lH4CV8@public.gmane.org>
2018-02-14 10:01 ` Geert Uytterhoeven
2018-02-15 15:13 ` Simon Horman
2018-02-13 11:24 ` [PATCH v2 2/2] arm64: dts: renesas: eagle: specify EtherAVB PHY IRQ Sergei Shtylyov
[not found] ` <0ccd631e-691a-2b15-7680-6e0c847a6ca2-M4DtvfQ/ZS1MRgGoP+s0PdBPR1lH4CV8@public.gmane.org>
2018-02-14 10:02 ` Geert Uytterhoeven
2018-02-15 8:51 ` Sergei Shtylyov
2018-02-15 15:16 ` Simon Horman
2019-01-08 19:56 ` Sergei Shtylyov [this message]
2019-01-09 8:29 ` [PATCH] arm64: dts: renesas: v3msk: " Geert Uytterhoeven
2019-01-10 9:39 ` 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=f9c6b067-80ba-c3c6-abcb-57d9524972fc@cogentembedded.com \
--to=sergei.shtylyov@cogentembedded.com \
--cc=devicetree@vger.kernel.org \
--cc=horms@verge.net.au \
--cc=linux-renesas-soc@vger.kernel.org \
--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).