Re: [RFC PATCH net-next 1/2] dt-bindings: net: ethernet-controller: add phy-needs-host-firmware

On Mon, Sep 07, 2026 at 06:26:31PM +0100, Conor Dooley wrote:

That doesn't seem right, sounds like it should be on the phy if the
behaviour is caused by the phy.

I'll move it to the phy node.

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?

There is no device to identify when the controller connects. The PHY's
MDIO bus is registered by the driver that loads its firmware, seconds
later, so phy-handle points at nothing yet. The chip does answer a
Clause 45 identifier before the firmware runs, I read it on my board, so
identification is not the blocker.

Or based on the fact that the phy has firmware-name.

Nothing carries firmware-name here, the blob names are in the driver. I
can add it to the phy node and key off that instead. Which do you want
in v2?