From: Oleksij Rempel <o.rempel@pengutronix.de>
To: Andrew Lunn <andrew@lunn.ch>
Cc: Jakub Kicinski <kuba@kernel.org>,
Michal Kubecek <mkubecek@suse.cz>,
Jonathan Corbet <corbet@lwn.net>,
netdev@vger.kernel.org, linux-kernel@vger.kernel.org,
Eric Dumazet <edumazet@google.com>,
kernel@pengutronix.de, Paolo Abeni <pabeni@redhat.com>,
"David S. Miller" <davem@davemloft.net>,
Heiner Kallweit <hkallweit1@gmail.com>
Subject: Re: [PATCH net-next v1 1/1] net: phy: add remote fault support
Date: Thu, 16 Jun 2022 11:34:51 +0200 [thread overview]
Message-ID: <20220616093451.GA28995@pengutronix.de> (raw)
In-Reply-To: <Yqo8BuxL+XKw8U+a@lunn.ch>
On Wed, Jun 15, 2022 at 10:07:34PM +0200, Andrew Lunn wrote:
> On Tue, Jun 14, 2022 at 10:09:48PM -0700, Jakub Kicinski wrote:
> > On Wed, 15 Jun 2022 05:37:46 +0200 Andrew Lunn wrote:
> > > > Does this dovetail well with ETHTOOL_A_LINKSTATE_EXT_STATE /
> > > > ETHTOOL_A_LINKSTATE_EXT_SUBSTATE ?
> > > >
> > > > That's where people who read extended link state out of FW put it
> > > > (and therefore it's read only now).
> > >
> > > I did wonder about that. But this is to do with autoneg which is part
> > > of ksetting. Firmware hindered MAC drivers also support ksetting
> > > set/get. This patchset is also opening the door to more information
> > > which is passed via autoneg. It can also contain the ID the link peer
> > > PHY, etc. This is all part of 802.3, where as
> > > ETHTOOL_A_LINKSTATE_EXT_STATE tends to be whatever the firmware
> > > offers, not something covered by a standard.
> >
> > I see, yeah, I think you're right.
> >
> > But I'm missing the bigger picture. I'm unclear on who is supposed
> > to be setting the fault user space or kernel / device?
>
> It is also a bit unclear, but at the moment, i think user
> space. However, i can see the kernel making use of maybe RF TEST to
> ask the link peer to go quiet in order to perform a cable test.
>
> Oleksij, what are your use cases?
Currently I was thinking only about diagnostic:
- request transmit pause for cable testing
- request remote loopback for selftest. In this case I will need to use
vendor specific NextPage to request something like this.
> Maybe add something to patch 0/X indicating how you plan to make use of this?
I can move it from first patch if needed.
--
Pengutronix e.K. | |
Steuerwalder Str. 21 | http://www.pengutronix.de/ |
31137 Hildesheim, Germany | Phone: +49-5121-206917-0 |
Amtsgericht Hildesheim, HRA 2686 | Fax: +49-5121-206917-5555 |
next prev parent reply other threads:[~2022-06-16 9:35 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-06-08 9:34 [PATCH net-next v1 1/1] net: phy: add remote fault support Oleksij Rempel
2022-06-11 15:50 ` Andrew Lunn
2022-06-11 16:11 ` Andrew Lunn
2022-06-13 12:55 ` Oleksij Rempel
2022-06-13 14:56 ` Andrew Lunn
2022-06-14 5:12 ` Oleksij Rempel
2022-06-14 21:37 ` Andrew Lunn
2022-06-15 1:52 ` Jakub Kicinski
2022-06-15 3:37 ` Andrew Lunn
2022-06-15 5:09 ` Jakub Kicinski
2022-06-15 20:07 ` Andrew Lunn
2022-06-16 9:34 ` Oleksij Rempel [this message]
2022-06-16 15:57 ` Jakub Kicinski
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=20220616093451.GA28995@pengutronix.de \
--to=o.rempel@pengutronix.de \
--cc=andrew@lunn.ch \
--cc=corbet@lwn.net \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=hkallweit1@gmail.com \
--cc=kernel@pengutronix.de \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mkubecek@suse.cz \
--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 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.