From: Joris Vaisvila <joey@tinyisr.com>
To: Andrew Lunn <andrew@lunn.ch>
Cc: netdev@vger.kernel.org, horms@kernel.org, pabeni@redhat.com,
kuba@kernel.org, edumazet@google.com, davem@davemloft.net,
olteanv@gmail.com
Subject: Re: [RFC v2 1/3] net: phy: mediatek: add phy driver for MT7628 built-in Fast Ethernet PHYs
Date: Sat, 21 Mar 2026 13:35:02 +0200 [thread overview]
Message-ID: <ab6AYAnJleA4bIGt@archlinux> (raw)
In-Reply-To: <6e1ef5b2-b380-47d9-99ab-5fcbe4a68ccf@lunn.ch>
Hi Andrew, thanks for the feedback.
On Tue, Mar 17, 2026 at 07:03:03PM +0100, Andrew Lunn wrote:
> > +config MEDIATEK_FE_SOC_PHY
> > + tristate "MediaTek MT7628 SoC Ethernet PHYs"
> > + select PHY_PACKAGE
> > + help
> > + Support for MediaTek MT7628 built-in Fast Ethernet PHYs.
> > +
>
> This file is sorted by tristate string.
>
> It might be best to change:
>
> config MEDIATEK_GE_SOC_PHY
> - tristate "MediaTek SoC Ethernet PHYs"
> + tristate "MediaTek SoC Gigabit Ethernet PHYs"
>
> And then you can add
>
> > +config MEDIATEK_FE_SOC_PHY
> > + tristate "MediaTek SoC Fast Ethernet PHYs"
>
> before?
> Also, why do you have `select PHY_PACKAGE`?
Will fix naming and sorting in v3. PHY_PACKAGE is not needed, remaint
from testing.
> > obj-$(CONFIG_MEDIATEK_2P5GE_PHY) += mtk-2p5ge.o
> > obj-$(CONFIG_MEDIATEK_GE_PHY) += mtk-ge.o
> > obj-$(CONFIG_MEDIATEK_GE_SOC_PHY) += mtk-ge-soc.o
> > +obj-$(CONFIG_MEDIATEK_FE_SOC_PHY) += mtk-fe-soc.o
> > obj-$(CONFIG_MTK_NET_PHYLIB) += mtk-phy-lib.o
>
> Please sort alphabetically.
will fix in v3.
> > +static struct phy_driver mtk_soc_fe_phy_driver[] = {
> > + {
> > + PHY_ID_MATCH_EXACT(MTK_FPHY_ID_MT7628),
> > + .name = "MediaTek MT7628 PHY",
> > + .config_init = mt7628_phy_config_init,
> > + .config_intr = genphy_no_config_intr,
> > + .handle_interrupt = genphy_handle_interrupt_no_ack,
>
> How do interrupts work in this device? Has this been simply
> cut/pasted, or have interrupts been tested using these functions?
>
> Andrew
Misunderstood the function and copied from other drivers, will re-test
and fix or remove in v3.
next prev parent reply other threads:[~2026-03-21 11:35 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-03-14 15:08 [RFC v2 0/3] net: dsa: MT7628 embedded switch initial support Joris Vaisvila
2026-03-14 15:08 ` [RFC v2 1/3] net: phy: mediatek: add phy driver for MT7628 built-in Fast Ethernet PHYs Joris Vaisvila
2026-03-17 18:03 ` Andrew Lunn
2026-03-21 11:35 ` Joris Vaisvila [this message]
2026-03-14 15:08 ` [RFC v2 2/3] net: dsa: initial MT7628 tagging driver Joris Vaisvila
2026-03-14 17:59 ` Daniel Golle
2026-03-14 20:46 ` Joris Vaišvila
2026-03-14 15:08 ` [RFC v2 3/3] net: dsa: initial support for MT7628 embedded switch Joris Vaisvila
2026-03-14 23:41 ` Daniel Golle
2026-03-15 7:02 ` 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=ab6AYAnJleA4bIGt@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.