Re: [RFC PATCH net-next 2/9] dt-bindings: net: ethernet-controller: add slow-to-probe

[sashiko-bot@kernel.org]

Thank you for your contribution! Sashiko AI review found 1 potential issue(s) to consider:
- [Medium] The `slow-to-probe` property describes OS/software behavior (driver loading and boot sequencing) instead of hardware, and lacks an OS-specific prefix.
--

commit f5e8127fdbf6369101e1a77cf0e55acf75f7b643
Author: Aleksei Sviridkin <f@lex.la>

dt-bindings: net: ethernet-controller: add slow-to-probe

This commit adds a slow-to-probe property to the ethernet controller binding.
It allows a port to keep a PHY reference and attach to it later if the driver
or firmware is unavailable during the initial probe.

> diff --git a/Documentation/devicetree/bindings/net/ethernet-controller.yaml b/Documentation/devicetree/bindings/net/ethernet-controller.yaml
> index 1bafd687dcb18..ca82672b6cb38 100644
> --- a/Documentation/devicetree/bindings/net/ethernet-controller.yaml
> +++ b/Documentation/devicetree/bindings/net/ethernet-controller.yaml
> @@ -113,6 +113,15 @@ properties:
>      description:
>        Specifies a reference to a node representing an IEEE 1588 PTP device.
>  
> +  slow-to-probe:
> +    $ref: /schemas/types.yaml#/definitions/flag
> +    description:
> +      The PHY referenced by phy-handle may not exist, or may not have a
> +      usable driver, when this controller connects to it, because the
> +      driver or firmware arrives later (for example from a filesystem
> +      mounted after the controller probed). Instead of failing, keep
> +      the port and connect the PHY once it becomes usable.

[Severity: Medium]
Does this property describe OS-specific software behavior rather than a
hardware configuration?

Since this flag addresses driver loading and boot sequencing (software
state), could it pollute the generic hardware Device Tree ABI by lacking
an OS-specific prefix like linux,?

-- 
Sashiko AI review · https://sashiko.dev/#/patchset/20260829052546.1152446-1-f@lex.la?part=2