From: Marek Vasut <marex@denx.de>
To: Andrew Lunn <andrew@lunn.ch>
Cc: linux-usb@vger.kernel.org,
"David S . Miller" <davem@davemloft.net>,
Nisar Sayed <Nisar.Sayed@microchip.com>,
Woojung Huh <Woojung.Huh@microchip.com>,
netdev <netdev@vger.kernel.org>,
Florian Fainelli <f.fainelli@gmail.com>
Subject: Re: [PATCH] smsc95xx: Add support for automated PHY address detection
Date: Sun, 23 Dec 2018 11:59:15 +0100 [thread overview]
Message-ID: <ff4273aa-dd2a-fa22-e16e-125304d9bc01@denx.de> (raw)
In-Reply-To: <20181223105643.GF32178@lunn.ch>
On 12/23/18 11:56 AM, Andrew Lunn wrote:
> On Sun, Dec 23, 2018 at 11:43:05AM +0100, Marek Vasut wrote:
>> On 12/23/18 11:23 AM, Andrew Lunn wrote:
>>>>> +static int smsc95xx_phy_address(struct usbnet *dev)
>>>>> +{
>>>>> + u32 read_buf;
>>>>> + int ret, id1, id2, phyad;
>>>>> +
>>>>> + ret = smsc95xx_read_reg(dev, HW_CFG, &read_buf);
>>>>> + if (ret < 0)
>>>>> + return ret;
>>>>> +
>>>>> + /* Check if using external PHY, if not, use internal PHY address */
>>>>> + if (!(read_buf & HW_CFG_PSEL_))
>>>>> + return SMSC95XX_INTERNAL_PHY_ID;
>>>>> +
>>>>> + /*
>>>>> + * Detect external PHY address. Here we probe the MDIO bus from
>>>>> + * the highest address, since some PHYs respond also on address
>>>>> + * zero, which they consider MDIO broadcast address. We really
>>>>> + * want to get their proper address instead though, so we scan
>>>>> + * address zero last.
>>>>> + */
>>>>> + for (phyad = 0x1f; phyad >= 0; phyad--) {
>>>>> + id1 = smsc95xx_mdio_read(dev->net, phyad, MII_PHYSID1);
>>>>> + id2 = smsc95xx_mdio_read(dev->net, phyad, MII_PHYSID2);
>>>>> + /* Check for valid response from the PHY */
>>>>> + if (id1 > 0 && id2 > 0 && id1 != 0x7fff && id2 != 0xffff)
>>>>> + return phyad;
>>>>> + }
>>>
>>> This would be so much easier if the driver used the core mdio/phy
>>> code. Just set mdio->phy_mask to ~BIT(0) and then use
>>> phy_find_first().
>>
>> That's in the pipeline, along with PM cleanups, but low prio.
>
> Great. Does using the broadcast address actually cause a problem? If
> not, i would say lets drop this part of the patch until you do the
> cleanup.
Yeah, at least the TJA11xx doesn't respond on 0x0, so I wouldn't depend
on the broadcast address. In my case, the PHY just sits at 0x4.
--
Best regards,
Marek Vasut
prev parent reply other threads:[~2018-12-23 11:01 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20180911101223.4217-1-marex@denx.de>
2018-12-23 9:30 ` [PATCH] smsc95xx: Add support for automated PHY address detection Marek Vasut
2018-12-23 10:23 ` Andrew Lunn
2018-12-23 10:43 ` Marek Vasut
2018-12-23 10:56 ` Andrew Lunn
2018-12-23 10:59 ` Marek Vasut [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=ff4273aa-dd2a-fa22-e16e-125304d9bc01@denx.de \
--to=marex@denx.de \
--cc=Nisar.Sayed@microchip.com \
--cc=Woojung.Huh@microchip.com \
--cc=andrew@lunn.ch \
--cc=davem@davemloft.net \
--cc=f.fainelli@gmail.com \
--cc=linux-usb@vger.kernel.org \
--cc=netdev@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).