[<prev] [next>] [day] [month] [year] [list]
Message-ID: <CAJ+vNU32MJA_YqX6Q3XVZViYrZZQD+ro83dUyRP+t57taghrWA@mail.gmail.com>
Date: Fri, 30 Jan 2026 11:19:30 -0800
From: Tim Harvey <tharvey@...eworks.com>
To: netdev <netdev@...r.kernel.org>, Heinrich Toews <ht@...-software.de>,
Andrew Lunn <andrew@...n.ch>
Cc: Florian Fainelli <f.fainelli@...il.com>, Vladimir Oltean <olteanv@...il.com>,
Rob Herring <robh+dt@...nel.org>,
Krzysztof Kozlowski <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.
Hi Heinrich,
The setting the SW_RESET bit of REG_SW_OPERATION in
ksz9477_reset_switch() resets all switch registers so even when the
mode/errata are taken care of in boot firmware that gets clobbered
when Linux starts. It is not inherited.
I have this switch with single-led mode on two of the boards I support
(imx8mp-venice-gw74xx.dts and imx8mm-venice-gw7901.dts) and am
interested in seeing your v2 of this series. Please add me to the cc
if you would not mind.
Best Regards,
Tim
Powered by blists - more mailing lists