mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Conor Dooley <conor@kernel.org>
To: Aleksei Sviridkin <f@lex.la>
Cc: linux@armlinux.org.uk, andrew@lunn.ch, andrew+netdev@lunn.ch,
	hkallweit1@gmail.com, davem@davemloft.net, edumazet@google.com,
	kuba@kernel.org, pabeni@redhat.com, horms@kernel.org,
	robh@kernel.org, krzk+dt@kernel.org, conor+dt@kernel.org,
	netdev@vger.kernel.org, devicetree@vger.kernel.org,
	linux-kernel@vger.kernel.org
Subject: Re: [RFC PATCH net-next 1/2] dt-bindings: net: ethernet-controller: add phy-needs-host-firmware
Date: Mon, 7 Sep 2026 18:26:31 +0100	[thread overview]
Message-ID: <20260907-shallow-universal-b614da6fe0c4@spud> (raw)
In-Reply-To: <20260906174621.4107320-1-f@lex.la>

[-- Attachment #1: Type: text/plain, Size: 2619 bytes --]

On Sun, Sep 06, 2026 at 05:46:18PM +0000, Aleksei Sviridkin wrote:
> A port can reference a PHY that cannot be identified or driven when
> the controller connects to it, because the firmware the chip needs is
> not in hand yet. Such a port is dropped at setup and stays unusable for
> the whole uptime, even though the PHY works seconds later.
> 
> The flag declares that the PHY behind phy-handle is expected to become
> usable only after this controller has probed. A consumer that sees it
> keeps the port and connects the PHY once its driver binds, instead of
> failing the connect. The prefix names the entity, like the other
> properties here that name what they describe rather than the
> controller; a PCS needing firmware would get pcs-needs-host-firmware
> by the same rule.
> 
> It sits on the controller here because that is where the waiting
> happens. The flag says nothing without a phy-handle to qualify, so it
> depends on one; the deprecated phy and phy-device spellings are left
> out, since no tree combines them with a property this new.

That doesn't seem right, sounds like it should be on the phy if the
behaviour is caused by the phy.
In fact, it seems like something that should be determined when the phy
is identified, not really sure why it needs a property at all? Or based
on the fact that the phy has firmware-name.

> 
> Assisted-by: LLM
> Signed-off-by: Aleksei Sviridkin <f@lex.la>
> ---
>  .../devicetree/bindings/net/ethernet-controller.yaml      | 8 ++++++++
>  1 file changed, 8 insertions(+)
> 
> diff --git a/Documentation/devicetree/bindings/net/ethernet-controller.yaml b/Documentation/devicetree/bindings/net/ethernet-controller.yaml
> index 1bafd687dcb1..074c54fa6d78 100644
> --- a/Documentation/devicetree/bindings/net/ethernet-controller.yaml
> +++ b/Documentation/devicetree/bindings/net/ethernet-controller.yaml
> @@ -108,6 +108,13 @@ properties:
>      $ref: "#/properties/phy-handle"
>      deprecated: true
>  
> +  phy-needs-host-firmware:
> +    $ref: /schemas/types.yaml#/definitions/flag
> +    description:
> +      The PHY referenced by phy-handle runs firmware that the host must
> +      load before the PHY can be driven, and so is not usable for as
> +      long as that has not happened.
> +
>    ptp-timer:
>      $ref: /schemas/types.yaml#/definitions/phandle
>      description:
> @@ -240,6 +247,7 @@ properties:
>  
>  dependencies:
>    pcs-handle-names: [pcs-handle]
> +  phy-needs-host-firmware: [phy-handle]
>  
>  allOf:
>    - $ref: /schemas/net/network-class.yaml#
> -- 
> 2.53.0
> 

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 228 bytes --]

  reply	other threads:[~2026-09-07 17:26 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-09-06 17:46 [RFC PATCH net-next 0/2] net: phylink: wait for a PHY that probes after the MAC Aleksei Sviridkin
2026-09-06 17:46 ` [RFC PATCH net-next 1/2] dt-bindings: net: ethernet-controller: add phy-needs-host-firmware Aleksei Sviridkin
2026-09-07 17:26   ` Conor Dooley [this message]
2026-09-07 20:07     ` Aleksei Sviridkin
2026-09-10 15:38     ` Aleksei Sviridkin
2026-09-06 17:46 ` [RFC PATCH net-next 2/2] net: phylink: wait for PHYs that are known to probe late Aleksei Sviridkin

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=20260907-shallow-universal-b614da6fe0c4@spud \
    --to=conor@kernel.org \
    --cc=andrew+netdev@lunn.ch \
    --cc=andrew@lunn.ch \
    --cc=conor+dt@kernel.org \
    --cc=davem@davemloft.net \
    --cc=devicetree@vger.kernel.org \
    --cc=edumazet@google.com \
    --cc=f@lex.la \
    --cc=hkallweit1@gmail.com \
    --cc=horms@kernel.org \
    --cc=krzk+dt@kernel.org \
    --cc=kuba@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux@armlinux.org.uk \
    --cc=netdev@vger.kernel.org \
    --cc=pabeni@redhat.com \
    --cc=robh@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

all inboxes | Powered by JetHome®