Devicetree
 help / color / mirror / Atom feed
From: Claudiu Manoil <claudiu.manoil@nxp.com>
To: netdev@vger.kernel.org
Cc: s32@nxp.com, Rob Herring <robh@kernel.org>,
	Saravana Kannan <saravanak@kernel.org>,
	devicetree@vger.kernel.org
Subject: [PATCH net-next v4 0/6] net: enetc: S32N79 pseudo-MAC (PPM) networking support
Date: Fri, 13 Nov 2026 17:02:31 +0200	[thread overview]
Message-ID: <cover.1794581338.git.claudiu.manoil@nxp.com> (raw)

This series adds networking support for the ENETCv4.4 pseudo-MAC (PPM)
ports found on the NXP S32N79 SoC. On S32N79, the ENETCv4 ports are
not wired to any external PHY/MII; instead they are internal "pseudo-MAC"
links into the on-chip NETC switch. These links are proprietary, expose
no standard IEEE interface, and run at a speed fixed at boot time by the
Port PCR[PSPEED] register.

A key use case is a port that has no "ethernet" DT node at all: NETC is
reached over PCI from a host that probes the ENETC, while the internal
NETC switch it connects to is not owned by Linux. Such a port must have
its fixed link synthesized at probe time.

The driver synthesizes the fixed link directly in C using an of_changeset:
of_changeset_create_node() adds a "fixed-link" subnode onto the PCI
function's dynamic OF node (CONFIG_PCI_DYNAMIC_OF_NODES), with the "speed"
property read from PCR[PSPEED] at probe time and "full-duplex" set.
phylink then picks up the fixed-link node through dev_fwnode().

The series touches three subsystems:
  - net/enetc:  pseudo-MAC fixed-link support, probing of 4.4 devices
                and a fix for more than 6 ring interrupt vectors
  - arm64 dts:  NETC IEP18 ECAM node on S32N79 and its RDB board enable
  - PCI:        a quirk creating the OF node for the ENETC PMAC functions

Because this is primarily a networking feature and the pieces are
interdependent at runtime, it would be most convenient to merge the
whole series through the netdev tree.

Patch 1 has a runtime (not Kconfig) dependency on
CONFIG_PCI_DYNAMIC_OF_NODES; absent that, the pseudo-MAC probe path
fails gracefully with -ENODEV.

v4:
 - Patch 1: made NXP_ENETC4 depend on OF, as OF_DYNAMIC is only
   available with OF; improved the commit message.
 - Patch 2: new, allocates the int_vector array dynamically to prevent
   an out-of-bounds access on S32N79.
 - Patch 3: clarified the commit message.
 - Patches 4-6: no changes.
v3:
 - Patch 1: fixed the CONFIG_OF_DYNAMIC dependency, refactored
   enetc4_add_ppm_fixed_link() as per Wei's feedback, and improved the
   commit message.
 - Patch 3: added sysclk_freq info for the v4.4 ENETC devices.
 - Patches 4-6: no changes.
v2:
 - Switched the fixed-link patch from a DT overlay blob
   (of_overlay_fdt_apply() + a .dtso compiled to .dtbo) to
   of_changeset_create_node(), per review feedback. This drops the
   embedded overlay externs, the Makefile .dtbo wrapping, and the
   OF_OVERLAY Kconfig dependency. The operating speed is now baked
   directly into the changeset-created fixed-link node (read once from
   PCR[PSPEED] at probe time); the phylink get_fixed_state callback is
   no longer needed and was removed.
 - Described why there are two ENETC PF IDs in the commit message, as
   per review.
 - Replaced the 'msi-parent' stub property with 'msi-map', as per H/W
   spec.
 - Reworded the PCI patch commit message to match the fixed-link
   approach (no functional change); added Bjorn's Acked-by.
v1: initial submission.

Link: https://lore.kernel.org/netdev/cover.1793712309.git.claudiu.manoil@nxp.com/

Claudiu Manoil (6):
  net: enetc: Add pseudo-MAC support for ENETCv4 Ports via a fixed-link
    node
  net: enetc: Allocate int_vector array dynamically
  net: enetc: Enable probing of version 4.4 devices
  arm64: dts: s32n79: add NETC IEP18 ECAM node for ENETC PPM ports
  arm64: dts: s32n79-rdb: enable NETC IEP18
  PCI: Create OF node for NXP ENETC pseudo-MAC functions

 arch/arm64/boot/dts/freescale/s32n79-rdb.dts  |   4 +
 arch/arm64/boot/dts/freescale/s32n79.dtsi     |  24 ++++
 drivers/net/ethernet/freescale/enetc/Kconfig  |   2 +
 drivers/net/ethernet/freescale/enetc/enetc.c  |  34 ++++++
 drivers/net/ethernet/freescale/enetc/enetc.h  |   3 +-
 .../net/ethernet/freescale/enetc/enetc4_pf.c  | 109 +++++++++++++++++-
 .../net/ethernet/freescale/enetc/enetc_hw.h   |   4 +-
 .../net/ethernet/freescale/enetc/enetc_pf.h   |   2 +
 .../freescale/enetc/enetc_pf_common.c         |  41 ++++++-
 .../freescale/enetc/enetc_pf_common.h         |   1 +
 drivers/pci/quirks.c                          |   2 +
 11 files changed, 214 insertions(+), 12 deletions(-)

-- 
2.34.1


             reply	other threads:[~2026-11-13 15:16 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-11-13 15:02 Claudiu Manoil [this message]
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-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

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=cover.1794581338.git.claudiu.manoil@nxp.com \
    --to=claudiu.manoil@nxp.com \
    --cc=devicetree@vger.kernel.org \
    --cc=netdev@vger.kernel.org \
    --cc=robh@kernel.org \
    --cc=s32@nxp.com \
    --cc=saravanak@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