linux/drivers/of
Roger Quadros 69226896ad mdio_bus: Issue GPIO RESET to PHYs.
Some boards [1] leave the PHYs at an invalid state
during system power-up or reset thus causing unreliability
issues with the PHY which manifests as PHY not being detected
or link not functional. To fix this, these PHYs need to be RESET
via a GPIO connected to the PHY's RESET pin.

Some boards have a single GPIO controlling the PHY RESET pin of all
PHYs on the bus whereas some others have separate GPIOs controlling
individual PHY RESETs.

In both cases, the RESET de-assertion cannot be done in the PHY driver
as the PHY will not probe till its reset is de-asserted.
So do the RESET de-assertion in the MDIO bus driver.

[1] - am572x-idk, am571x-idk, a437x-idk

Signed-off-by: Roger Quadros <rogerq@ti.com>
Signed-off-by: David S. Miller <davem@davemloft.net>
2017-04-24 12:40:24 -04:00
..
unittest-data
address.c
base.c DeviceTree updates for 4.11: 2017-02-22 19:23:14 -08:00
device.c
dynamic.c
fdt_address.c
fdt.c DeviceTree updates for 4.11: 2017-02-22 19:23:14 -08:00
irq.c
Kconfig
Makefile
of_mdio.c mdio_bus: Issue GPIO RESET to PHYs. 2017-04-24 12:40:24 -04:00
of_net.c
of_numa.c
of_pci_irq.c
of_pci.c
of_private.h
of_reserved_mem.c
overlay.c
pdt.c
platform.c
resolver.c
unittest.c