From: Andrew Lunn <andrew@lunn.ch>
To: "huangguangbin (A)" <huangguangbin2@huawei.com>
Cc: Jakub Kicinski <kuba@kernel.org>,
davem@davemloft.net, netdev@vger.kernel.org,
linux-kernel@vger.kernel.org, salil.mehta@huawei.com,
lipeng321@huawei.com
Subject: Re: [PATCH net-next 3/3] net: hns3: add support for link diagnosis info in debugfs
Date: Sun, 4 Jul 2021 21:57:52 +0200 [thread overview]
Message-ID: <YOISwD+8ZoMpjP2m@lunn.ch> (raw)
In-Reply-To: <a5d42bf6-d71f-978e-b9ae-6b04f072d988@huawei.com>
> > > Hi Jakub, I have a question to consult you.
> > > Some fault information in our patch are not existed in current ethtool extended
> > > link states, for examples:
> > > "Serdes reference clock lost"
> > > "Serdes analog loss of signal"
> > > "SFP tx is disabled"
> > > "PHY power down"
> >
> > Why would the PHY be powered down if user requested port to be up?
> >
> In the case of other user may use MDIO tool to write PHY register directly to make
> PHY power down, if link state can display this information, I think it is helpful.
If the user directly writes to PHY registers, they should expect bad
things to happen. They can do a lot more than power the PHY down. They
could configure it into loopback mode, turn off autoneg and force a
mode which is compatible with the peer, etc.
I don't think you need to tell the user they have pointed a foot gun
at their feet and pulled the trigger.
Andrew
next prev parent reply other threads:[~2021-07-04 19:58 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-06-24 14:36 [PATCH net-next 0/3] net: hns3: add new debugfs commands Guangbin Huang
2021-06-24 14:36 ` [PATCH net-next 1/3] net: hns3: add support for FD counter in debugfs Guangbin Huang
2021-06-24 14:36 ` [PATCH net-next 2/3] net: hns3: add support for dumping MAC umv " Guangbin Huang
2021-06-24 14:36 ` [PATCH net-next 3/3] net: hns3: add support for link diagnosis info " Guangbin Huang
2021-06-24 19:25 ` Jakub Kicinski
2021-06-25 7:08 ` huangguangbin (A)
2021-07-01 9:03 ` huangguangbin (A)
2021-07-01 15:54 ` Jakub Kicinski
2021-07-04 1:37 ` huangguangbin (A)
2021-07-04 19:57 ` Andrew Lunn [this message]
2021-07-05 1:12 ` huangguangbin (A)
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=YOISwD+8ZoMpjP2m@lunn.ch \
--to=andrew@lunn.ch \
--cc=davem@davemloft.net \
--cc=huangguangbin2@huawei.com \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=lipeng321@huawei.com \
--cc=netdev@vger.kernel.org \
--cc=salil.mehta@huawei.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).