From: Christian Marangi <ansuelsmth@gmail.com>
To: Andrew Lunn <andrew@lunn.ch>,
Heiner Kallweit <hkallweit1@gmail.com>,
Russell King <linux@armlinux.org.uk>,
"David S. Miller" <davem@davemloft.net>,
Eric Dumazet <edumazet@google.com>,
Jakub Kicinski <kuba@kernel.org>, Paolo Abeni <pabeni@redhat.com>,
Rob Herring <robh+dt@kernel.org>,
Krzysztof Kozlowski <krzysztof.kozlowski+dt@linaro.org>,
Conor Dooley <conor+dt@kernel.org>,
Florian Fainelli <f.fainelli@gmail.com>,
Christian Marangi <ansuelsmth@gmail.com>,
netdev@vger.kernel.org, devicetree@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: [net-next PATCH v3 1/4] dt-bindings: net: phy: Document new LEDs active-low property
Date: Wed, 13 Dec 2023 12:13:19 +0100 [thread overview]
Message-ID: <20231213111322.6152-1-ansuelsmth@gmail.com> (raw)
Document new LEDs active-low property to define if the LED require to be
set low to be turned on.
active-low can be defined in the leds node for PHY that apply the LED
polarity globally for each attached LED or in the specific led node for
PHY that supports setting the LED polarity per LED.
Declaring both way is not supported and will result in the schema
getting rejected.
Signed-off-by: Christian Marangi <ansuelsmth@gmail.com>
---
Changes v3:
- Out of RFC
Changes v2:
- Add this patch
.../devicetree/bindings/net/ethernet-phy.yaml | 20 +++++++++++++++++++
1 file changed, 20 insertions(+)
diff --git a/Documentation/devicetree/bindings/net/ethernet-phy.yaml b/Documentation/devicetree/bindings/net/ethernet-phy.yaml
index 8fb2a6ee7e5b..9cb3981fed2a 100644
--- a/Documentation/devicetree/bindings/net/ethernet-phy.yaml
+++ b/Documentation/devicetree/bindings/net/ethernet-phy.yaml
@@ -213,6 +213,11 @@ properties:
'#size-cells':
const: 0
+ 'active-low':
+ type: boolean
+ description:
+ This define whether all LEDs needs to be low to be turned on.
+
patternProperties:
'^led@[a-f0-9]+$':
$ref: /schemas/leds/common.yaml#
@@ -225,11 +230,26 @@ properties:
driver dependent and required for ports that define multiple
LED for the same port.
+ 'active-low':
+ type: boolean
+ description:
+ This define whether the LED needs to be low to be turned on.
+
required:
- reg
unevaluatedProperties: false
+ allOf:
+ - if:
+ required:
+ - active-low
+ then:
+ patternProperties:
+ '^led@[a-f0-9]+$':
+ properties:
+ 'active-low': false
+
additionalProperties: false
required:
--
2.40.1
next reply other threads:[~2023-12-13 11:13 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-12-13 11:13 Christian Marangi [this message]
2023-12-13 11:13 ` [net-next PATCH v3 2/4] net: phy: add support for PHY LEDs active-low Christian Marangi
2023-12-13 11:13 ` [net-next PATCH v3 3/4] dt-bindings: net: Document QCA808x PHYs Christian Marangi
2023-12-15 14:49 ` Rob Herring
2023-12-13 11:13 ` [net-next PATCH v3 4/4] net: phy: at803x: add LED support for qca808x Christian Marangi
2023-12-15 13:48 ` [net-next PATCH v3 1/4] dt-bindings: net: phy: Document new LEDs active-low property Rob Herring
2023-12-15 15:48 ` Krzysztof Kozlowski
2023-12-15 14:24 ` Christian Marangi
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20231213111322.6152-1-ansuelsmth@gmail.com \
--to=ansuelsmth@gmail.com \
--cc=andrew@lunn.ch \
--cc=conor+dt@kernel.org \
--cc=davem@davemloft.net \
--cc=devicetree@vger.kernel.org \
--cc=edumazet@google.com \
--cc=f.fainelli@gmail.com \
--cc=hkallweit1@gmail.com \
--cc=krzysztof.kozlowski+dt@linaro.org \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@armlinux.org.uk \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=robh+dt@kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).