From: Claudiu Manoil <claudiu.manoil@nxp.com>
To: "netdev-bot+sashiko@kernel.org" <netdev-bot+sashiko@kernel.org>
Cc: "netdev@vger.kernel.org" <netdev@vger.kernel.org>,
dl-S32 <S32@nxp.com>, "bhelgaas@google.com" <bhelgaas@google.com>,
"linux-pci@vger.kernel.org" <linux-pci@vger.kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"kuba@kernel.org" <kuba@kernel.org>
Subject: RE: [PATCH net-next v4 6/6] PCI: Create OF node for NXP ENETC pseudo-MAC functions
Date: Wed, 18 Nov 2026 16:49:51 +0000 [thread overview]
Message-ID: <GV2PR04MB117403B25990A8A4E558DB0B4967A2@GV2PR04MB11740.eurprd04.prod.outlook.com> (raw)
In-Reply-To: <179493091275.3136.9482657927785539194@kernel.org>
From: netdev-bot+sashiko@kernel.org <netdev-bot+sashiko@kernel.org>
Sent: Tuesday, November 17, 2026 5:55 PM
> To: Claudiu Manoil <claudiu.manoil@nxp.com>
> Cc: netdev@vger.kernel.org; dl-S32 <S32@nxp.com>; bhelgaas@google.com;
> linux-pci@vger.kernel.org; linux-kernel@vger.kernel.org; kuba@kernel.org
> Subject: Re: [PATCH net-next v4 6/6] PCI: Create OF node for NXP ENETC
> pseudo-MAC functions
>
> Thank you for your contribution! Sashiko AI review found 2 potential
> issue(s) to consider.
>
> Critical: 0 * High: 0 * Medium: 1 * Low: 1
>
> If you believe none of the issues are legitimate, please reply to each
> issue of Medium severity or higher and explain why the AI is wrong.
> If any of them are legitimate and you plan to respin, please let patchwork
> know by including "pw-bot: cr" as a separate line at the end of your reply
> (one such reply per series is enough).
>
> - [Medium] The two new fixups for 0xe101 and 0xe110 in
> drivers/pci/quirks.c only do something when...
> - [Low] The comment above the of_pci_make_dev_node() fixup block in
> drivers/pci/quirks.c (lines 6553-6560) gives one reason for the...
>
> --
>
> PCI: Create OF node for NXP ENETC pseudo-MAC functions
>
> This commit registers of_pci_make_dev_node() as a final fixup for the NXP
> ENETC4 PCI device IDs 0xe101 and 0xe110. The new per-function OF node lets
> the ENETC4 driver attach a fixed-link child to pseudo-MAC ports that have
> no static DT node. The fixup only does anything when
> CONFIG_PCI_DYNAMIC_OF_NODES is enabled.
>
> > diff --git a/drivers/pci/quirks.c b/drivers/pci/quirks.c
> > index 7f1f47ea2ee41..71f272d8a2965 100644
> > --- a/drivers/pci/quirks.c
> > +++ b/drivers/pci/quirks.c
> > @@ -6563,6 +6563,8 @@
> DECLARE_PCI_FIXUP_FINAL(PCI_VENDOR_ID_XILINX, 0x5021,
> of_pci_make_dev_node);
> > DECLARE_PCI_FIXUP_FINAL(PCI_VENDOR_ID_REDHAT, 0x0005,
> of_pci_make_dev_node);
> > DECLARE_PCI_FIXUP_FINAL(PCI_VENDOR_ID_EFAR, 0x9660,
> of_pci_make_dev_node);
> > DECLARE_PCI_FIXUP_FINAL(PCI_VENDOR_ID_TOSHIBA, 0x0220,
> of_pci_make_dev_node);
> > +DECLARE_PCI_FIXUP_FINAL(PCI_VENDOR_ID_PHILIPS, 0xe101,
> of_pci_make_dev_node);
> > +DECLARE_PCI_FIXUP_FINAL(PCI_VENDOR_ID_PHILIPS, 0xe110,
> of_pci_make_dev_node);
>
> [Severity: Medium]
> With the default arm64 config, will these fixups do anything on the
> S32N79 platform this series targets?
>
> If CONFIG_PCI_DYNAMIC_OF_NODES is not set, of_pci_make_dev_node() is
> an
> empty stub:
>
> drivers/pci/pci.h:
> #else
> static inline void of_pci_make_dev_node(struct pci_dev *pdev) { }
>
> PCI_DYNAMIC_OF_NODES is a user-visible bool, and nothing in the tree
> selects it. NXP_ENETC4 selects OF_DYNAMIC, so there is no build problem.
> However, it does not select or imply PCI_DYNAMIC_OF_NODES.
>
> arch/arm64/configs/defconfig sets CONFIG_ARCH_S32=y and
> CONFIG_NXP_ENETC4=m, but it does not set PCI_DYNAMIC_OF_NODES.
>
> The s32n79.dtsi change in this series adds netc_iep18 without child nodes
> for the PCI functions. So dev->of_node stays NULL for the pseudo-MAC PF,
> and enetc4_link_init() fails the probe:
>
> drivers/net/ethernet/freescale/enetc/enetc4_pf.c:enetc4_link_init() {
> ...
> if (!node) {
> dev_err(dev, "Missing of_node for Pseudo-MAC
> port\n");
> return -ENODEV;
> }
> ...
> }
>
> This error message does not mention the missing config option.
>
> So with the default arm64 config, "arm64: dts: s32n79-rdb: enable NETC
> IEP18" does not get the PPM PF/VF instances probed, which is what it sets
> out to do.
>
> The commit messages say this dependency is intentional, because the
> driver also handles ports described by static DT. That is a reason not to
> add a hard "depends on". Would an "imply PCI_DYNAMIC_OF_NODES" on
> NXP_ENETC4, or a defconfig update, work instead? The Kconfig help text
> notes that turning the option on also creates OF nodes for all PCI
> bridges.
Same reply as here, for v2:
https://lore.kernel.org/all/GV2PR04MB117408067A4647C476FAD617596692@GV2PR04MB11740.eurprd04.prod.outlook.com/
CONFIG_PCI_DYNAMIC_OF_NODES is not a hard Kconfig dependency
because only the newly introduced S32N79 chip makes use of this feature
currently. This is intentional. So, this config will be enabled only for S32N79
platforms, for now, separately.
prev parent reply other threads:[~2026-11-18 16:49 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <cover.1794581338.git.claudiu.manoil@nxp.com>
2026-11-13 15:02 ` [PATCH net-next v4 1/6] net: enetc: Add pseudo-MAC support for ENETCv4 Ports via a fixed-link node Claudiu Manoil
2026-11-17 15:55 ` netdev-bot+sashiko
2026-11-18 16:11 ` Claudiu Manoil
2026-11-13 15:02 ` [PATCH net-next v4 2/6] net: enetc: Allocate int_vector array dynamically Claudiu Manoil
2026-11-13 15:02 ` [PATCH net-next v4 3/6] net: enetc: Enable probing of version 4.4 devices Claudiu Manoil
2026-11-17 15:55 ` netdev-bot+sashiko
2026-11-18 15:43 ` Claudiu Manoil
2026-11-13 15:02 ` [PATCH net-next v4 4/6] arm64: dts: s32n79: add NETC IEP18 ECAM node for ENETC PPM ports Claudiu Manoil
2026-11-13 15:02 ` [PATCH net-next v4 5/6] arm64: dts: s32n79-rdb: enable NETC IEP18 Claudiu Manoil
2026-11-17 15:55 ` netdev-bot+sashiko
2026-11-18 16:40 ` Claudiu Manoil
2026-11-13 15:02 ` [PATCH net-next v4 6/6] PCI: Create OF node for NXP ENETC pseudo-MAC functions Claudiu Manoil
2026-11-17 15:55 ` netdev-bot+sashiko
2026-11-18 16:49 ` Claudiu Manoil [this message]
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=GV2PR04MB117403B25990A8A4E558DB0B4967A2@GV2PR04MB11740.eurprd04.prod.outlook.com \
--to=claudiu.manoil@nxp.com \
--cc=S32@nxp.com \
--cc=bhelgaas@google.com \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pci@vger.kernel.org \
--cc=netdev-bot+sashiko@kernel.org \
--cc=netdev@vger.kernel.org \
/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®