summaryrefslogtreecommitdiff
path: root/arch/arm64/boot/dts/renesas/r8a77970.dtsi
diff options
context:
space:
mode:
authorSergei Shtylyov <sergei.shtylyov@cogentembedded.com>2018-05-11 23:21:57 +0300
committerSimon Horman <horms+renesas@verge.net.au>2018-05-16 11:47:15 +0300
commit9223eef03f2659bd9650c2bc4364b1748e62eade (patch)
tree7212e5799f3d94269fe8150f6982dacca762d724 /arch/arm64/boot/dts/renesas/r8a77970.dtsi
parentd86bd47fefbb6e4db53d733fe95bc13bc9ddedb1 (diff)
downloadlinux-9223eef03f2659bd9650c2bc4364b1748e62eade.tar.xz
arm64: dts: renesas: r8a77970: disable EtherAVB
When adding the R8A77970 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: bea2ab136eaa ("arm64: dts: renesas: r8a77970: 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/boot/dts/renesas/r8a77970.dtsi')
-rw-r--r--arch/arm64/boot/dts/renesas/r8a77970.dtsi1
1 files changed, 1 insertions, 0 deletions
diff --git a/arch/arm64/boot/dts/renesas/r8a77970.dtsi b/arch/arm64/boot/dts/renesas/r8a77970.dtsi
index 50046405d348..c8464d1ef1b2 100644
--- a/arch/arm64/boot/dts/renesas/r8a77970.dtsi
+++ b/arch/arm64/boot/dts/renesas/r8a77970.dtsi
@@ -473,6 +473,7 @@
iommus = <&ipmmu_rt 3>;
#address-cells = <1>;
#size-cells = <0>;
+ status = "disabled";
};
scif0: serial@e6e60000 {