[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <74cb1d1c-64b8-4fb0-9e6d-c2fad8417232@lunn.ch>
Date: Fri, 15 Dec 2023 12:19:59 +0100
From: Andrew Lunn <andrew@...n.ch>
To: Tobias Waldekranz <tobias@...dekranz.com>
Cc: davem@...emloft.net, kuba@...nel.org, linux@...linux.org.uk,
kabel@...nel.org, hkallweit1@...il.com, robh+dt@...nel.org,
krzysztof.kozlowski+dt@...aro.org, conor+dt@...nel.org,
netdev@...r.kernel.org, devicetree@...r.kernel.org
Subject: Re: [PATCH net-next 4/4] dt-bindings: net: marvell10g: Document LED
polarity
> + properties:
> + marvell,polarity:
> + description: |
> + Electrical polarity and drive type for this LED. In the
> + active state, hardware may drive the pin either low or
> + high. In the inactive state, the pin can either be
> + driven to the opposite logic level, or be tristated.
> + $ref: /schemas/types.yaml#/definitions/string
> + enum:
> + - active-low
> + - active-high
> + - active-low-tristate
> + - active-high-tristate
Christian is working on adding a generic active-low property, which
any PHY LED could use. The assumption being if the bool property is
not present, it defaults to active-high.
So we should consider, how popular are these two tristate values? Is
this a Marvell only thing, or do other PHYs also have them? Do we want
to make them part of the generic PHY led binding? Also, is an enum the
correct representation? Maybe tristate should be another bool
property? Hi/Low and tristate seem to be orthogonal, so maybe two
properties would make it cleaner with respect to generic properties?
Please work with Christian on this.
Thanks
Andrew
Powered by blists - more mailing lists