From: "Joris Vaišvila" <joey@tinyisr.com>
To: Andrew Lunn <andrew@lunn.ch>
Cc: netdev@vger.kernel.org, Vladimir Oltean <olteanv@gmail.com>,
"David S. Miller" <davem@davemloft.net>,
Eric Dumazet <edumazet@google.com>,
Jakub Kicinski <kuba@kernel.org>,
Paolo Abeni <pabeni@redhat.com>, Simon Horman <horms@kernel.org>
Subject: Re: [RFC PATCH 2/2 net-next] net: dsa: initial support for MT7628 embedded switch
Date: Sun, 1 Mar 2026 19:23:25 +0200 [thread overview]
Message-ID: <aaRwcIwW9wIKkXDD@archlinux> (raw)
In-Reply-To: <62e825cd-7b5d-4839-a8d7-ae936dfa03fe@lunn.ch>
Hi Andrew,
Thank you for the review.
> Does "special" actually add anything useful to the naming? If there a
> "normal" tag as well? If you where to see a stack trace with
> dsa_user_special_xmit() i would think it was some sort of generic
> code. dsa_user_mt7628_xmit() is more meaningful. Especially when some
> other vendor thinks their silicon is special and want to use that name
> as well.
The "special tag" is just vendor naming. Will update the patches to
consistently refer to it as the MT7628 tag in v2.
> Although phy_read/phy_write still works, all recent DSA drivers have
> declared where own MDIO bus, and called of_mdiobus_register(). That
> would be the preferred solution.
Will fix in v2.
> Do you have any idea what this is actually doing?
>
> Normally, a MAC driver would not touch the PHY. It would be the PHY
> driver which enables workarounds for erratas etc.
>
> Does this PHY support C45 over C22? Can EEE be disabled in the normal
> way, writing to the standard EEE registers?
>
> I would try to put this code into the probe function of a PHY driver.
The PHY init was inherited from OpenWRT, I am yet to figure out the
specifics of what this is doing. I will investigate further and rework
this into a proper PHY driver for v2.
next prev parent reply other threads:[~2026-03-01 17:23 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-02-28 18:52 [RFC 0/2 net-next] net: dsa: MT7628 embedded switch initial support Joris Vaisvila
2026-02-28 18:52 ` [RFC PATCH 1/2 net-next] net: dsa: initial MT7628 special tag driver Joris Vaisvila
2026-02-28 20:12 ` Andrew Lunn
2026-03-04 22:16 ` Vladimir Oltean
2026-02-28 18:52 ` [RFC PATCH 2/2 net-next] net: dsa: initial support for MT7628 embedded switch Joris Vaisvila
2026-02-28 20:16 ` Andrew Lunn
2026-02-28 20:31 ` Andrew Lunn
2026-03-01 17:23 ` Joris Vaišvila [this message]
2026-02-28 23:40 ` [RFC 0/2 net-next] net: dsa: MT7628 embedded switch initial support Vladimir Oltean
2026-03-01 12:00 ` Daniel Golle
2026-03-01 12:36 ` Vladimir Oltean
2026-03-01 13:13 ` Joris Vaišvila
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=aaRwcIwW9wIKkXDD@archlinux \
--to=joey@tinyisr.com \
--cc=andrew@lunn.ch \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=horms@kernel.org \
--cc=kuba@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.