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: <davem@davemloft.net>, <kuba@kernel.org>, <wangjie125@huawei.com>,
	<netdev@vger.kernel.org>, <linux-kernel@vger.kernel.org>,
	<lipeng321@huawei.com>, <chenhao288@hisilicon.com>
Subject: Re: [PATCH net 1/7] net: hns3: fix pause config problem after autoneg disabled
Date: Thu, 28 Oct 2021 21:14:01 +0800	[thread overview]
Message-ID: <41ed2a6f-b9fc-4806-72d1-1e65f946fe30@huawei.com> (raw)
In-Reply-To: <YXqX7z2GljD6bxTr@lunn.ch>



On 2021/10/28 20:30, Andrew Lunn wrote:
>> Hi Andrew, thanks very much for your guidance on how to use pause autoneg,
>> it confuses me before because PHY registers actually have no separate setting
>> bit of pause autoneg.
>>
>> So, summarize what you mean:
>> 1. If pause autoneg is on, driver should always use the autoneg result to program
>>     the MAC. Eventhough general autoneg is off now and link state is no changed then
>>     driver just needs to keep the last configuration for the MAC, if link state is
>>     changed and phy goes down and up then driver needs to program the MAC according
>>     to the autoneg result in the link_adjust callback.
>> 2. If pause autoneg is off, driver should directly configure the MAC with tx pause
>>     and rx pause. Eventhough general autoneg is on, driver should ignore the autoneg
>>     result.
>>
>> Do I understand right?
> 
> Yes, that fits my understanding of ethtool, etc.
> 
> phylink tried to clear up some of these problems by fully implementing
> the call within phylink. All the MAC driver needs to provide is a
> method to configure the MAC pause settings. Take a look at
> phylink_ethtool_set_pauseparam() and the commit messages related to
> that.
> 
> 	Andrew
> .
> 
Ok, thanks!

  reply	other threads:[~2021-10-28 13:14 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-10-27 12:11 [PATCH net 0/7] net: hns3: add some fixes for -net Guangbin Huang
2021-10-27 12:11 ` [PATCH net 1/7] net: hns3: fix pause config problem after autoneg disabled Guangbin Huang
2021-10-27 17:23   ` Andrew Lunn
2021-10-28 11:54     ` huangguangbin (A)
2021-10-28 12:30       ` Andrew Lunn
2021-10-28 13:14         ` huangguangbin (A) [this message]
2021-10-27 12:11 ` [PATCH net 2/7] net: hns3: change hclge/hclgevf workqueue to WQ_UNBOUND mode Guangbin Huang
2021-10-27 12:11 ` [PATCH net 3/7] net: hns3: ignore reset event before initialization process is done Guangbin Huang
2021-10-27 12:11 ` [PATCH net 4/7] net: hns3: fix data endian problem of some functions of debugfs Guangbin Huang
2021-10-27 12:11 ` [PATCH net 5/7] net: hns3: add more string spaces for dumping packets number of queue info in debugfs Guangbin Huang
2021-10-27 12:11 ` [PATCH net 6/7] net: hns3: expand buffer len for some debugfs command Guangbin Huang
2021-10-27 12:11 ` [PATCH net 7/7] net: hns3: adjust string spaces of some parameters of tx bd info in debugfs Guangbin Huang
2021-10-27 13:50 ` [PATCH net 0/7] net: hns3: add some fixes for -net patchwork-bot+netdevbpf

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=41ed2a6f-b9fc-4806-72d1-1e65f946fe30@huawei.com \
    --to=huangguangbin2@huawei.com \
    --cc=andrew@lunn.ch \
    --cc=chenhao288@hisilicon.com \
    --cc=davem@davemloft.net \
    --cc=kuba@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=lipeng321@huawei.com \
    --cc=netdev@vger.kernel.org \
    --cc=wangjie125@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®