[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <535561BE.9070303@cogentembedded.com>
Date: Mon, 21 Apr 2014 22:21:50 +0400
From: Sergei Shtylyov <sergei.shtylyov@...entembedded.com>
To: Florian Fainelli <f.fainelli@...il.com>
CC: Zhangfei Gao <zhangfei.gao@...aro.org>,
David Miller <davem@...emloft.net>,
Russell King <linux@....linux.org.uk>,
Arnd Bergmann <arnd@...db.de>,
Mark Rutland <mark.rutland@....com>,
David Laight <David.Laight@...lab.com>,
Eric Dumazet <eric.dumazet@...il.com>, xuwei5@...ilicon.com,
"linux-arm-kernel@...ts.infradead.org"
<linux-arm-kernel@...ts.infradead.org>,
netdev <netdev@...r.kernel.org>,
"devicetree@...r.kernel.org" <devicetree@...r.kernel.org>
Subject: Re: [PATCH v8 2/3] net: hisilicon: new hip04 MDIO driver
On 04/21/2014 10:03 PM, Florian Fainelli wrote:
>>> Hisilicon hip04 platform mdio driver
>>> Reuse Marvell phy drivers/net/phy/marvell.c
>>> Signed-off-by: Zhangfei Gao <zhangfei.gao@...aro.org>
>> [...]
>>> diff --git a/drivers/net/ethernet/hisilicon/hip04_mdio.c
>>> b/drivers/net/ethernet/hisilicon/hip04_mdio.c
>>> new file mode 100644
>>> index 0000000..19826a3
>>> --- /dev/null
>>> +++ b/drivers/net/ethernet/hisilicon/hip04_mdio.c
>>> @@ -0,0 +1,185 @@
[...]
>>> +static int hip04_mdio_reset(struct mii_bus *bus)
>>> +{
>>> + int temp, err, i;
>>> +
>>> + for (i = 0; i < PHY_MAX_ADDR; i++) {
>>> + hip04_mdio_write(bus, i, 22, 0);
>> Why? What kind of a register this is? <uapi/linux/mii.h> tells me it's
>> MII_SREVISION...
> I think this rather means clause 22 as opposed to clause 45.
No, the corresponding hip04_mdio_write()'s parameter is a register #, so
this is a write of 0 to register #22. A comment certainly wouldn't hurt here...
>>> + temp = hip04_mdio_read(bus, i, MII_BMCR);
>> You're not checking for error...
>>> + temp |= BMCR_RESET;
>>> + err = hip04_mdio_write(bus, i, MII_BMCR, temp);
>> Hmm, why you're open coding BMCR reset? There's phy_init_hw() doing this
>> correctly...
> Except that this runs way before we have created the PHY driver, so we
> can't use that function just yet.
Ah, you're right.
> I already asked about this, and he
> explained that this was because the PHY devices he uses are not
> responding correcty to MII_PHYSID1/2 reads.
So, this manual reset loop helps with reading the ID registers? A comment
wouldn't hurt either...
>>> + if (err < 0)
>>> + return err;
I'm not at all sure we want to leave the reset loop on a first write error.
>>> + }
>>> +
>>> + mdelay(500);
I'm not sure this is enough, given that in phy_init_hw() we poll for 600
ms + 1 ms.
>>> + return 0;
>>> +}
>>> +
>>> +static int hip04_mdio_probe(struct platform_device *pdev)
>>> +{
>>> + struct resource *r;
>>> + struct mii_bus *bus;
>>> + struct hip04_mdio_priv *priv;
>>> + int ret;
>>> +
>>> + bus = mdiobus_alloc_size(sizeof(struct hip04_mdio_priv));
>>> + if (!bus) {
>>> + dev_err(&pdev->dev, "Cannot allocate MDIO bus\n");
>>> + return -ENOMEM;
>>> + }
>>> +
>>> + bus->name = "hip04_mdio_bus";
>>> + bus->read = hip04_mdio_read;
>>> + bus->write = hip04_mdio_write;
>>> + bus->reset = hip04_mdio_reset;
>> Ah... However I don't think it a good implementation of that bus
>> method...
I assumed this method exists to do a hardware reset of the whole bus, not
to do a loop of soft-resetting all PHYs...
WBR, Sergei
--
To unsubscribe from this list: send the line "unsubscribe netdev" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Powered by blists - more mailing lists