mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: "huangguangbin (A)" <huangguangbin2@huawei.com>
To: Andrew Lunn <andrew@lunn.ch>
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: Mon, 5 Jul 2021 09:12:28 +0800	[thread overview]
Message-ID: <ce0b9907-faa7-1f54-4040-e139ae153dec@huawei.com> (raw)
In-Reply-To: <YOISwD+8ZoMpjP2m@lunn.ch>



On 2021/7/5 3:57, Andrew Lunn wrote:
>>>> 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
> .
> 
OK, I accept your point, thanks!

      reply	other threads:[~2021-07-05  1:13 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
2021-07-05  1:12             ` huangguangbin (A) [this message]

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=ce0b9907-faa7-1f54-4040-e139ae153dec@huawei.com \
    --to=huangguangbin2@huawei.com \
    --cc=andrew@lunn.ch \
    --cc=davem@davemloft.net \
    --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

all inboxes | Powered by JetHome®