From: "Yajun Deng" <yajun.deng@linux.dev>
To: "Andrew Lunn" <andrew@lunn.ch>
Cc: hkallweit1@gmail.com, linux@armlinux.org.uk, 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: Mon, 26 May 2025 08:11:21 +0000 [thread overview]
Message-ID: <fad26dc95cbe08a87b30d98a55b7e3d987683589@linux.dev> (raw)
In-Reply-To: <2eec1d17-a6d1-4859-9cc9-43eeac23edbd@lunn.ch>
May 23, 2025 at 9:55 PM, "Andrew Lunn" <andrew@lunn.ch> wrote:
>
> >
> > +What: /sys/class/mdio_bus/<bus>/<device>/c45_phy_ids
> >
> > +Date: May 2025
> >
> > +KernelVersion: 6.16
> >
> > +Contact: netdev@vger.kernel.org
> >
> > +Description:
> >
> > + This attribute contains the 32-bit PHY Identifier as reported
> >
> > + by the device during bus enumeration, encoded in hexadecimal.
> >
> > + These C45 IDs are used to match the device with the appropriate
> >
> > + driver.
> >
>
> https://docs.kernel.org/filesystems/sysfs.html#attributes
>
> Attributes should be ASCII text files, preferably with only one
>
> value per file. It is noted that it may not be efficient to contain
>
> only one value per file, so it is socially acceptable to express an
>
> array of values of the same type.
>
> These are static values, so efficiency is not an issue.
>
> It might be better to have a directory
>
> /sys/class/mdio_bus/<bus>/<device>/c45_phy_ids and then for each MMD
>
> create a file. I would also suggest using is_visible() == 0 for those
>
> with an ID == 0.
>
is_visible only hide files, not directory. It will look like this:
c45 device:
$ ls /sys/class/net/eth0/phydev/
attached_dev driver of_node phy_id power subsystem
c45_phy_ids hwmon phy_has_fixups phy_interface statistics uevent
$ 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
c22 device:
$ ls /sys/class/net/eth0/phydev/
attached_dev driver of_node phy_id power subsystem
c45_phy_ids hwmon phy_has_fixups phy_interface statistics uevent
$ ls /sys/class/net/eth0/phydev/c45_phy_ids
So is that fine?
> Andrew
>
next prev parent reply other threads:[~2025-05-26 8:11 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 [this message]
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)
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=fad26dc95cbe08a87b30d98a55b7e3d987683589@linux.dev \
--to=yajun.deng@linux.dev \
--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=linux@armlinux.org.uk \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.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).