Home
last modified time | relevance | path

Searched hist:"91 a208f2185ad4855ff03c342d0b7e4f5fc6f5df" (Results 1 – 11 of 11) sorted by relevance

/openbmc/linux/Documentation/networking/
H A Dsfp-phylink.rstdiff 91a208f2185ad4855ff03c342d0b7e4f5fc6f5df Wed Feb 26 04:23:41 CST 2020 Russell King <rmk+kernel@armlinux.org.uk> net: phylink: propagate resolved link config via mac_link_up()

Propagate the resolved link parameters via the mac_link_up() call for
MACs that do not automatically track their PCS state. We propagate the
link parameters via function arguments so that inappropriate members
of struct phylink_link_state can't be accessed, and creating a new
structure just for this adds needless complexity to the API.

Tested-by: Andre Przywara <andre.przywara@arm.com>
Tested-by: Alexandre Belloni <alexandre.belloni@bootlin.com>
Tested-by: Vladimir Oltean <vladimir.oltean@nxp.com>
Signed-off-by: Russell King <rmk+kernel@armlinux.org.uk>
Signed-off-by: David S. Miller <davem@davemloft.net>
/openbmc/linux/drivers/net/ethernet/freescale/dpaa2/
H A Ddpaa2-mac.cdiff 91a208f2185ad4855ff03c342d0b7e4f5fc6f5df Wed Feb 26 04:23:41 CST 2020 Russell King <rmk+kernel@armlinux.org.uk> net: phylink: propagate resolved link config via mac_link_up()

Propagate the resolved link parameters via the mac_link_up() call for
MACs that do not automatically track their PCS state. We propagate the
link parameters via function arguments so that inappropriate members
of struct phylink_link_state can't be accessed, and creating a new
structure just for this adds needless complexity to the API.

Tested-by: Andre Przywara <andre.przywara@arm.com>
Tested-by: Alexandre Belloni <alexandre.belloni@bootlin.com>
Tested-by: Vladimir Oltean <vladimir.oltean@nxp.com>
Signed-off-by: Russell King <rmk+kernel@armlinux.org.uk>
Signed-off-by: David S. Miller <davem@davemloft.net>
/openbmc/linux/include/linux/
H A Dphylink.hdiff 91a208f2185ad4855ff03c342d0b7e4f5fc6f5df Wed Feb 26 04:23:41 CST 2020 Russell King <rmk+kernel@armlinux.org.uk> net: phylink: propagate resolved link config via mac_link_up()

Propagate the resolved link parameters via the mac_link_up() call for
MACs that do not automatically track their PCS state. We propagate the
link parameters via function arguments so that inappropriate members
of struct phylink_link_state can't be accessed, and creating a new
structure just for this adds needless complexity to the API.

Tested-by: Andre Przywara <andre.przywara@arm.com>
Tested-by: Alexandre Belloni <alexandre.belloni@bootlin.com>
Tested-by: Vladimir Oltean <vladimir.oltean@nxp.com>
Signed-off-by: Russell King <rmk+kernel@armlinux.org.uk>
Signed-off-by: David S. Miller <davem@davemloft.net>
/openbmc/linux/net/dsa/
H A Dport.cdiff 91a208f2185ad4855ff03c342d0b7e4f5fc6f5df Wed Feb 26 04:23:41 CST 2020 Russell King <rmk+kernel@armlinux.org.uk> net: phylink: propagate resolved link config via mac_link_up()

Propagate the resolved link parameters via the mac_link_up() call for
MACs that do not automatically track their PCS state. We propagate the
link parameters via function arguments so that inappropriate members
of struct phylink_link_state can't be accessed, and creating a new
structure just for this adds needless complexity to the API.

Tested-by: Andre Przywara <andre.przywara@arm.com>
Tested-by: Alexandre Belloni <alexandre.belloni@bootlin.com>
Tested-by: Vladimir Oltean <vladimir.oltean@nxp.com>
Signed-off-by: Russell King <rmk+kernel@armlinux.org.uk>
Signed-off-by: David S. Miller <davem@davemloft.net>
/openbmc/linux/drivers/net/ethernet/marvell/mvpp2/
H A Dmvpp2_main.cdiff 91a208f2185ad4855ff03c342d0b7e4f5fc6f5df Wed Feb 26 04:23:41 CST 2020 Russell King <rmk+kernel@armlinux.org.uk> net: phylink: propagate resolved link config via mac_link_up()

Propagate the resolved link parameters via the mac_link_up() call for
MACs that do not automatically track their PCS state. We propagate the
link parameters via function arguments so that inappropriate members
of struct phylink_link_state can't be accessed, and creating a new
structure just for this adds needless complexity to the API.

Tested-by: Andre Przywara <andre.przywara@arm.com>
Tested-by: Alexandre Belloni <alexandre.belloni@bootlin.com>
Tested-by: Vladimir Oltean <vladimir.oltean@nxp.com>
Signed-off-by: Russell King <rmk+kernel@armlinux.org.uk>
Signed-off-by: David S. Miller <davem@davemloft.net>
/openbmc/linux/drivers/net/ethernet/xilinx/
H A Dxilinx_axienet_main.cdiff 91a208f2185ad4855ff03c342d0b7e4f5fc6f5df Wed Feb 26 04:23:41 CST 2020 Russell King <rmk+kernel@armlinux.org.uk> net: phylink: propagate resolved link config via mac_link_up()

Propagate the resolved link parameters via the mac_link_up() call for
MACs that do not automatically track their PCS state. We propagate the
link parameters via function arguments so that inappropriate members
of struct phylink_link_state can't be accessed, and creating a new
structure just for this adds needless complexity to the API.

Tested-by: Andre Przywara <andre.przywara@arm.com>
Tested-by: Alexandre Belloni <alexandre.belloni@bootlin.com>
Tested-by: Vladimir Oltean <vladimir.oltean@nxp.com>
Signed-off-by: Russell King <rmk+kernel@armlinux.org.uk>
Signed-off-by: David S. Miller <davem@davemloft.net>
/openbmc/linux/drivers/net/phy/
H A Dphylink.cdiff 91a208f2185ad4855ff03c342d0b7e4f5fc6f5df Wed Feb 26 04:23:41 CST 2020 Russell King <rmk+kernel@armlinux.org.uk> net: phylink: propagate resolved link config via mac_link_up()

Propagate the resolved link parameters via the mac_link_up() call for
MACs that do not automatically track their PCS state. We propagate the
link parameters via function arguments so that inappropriate members
of struct phylink_link_state can't be accessed, and creating a new
structure just for this adds needless complexity to the API.

Tested-by: Andre Przywara <andre.przywara@arm.com>
Tested-by: Alexandre Belloni <alexandre.belloni@bootlin.com>
Tested-by: Vladimir Oltean <vladimir.oltean@nxp.com>
Signed-off-by: Russell King <rmk+kernel@armlinux.org.uk>
Signed-off-by: David S. Miller <davem@davemloft.net>
/openbmc/linux/drivers/net/ethernet/mediatek/
H A Dmtk_eth_soc.cdiff 91a208f2185ad4855ff03c342d0b7e4f5fc6f5df Wed Feb 26 04:23:41 CST 2020 Russell King <rmk+kernel@armlinux.org.uk> net: phylink: propagate resolved link config via mac_link_up()

Propagate the resolved link parameters via the mac_link_up() call for
MACs that do not automatically track their PCS state. We propagate the
link parameters via function arguments so that inappropriate members
of struct phylink_link_state can't be accessed, and creating a new
structure just for this adds needless complexity to the API.

Tested-by: Andre Przywara <andre.przywara@arm.com>
Tested-by: Alexandre Belloni <alexandre.belloni@bootlin.com>
Tested-by: Vladimir Oltean <vladimir.oltean@nxp.com>
Signed-off-by: Russell King <rmk+kernel@armlinux.org.uk>
Signed-off-by: David S. Miller <davem@davemloft.net>
/openbmc/linux/drivers/net/ethernet/cadence/
H A Dmacb_main.cdiff 91a208f2185ad4855ff03c342d0b7e4f5fc6f5df Wed Feb 26 04:23:41 CST 2020 Russell King <rmk+kernel@armlinux.org.uk> net: phylink: propagate resolved link config via mac_link_up()

Propagate the resolved link parameters via the mac_link_up() call for
MACs that do not automatically track their PCS state. We propagate the
link parameters via function arguments so that inappropriate members
of struct phylink_link_state can't be accessed, and creating a new
structure just for this adds needless complexity to the API.

Tested-by: Andre Przywara <andre.przywara@arm.com>
Tested-by: Alexandre Belloni <alexandre.belloni@bootlin.com>
Tested-by: Vladimir Oltean <vladimir.oltean@nxp.com>
Signed-off-by: Russell King <rmk+kernel@armlinux.org.uk>
Signed-off-by: David S. Miller <davem@davemloft.net>
/openbmc/linux/drivers/net/ethernet/marvell/
H A Dmvneta.cdiff 91a208f2185ad4855ff03c342d0b7e4f5fc6f5df Wed Feb 26 04:23:41 CST 2020 Russell King <rmk+kernel@armlinux.org.uk> net: phylink: propagate resolved link config via mac_link_up()

Propagate the resolved link parameters via the mac_link_up() call for
MACs that do not automatically track their PCS state. We propagate the
link parameters via function arguments so that inappropriate members
of struct phylink_link_state can't be accessed, and creating a new
structure just for this adds needless complexity to the API.

Tested-by: Andre Przywara <andre.przywara@arm.com>
Tested-by: Alexandre Belloni <alexandre.belloni@bootlin.com>
Tested-by: Vladimir Oltean <vladimir.oltean@nxp.com>
Signed-off-by: Russell King <rmk+kernel@armlinux.org.uk>
Signed-off-by: David S. Miller <davem@davemloft.net>
/openbmc/linux/drivers/net/ethernet/stmicro/stmmac/
H A Dstmmac_main.cdiff 91a208f2185ad4855ff03c342d0b7e4f5fc6f5df Wed Feb 26 04:23:41 CST 2020 Russell King <rmk+kernel@armlinux.org.uk> net: phylink: propagate resolved link config via mac_link_up()

Propagate the resolved link parameters via the mac_link_up() call for
MACs that do not automatically track their PCS state. We propagate the
link parameters via function arguments so that inappropriate members
of struct phylink_link_state can't be accessed, and creating a new
structure just for this adds needless complexity to the API.

Tested-by: Andre Przywara <andre.przywara@arm.com>
Tested-by: Alexandre Belloni <alexandre.belloni@bootlin.com>
Tested-by: Vladimir Oltean <vladimir.oltean@nxp.com>
Signed-off-by: Russell King <rmk+kernel@armlinux.org.uk>
Signed-off-by: David S. Miller <davem@davemloft.net>