From: "Uwe Kleine-König" <u.kleine-koenig@pengutronix.de>
To: Yuiko Oshino <yuiko.oshino@microchip.com>
Cc: netdev@vger.kernel.org, Andrew Lunn <andrew@lunn.ch>,
Florian Fainelli <f.fainelli@gmail.com>,
kernel@pengutronix.de, Heiner Kallweit <hkallweit1@gmail.com>
Subject: Re: net: micrel: confusion about phyids used in driver
Date: Tue, 2 Jul 2019 22:31:52 +0200 [thread overview]
Message-ID: <20190702203152.gviukfldjhdnmu7j@pengutronix.de> (raw)
In-Reply-To: <20190510072243.h6h3bgvr2ovsh5g5@pengutronix.de>
Hello Yuiko Oshino,
On Fri, May 10, 2019 at 09:22:43AM +0200, Uwe Kleine-König wrote:
> On Thu, May 09, 2019 at 11:07:45PM +0200, Andrew Lunn wrote:
> > On Thu, May 09, 2019 at 10:55:29PM +0200, Heiner Kallweit wrote:
> > > On 09.05.2019 22:29, Uwe Kleine-König wrote:
> > > > I have a board here that has a KSZ8051MLL (datasheet:
> > > > http://ww1.microchip.com/downloads/en/DeviceDoc/ksz8051mll.pdf, phyid:
> > > > 0x0022155x) assembled. The actual phyid is 0x00221556.
> > >
> > > I think the datasheets are the source of the confusion. If the
> > > datasheets for different chips list 0x0022155x as PHYID each, and
> > > authors of support for additional chips don't check the existing code,
> > > then happens what happened.
> > >
> > > However it's not a rare exception and not Microchip-specific that
> > > sometimes vendors use the same PHYID for different chips.
>
> From the vendor's POV it is even sensible to reuse the phy IDs iff the
> chips are "compatible".
>
> Assuming that the last nibble of the phy ID actually helps to
> distinguish the different (not completely) compatible chips, we need
> some more detailed information than available in the data sheets I have.
> There is one person in the recipents of this mail with an @microchip.com
> address (hint, hint!).
can you give some input here or forward to a person who can?
Best regards
Uwe
--
Pengutronix e.K. | Uwe Kleine-König |
Industrial Linux Solutions | http://www.pengutronix.de/ |
next prev parent reply other threads:[~2019-07-03 1:29 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-05-09 20:29 net: micrel: confusion about phyids used in driver Uwe Kleine-König
2019-05-09 20:55 ` Heiner Kallweit
2019-05-09 21:07 ` Andrew Lunn
2019-05-10 7:22 ` Uwe Kleine-König
2019-07-02 20:31 ` Uwe Kleine-König [this message]
2019-07-02 20:55 ` Yuiko.Oshino
2019-08-08 8:36 ` Uwe Kleine-König
2019-08-20 20:25 ` Uwe Kleine-König
2019-08-20 20:30 ` Heiner Kallweit
2019-08-21 17:24 ` Florian Fainelli
2019-08-21 18:49 ` allan.nielsen
2019-08-21 19:53 ` Woojung.Huh
2019-10-16 9:09 ` Uwe Kleine-König
2019-10-16 11:45 ` Yuiko.Oshino
2019-05-11 14:00 ` Heiner Kallweit
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=20190702203152.gviukfldjhdnmu7j@pengutronix.de \
--to=u.kleine-koenig@pengutronix.de \
--cc=andrew@lunn.ch \
--cc=f.fainelli@gmail.com \
--cc=hkallweit1@gmail.com \
--cc=kernel@pengutronix.de \
--cc=netdev@vger.kernel.org \
--cc=yuiko.oshino@microchip.com \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.