summaryrefslogtreecommitdiff
path: root/drivers/ddr/marvell/a38x/old/ddr3_training.c
diff options
context:
space:
mode:
authorMarek BehĂșn <kabel@kernel.org>2024-06-18 17:34:30 +0200
committerStefan Roese <sr@denx.de>2024-07-08 08:20:58 +0200
commit1a05180762ea1603a605f868bc0523ae2d36016f (patch)
tree2114d906f0b2b0bb618f3d2580488c54e92aef45 /drivers/ddr/marvell/a38x/old/ddr3_training.c
parent529d24002b6cefb88cd00cef307b8752dbeebfc4 (diff)
arm: mvebu: turris_omnia: Fix ethernet PHY reset gpio FDT fixup
For board revisions where the WAN ethernet PHY reset GPIO is controllable via MCU we currently insert a phy-reset-gpios property into the ethernet controller node. The mvneta driver parses this property and uses the GPIO to reset the PHY. But this phy-reset-gpios property is not a valid DT binding in upstream kernel. Instead, a reset-gpios property should be inserted into the ethernet PHY node. This correct DT binding is supported by the DM ETH PHY U-Boot driver. Insert the reset-gpios property into the WAN PHY node instead the phy-reset-gpios property in WAN ETH node so that Linux will correctly use the reset GPIO. Enable the CONFIG_DM_ETH_PHY config option so that U-Boot will also use the correct DT property. Note: currently there are 4 ethernet controller drivers parsing the wrong DT property: dwc_eth_qos, fex_mxc, mvneta and mvpp2. We should convert all relevant device-trees to use reset-gpios so that we can get rid of these drivers parsing this property. Fixes: 1da53ae26afc ("arm: mvebu: turris_omnia: Add support for design with SW reset signals") Signed-off-by: Marek BehĂșn <kabel@kernel.org>
Diffstat (limited to 'drivers/ddr/marvell/a38x/old/ddr3_training.c')
0 files changed, 0 insertions, 0 deletions