mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Andrew Lunn <andrew@lunn.ch>
To: Jakub Kicinski <kuba@kernel.org>
Cc: "George Moussalem via B4 Relay"
	<devnull+george.moussalem.outlook.com@kernel.org>,
	george.moussalem@outlook.com,
	"Vladimir Oltean" <olteanv@gmail.com>,
	"David S. Miller" <davem@davemloft.net>,
	"Eric Dumazet" <edumazet@google.com>,
	"Paolo Abeni" <pabeni@redhat.com>,
	netdev@vger.kernel.org, linux-kernel@vger.kernel.org,
	"Marek Behún" <kabel@kernel.org>
Subject: Re: [PATCH] net: dsa: qca8k: fix led devicename when using external mdio bus
Date: Tue, 29 Apr 2025 21:00:05 +0200	[thread overview]
Message-ID: <6940ad35-1840-4b3b-ae71-27d91f648702@lunn.ch> (raw)
In-Reply-To: <20250429114128.5b7790ad@kernel.org>

On Tue, Apr 29, 2025 at 11:41:28AM -0700, Jakub Kicinski wrote:
> On Fri, 25 Apr 2025 10:49:55 +0400 George Moussalem via B4 Relay wrote:
> > From: George Moussalem <george.moussalem@outlook.com>
> > 
> > The qca8k dsa switch can use either an external or internal mdio bus.
> > This depends on whether the mdio node is defined under the switch node
> > itself and, as such, the internal_mdio_mask is populated with its
> > internal phys. Upon registering the internal mdio bus, the slave_mii_bus
> > of the dsa switch is assigned to this bus. When an external mdio bus is
> > used, it is left unassigned, though its id is used to create the device
> > names of the leds.
> > This leads to the leds being named '(efault):00:green:lan' and so on as
> > the slave_mii_bus is null. So let's fix this by adding a null check and
> > use the devicename of the external bus instead when an external bus is
> > configured.
> 
> Hi Andrew, would you mind taking a quick look?

There is a somewhat ongoing discussion which could affect this:

https://patchwork.kernel.org/project/netdevbpf/patch/20250425151309.30493-1-kabel@kernel.org/

It could well be there is no internal and external MDIO bus, its just
one bus with two bus masters. LED names are somewhere ABI, so i think
we need to resolve the other thread first.

	Andrew

      reply	other threads:[~2025-04-29 19:00 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-04-25  6:49 George Moussalem via B4 Relay
2025-04-29 18:41 ` Jakub Kicinski
2025-04-29 19:00   ` Andrew Lunn [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=6940ad35-1840-4b3b-ae71-27d91f648702@lunn.ch \
    --to=andrew@lunn.ch \
    --cc=davem@davemloft.net \
    --cc=devnull+george.moussalem.outlook.com@kernel.org \
    --cc=edumazet@google.com \
    --cc=george.moussalem@outlook.com \
    --cc=kabel@kernel.org \
    --cc=kuba@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=netdev@vger.kernel.org \
    --cc=olteanv@gmail.com \
    --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

all inboxes | Powered by JetHome®