All of lore.kernel.org
 help / color / mirror / Atom feed
From: Leon Romanovsky <leon@kernel.org>
To: Jiawen Wu <jiawenwu@trustnetic.com>
Cc: netdev@vger.kernel.org, pabeni@redhat.com,
	simon.horman@corigine.com, mengyuanlou@net-swift.com
Subject: Re: [PATCH net-next v4] net: txgbe: change LAN reset mode
Date: Mon, 17 Jul 2023 08:51:55 +0300	[thread overview]
Message-ID: <20230717055155.GD9461@unreal> (raw)
In-Reply-To: <20230717021333.94181-1-jiawenwu@trustnetic.com>

On Mon, Jul 17, 2023 at 10:13:33AM +0800, Jiawen Wu wrote:
> The old way to do LAN reset is sending reset command to firmware. Once
> firmware performs reset, it reconfigures what it needs.
> 
> In the new firmware versions, veto bit is introduced for NCSI/LLDP to
> block PHY domain in LAN reset. At this point, writing register of LAN
> reset directly makes the same effect as the old way. And it does not
> reset MNG domain, so that veto bit does not change.
> 
> Since veto bit was never used, the old firmware is compatible with the
> driver before and after this change. The new firmware needs to use with
> the driver after this change if it wants to implement the new feature,
> otherwise it is the same as the old firmware.
> 
> Signed-off-by: Jiawen Wu <jiawenwu@trustnetic.com>
> ---
> v3 -> v4:
> - detail commit log
> - drop fixes tag
> v2 -> v3:
> - post to net-next
> v1 -> v2:
> - detail commit log
> ---
>  drivers/net/ethernet/wangxun/libwx/wx_hw.c    | 65 -------------------
>  drivers/net/ethernet/wangxun/libwx/wx_hw.h    |  1 -
>  drivers/net/ethernet/wangxun/txgbe/txgbe_hw.c |  8 +--
>  3 files changed, 4 insertions(+), 70 deletions(-)
> 

Thanks,
Reviewed-by: Leon Romanovsky <leonro@nvidia.com>

  reply	other threads:[~2023-07-17  5:51 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-07-17  2:13 [PATCH net-next v4] net: txgbe: change LAN reset mode Jiawen Wu
2023-07-17  5:51 ` Leon Romanovsky [this message]
2023-07-19  1:00 ` 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=20230717055155.GD9461@unreal \
    --to=leon@kernel.org \
    --cc=jiawenwu@trustnetic.com \
    --cc=mengyuanlou@net-swift.com \
    --cc=netdev@vger.kernel.org \
    --cc=pabeni@redhat.com \
    --cc=simon.horman@corigine.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.