summaryrefslogtreecommitdiffstats
path: root/arch/arm64
diff options
context:
space:
mode:
authorSergei Shtylyov <sergei.shtylyov@cogentembedded.com>2018-05-11 23:23:26 +0300
committerSimon Horman <horms+renesas@verge.net.au>2018-05-16 10:47:15 +0200
commit52d2e0cec73e61123860230d6d034cd07775dd78 (patch)
tree869bd1a9e6c3a71fa4998f9431c6305ad98c30d7 /arch/arm64
parent9223eef03f2659bd9650c2bc4364b1748e62eade (diff)
downloadop-kernel-dev-52d2e0cec73e61123860230d6d034cd07775dd78.zip
op-kernel-dev-52d2e0cec73e61123860230d6d034cd07775dd78.tar.gz
arm64: dts: renesas: r8a77980: disable EtherAVB
When adding the R8A77980 EtherAVB device I failed to notice that it does not have the usual "status" property disabling the described devices in anticipation that the board device trees enable the devices according to their needs. This causes the EtherAVB driver to successfully probe despite e.g. the needed pins not having been configured -- luckily, "eth<n>" device can't be opened anyway... Fixes: bf6f90832f81 ("arm64: dts: renesas: r8a77980: add EtherAVB support") Signed-off-by: Sergei Shtylyov <sergei.shtylyov@cogentembedded.com> Signed-off-by: Simon Horman <horms+renesas@verge.net.au>
Diffstat (limited to 'arch/arm64')
-rw-r--r--arch/arm64/boot/dts/renesas/r8a77980.dtsi1
1 files changed, 1 insertions, 0 deletions
diff --git a/arch/arm64/boot/dts/renesas/r8a77980.dtsi b/arch/arm64/boot/dts/renesas/r8a77980.dtsi
index 32db26f..4c40f9f 100644
--- a/arch/arm64/boot/dts/renesas/r8a77980.dtsi
+++ b/arch/arm64/boot/dts/renesas/r8a77980.dtsi
@@ -244,6 +244,7 @@
phy-mode = "rgmii";
#address-cells = <1>;
#size-cells = <0>;
+ status = "disabled";
};
scif0: serial@e6e60000 {
OpenPOWER on IntegriCloud