From: sashiko-bot@kernel.org
To: wei.fang@oss.nxp.com
Cc: imx@lists.linux.dev, Frank.Li@kernel.org
Subject: Re: [PATCH v3 net-next 07/14] net: enetc: differentiate phylink capabilities for pseudo-MAC and standalone MAC
Date: Sat, 04 Jul 2026 10:43:44 +0000 [thread overview]
Message-ID: <20260704104345.5B94F1F00A3A@smtp.kernel.org> (raw)
In-Reply-To: <20260703101328.550714-8-wei.fang@oss.nxp.com>
Thank you for your contribution! Sashiko AI review found 1 potential issue(s) to consider:
- [High] Adding PHY_INTERFACE_MODE_10GBASER to `enetc_port_has_pcs()` causes ENETC v4 probe to fail because `.create_pcs` is not implemented.
--
commit 394f96d762ecbfe37dfe5cfd42c152159d4e5353
Author: Claudiu Manoil <claudiu.manoil@nxp.com>
net: enetc: differentiate phylink capabilities for pseudo-MAC and standalone MAC
This commit differentiates phylink capabilities between ENETC pseudo-MACs and
standalone MACs. It restricts pseudo-MACs to internal mode while configuring a
wide range of speeds, and expands standalone ENETC (v4) to support 10GBASER
mode.
> diff --git a/drivers/net/ethernet/freescale/enetc/enetc_pf_common.c b/drivers/net/ethernet/freescale/enetc/enetc_pf_common.c
> index 3597cb81a7ccb..781b22198ca86 100644
> --- a/drivers/net/ethernet/freescale/enetc/enetc_pf_common.c
> +++ b/drivers/net/ethernet/freescale/enetc/enetc_pf_common.c
> @@ -359,7 +359,8 @@ static bool enetc_port_has_pcs(struct enetc_pf *pf)
> return (pf->if_mode == PHY_INTERFACE_MODE_SGMII ||
> pf->if_mode == PHY_INTERFACE_MODE_1000BASEX ||
> pf->if_mode == PHY_INTERFACE_MODE_2500BASEX ||
> - pf->if_mode == PHY_INTERFACE_MODE_USXGMII);
> + pf->if_mode == PHY_INTERFACE_MODE_USXGMII ||
> + pf->if_mode == PHY_INTERFACE_MODE_10GBASER);
> }
[Severity: High]
Will adding PHY_INTERFACE_MODE_10GBASER here cause the ENETC v4 probe to fail?
If enetc_port_has_pcs() returns true for 10gbase-r, enetc_mdiobus_create()
will call enetc_imdio_create(), which does this check:
enetc_imdio_create() {
...
if (!pf->ops->create_pcs) {
dev_err(dev, "Creating PCS is not supported\n");
return -EOPNOTSUPP;
}
...
}
Since enetc4_pf_ops doesn't appear to implement .create_pcs, will device
initialization now fail entirely with -EOPNOTSUPP when configured with
the newly supported 10GBASER mode?
> @@ -400,25 +401,42 @@ int enetc_phylink_create(struct enetc_ndev_priv *priv, struct device_node *node,
[ ... ]
> + if (!is_enetc_rev1(priv->si)) {
> + mac_caps |= MAC_5000FD | MAC_10000FD;
> + __set_bit(PHY_INTERFACE_MODE_10GBASER,
> + pf->phylink_config.supported_interfaces);
> + }
> +
> + phy_interface_set_rgmii(pf->phylink_config.supported_interfaces);
> + } else {
> + mac_caps |= MAC_10FD | MAC_100FD | MAC_1000FD | MAC_2500FD |
> + MAC_5000FD | MAC_10000FD | MAC_20000FD |
> + MAC_25000FD;
> + }
> +
> + pf->phylink_config.mac_capabilities = mac_caps;
> phylink = phylink_create(&pf->phylink_config, of_fwnode_handle(node),
> pf->if_mode, ops);
--
Sashiko AI review · https://sashiko.dev/#/patchset/20260703101328.550714-1-wei.fang@oss.nxp.com?part=7
next prev parent reply other threads:[~2026-07-04 10:43 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-07-03 10:13 [PATCH v3 net-next 00/14] net: enetc: cleanups and improvements wei.fang
2026-07-03 10:13 ` [PATCH v3 net-next 01/14] net: enetc: extract common helpers for MAC promiscuous mode setting wei.fang
2026-07-03 10:13 ` [PATCH v3 net-next 02/14] net: enetc: extract common helpers for MAC hash filter configuration wei.fang
2026-07-04 10:43 ` sashiko-bot
2026-07-03 10:13 ` [PATCH v3 net-next 03/14] net: enetc: convert ndo_set_rx_mode() to ndo_set_rx_mode_async() wei.fang
2026-07-03 10:13 ` [PATCH v3 net-next 04/14] net: enetc: improve MAFT entry management with bitmap tracking wei.fang
2026-07-03 10:13 ` [PATCH v3 net-next 05/14] net: enetc: use PCI device name for debugfs directory wei.fang
2026-07-03 10:13 ` [PATCH v3 net-next 06/14] net: enetc: simplify enetc4_set_port_speed() wei.fang
2026-07-03 10:13 ` [PATCH v3 net-next 07/14] net: enetc: differentiate phylink capabilities for pseudo-MAC and standalone MAC wei.fang
2026-07-04 10:43 ` sashiko-bot [this message]
2026-07-06 1:25 ` Wei Fang (OSS)
2026-07-03 10:13 ` [PATCH v3 net-next 08/14] net: enetc: remove invalid code from enetc4_pl_mac_link_up() wei.fang
2026-07-03 10:13 ` [PATCH v3 net-next 09/14] net: enetc: open-code enetc4_set_default_si_vlan_promisc() wei.fang
2026-07-03 10:13 ` [PATCH v3 net-next 10/14] net: enetc: refactor SI VLAN promiscuous mode configuration wei.fang
2026-07-04 10:43 ` sashiko-bot
2026-07-06 1:42 ` Wei Fang (OSS)
2026-07-06 1:45 ` Wei Fang (OSS)
2026-07-03 10:13 ` [PATCH v3 net-next 11/14] net: enetc: move enetc_set_si_vlan_promisc() to enetc_pf_common.c wei.fang
2026-07-03 10:13 ` [PATCH v3 net-next 12/14] net: enetc: remove redundant num_vsi field from enetc_port_caps wei.fang
2026-07-04 10:43 ` sashiko-bot
2026-07-06 2:27 ` Wei Fang (OSS)
2026-07-03 10:13 ` [PATCH v3 net-next 13/14] net: enetc: use alloc_etherdev_mqs() to create netdev for VF driver wei.fang
2026-07-04 10:43 ` sashiko-bot
2026-07-03 10:13 ` [PATCH v3 net-next 14/14] net: enetc: use kzalloc_flex() for enetc_psfp_gate allocation wei.fang
2026-07-04 10:43 ` sashiko-bot
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=20260704104345.5B94F1F00A3A@smtp.kernel.org \
--to=sashiko-bot@kernel.org \
--cc=Frank.Li@kernel.org \
--cc=imx@lists.linux.dev \
--cc=sashiko-reviews@lists.linux.dev \
--cc=wei.fang@oss.nxp.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