netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Tim Harvey <tharvey@gateworks.com>
To: linux-kernel@vger.kernel.org,
	linux-arm-kernel@lists.infradead.org, devicetree@vger.kernel.org,
	netdev@vger.kernel.org, Andrew Lunn <andrew@lunn.ch>,
	Heiner Kallweit <hkallweit1@gmail.com>,
	Russell King <linux@armlinux.org.uk>,
	Shawn Guo <shawnguo@kernel.org>,
	Sascha Hauer <s.hauer@pengutronix.de>,
	Pengutronix Kernel Team <kernel@pengutronix.de>,
	Fabio Estevam <festevam@gmail.com>,
	Rob Herring <robh+dt@kernel.org>,
	Krzysztof Kozlowski <krzysztof.kozlowski+dt@linaro.org>
Cc: Tim Harvey <tharvey@gateworks.com>
Subject: [PATCH 1/3] dt-bindings: net: phy: dp83867: add LED mode property
Date: Thu, 17 Nov 2022 16:15:46 -0800	[thread overview]
Message-ID: <20221118001548.635752-2-tharvey@gateworks.com> (raw)
In-Reply-To: <20221118001548.635752-1-tharvey@gateworks.com>

Add description for new property ti,led-modes in binding file.

Signed-off-by: Tim Harvey <tharvey@gateworks.com>
---
 .../devicetree/bindings/net/ti,dp83867.yaml      |  6 ++++++
 include/dt-bindings/net/ti-dp83867.h             | 16 ++++++++++++++++
 2 files changed, 22 insertions(+)

diff --git a/Documentation/devicetree/bindings/net/ti,dp83867.yaml b/Documentation/devicetree/bindings/net/ti,dp83867.yaml
index b8c0e4b5b494..8b84c34d389f 100644
--- a/Documentation/devicetree/bindings/net/ti,dp83867.yaml
+++ b/Documentation/devicetree/bindings/net/ti,dp83867.yaml
@@ -118,6 +118,12 @@ properties:
       Transmitt FIFO depth- see dt-bindings/net/ti-dp83867.h for applicable
       values.
 
+  ti,led-modes:
+    description: |
+      List of LED modes - see dt-bindings/net/ti-dp83867.h for applicable
+      values.
+    $ref: schemas/types.yaml#/definitions/uint32-array
+
 required:
   - reg
 
diff --git a/include/dt-bindings/net/ti-dp83867.h b/include/dt-bindings/net/ti-dp83867.h
index 6fc4b445d3a1..ea3e17b27427 100644
--- a/include/dt-bindings/net/ti-dp83867.h
+++ b/include/dt-bindings/net/ti-dp83867.h
@@ -50,4 +50,20 @@
 #define DP83867_CLK_O_SEL_REF_CLK		0xC
 /* Special flag to indicate clock should be off */
 #define DP83867_CLK_O_SEL_OFF			0xFFFFFFFF
+
+/* LED_CFG - LED configuration selection */
+#define DP83867_LED_SEL_LINK			0
+#define DP83867_LED_SEL_ACT			1
+#define DP83867_LED_SEL_ACT_TX			2
+#define DP83867_LED_SEL_ACT_RX			3
+#define DP83867_LED_SEL_COL			4
+#define DP83867_LED_SEL_LINK_1000BT		5
+#define DP83867_LED_SEL_LINK_100BT		6
+#define DP83867_LED_SEL_LINK_10BT		7
+#define DP83867_LED_SEL_LINK_10_100BT		8
+#define DP83867_LED_SEL_LINK_100_1000BT		9
+#define DP83867_LED_SEL_FULL_DUPLEX		10
+#define DP83867_LED_SEL_LINK_ACT		11
+#define DP83867_LED_SEL_ERR_TX_RX		13
+#define DP83867_LED_SEL_ERR_RX			14
 #endif
-- 
2.25.1


  reply	other threads:[~2022-11-18  0:44 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-11-18  0:15 [PATCH 0/3] add dt configuration for dp83867 led modes Tim Harvey
2022-11-18  0:15 ` Tim Harvey [this message]
2022-11-18  3:56   ` [PATCH 1/3] dt-bindings: net: phy: dp83867: add LED mode property Rob Herring
2022-11-18  0:15 ` [PATCH 2/3] net: phy: dp83867: add LED mode configuration via dt Tim Harvey
2022-11-18  0:15 ` [PATCH 3/3] arm64: dts: imx8m*-venice: add dp83867 PHY LED mode configuration Tim Harvey
2022-11-18  0:27 ` [PATCH 0/3] add dt configuration for dp83867 led modes Andrew Lunn
2022-11-18  0:54   ` Tim Harvey
2022-11-18 13:11     ` Andrew Lunn
2022-11-18 19:57       ` Tim Harvey
2022-11-20 23:35         ` Andrew Lunn
2022-12-01 18:26           ` Tim Harvey
2022-12-01 18:31             ` Christian Marangi
2022-12-01 18:35               ` Tim Harvey
2022-12-01 18:38                 ` Christian Marangi
2022-12-01 19:40                   ` Andrew Lunn
2022-12-07 10:40                   ` Alexander Stein
2022-12-07 10:48                     ` Rasmus Villemoes

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=20221118001548.635752-2-tharvey@gateworks.com \
    --to=tharvey@gateworks.com \
    --cc=andrew@lunn.ch \
    --cc=devicetree@vger.kernel.org \
    --cc=festevam@gmail.com \
    --cc=hkallweit1@gmail.com \
    --cc=kernel@pengutronix.de \
    --cc=krzysztof.kozlowski+dt@linaro.org \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux@armlinux.org.uk \
    --cc=netdev@vger.kernel.org \
    --cc=robh+dt@kernel.org \
    --cc=s.hauer@pengutronix.de \
    --cc=shawnguo@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).