netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Simon Horman <horms@kernel.org>
To: Alexander Duyck <alexander.duyck@gmail.com>
Cc: netdev@vger.kernel.org, linux@armlinux.org.uk,
	hkallweit1@gmail.com, andrew+netdev@lunn.ch, davem@davemloft.net,
	pabeni@redhat.com, kuba@kernel.org, kernel-team@meta.com,
	edumazet@google.com
Subject: Re: [net-next PATCH v2 3/6] fbnic: Replace 'link_mode' with 'aui'
Date: Mon, 16 Jun 2025 16:34:38 +0100	[thread overview]
Message-ID: <20250616153438.GE6918@horms.kernel.org> (raw)
In-Reply-To: <174974092054.3327565.9587401305919779622.stgit@ahduyck-xeon-server.home.arpa>

On Thu, Jun 12, 2025 at 08:08:40AM -0700, Alexander Duyck wrote:
> From: Alexander Duyck <alexanderduyck@fb.com>
> 
> The way we were using "link_mode" really was more to describe the
> interface between the attachment unit interface(s) we were using on the
> device. Specifically the AUI is describing the modulation and the number of
> lanes we are using. So we can simplify this by replacing link_mode with
> aui.
> 
> In addition this change makes it so that the enum we use for the FW values
> represents actual link modes that will be normally advertised by a link
> partner. The general idea is to look at using this to populate
> lp_advertising in the future so that we don't have to force the value and
> can instead default to autoneg allowing the user to change it should they
> want to force the link down or are doing some sort of manufacturing test
> with a loopback plug.
> 
> Lastly we make the transition from fw_settings to aui/fec a one time thing
> during phylink_init. The general idea is when we start phylink we should no
> longer update the setting based on the FW and instead only allow the user
> to provide the settings.
> 
> Signed-off-by: Alexander Duyck <alexanderduyck@fb.com>

Hi Alexander,

This patch is doing a lot - I count 3 things.
Could you try and break it up a bit in v3?

  reply	other threads:[~2025-06-16 15:34 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-06-12 15:08 [net-next PATCH v2 0/6] Add support for 25G, 50G, and 100G to fbnic Alexander Duyck
2025-06-12 15:08 ` [net-next PATCH v2 1/6] net: phy: Add interface types for 50G and 100G Alexander Duyck
2025-06-12 15:08 ` [net-next PATCH v2 2/6] fbnic: Do not consider mailbox "initialized" until we have verified fw version Alexander Duyck
2025-06-12 15:08 ` [net-next PATCH v2 3/6] fbnic: Replace 'link_mode' with 'aui' Alexander Duyck
2025-06-16 15:34   ` Simon Horman [this message]
2025-06-16 16:14     ` Alexander Duyck
2025-06-17  7:00       ` Simon Horman
2025-06-12 15:08 ` [net-next PATCH v2 4/6] fbnic: Set correct supported modes and speeds based on FW setting Alexander Duyck
2025-06-12 15:08 ` [net-next PATCH v2 5/6] fbnic: Add support for reporting link config Alexander Duyck
2025-06-14 22:27   ` Andrew Lunn
2025-06-12 15:09 ` [net-next PATCH v2 6/6] fbnic: Add support for setting/getting pause configuration Alexander Duyck
2025-06-14 22:29   ` Andrew Lunn

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=20250616153438.GE6918@horms.kernel.org \
    --to=horms@kernel.org \
    --cc=alexander.duyck@gmail.com \
    --cc=andrew+netdev@lunn.ch \
    --cc=davem@davemloft.net \
    --cc=edumazet@google.com \
    --cc=hkallweit1@gmail.com \
    --cc=kernel-team@meta.com \
    --cc=kuba@kernel.org \
    --cc=linux@armlinux.org.uk \
    --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 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).