aboutsummaryrefslogtreecommitdiffstatshomepage
path: root/arch/arm64/boot/dts/renesas/r8a77980-v3hsk.dts
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/boot/dts/renesas/r8a77980-v3hsk.dts
parentarm64: dts: renesas: r8a77970: disable EtherAVB (diff)
downloadwireguard-linux-52d2e0cec73e61123860230d6d034cd07775dd78.tar.xz
wireguard-linux-52d2e0cec73e61123860230d6d034cd07775dd78.zip
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/boot/dts/renesas/r8a77980-v3hsk.dts')
0 files changed, 0 insertions, 0 deletions