BMC/Intel-BMC/linux.git/drivers/net/phy, branch dev-4.4

Merge tag 'v4.4.26' into dev-4.4

2016-10-21T01:33:35+00:00

This is the 4.4.26 stable release

Revert "phy: IRQ cannot be shared"

2016-09-30T08:18:37+00:00

[ Upstream commit c3e70edd7c2eed6acd234627a6007627f5c76e8e ] This reverts: commit 33c133cc7598 ("phy: IRQ cannot be shared") On hardware with multiple PHY devices hooked up to the same IRQ line, allow them to share it. Sergei Shtylyov says: "I'm not sure now what was the reason I concluded that the IRQ sharing was impossible... most probably I thought that the kernel IRQ handling code exited the loop over the IRQ actions once IRQ_HANDLED was returned -- which is obviously not so in reality..." Signed-off-by: Xander Huff Signed-off-by: Nathan Sullivan Signed-off-by: David S. Miller Signed-off-by: Greg Kroah-Hartman

net/phy: Expose 100base-T capability only

2016-05-05T14:08:55+00:00

I don't know the specific PHY model deployed on Firestone BMC, but currently used one (PHY_ID_BCM54210E) isn't correct. BCM54210E supports 1000base-T but the PHY on Firestone BMC shouldn't support that mode as uboot uses 100base-T mode. When exposing 1000base-T capability, the MAC is forced to have the same mode though the PHY is working in 100base-T mode in fact. It causes the mode mismatch between PHY/MAC and the ethernet network doesn't work. It's a temporary fix. After the PHY model is confirmed, we need to enable the correct PHY driver instead current one for BCM54210E. Signed-off-by: Gavin Shan [Cyril] The plot thickens, it does appear that this IS the correct PHY on firestones. This patch is definitely required for networking to be functional though. Signed-off-by: Cyril Bur Signed-off-by: Joel Stanley

phy/broadcom: Add support for the BCM54210E

2016-05-05T14:08:30+00:00

Signed-off-by: Joel Stanley Signed-off-by: Cyril Bur

net: dp83640: Fix tx timestamp overflow handling.

2016-03-03T23:07:04+00:00

[ Upstream commit 81e8f2e930fe76b9814c71b9d87c30760b5eb705 ] PHY status frames are not reliable, the PHY may not be able to send them during heavy receive traffic. This overflow condition is signaled by the PHY in the next status frame, but the driver did not make use of it. Instead it always reported wrong tx timestamps to user space after an overflow happened because it assigned newly received tx timestamps to old packets in the queue. This commit fixes this issue by clearing the tx timestamp queue every time an overflow happens, so that no timestamps are delivered for overflow packets. This way time stamping will continue correctly after an overflow. Signed-off-by: Manfred Rudigier Acked-by: Richard Cochran Signed-off-by: David S. Miller Signed-off-by: Greg Kroah-Hartman

net: phy: mdio-mux: Check return value of mdiobus_alloc()

2015-12-14T19:27:40+00:00

mdiobus_alloc() might return NULL, but its return value is not checked in mdio_mux_init(). This could potentially lead to a NULL pointer dereference. Fix it by checking the return value Fixes: 0ca2997d1452 ("netdev/of/phy: Add MDIO bus multiplexer support.") Signed-off-by: Tobias Klauser Signed-off-by: David S. Miller

phy: micrel: Fix finding PHY properties in MAC node.

2015-12-12T01:31:15+00:00

commit 8b63ec1837fa ("phylib: Make PHYs children of their MDIO bus, not the bus' parent.") changed the parenting of PHY devices, making them a child of the MDIO bus, instead of the MAC device. This broken the Micrel PHY driver which has a deprecated feature of allowing PHY properties to be placed into the MAC node. In order to find the MAC node, we need to walk up the tree of devices until we find one with an OF node attached. Reported-by: Dinh Nguyen Suggested-by: David Daney Acked-by: David Daney Fixes: 8b63ec1837fa ("phylib: Make PHYs children of their MDIO bus, not the bus' parent.") Signed-off-by: Andrew Lunn Tested-by: Dinh Nguyen Acked-by: Florian Fainelli Signed-off-by: David S. Miller

net: phy: reset only targeted phy

2015-12-03T20:26:13+00:00

It is possible to address another chip on same MDIO bus. The case is correctly handled for media advertising. It is taken into account only if mii_data->phy_id == phydev->addr. However, this condition was missing for reset case. Signed-off-by: Jérôme Pouiller Signed-off-by: David S. Miller

broadcom: fix PHY_ID_BCM5481 entry in the id table

2015-11-24T04:29:27+00:00

Commit fcb26ec5b18d ("broadcom: move all PHY_ID's to header") updated broadcom_tbl to use PHY_IDs, but incorrectly replaced 0x0143bca0 with PHY_ID_BCM5482 (making a duplicate entry, and completely omitting the original). Fix that. Fixes: fcb26ec5b18d ("broadcom: move all PHY_ID's to header") Signed-off-by: Aaro Koskinen Signed-off-by: David S. Miller

net: phy: Use interrupts when available in NOLINK state

2015-11-17T20:25:44+00:00

The NOLINK state will poll the phy once a second to see if the link has come up. If the phy has an interrupt line, this polling can be skipped, since the phy should interrupt when the link returns. Signed-off-by: Andrew Lunn Signed-off-by: David S. Miller