[lkml]   [2018]   [Feb]   [26]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
Messages in this thread
Subject[PATCH 0/8] R-Car M3-N: Enable EtherAVB device node
Hi Simon,
as discussed with you Sergei and Geert, in order to enable EtherAVB for
R8A77965 we first wanted to make the phy-mode "rgmii-txid" a board specific
property for all other SoCs.

This series adds the phy-mode property to salvator-common.dtsi and reset the
one for R8A77965/R8A7796/R8A77995 to "rgmii".

Then, in order to enable EtherAVB for R-Car M3-N, iommu nodes had to be added
as they are referenced by the "avb" device node (CC the iommu list for the
series for that reason).

Series based on what you already applied to your development tree (M3-N initial
support - EtherAVB + DTS fixes). A branch for testing is available at

git:// m3-n/renesas-drivers-2018-02-13-v4.16-rc1/v2-simon


Jacopo Mondi (8):
arm64: dts: renesas: salvator-common: Override EtherAVB phy-mode
arm64: dts: renesas: r8a7796: Set EtherAVB phy mode to "rgmii"
arm64: dts: renesas: r8a7795: Set EtherAVB phy mode to "rgmii"
arm64: dts: renesas: r8a77995: Set EtherAVB phy mode to "rgmii"
dt-bindings: iommu/ipmmu-vmsa: Add R-Car M3-N (R8A77965)
iommu/ipmmu-vmsa: Hook up R8A77965 DT matching code
arm64: dts: renesas: r8a77965: Add IPMMU mm and ds0 blocks
arm64: dts: renesas: r8a77965: Add EtherAVB device node

.../bindings/iommu/renesas,ipmmu-vmsa.txt | 1 +
arch/arm64/boot/dts/renesas/r8a7795.dtsi | 2 +-
arch/arm64/boot/dts/renesas/r8a7796.dtsi | 2 +-
arch/arm64/boot/dts/renesas/r8a77965.dtsi | 61 ++++++++++++++++++++--
arch/arm64/boot/dts/renesas/r8a77995.dtsi | 2 +-
arch/arm64/boot/dts/renesas/salvator-common.dtsi | 1 +
drivers/iommu/ipmmu-vmsa.c | 5 ++
7 files changed, 68 insertions(+), 6 deletions(-)


 \ /
  Last update: 2018-02-26 19:01    [W:0.148 / U:1.516 seconds]
©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site