From: sashiko-bot@kernel.org
To: "Christian Marangi" <ansuelsmth@gmail.com>
Cc: conor+dt@kernel.org, devicetree@vger.kernel.org, robh@kernel.org
Subject: Re: [PATCH net-next v9 08/12] of: property: fw_devlink: Add support for "pcs-handle"
Date: Sat, 18 Jul 2026 09:01:18 +0000 [thread overview]
Message-ID: <20260718090119.434621F000E9@smtp.kernel.org> (raw)
In-Reply-To: <20260717065448.1498335-9-ansuelsmth@gmail.com>
Thank you for your contribution! Sashiko AI review found 1 potential issue(s) to consider:
- [High] Adding `pcs-handle` to `fw_devlink` supplier bindings defeats the dynamic 'late PCS provider attach' and hotplug logic in `phylink`.
--
--- Patch [8]: [PATCH net-next v9 08/12] of: property: fw_devlink: Add support for "pcs-handle" ---
commit f6fc253d355d434feccac1a9dee68ebce25d5fe8
Author: Christian Marangi <ansuelsmth@gmail.com>
of: property: fw_devlink: Add support for "pcs-handle"
This commit adds support for parsing the "pcs-handle" binding, allowing
fw_devlink to enforce device dependencies with Ethernet ports.
> diff --git a/drivers/of/property.c b/drivers/of/property.c
> index 72cf12907de03..91c3e3931fa6e 100644
> --- a/drivers/of/property.c
> +++ b/drivers/of/property.c
[ ... ]
> @@ -1571,6 +1572,7 @@ static const struct supplier_bindings of_supplier_bindings[] = {
> { .parse_prop = parse_interrupts, },
> { .parse_prop = parse_interrupt_map, },
> { .parse_prop = parse_access_controllers, },
> + { .parse_prop = parse_pcs_handle, },
[Severity: High]
Does enforcing a strict supplier-consumer dependency here conflict with the
dynamic hotplug and late-attach logic in phylink?
If fw_devlink creates a managed device link for pcs-handle, it enforces strict
boot ordering. This prevents the MAC from probing before the PCS, which blocks
phylink's late-attach feature.
Additionally, because fw_devlink applies DL_FLAG_AUTOREMOVE_CONSUMER, unloading
the PCS module would cause the driver core to unceremoniously unbind the MAC
driver and remove the network interface. This circumvents phylink's graceful
link down handling via phylink_release_pcs().
Since similar properties like phy-handle are intentionally omitted from
of_supplier_bindings to allow for dynamic PHY/PCS presence, should pcs-handle
also be excluded to preserve these phylink features?
> { .parse_prop = parse_regulators, },
> { .parse_prop = parse_gpio, },
> { .parse_prop = parse_gpios, },
--
Sashiko AI review · https://sashiko.dev/#/patchset/20260717065448.1498335-1-ansuelsmth@gmail.com?part=8
next prev parent reply other threads:[~2026-07-18 9:01 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-07-17 6:54 [PATCH net-next v9 00/12] net: pcs: Introduce support for fwnode PCS Christian Marangi
2026-07-17 6:54 ` [PATCH net-next v9 01/12] net: phylink: keep and use MAC supported_interfaces in phylink struct Christian Marangi
2026-07-18 9:01 ` sashiko-bot
2026-07-17 6:54 ` [PATCH net-next v9 02/12] net: phylink: introduce internal phylink PCS handling Christian Marangi
2026-07-18 9:01 ` sashiko-bot
2026-07-17 6:54 ` [PATCH net-next v9 03/12] net: phylink: add phylink_release_pcs() to externally release a PCS Christian Marangi
2026-07-18 9:01 ` sashiko-bot
2026-07-17 6:54 ` [PATCH net-next v9 04/12] net: pcs: implement Firmware node support for PCS driver Christian Marangi
2026-07-18 9:01 ` sashiko-bot
2026-07-17 6:54 ` [PATCH net-next v9 05/12] net: phylink: support late PCS provider attach Christian Marangi
2026-07-18 9:01 ` sashiko-bot
2026-07-17 6:54 ` [PATCH net-next v9 06/12] net: Document PCS subsystem Christian Marangi
2026-07-18 9:01 ` sashiko-bot
2026-07-17 6:54 ` [PATCH net-next v9 07/12] MAINTAINERS: add myself as PCS subsystem maintainer Christian Marangi
2026-07-17 6:54 ` [PATCH net-next v9 08/12] of: property: fw_devlink: Add support for "pcs-handle" Christian Marangi
2026-07-18 9:01 ` sashiko-bot [this message]
2026-07-17 6:54 ` [PATCH net-next v9 09/12] net: phylink: add .pcs_link_down PCS OP Christian Marangi
2026-07-18 9:01 ` sashiko-bot
2026-07-17 6:54 ` [PATCH net-next v9 10/12] dt-bindings: net: pcs: Document support for Airoha Ethernet PCS Christian Marangi
2026-07-17 6:54 ` [PATCH net-next v9 11/12] net: pcs: airoha: add PCS driver for Airoha AN7581 SoC Christian Marangi
2026-07-18 9:01 ` sashiko-bot
2026-07-17 6:54 ` [PATCH net-next v9 12/12] net: airoha: add phylink support Christian Marangi
2026-07-18 9:01 ` 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=20260718090119.434621F000E9@smtp.kernel.org \
--to=sashiko-bot@kernel.org \
--cc=ansuelsmth@gmail.com \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=robh@kernel.org \
--cc=sashiko-reviews@lists.linux.dev \
/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