[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <41567aec-adf2-422a-867e-9087ef33ef36@lunn.ch>
Date: Sat, 20 Apr 2024 18:10:35 +0200
From: Andrew Lunn <andrew@...n.ch>
To: Josua Mayer <josua@...id-run.com>
Cc: Michael Hennerich <michael.hennerich@...log.com>,
"David S. Miller" <davem@...emloft.net>,
Eric Dumazet <edumazet@...gle.com>,
Jakub Kicinski <kuba@...nel.org>, Paolo Abeni <pabeni@...hat.com>,
Rob Herring <robh@...nel.org>,
Krzysztof Kozlowski <krzysztof.kozlowski+dt@...aro.org>,
Conor Dooley <conor+dt@...nel.org>,
Alexandru Tachici <alexandru.tachici@...log.com>,
Heiner Kallweit <hkallweit1@...il.com>,
Russell King <linux@...linux.org.uk>,
Jon Nettleton <jon@...id-run.com>,
Yazan Shhady <yazan.shhady@...id-run.com>, netdev@...r.kernel.org,
devicetree@...r.kernel.org, linux-kernel@...r.kernel.org
Subject: Re: [PATCH net-next v2 1/2] dt-bindings: net: adin: add property for
link-status pin polarity
> + adi,link-st-polarity:
> + $ref: /schemas/types.yaml#/definitions/uint32
> + description:
> + LINK_ST pin polarity.
> + enum:
> + - 0 # active high
> + - 1 # active low
> + default: 0
> +
How does this differ from:
Documentation/devicetree/bindings/leds/common.yaml
+ active-low:
+ type: boolean
+ description:
+ Makes LED active low. To turn the LED ON, line needs to be
+ set to low voltage instead of high.
Why do we need a vendor property when there is a generic property?
Andrew
Powered by blists - more mailing lists