netdev - Re: [PATCH v1 1/3] dt-bindings: net: dsa: microchip: add microchip,single-led-mode flag

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] [thread-next>] [day] [month] [year] [list]

Message-ID: <da974b72-8ba7-46b8-ac21-86a2fa26e22d@twx-software.de>
Date: Wed, 28 Jan 2026 16:53:29 +0100
From: Heinrich Töws (TWx) <ht@...-software.de>
To: Andrew Lunn <andrew@...n.ch>
Cc: netdev@...r.kernel.org, f.fainelli@...il.com, olteanv@...il.com,
 robh+dt@...nel.org, krzysztof.kozlowski+dt@...aro.org
Subject: Re: [PATCH v1 1/3] dt-bindings: net: dsa: microchip: add
 microchip,single-led-mode flag

Hi Andrew,

Am 28.01.26 um 16:22 schrieb Andrew Lunn:
> Is that really true? Generally, what actually happens is the
> configuration is left alone. So if the boot loader, for example, has
> set the configuration, that configuration is left unchanged. So it
> could actually be in single LED mode, not tri-colour.

Oh, you're right. We cannot assume a hardware reset state here.
Since the driver currently does not touch these registers, the 
configuration is indeed "inherited" from the bootloader or the
hardware strapping.

Thanks,

Heinrich.