netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Niklas Söderlund" <niklas.soderlund+renesas@ragnatech.se>
To: Andrew Lunn <andrew@lunn.ch>
Cc: Yoshihiro Shimoda <yoshihiro.shimoda.uh@renesas.com>,
	"David S. Miller" <davem@davemloft.net>,
	Eric Dumazet <edumazet@google.com>,
	Jakub Kicinski <kuba@kernel.org>, Paolo Abeni <pabeni@redhat.com>,
	netdev@vger.kernel.org, linux-renesas-soc@vger.kernel.org
Subject: Re: [net-next] net: ethernet: rtsn: Add support for Renesas Ethernet-TSN
Date: Tue, 7 May 2024 13:14:28 +0200	[thread overview]
Message-ID: <20240507111428.GJ720810@ragnatech.se> (raw)
In-Reply-To: <0b686943-51de-49c9-afef-04db18b8fdbc@lunn.ch>

On 2024-05-06 21:53:58 +0200, Andrew Lunn wrote:
> On Mon, May 06, 2024 at 04:05:33PM +0200, Niklas Söderlund wrote:
> > Hi Andrew,
> > 
> > Thanks for this explanation, it helps understand what's going on.
> > 
> > On 2024-05-06 03:51:45 +0200, Andrew Lunn wrote:
> > 
> > > What PHY is this? Does it have C22 registers? Can it be identified via
> > > C22 registers 2 and 3?
> > 
> > The PHY in question is mv88q2110 (drivers/net/phy/marvell-88q2xxx.c), 
> > unfortunately I do not have a datasheet for it so I can't tell you much 
> > about it.
> 
> The mv88q2110 declares itself as 0x002b0b20.
> 
> > 
> > <snip>
> > 
> > > 
> > > So i would drop the compatible. See if C22 is sufficient to get the
> > > correct driver loaded.
> > 
> > - Remove C45 compatible; Remove C45 read/write in driver
> > 
> >   The PHY is identified as "Generic PHY", and the correct PHY driver is 
> >   not used. I can't test more than that as the generic PHY driver do not 
> >   implement some quirks I need to get the link up.
> 
> What ID does it return in registers 2 and 3? Anything like 0x002b0b20?
> If there is some usable value there, we can probably extend the driver
> to accept that ID as well.
> 
> Another option it to use a compatible conforming to:
> 
>       - pattern: "^ethernet-phy-id[a-f0-9]{4}\\.[a-f0-9]{4}$"
> 
> ethernet-phy-id002b.0b20
> 
> That will bypass reading ID registers for the ID, and just use the ID
> in the compatible. However, it would be better to read them from the
> PHY.

Thanks for these hints. Using a compatible to indicate which PHY to use 
allows the RTSN driver to not implement C45 read/write functions and 
still operate.

I will look into if I can extend the PHY driver with identification from 
register 2 and 3, but that will be a separate work item.

Unrelated note: I use the ID 0x002b0980 instead of 0x002b0b20 as I have 
a 88Q2110 and not a 88Q2220 PHY, but both are handled by the same PHY
driver.

> 
> 	Andrew
> 
> 

-- 
Kind Regards,
Niklas Söderlund

  reply	other threads:[~2024-05-07 11:14 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-04-14 13:59 [net-next] net: ethernet: rtsn: Add support for Renesas Ethernet-TSN Niklas Söderlund
2024-04-15  7:34 ` Paul Barker
2024-04-16  8:36   ` Niklas Söderlund
2024-04-15 22:55 ` Andrew Lunn
2024-04-16  8:58   ` Niklas Söderlund
2024-04-16 13:05     ` Andrew Lunn
2024-04-19  8:16       ` Geert Uytterhoeven
2024-04-19 12:56         ` Andrew Lunn
2024-05-03 10:20   ` Niklas Söderlund
2024-05-03 11:59     ` Andrew Lunn
2024-05-03 13:30       ` Niklas Söderlund
2024-05-06  1:51         ` Andrew Lunn
2024-05-06 14:05           ` Niklas Söderlund
2024-05-06 17:43             ` Geert Uytterhoeven
2024-05-06 18:26               ` Niklas Söderlund
2024-05-06 20:00                 ` Andrew Lunn
2024-05-07 11:18                   ` Niklas Söderlund
2024-05-06 19:53             ` Andrew Lunn
2024-05-07 11:14               ` Niklas Söderlund [this message]
2024-04-18 18:32 ` Simon Horman
2024-04-18 19:03   ` Arnd Bergmann
2024-05-03  8:50     ` Niklas Söderlund
2024-04-18 18:35 ` Simon Horman

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=20240507111428.GJ720810@ragnatech.se \
    --to=niklas.soderlund+renesas@ragnatech.se \
    --cc=andrew@lunn.ch \
    --cc=davem@davemloft.net \
    --cc=edumazet@google.com \
    --cc=kuba@kernel.org \
    --cc=linux-renesas-soc@vger.kernel.org \
    --cc=netdev@vger.kernel.org \
    --cc=pabeni@redhat.com \
    --cc=yoshihiro.shimoda.uh@renesas.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 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).