diff options
author | Anton Vorontsov <avorontsov@ru.mvista.com> | 2009-01-14 22:38:02 (GMT) |
---|---|---|
committer | David S. Miller <davem@davemloft.net> | 2009-01-14 22:38:02 (GMT) |
commit | f0d44ae310bc8eb0b6694e257015d8b24e1a357c (patch) | |
tree | 5687fbe1f5c7e2eeaa55de384b58f0764fae6ab8 /drivers/isdn | |
parent | f17f5c91ae3bfeb5cfc37fa132a5fdfceb8927be (diff) | |
download | linux-f0d44ae310bc8eb0b6694e257015d8b24e1a357c.tar.xz |
phylib: Fix Freescale TBI PHY detection
Freescale on-chip TBI PHYs reports PHY ID as 0x0, but as of
commit 3ee82383f0098a2e13acc8cf1be8e47512f41e5a
Author: Giulio Benetti <giulio.benetti@micronovasrl.com>
Date: Thu Nov 13 21:53:13 2008 +0000
phy: fix phy address bug
PHYID returns 0xffff and not 0xffffffff when not found and in some
case(at91sam9263) 0x0. Maybe this patch could be useful.
phy_device.c treats PHY ID == 0x0 as bogus IDs, and that results in
gianfar driver failure to see the TBI PHYs. This code snippet triggers:
if (!priv->tbiphy) {
printk(KERN_WARNING "SGMII mode requires that the device "
"tree specify a tbi-handle\n");
return;
}
Although tbi-handle is specified in the device tree.
Btw, technically PHY ID == 0x0 is a valid ID (if we ever see a PHY
manufactured by Xerox :-).
Signed-off-by: Anton Vorontsov <avorontsov@ru.mvista.com>
Acked-by: Andy Fleming <afleming@freescale.com>
Signed-off-by: David S. Miller <davem@davemloft.net>
Diffstat (limited to 'drivers/isdn')
0 files changed, 0 insertions, 0 deletions