On 11/15/2017 11:21 PM, Sergei Shtylyov wrote:
Add the (previously omitted) EtherAVB pin data to the Eagle board's
device tree.
--- renesas.orig/arch/arm64/boot/dts/renesas/r8a77970-eagle.dts
+++ renesas/arch/arm64/boot/dts/renesas/r8a77970-eagle.dts
@@ -34,6 +34,9 @@
[...]
@@ -53,6 +56,11 @@
};
&pfc {
+ avb_pins: avb {
+ groups = "avb0_mdio", "avb0_mii";
Oh no, its'called "avb0_mdio" here, but "avb(0)_mdc" on all other
R-Car Gen3 SoCs?
Can you remember the reason? I don;t want to follow the bad example. :-)
Sorry, I don't know.
Hm, you seem to have participated in the related discussions for H2/M3-W...
H3, of course...
The reason was that omlu AVB_MDC signal was multiplexed, AVB_MDIO signal (and
s/omlu/only/.
AVB MII signals) was mapped to a dedicated pin without any multiplexing, so
the "avb_mdc" group initially contained only AVB_MDC.
Gr{oetje,eeting}s,
MBR, Sergei
--
To unsubscribe from this list: send the line "unsubscribe devicetree" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
