From: Andrew Lunn <andrew@lunn.ch>
To: Thangaraj.S@microchip.com
Cc: netdev@vger.kernel.org, andrew+netdev@lunn.ch,
davem@davemloft.net, edumazet@google.com, kuba@kernel.org,
pabeni@redhat.com, Bryan.Whitehead@microchip.com,
UNGLinuxDriver@microchip.com, linux@armlinux.org.uk,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH v4 2/5] net: lan743x: read SFP straps from PCI11x1x device
Date: Mon, 1 Jun 2026 14:41:24 +0200 [thread overview]
Message-ID: <e6ef6386-47e2-4a96-ad89-bcf018d794fe@lunn.ch> (raw)
In-Reply-To: <DSWPR11MB97156347E4D54CC898A1CA43EC152@DSWPR11MB9715.namprd11.prod.outlook.com>
> > In practice distributions turn on nearly everything. So the code is likely to be
> > built. Rather than a Kconfig symbol, can you move the code into a module,
> > which only gets loaded for pci11x1x?
> [Thangaraj Samynathan] Thanks for the suggestion. We agree this is a reasonable direction.
> For this series, CONFIG_LAN743X_SFP addresses the dependency concern.
> For distro builds that enable most options, a separate module would
> typically be built and loaded as well, so the practical result is the
> same.
Not necessarily. You have a strapping pin, which indicates if the
hardware has been designed for SFP. Use that to load the kernel module
with all the SFP code.
Maybe also go talk to Marketing. What has this device been designed
for and what applications is it marketed towards? You talk about Intel
drivers. They are used in servers and desktop machines. You generally
don't worry too much about code size for those targets, there is a lot
of RAM available. However, if the target market is deeply embedded,
RAM can be short. However, why would use pick an embedded SoC which
does not have integrated Ethernet? Pretty much all embedded SoCs do.
Make the architecture fit the use case.
Andrew
next prev parent reply other threads:[~2026-06-01 12:41 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-05-14 10:50 [PATCH v4 0/5] net: lan743x: Add SFP support for PCI11x1x Thangaraj Samynathan
2026-05-14 10:50 ` [PATCH v4 1/5] net: lan743x: rename is_sgmii_en to is_pcs_en Thangaraj Samynathan
2026-05-14 12:38 ` Andrew Lunn
2026-05-27 6:21 ` Thangaraj.S
2026-05-14 10:50 ` [PATCH v4 2/5] net: lan743x: read SFP straps from PCI11x1x device Thangaraj Samynathan
2026-05-14 12:47 ` Andrew Lunn
2026-05-27 7:08 ` Thangaraj.S
2026-05-27 13:23 ` Andrew Lunn
2026-06-01 6:10 ` Thangaraj.S
2026-06-01 12:41 ` Andrew Lunn [this message]
2026-06-05 0:10 ` Ronnie.Kunin
2026-05-14 10:50 ` [PATCH v4 3/5] net: lan743x: Add support to software-nodes for SFP Thangaraj Samynathan
2026-05-14 12:57 ` Andrew Lunn
2026-05-14 13:02 ` Andrew Lunn
2026-05-27 7:28 ` Thangaraj.S
2026-05-27 13:29 ` Andrew Lunn
2026-05-14 10:50 ` [PATCH v4 4/5] net: lan743x: Register SFP platform device for PCI11x1x Thangaraj Samynathan
2026-05-14 10:50 ` [PATCH v4 5/5] net: lan743x: Add PCS/XPCS support for SFP on PCI11x1x Thangaraj Samynathan
2026-05-14 13:16 ` 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=e6ef6386-47e2-4a96-ad89-bcf018d794fe@lunn.ch \
--to=andrew@lunn.ch \
--cc=Bryan.Whitehead@microchip.com \
--cc=Thangaraj.S@microchip.com \
--cc=UNGLinuxDriver@microchip.com \
--cc=andrew+netdev@lunn.ch \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@armlinux.org.uk \
--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®