From: Vladimir Oltean <olteanv@gmail.com>
To: "Alvin Šipraga" <ALSI@bang-olufsen.dk>
Cc: Vladimir Oltean <vladimir.oltean@nxp.com>,
"netdev@vger.kernel.org" <netdev@vger.kernel.org>,
Woojung Huh <woojung.huh@microchip.com>,
"UNGLinuxDriver@microchip.com" <UNGLinuxDriver@microchip.com>,
Andrew Lunn <andrew@lunn.ch>,
Vivien Didelot <vivien.didelot@gmail.com>,
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>,
Russell King <linux@armlinux.org.uk>,
Michael Grzeschik <m.grzeschik@pengutronix.de>,
Oleksij Rempel <linux@rempel-privat.de>,
Thorsten Leemhuis <regressions@leemhuis.info>,
Rasmus Villemoes <linux@rasmusvillemoes.dk>,
Craig McQueen <craig@mcqueen.id.au>
Subject: Re: [PATCH net] net: dsa: microchip: keep compatibility with device tree blobs with no phy-mode
Date: Thu, 18 Aug 2022 18:18:06 +0300 [thread overview]
Message-ID: <20220818151806.yv5crkdab6tpkvph@skbuf> (raw)
In-Reply-To: <20220818150644.ic6pf5arbh34lr5z@bang-olufsen.dk>
On Thu, Aug 18, 2022 at 03:06:44PM +0000, Alvin Šipraga wrote:
> Reviewed-by: Alvin Šipraga <alsi@bang-olufsen.dk>
Thanks.
> Some quick grepping shows at least a few other drivers which do not set
> PHY_INTERFACE_MODE_GMII for their ports with internal PHY:
>
> bcm_sf2
> ar9331 (*)
> lantiq_gswip
>
> Should these be "fixed" too? Or only if somebody reports a regression?
>
> (*) I note that ar9331 ought not to rely on DSA workarounds, per your
> other patchset, so I there is actually no need to "fix" that one, since
> the new validation you are introducing will require a phy-mode to be
> specified for those switches' ports anyway.
Note that my patch set which you are talking about
https://patchwork.kernel.org/project/netdevbpf/cover/20220818115500.2592578-1-vladimir.oltean@nxp.com/
only enforces phy-mode presence for CPU and DSA ports. Whereas internal
PHYs are more typical on user ports. So the problem is equally
applicable to ar9331, as long as it won't specify a phy-mode but rely on
DSA's assumption that user ports with lacking DT descriptions want to
connect to an internal PHY.
IDK, if I had infinite time I'd go fix every driver. I don't know why
some have GMII and some don't, and I'm not exactly keen to go study
every driver's subtleties unless a problem is reported.
next prev parent reply other threads:[~2022-08-18 15:18 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-08-18 14:32 [PATCH net] net: dsa: microchip: keep compatibility with device tree blobs with no phy-mode Vladimir Oltean
2022-08-18 15:06 ` Alvin Šipraga
2022-08-18 15:18 ` Vladimir Oltean [this message]
2022-08-18 15:25 ` Alvin Šipraga
2022-08-18 15:13 ` Andrew Lunn
2022-08-18 15:21 ` Vladimir Oltean
2022-08-18 15:33 ` Russell King (Oracle)
2022-08-19 10:19 ` Rasmus Villemoes
2022-08-19 10:57 ` Vladimir Oltean
2022-08-19 11:47 ` Rasmus Villemoes
2022-08-19 16:41 ` Vladimir Oltean
2022-08-22 20:11 ` Tim Harvey
2022-08-19 23:32 ` Jakub Kicinski
2022-08-20 11:24 ` Vladimir Oltean
2022-08-23 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=20220818151806.yv5crkdab6tpkvph@skbuf \
--to=olteanv@gmail.com \
--cc=ALSI@bang-olufsen.dk \
--cc=UNGLinuxDriver@microchip.com \
--cc=andrew@lunn.ch \
--cc=craig@mcqueen.id.au \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=f.fainelli@gmail.com \
--cc=kuba@kernel.org \
--cc=linux@armlinux.org.uk \
--cc=linux@rasmusvillemoes.dk \
--cc=linux@rempel-privat.de \
--cc=m.grzeschik@pengutronix.de \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=regressions@leemhuis.info \
--cc=vivien.didelot@gmail.com \
--cc=vladimir.oltean@nxp.com \
--cc=woojung.huh@microchip.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).