Netdev List
 help / color / mirror / Atom feed
From: Vladimir Oltean <olteanv@gmail.com>
To: Andrew Lunn <andrew@lunn.ch>
Cc: davem@davemloft.net, netdev@vger.kernel.org,
	linux@armlinux.org.uk, f.fainelli@gmail.com,
	hkallweit1@gmail.com, claudiu.manoil@nxp.com,
	alexandru.marginean@nxp.com, ioana.ciornei@nxp.com,
	michael@walle.cc
Subject: Re: [PATCH net-next] net: phy: continue searching for C45 MMDs even if first returned ffff:ffff
Date: Thu, 16 Jul 2020 23:51:37 +0300	[thread overview]
Message-ID: <20200716205137.goazvzvhie5s7ttl@skbuf> (raw)
In-Reply-To: <20200716201210.GE1308244@lunn.ch>

On Thu, Jul 16, 2020 at 10:12:10PM +0200, Andrew Lunn wrote:
> > Then the rest of the code just carried on thinking "ok, MMD 1 (PMA/PMD)
> > says that there are 31 devices in that package, each having a device id
> > of ffff:ffff, that's perfectly fine, let's go ahead and probe this PHY
> > device".
> 
> With a device ID of ffff:ffff, what PHY driver was getting loaded?
> 

You mean ffff:fffe.
No PHY driver. I am driving this PCS locally from within
drivers/net/dsa/ocelot/felix_vsc9959.c. I call get_phy_device at the
address where I know a PCS is present, for the simple reason that I like
an extra validation that my internal MDIO reads/writes are going
somewhere. I've had situations in the past where the PCS was working
because the bootloader had initialized it, however the internal MDIO
reads/writes from Linux were broken. So, the fact that get_phy_device
can read the PHY ID correctly is giving me some assurance.

> > - MDIO_DEVS1=0x008a, MDIO_DEVS2=0x0000,
> > - MDIO_DEVID1=0x0083, MDIO_DEVID2=0xe400
> 
> Now that we have valid IDs, is the same driver getting loaded? Do this
> ID adding somewhere?
> 

Not applicable, see above.

> > Signed-off-by: Vladimir Oltean <vladimir.oltean@nxp.com>
> 
> Reviewed-by: Andrew Lunn <andrew@lunn.ch>
> 
>     Andrew

Thanks,
-Vladimir

  reply	other threads:[~2020-07-16 20:51 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-07-12 16:48 [PATCH net-next] net: phy: continue searching for C45 MMDs even if first returned ffff:ffff Vladimir Oltean
2020-07-16 19:01 ` Jakub Kicinski
2020-07-16 20:09   ` Andrew Lunn
2020-07-16 20:12 ` Andrew Lunn
2020-07-16 20:51   ` Vladimir Oltean [this message]
2020-07-16 20:58     ` Vladimir Oltean
2020-07-17 17:23 ` David Miller

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=20200716205137.goazvzvhie5s7ttl@skbuf \
    --to=olteanv@gmail.com \
    --cc=alexandru.marginean@nxp.com \
    --cc=andrew@lunn.ch \
    --cc=claudiu.manoil@nxp.com \
    --cc=davem@davemloft.net \
    --cc=f.fainelli@gmail.com \
    --cc=hkallweit1@gmail.com \
    --cc=ioana.ciornei@nxp.com \
    --cc=linux@armlinux.org.uk \
    --cc=michael@walle.cc \
    --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