From: "Marek Behún" <marek.behun@nic.cz>
To: netdev@vger.kernel.org
Cc: linux-leds@vger.kernel.org, "Pavel Machek" <pavel@ucw.cz>,
"Dan Murphy" <dmurphy@ti.com>,
"Ondřej Jirman" <megous@megous.com>,
"Russell King" <linux@armlinux.org.uk>,
"Andrew Lunn" <andrew@lunn.ch>,
linux-kernel@vger.kernel.org,
"Matthias Schiffer" <matthias.schiffer@ew.tq-group.com>,
"Marek Behún" <marek.behun@nic.cz>,
"Rob Herring" <robh+dt@kernel.org>
Subject: [PATCH net-next v1 1/3] dt-bindings: net: ethernet-phy: add description for PHY LEDs
Date: Tue, 8 Sep 2020 02:02:58 +0200 [thread overview]
Message-ID: <20200908000300.6982-2-marek.behun@nic.cz> (raw)
In-Reply-To: <20200908000300.6982-1-marek.behun@nic.cz>
Document binding for LEDs connected to and controlled by ethernet PHY
chips.
Signed-off-by: Marek Behún <marek.behun@nic.cz>
Cc: Rob Herring <robh+dt@kernel.org>
---
.../devicetree/bindings/net/ethernet-phy.yaml | 31 +++++++++++++++++++
1 file changed, 31 insertions(+)
diff --git a/Documentation/devicetree/bindings/net/ethernet-phy.yaml b/Documentation/devicetree/bindings/net/ethernet-phy.yaml
index a9e547ac79051..11839265cc2f9 100644
--- a/Documentation/devicetree/bindings/net/ethernet-phy.yaml
+++ b/Documentation/devicetree/bindings/net/ethernet-phy.yaml
@@ -174,6 +174,37 @@ properties:
PHY's that have configurable TX internal delays. If this property is
present then the PHY applies the TX delay.
+patternProperties:
+ "^led@[0-9a-f]+$":
+ type: object
+ description:
+ This node represents a LED device connected to the PHY chip.
+ $ref: /schemas/leds/common.yaml#
+
+ properties:
+ reg:
+ maxItems: 1
+
+ enable-active-high:
+ description:
+ Polarity of LED is active high. If missing, assumed default is active low.
+ type: boolean
+
+ led-open-drain:
+ description:
+ LED pin is open drain type. If missing, assumed false.
+ type: boolean
+
+ linux,default-hw-mode:
+ description:
+ This parameter, if present, specifies the default HW triggering mode of the LED
+ when LED trigger is set to `phydev-hw-mode`.
+ Available values are specific per PHY chip and per LED.
+ $ref: /schemas/types.yaml#definitions/string
+
+ required:
+ - reg
+
required:
- reg
--
2.26.2
next prev parent reply other threads:[~2020-09-08 0:03 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-09-08 0:02 [PATCH net-next v1 0/3] Add support for LEDs on Marvell PHYs Marek Behún
2020-09-08 0:02 ` Marek Behún [this message]
2020-09-08 22:02 ` [PATCH net-next v1 1/3] dt-bindings: net: ethernet-phy: add description for PHY LEDs Marek Behun
2020-09-08 22:03 ` Marek Behun
2020-09-08 0:02 ` [PATCH net-next v1 2/3] net: phy: add API for LEDs controlled by ethernet PHY chips Marek Behún
2020-09-10 2:27 ` kernel test robot
2020-10-04 9:58 ` Pavel Machek
2020-09-08 0:03 ` [PATCH net-next v1 3/3] net: phy: marvell: add support for LEDs controlled by Marvell PHYs Marek Behún
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=20200908000300.6982-2-marek.behun@nic.cz \
--to=marek.behun@nic.cz \
--cc=andrew@lunn.ch \
--cc=dmurphy@ti.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-leds@vger.kernel.org \
--cc=linux@armlinux.org.uk \
--cc=matthias.schiffer@ew.tq-group.com \
--cc=megous@megous.com \
--cc=netdev@vger.kernel.org \
--cc=pavel@ucw.cz \
--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).