On Oct 18, 2008, at 21:07, Maxime Bizon wrote:
Signed-off-by: Maxime Bizon <email@example.com>
drivers/net/phy/Kconfig | 6 ++
drivers/net/phy/Makefile | 1 +
drivers/net/phy/bcm63xx.c | 132 ++++++++++++++++++++++++++++++++++++
3 files changed, 139 insertions(+), 0 deletions(-)
create mode 100644 drivers/net/phy/bcm63xx.c
diff --git a/drivers/net/phy/Kconfig b/drivers/net/phy/Kconfig
index d55932a..a5d2c2d 100644
@@ -56,6 +56,12 @@ config BROADCOM_PHY
Currently supports the BCM5411, BCM5421, BCM5461, BCM5464, BCM5481
and BCM5482 PHYs.
+ tristate "Drivers for Broadcom 63xx SOCs internal PHY"
+ depends on BCM63XX
This is probably right, but just to check: These PHYs will never be
used outside of the BCM63xx family?
+ Currently supports the 6348 and 6358 PHYs.
tristate "Drivers for ICPlus PHYs"
diff --git a/drivers/net/phy/bcm63xx.c b/drivers/net/phy/bcm63xx.c
new file mode 100644
+static int bcm63xx_config_init(struct phy_device *phydev)
+ int reg, err;
+ reg = phy_read(phydev, MII_BCM63XX_IR);
+ if (reg < 0)
+ return reg;
+ /* Mask interrupts globally. */
+ reg |= MII_BCM63XX_IR_GMASK;
+ err = phy_write(phydev, MII_BCM63XX_IR, reg);
+ if (err < 0)
+ return err;
+ /* Unmask events we are interested in */
+ reg = ~(MII_BCM63XX_IR_DUPLEX |
+ MII_BCM63XX_IR_SPEED |
+ MII_BCM63XX_IR_LINK) |
You just cleared the global interrupt mask. I have two problems with
1) If there's some reason you need to mask and then unmask interrupts,
you should make that clear in the comments. If there's not a reason,
then it's a bit silly to do both.
2) Interrupts should not be enabled until the PHY's config_intr()
function is called, and asks for them to be enabled.
Maybe you just wanted that to be:
reg &= ~(MII_BCM63XX_IR_DUPLEX |
The other comment I have is that these probably should go in the
broadcom.c file. I'm not deeply tied to the notion of one file per
company, but it has become the way it is done.