netdev - Re: [PATCH net-next v2 1/2] dt-bindings: net: pcs: renesas,rzn1-miic: Add renesas,miic-phylink-active-low property

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Message-ID: <176849776989.913679.4064770470334805366.robh@kernel.org>
Date: Thu, 15 Jan 2026 11:22:50 -0600
From: "Rob Herring (Arm)" <robh@...nel.org>
To: Prabhakar <prabhakar.csengg@...il.com>
Cc: Jakub Kicinski <kuba@...nel.org>, Biju Das <biju.das.jz@...renesas.com>,
	Magnus Damm <magnus.damm@...il.com>,
	Heiner Kallweit <hkallweit1@...il.com>,
	Russell King <linux@...linux.org.uk>,
	Krzysztof Kozlowski <krzk+dt@...nel.org>,
	Andrew Lunn <andrew+netdev@...n.ch>,
	Fabrizio Castro <fabrizio.castro.jz@...esas.com>,
	Eric Dumazet <edumazet@...gle.com>, linux-kernel@...r.kernel.org,
	Geert Uytterhoeven <geert+renesas@...der.be>,
	Clément Léger <clement.leger@...tlin.com>,
	Paolo Abeni <pabeni@...hat.com>, Conor Dooley <conor+dt@...nel.org>,
	Lad Prabhakar <prabhakar.mahadev-lad.rj@...renesas.com>,
	netdev@...r.kernel.org, "David S. Miller" <davem@...emloft.net>,
	linux-renesas-soc@...r.kernel.org, devicetree@...r.kernel.org
Subject: Re: [PATCH net-next v2 1/2] dt-bindings: net: pcs:
 renesas,rzn1-miic: Add renesas,miic-phylink-active-low property


On Fri, 09 Jan 2026 14:22:49 +0000, Prabhakar wrote:
> From: Lad Prabhakar <prabhakar.mahadev-lad.rj@...renesas.com>
> 
> Add the renesas,miic-phylink-active-low property to allow configuring the
> active level of PHY link status signals provided by the MIIC block.
> 
> EtherPHY link-up and link-down status is required as a hardware feature
> independent of whether GMAC or ETHSW is used. With GMAC, link status is
> obtained via MDC/MDIO and handled in software. In contrast, ETHSW exposes
> dedicated PHY link pins that provide this information directly in
> hardware.
> 
> These PHY link signals are required not only for host-controlled traffic
> but also for switch-only forwarding paths where frames are exchanged
> between external nodes without CPU involvement. This is particularly
> important for redundancy protocols such as DLR (Device Level Ring),
> which depend on fast detection of link-down events caused by cable or
> port failures. Handling such events purely in software introduces
> latency, which is why ETHSW provides dedicated hardware link pins.
> 
> Signed-off-by: Lad Prabhakar <prabhakar.mahadev-lad.rj@...renesas.com>
> ---
> v1->v2:
> - Updated commit message to elaborate the necessity of PHY link signals.
> ---
>  .../devicetree/bindings/net/pcs/renesas,rzn1-miic.yaml     | 7 +++++++
>  1 file changed, 7 insertions(+)
> 

Acked-by: Rob Herring (Arm) <robh@...nel.org>