From: Vladimir Oltean <olteanv@gmail.com>
To: "Arınç ÜNAL" <arinc.unal@arinc9.com>,
"Luiz Angelo Daros de Luca" <luizluca@gmail.com>
Cc: "Andrew Lunn" <andrew@lunn.ch>,
"Florian Fainelli" <f.fainelli@gmail.com>,
"David S. Miller" <davem@davemloft.net>,
"Eric Dumazet" <edumazet@google.com>,
"Jakub Kicinski" <kuba@kernel.org>,
"Paolo Abeni" <pabeni@redhat.com>,
mithat.guner@xeront.com, erkin.bozoglu@xeront.com,
"Alvin Šipraga" <ALSI@bang-olufsen.dk>,
netdev@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH net-next] net: dsa: remove OF-based MDIO bus registration from DSA core
Date: Thu, 25 Jan 2024 11:00:46 +0200 [thread overview]
Message-ID: <20240125090046.jyggdontwkhthqjh@skbuf> (raw)
In-Reply-To: <d32d17ed-87b5-4032-b310-f387cea72837@arinc9.com>
On Wed, Jan 24, 2024 at 08:30:11AM +0300, Arınç ÜNAL wrote:
> On 23.01.2024 18:44, Vladimir Oltean wrote:
> > On Mon, Jan 22, 2024 at 08:33:48AM +0300, Arınç ÜNAL wrote:
> > > These subdrivers which control switches [with MDIO bus] probed on OF, will
> > > lose the ability to register the MDIO bus OF-based:
> > >
> > > drivers/net/dsa/b53/b53_common.c
> > > drivers/net/dsa/lan9303-core.c
> > > drivers/net/dsa/realtek/realtek-mdio.c
> > > drivers/net/dsa/vitesse-vsc73xx-core.c
> > >
> > > These subdrivers let the DSA core driver register the bus:
> > > - ds->ops->phy_read() and ds->ops->phy_write() are present.
> > > - ds->user_mii_bus is not populated.
> > >
> > > The commit fe7324b93222 ("net: dsa: OF-ware slave_mii_bus") which brought
> > > OF-based MDIO bus registration on the DSA core driver is reasonably recent
> > > and, in this time frame, there have been no device trees in the Linux
> > > repository that started describing the MDIO bus, or dt-bindings defining
> > > the MDIO bus for the switches these subdrivers control. So I don't expect
> > > any devices to be affected.
> >
> > IIUC, Luiz made the original patch for the realtek switches. Shouldn't
> > we wait until realtek registers ds->user_mii_bus on its own, before
> > reverting? Otherwise, you're basically saying that Luiz made the DSA
> > core patch without needing it.
>
> My findings point to that. Luiz made the patch to optionally register the
> MDIO bus of the MDIO controlled Realtek switches OF-based. So it's not
> necessary to wait.
>
> Arınç
Well, Luiz is copied, he can ack or nack if so.
next prev parent reply other threads:[~2024-01-25 9:00 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-01-22 5:33 [PATCH net-next] net: dsa: remove OF-based MDIO bus registration from DSA core Arınç ÜNAL
2024-01-23 15:44 ` Vladimir Oltean
2024-01-24 5:30 ` Arınç ÜNAL
2024-01-25 9:00 ` Vladimir Oltean [this message]
2024-01-28 2:23 ` Luiz Angelo Daros de Luca
2024-01-29 14:56 ` Vladimir Oltean
2024-01-29 15:53 ` Arınç ÜNAL
2024-01-29 16:08 ` Florian Fainelli
2024-02-12 20:48 ` Luiz Angelo Daros de Luca
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=20240125090046.jyggdontwkhthqjh@skbuf \
--to=olteanv@gmail.com \
--cc=ALSI@bang-olufsen.dk \
--cc=andrew@lunn.ch \
--cc=arinc.unal@arinc9.com \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=erkin.bozoglu@xeront.com \
--cc=f.fainelli@gmail.com \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=luizluca@gmail.com \
--cc=mithat.guner@xeront.com \
--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