All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Russell King (Oracle)" <linux@armlinux.org.uk>
To: Yajun Deng <yajun.deng@linux.dev>
Cc: Andrew Lunn <andrew@lunn.ch>,
	hkallweit1@gmail.com, davem@davemloft.net, edumazet@google.com,
	kuba@kernel.org, pabeni@redhat.com, netdev@vger.kernel.org,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH net-next] net: phy: Add c45_phy_ids sysfs entry
Date: Wed, 28 May 2025 14:08:15 +0100	[thread overview]
Message-ID: <aDcKvwDaa6_1gZY7@shell.armlinux.org.uk> (raw)
In-Reply-To: <552f550315dc503250cc61fdcd13db38c1ea00f5@linux.dev>

On Mon, May 26, 2025 at 08:52:12AM +0000, Yajun Deng wrote:
> May 26, 2025 at 4:19 PM, "Russell King (Oracle)" <linux@armlinux.org.uk> wrote:
> > On Mon, May 26, 2025 at 08:11:21AM +0000, Yajun Deng wrote:
> > >  $ ls /sys/class/net/eth0/phydev/c45_phy_ids
> > > 
> > >  mmd10_device_id mmd17_device_id mmd23_device_id mmd2_device_id mmd7_device_id
> > > 
> > >  mmd11_device_id mmd18_device_id mmd24_device_id mmd30_device_id mmd8_device_id
> > > 
> > >  mmd12_device_id mmd19_device_id mmd25_device_id mmd31_device_id mmd9_device_id
> > > 
> > >  mmd13_device_id mmd1_device_id mmd26_device_id mmd3_device_id
> > > 
> > >  mmd14_device_id mmd20_device_id mmd27_device_id mmd4_device_id
> > > 
> > >  mmd15_device_id mmd21_device_id mmd28_device_id mmd5_device_id
> > > 
> > >  mmd16_device_id mmd22_device_id mmd29_device_id mmd6_device_id
> > > 
> > 
> > I suspect you don't have a PHY that defines all these IDs. Are you sure
> > 
> > your .is_visible() is working properly?
> > 
> 
> I'm just determining if it's a c45 device and not filtering PHY ID content now.
> I can add this condition. 

I'm talking about listing all 31 entries, whether they're implemented in
the PHY or not. Look at mmds_present in struct phy_c45_device_ids to
determine which IDs should be exported as well as checking whether the
ID value you're exporting is not 0 or ~0.

-- 
RMK's Patch system: https://www.armlinux.org.uk/developer/patches/
FTTP is here! 80Mbps down 10Mbps up. Decent connectivity at last!

  parent reply	other threads:[~2025-05-28 13:08 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-05-23 13:26 [PATCH net-next] net: phy: Add c45_phy_ids sysfs entry Yajun Deng
2025-05-23 13:55 ` Andrew Lunn
2025-05-26  8:11   ` Yajun Deng
2025-05-26  8:19     ` Russell King (Oracle)
2025-05-26  8:52       ` Yajun Deng
2025-05-26 14:02         ` Andrew Lunn
2025-05-28 13:08         ` Russell King (Oracle) [this message]
2025-05-29  1:51           ` Yajun Deng

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=aDcKvwDaa6_1gZY7@shell.armlinux.org.uk \
    --to=linux@armlinux.org.uk \
    --cc=andrew@lunn.ch \
    --cc=davem@davemloft.net \
    --cc=edumazet@google.com \
    --cc=hkallweit1@gmail.com \
    --cc=kuba@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=netdev@vger.kernel.org \
    --cc=pabeni@redhat.com \
    --cc=yajun.deng@linux.dev \
    /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.