summaryrefslogtreecommitdiff
path: root/drivers/ddr/imx/imx8m/ddrphy_train.c
diff options
context:
space:
mode:
authorVladimir Oltean <vladimir.oltean@nxp.com>2021-06-29 20:53:16 +0300
committerRamon Fried <rfried.dev@gmail.com>2021-07-06 05:22:41 +0300
commit71346a84860c67827ef4852bc1c0ad31ac3f46ed (patch)
tree15f96683272227f097041eb37287bab5d0fc0f98 /drivers/ddr/imx/imx8m/ddrphy_train.c
parentcd8817ac73bab6fd352b93bbd675cc50083f241d (diff)
net: enetc: force the RGMII MAC speed/duplex instead of using in-band signaling
The RGMII spec supports optional in-band status reporting for the speed and duplex negotiated on the copper side, and the ENETC driver enables this feature by default. However, this does not work when the PHY does not implement the in-band reporting, or when there is a MAC-to-MAC connection described using a fixed-link. In that case, it would be better to disable the feature in the ENETC MAC and always force the speed and duplex to the values that were negotiated and retrieved over MDIO once the autoneg is finished. Since this works always, we just do it unconditionally and drop the in-band code. Note that because we need to wait for the autoneg to complete, we need to move enetc_setup_mac_iface() after phy_startup() returns, and then pass the phydev pointer all the way to enetc_init_rgmii(). The same considerations have led to a similar Linux driver patch as well: https://git.kernel.org/pub/scm/linux/kernel/git/netdev/net-next.git/commit/?id=c76a97218dcbb2cb7cec1404ace43ef96c87d874 Signed-off-by: Vladimir Oltean <vladimir.oltean@nxp.com> Reviewed-by: Ramon Fried <rfried.dev@gmail.com>
Diffstat (limited to 'drivers/ddr/imx/imx8m/ddrphy_train.c')
0 files changed, 0 insertions, 0 deletions