public inbox for netdev@vger.kernel.org
 help / color / mirror / Atom feed
From: Vladimir Oltean <olteanv@gmail.com>
To: "A. Sverdlin" <alexander.sverdlin@siemens.com>
Cc: netdev@vger.kernel.org, Andrew Lunn <andrew@lunn.ch>
Subject: Re: [PATCH net-next] net: dsa: honor "max-speed" for implicit PHYs on user ports
Date: Thu, 19 Dec 2024 19:46:26 +0200	[thread overview]
Message-ID: <20241219174626.6ga354quln36v4de@skbuf> (raw)
In-Reply-To: <20241219173805.503900-1-alexander.sverdlin@siemens.com>

On Thu, Dec 19, 2024 at 06:38:01PM +0100, A. Sverdlin wrote:
> From: Alexander Sverdlin <alexander.sverdlin@siemens.com>
> 
> If the PHYs on user ports are not specified explicitly, but a common
> user_mii_bus is being registered and scanned there is no way to limit
> Auto Negotiation options currently. If a gigabit switch is deployed in a
> way that the ports cannot support gigabit rates (4-wire PCB/magnetics,
> for instance), there is no way to limit ports' AN not to advertise gigabit
> options. Some PHYs take considerably longer time to AutoNegotiate in such
> cases.
> 
> Provide a way to limit AN advertisement options by examining "max-speed"
> property in the DT node of the corresponding user port and call
> phy_set_max_speed() right before attaching the PHY to he port netdevice.
> 
> Signed-off-by: Alexander Sverdlin <alexander.sverdlin@siemens.com>
> ---

The user_mii_bus mechanism is redundant when we have device tree
available (as opposed to probing on platform data), let's not make it
even more redundant. Why don't you just declare the MDIO bus in the
device tree, with the PHYs on it, and place max-speed there?

  reply	other threads:[~2024-12-19 17:46 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-12-19 17:38 [PATCH net-next] net: dsa: honor "max-speed" for implicit PHYs on user ports A. Sverdlin
2024-12-19 17:46 ` Vladimir Oltean [this message]
2024-12-19 18:50   ` Sverdlin, Alexander
2024-12-19 19:36     ` Vladimir Oltean
2024-12-20  7:17       ` Sverdlin, Alexander
2024-12-20  7:30         ` Sverdlin, Alexander
2024-12-20  8:28           ` Andrew Lunn
2024-12-20 10:15         ` Vladimir Oltean
2024-12-19 17:46 ` 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=20241219174626.6ga354quln36v4de@skbuf \
    --to=olteanv@gmail.com \
    --cc=alexander.sverdlin@siemens.com \
    --cc=andrew@lunn.ch \
    --cc=netdev@vger.kernel.org \
    /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