summaryrefslogtreecommitdiffstats
path: root/include/linux/ratelimit.h
diff options
context:
space:
mode:
authorDavid Daney <david.daney@cavium.com>2012-06-27 07:33:37 +0000
committerDavid S. Miller <davem@davemloft.net>2012-06-27 21:23:25 -0700
commita30e2c1891296b5ee8de48430a07fdf8b818c661 (patch)
tree3d66f111e7e5e467774eca749f6a1833b85f85b8 /include/linux/ratelimit.h
parent6bd47ac2e434611e52027155438d7b4ad3c76bdb (diff)
downloadtalos-obmc-linux-a30e2c1891296b5ee8de48430a07fdf8b818c661.tar.gz
talos-obmc-linux-a30e2c1891296b5ee8de48430a07fdf8b818c661.zip
netdev/phy/of: Add more methods for binding PHY devices to drivers.
Allow PHY drivers to supply their own device matching function (match_phy_device()), or to be matched OF compatible properties. PHYs following IEEE802.3 clause 45 have more than one device identifier constants, which breaks the default device matching code. Other 10G PHYs don't follow the standard manufacturer/device identifier register layout standards, but they do use the standard MDIO bus protocols for register access. Both of these require adjustments to the PHY driver to device matching code. If the there is an of_node associated with such a PHY, we can match it to its driver using the "compatible" properties, just as we do with certain platform devices. If the "compatible" property match fails, first check if there is a driver supplied matching function, and if not fall back to the existing identifier matching rules. Signed-off-by: David Daney <david.daney@cavium.com> Signed-off-by: David S. Miller <davem@davemloft.net>
Diffstat (limited to 'include/linux/ratelimit.h')
0 files changed, 0 insertions, 0 deletions
OpenPOWER on IntegriCloud