From: Tiezhu Yang <yangtiezhu@loongson.cn>
To: Maxime Chevallier <maxime.chevallier@bootlin.com>,
Jakub Kicinski <kuba@kernel.org>, Paolo Abeni <pabeni@redhat.com>,
Yao Zi <me@ziyao.cc>
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: Thu, 17 Sep 2026 09:01:44 +0800 [thread overview]
Message-ID: <f6b93b98-e0d3-9e28-e366-4df126e6ab5f@loongson.cn> (raw)
In-Reply-To: <90a666a8-9f6a-4640-a219-731f3d551c66@bootlin.com>
On 2026/9/17 上午12:54, Maxime Chevallier wrote:
> Hi
>
> On 9/15/26 09:32, Tiezhu Yang wrote:
>> Currently, there is no network connectivity when upgrading to the
>> latest upstream mainline kernel on certain Loongson machines such
>> as Loongson-3C6000 server, because the driver for the onboard NIC
>> is not enabled.
>>
>> Enable the Motorcomm PCI DWMAC driver as a module by default when
>> building for the Loongson-64 platform.
>>
>> This ensures out-of-the-box support for Motorcomm YT6801 Ethernet
>> controllers on Loongson machines, enabling demand-loading without
>> increasing the core kernel image size.
>>
>> Signed-off-by: Tiezhu Yang <yangtiezhu@loongson.cn>
>> ---
>> drivers/net/ethernet/stmicro/stmmac/Kconfig | 1 +
>> 1 file changed, 1 insertion(+)
>>
>> diff --git a/drivers/net/ethernet/stmicro/stmmac/Kconfig b/drivers/net/ethernet/stmicro/stmmac/Kconfig
>> index ab3c4cf96423..c86d6c08977c 100644
>> --- a/drivers/net/ethernet/stmicro/stmmac/Kconfig
>> +++ b/drivers/net/ethernet/stmicro/stmmac/Kconfig
>> @@ -408,6 +408,7 @@ config DWMAC_LOONGSON
>>
>> config DWMAC_MOTORCOMM
>> tristate "Motorcomm PCI DWMAC support"
>> + default m if MACH_LOONGSON64
>> depends on PCI
>> select MOTORCOMM_PHY
>> select STMMAC_LIBPCI
>
> I agree with Yao Zi, this belongs in your .config, maybe your
> defconfig, but not in the stmmac Kconfig.
Thanks for the constructive suggestions.
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.
Please let me know whether it makes sense:
```
diff --git a/drivers/net/ethernet/stmicro/stmmac/Kconfig
b/drivers/net/ethernet/stmicro/stmmac/Kconfig
index ab3c4cf96423..bea18cb4b697 100644
--- a/drivers/net/ethernet/stmicro/stmmac/Kconfig
+++ b/drivers/net/ethernet/stmicro/stmmac/Kconfig
@@ -408,6 +408,7 @@ config DWMAC_LOONGSON
config DWMAC_MOTORCOMM
tristate "Motorcomm PCI DWMAC support"
+ default m
depends on PCI
select MOTORCOMM_PHY
select STMMAC_LIBPCI
```
If no, I will modify the arch-specific config.
Thanks,
Tiezhu
next prev parent reply other threads:[~2026-09-17 1:01 UTC|newest]
Thread overview: 5+ 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 [this message]
2026-09-17 14:45 ` 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=f6b93b98-e0d3-9e28-e366-4df126e6ab5f@loongson.cn \
--to=yangtiezhu@loongson.cn \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=maxime.chevallier@bootlin.com \
--cc=me@ziyao.cc \
--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
all inboxes | Powered by JetHome®