[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20231220152209.GA229412-robh@kernel.org>
Date: Wed, 20 Dec 2023 09:22:09 -0600
From: Rob Herring <robh@...nel.org>
To: Christian Marangi <ansuelsmth@...il.com>
Cc: Andrew Lunn <andrew@...n.ch>, Heiner Kallweit <hkallweit1@...il.com>, Russell King <linux@...linux.org.uk>, "David S. Miller" <davem@...emloft.net>, Eric Dumazet <edumazet@...gle.com>, Jakub Kicinski <kuba@...nel.org>, Paolo Abeni <pabeni@...hat.com>, Krzysztof Kozlowski <krzysztof.kozlowski+dt@...aro.org>, Conor Dooley <conor+dt@...nel.org>, Florian Fainelli <f.fainelli@...il.com>, netdev@...r.kernel.org, devicetree@...r.kernel.org, linux-kernel@...r.kernel.org, Tobias Waldekranz <tobias@...dekranz.com>
Subject: Re: [net-next PATCH v4 1/4] dt-bindings: net: phy: Document new LEDs
polarity property
On Fri, Dec 15, 2023 at 10:22:41PM +0100, Christian Marangi wrote:
> Document new LEDs polarity property to define what mode the LED needs to
> be put to turn it on.
>
> Currently supported modes are:
>
> - active-low
> - active-high
> - active-low-tristate
> - active-high-tristate
Why is having a polarity unique to LEDs on ethernet PHYs? It's not. We
already have 'active-low' established on several LED bindings. Please
move the definition to leds/common.yaml and extend it. I would simply
add an 'inactive-tristate' boolean property (if there's an actual user).
I do worry this continues to evolve until we've re-created the pinctrl
binding...
Rob
Powered by blists - more mailing lists