Linux kernel and device drivers for NXP i.MX platforms
 help / color / mirror / Atom feed
From: sashiko-bot@kernel.org
To: wei.fang@oss.nxp.com
Cc: Frank.Li@kernel.org, imx@lists.linux.dev
Subject: Re: [PATCH v4 net-next 07/14] net: enetc: differentiate phylink capabilities for pseudo-MAC and standalone MAC
Date: Wed, 08 Jul 2026 08:48:29 +0000	[thread overview]
Message-ID: <20260708084829.D6AE21F00A3A@smtp.kernel.org> (raw)
In-Reply-To: <20260707081834.710730-8-wei.fang@oss.nxp.com>

Thank you for your contribution! Sashiko AI review found 1 potential issue(s) to consider:

Pre-existing issues:
- [High] Unhandled PHY_INTERFACE_MODE_1000BASEX in enetc4_mac_config() causes MAC configuration failure.
--

--- Patch [7]: [PATCH v4 net-next 07/14] net: enetc: differentiate phylink capabilities for pseudo-MAC and standalone MAC ---
commit 77043a189039feeceb8a61d08f960e3ed8ff9d08
Author: Claudiu Manoil <claudiu.manoil@nxp.com>

net: enetc: differentiate phylink capabilities for pseudo-MAC and standalone MAC

The ENETC pseudo-MACs are proprietary internal links that do not
implement any standard MII interface, so restrict their supported PHY
interface modes to PHY_INTERFACE_MODE_INTERNAL only. For standalone
ENETC (v4), expand the supported interface modes to include 10GBASER.

> diff --git a/drivers/net/ethernet/freescale/enetc/enetc4_pf.c b/drivers/net/ethernet/freescale/enetc/enetc4_pf.c
> index f24269a48c26b..75ee117e9b1df 100644
> --- a/drivers/net/ethernet/freescale/enetc/enetc4_pf.c
> +++ b/drivers/net/ethernet/freescale/enetc/enetc4_pf.c
> @@ -602,7 +602,6 @@ static void enetc4_mac_config(struct enetc_pf *pf, unsigned int mode,
>  		val |= IFMODE_SGMII;
>  		break;
>  	case PHY_INTERFACE_MODE_10GBASER:
> -	case PHY_INTERFACE_MODE_XGMII:
>  	case PHY_INTERFACE_MODE_USXGMII:
>  		val |= IFMODE_XGMII;
>  		break;

[Severity: High]
This isn't a bug introduced by this patch, but does enetc4_mac_config()
miss handling for PHY_INTERFACE_MODE_1000BASEX?

Since enetc_phylink_create() explicitly advertises support for
PHY_INTERFACE_MODE_1000BASEX, it appears that mode will fall through to
the default branch in this switch statement, printing an error and
aborting MAC configuration.

Could PHY_INTERFACE_MODE_1000BASEX be handled alongside
PHY_INTERFACE_MODE_SGMII and PHY_INTERFACE_MODE_2500BASEX?

-- 
Sashiko AI review · https://sashiko.dev/#/patchset/20260707081834.710730-1-wei.fang@oss.nxp.com?part=7

  reply	other threads:[~2026-07-08  8:48 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-07-07  8:18 [PATCH v4 net-next 00/14] net: enetc: cleanups and improvements wei.fang
2026-07-07  8:18 ` [PATCH v4 net-next 01/14] net: enetc: extract common helpers for MAC promiscuous mode setting wei.fang
2026-07-07  8:18 ` [PATCH v4 net-next 02/14] net: enetc: extract common helpers for MAC hash filter configuration wei.fang
2026-07-08  8:48   ` sashiko-bot
2026-07-07  8:18 ` [PATCH v4 net-next 03/14] net: enetc: convert ndo_set_rx_mode() to ndo_set_rx_mode_async() wei.fang
2026-07-07  8:18 ` [PATCH v4 net-next 04/14] net: enetc: improve MAFT entry management with bitmap tracking wei.fang
2026-07-07  8:18 ` [PATCH v4 net-next 05/14] net: enetc: use PCI device name for debugfs directory wei.fang
2026-07-07  8:18 ` [PATCH v4 net-next 06/14] net: enetc: simplify enetc4_set_port_speed() wei.fang
2026-07-07  8:18 ` [PATCH v4 net-next 07/14] net: enetc: differentiate phylink capabilities for pseudo-MAC and standalone MAC wei.fang
2026-07-08  8:48   ` sashiko-bot [this message]
2026-07-07  8:18 ` [PATCH v4 net-next 08/14] net: enetc: remove invalid code from enetc4_pl_mac_link_up() wei.fang
2026-07-07  8:18 ` [PATCH v4 net-next 09/14] net: enetc: open-code enetc4_set_default_si_vlan_promisc() wei.fang
2026-07-07  8:18 ` [PATCH v4 net-next 10/14] net: enetc: refactor SI VLAN promiscuous mode configuration wei.fang
2026-07-07  8:18 ` [PATCH v4 net-next 11/14] net: enetc: move enetc_set_si_vlan_promisc() to enetc_pf_common.c wei.fang
2026-07-07  8:18 ` [PATCH v4 net-next 12/14] net: enetc: remove redundant num_vsi field from enetc_port_caps wei.fang
2026-07-08  8:48   ` sashiko-bot
2026-07-08 12:01     ` Wei Fang (OSS)
2026-07-07  8:18 ` [PATCH v4 net-next 13/14] net: enetc: use alloc_etherdev_mqs() to create netdev for VF driver wei.fang
2026-07-08  8:48   ` sashiko-bot
2026-07-07  8:18 ` [PATCH v4 net-next 14/14] net: enetc: use kzalloc_flex() for enetc_psfp_gate allocation wei.fang
2026-07-08  8:48   ` 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=20260708084829.D6AE21F00A3A@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