From: Yao Zi <me@ziyao.cc>
To: Tiezhu Yang <yangtiezhu@loongson.cn>, Andrew Lunn <andrew@lunn.ch>
Cc: Maxime Chevallier <maxime.chevallier@bootlin.com>,
Jakub Kicinski <kuba@kernel.org>, Paolo Abeni <pabeni@redhat.com>,
Yao Zi <me@ziyao.cc>,
netdev@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH net-next v1] net: stmmac: Default DWMAC_MOTORCOMM to m on MACH_LOONGSON64
Date: Fri, 18 Sep 2026 07:10:32 +0000 [thread overview]
Message-ID: <aqzj6CV_xl63JFeT@pie> (raw)
In-Reply-To: <36a43b65-f94e-4836-b511-715fb136c10d@loongson.cn>
On Fri, Sep 18, 2026 at 02:48:45PM +0800, Tiezhu Yang wrote:
> On 2026/9/17 下午10:45, Andrew Lunn wrote:
> > > Before moving forward, I'd like to share an alternative thought.
> > > As noted in the earlier review, this network controller could be
> > > used across multiple architectures. To avoid the redundant churn
> > > in the defconfigs of every single architecture, I am wondering if
> > > we could unconditionally set it to default m in the Kconfig instead.
> >
> > ~/linux/drivers/net/ethernet/stmicro/stmmac$ grep default Kconfig
> > default n
> > default y
> > default STMMAC_PLATFORM
> > default ARC
> > default MACH_INGENIC
> > default ARCH_QCOM
> > default ARCH_LPC18XX
> > default ARCH_MESON
> > default ARCH_MA35
> > default ARCH_QCOM
> > default ARCH_RENESAS
> > default ARCH_ROCKCHIP
> > default ARCH_RZN1
> > default ARCH_S32
> > default ARCH_INTEL_SOCFPGA
> > default m if ARCH_SOPHGO
> > default m if ARCH_SPACEMIT
> > default m if ARCH_STARFIVE
> > default ARCH_STI
> > default ARCH_STM32
> > default ARCH_SUNXI
> > default ARCH_SUNXI
> > default ARCH_SUNXI
> > default ARCH_MXC
> > default MACH_LOONGSON32
> > default ARCH_VISCONTI
> > default X86
> > default MACH_LOONGSON64
> >
> > No other glue driver does this. Why is this one special?
>
> If it is not proper to change Kconfig,
> I am fine to modify the arch-specific defconfig instead.
I'm against both of the ideas. From the aspect of a distribution
maintainer, there are too many stuff missing from architecture
defconfigs, so only enabling one or two drivers by default doesn't even
improve the situation much, costs (kernel) maintainers' time.
From the aspect of a kernel developer, a bloated defconfig/default only
further lengthen the compilation process, forcing ones that don't have a
good enough machine to spend more time on turning off one and another
options their platforms don't need.
> But by the way, I noticed that there are the following code:
>
> $ grep -rnw "default m" drivers/net/ethernet/
> drivers/net/ethernet/stmicro/stmmac/Kconfig:221: default m if ARCH_SOPHGO
> drivers/net/ethernet/stmicro/stmmac/Kconfig:233: default m if ARCH_SPACEMIT
> drivers/net/ethernet/stmicro/stmmac/Kconfig:245: default m if ARCH_STARFIVE
> drivers/net/ethernet/spacemit/Kconfig:21: default m if ARCH_SPACEMIT
> drivers/net/ethernet/marvell/octeontx2/Kconfig:54: default m
> drivers/net/ethernet/hisilicon/Kconfig:106: default m
> drivers/net/ethernet/hisilicon/Kconfig:134: default m
> drivers/net/ethernet/sun/Kconfig:77: default m
> drivers/net/ethernet/sun/Kconfig:81: default m
> drivers/net/ethernet/sun/Kconfig:89: default m
> drivers/net/ethernet/mellanox/mlxsw/Kconfig:37: default m
> drivers/net/ethernet/mellanox/mlxsw/Kconfig:47: default m
> drivers/net/ethernet/mellanox/mlxsw/Kconfig:67: default m
> drivers/net/ethernet/mellanox/mlxsw/Kconfig:86: default m
>
> Thanks,
> Tiezhu
>
Best regards,
Yao Zi
next prev parent reply other threads:[~2026-09-18 7:11 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-15 7:32 Tiezhu Yang
2026-09-16 16:49 ` Yao Zi
2026-09-16 16:54 ` Maxime Chevallier
2026-09-17 1:01 ` Tiezhu Yang
2026-09-17 14:45 ` Andrew Lunn
2026-09-18 6:48 ` Tiezhu Yang
2026-09-18 7:10 ` Yao Zi [this message]
2026-09-18 11:53 ` Andrew Lunn
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=aqzj6CV_xl63JFeT@pie \
--to=me@ziyao.cc \
--cc=andrew@lunn.ch \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=maxime.chevallier@bootlin.com \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=yangtiezhu@loongson.cn \
/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®