From: "Rafał Miłecki" <zajec5@gmail.com> To: Rob Herring <robh+dt@kernel.org>, Krzysztof Kozlowski <krzysztof.kozlowski+dt@linaro.org> Cc: "Pavel Machek" <pavel@ucw.cz>, "David S . Miller" <davem@davemloft.net>, "Jakub Kicinski" <kuba@kernel.org>, "Paolo Abeni" <pabeni@redhat.com>, "Florian Fainelli" <f.fainelli@gmail.com>, "Hauke Mehrtens" <hauke@hauke-m.de>, "Jacek Anaszewski" <jacek.anaszewski@gmail.com>, devicetree@vger.kernel.org, netdev@vger.kernel.org, linux-leds@vger.kernel.org, linux-arm-kernel@lists.infradead.org, linux-kernel@vger.kernel.org, bcm-kernel-feedback-list@broadcom.com, "Rafał Miłecki" <rafal@milecki.pl> Subject: [PATCH 3/4] dt-bindings: leds: add Ethernet triggered LEDs to example Date: Tue, 3 May 2022 17:36:12 +0200 [thread overview] Message-ID: <20220503153613.15320-3-zajec5@gmail.com> (raw) In-Reply-To: <20220503153613.15320-1-zajec5@gmail.com> From: Rafał Miłecki <rafal@milecki.pl> This adds 3 entries to existing example: 1. LED triggered by switch port in 10 / 100 Mbps link state 2. LED triggered by switch port in 1000 Mbps link 3. LED triggered by Ethernet interface (any speed) Signed-off-by: Rafał Miłecki <rafal@milecki.pl> --- .../devicetree/bindings/leds/common.yaml | 21 +++++++++++++++++++ 1 file changed, 21 insertions(+) diff --git a/Documentation/devicetree/bindings/leds/common.yaml b/Documentation/devicetree/bindings/leds/common.yaml index 328952d7acbb..6c72121a1656 100644 --- a/Documentation/devicetree/bindings/leds/common.yaml +++ b/Documentation/devicetree/bindings/leds/common.yaml @@ -168,6 +168,7 @@ examples: - | #include <dt-bindings/gpio/gpio.h> #include <dt-bindings/leds/common.h> + #include <dt-bindings/net/eth.h> led-controller { compatible = "gpio-leds"; @@ -183,6 +184,26 @@ examples: gpios = <&gpio0 1 GPIO_ACTIVE_HIGH>; trigger-sources = <&ohci_port1>, <&ehci_port1>; }; + + led-2 { + function = LED_FUNCTION_WAN; + color = <LED_COLOR_ID_AMBER>; + gpios = <&gpio0 2 GPIO_ACTIVE_LOW>; + trigger-sources = <&wan_port (SPEED_10 | SPEED_100)>; + }; + + led-3 { + function = LED_FUNCTION_WAN; + color = <LED_COLOR_ID_GREEN>; + gpios = <&gpio0 3 GPIO_ACTIVE_LOW>; + trigger-sources = <&wan_port SPEED_1000>; + }; + + led-4 { + function = LED_FUNCTION_LAN; + gpios = <&gpio0 4 GPIO_ACTIVE_LOW>; + trigger-sources = <&gmac 0>; + }; }; - | -- 2.34.1
WARNING: multiple messages have this Message-ID (diff)
From: "Rafał Miłecki" <zajec5@gmail.com> To: Rob Herring <robh+dt@kernel.org>, Krzysztof Kozlowski <krzysztof.kozlowski+dt@linaro.org> Cc: "Pavel Machek" <pavel@ucw.cz>, "David S . Miller" <davem@davemloft.net>, "Jakub Kicinski" <kuba@kernel.org>, "Paolo Abeni" <pabeni@redhat.com>, "Florian Fainelli" <f.fainelli@gmail.com>, "Hauke Mehrtens" <hauke@hauke-m.de>, "Jacek Anaszewski" <jacek.anaszewski@gmail.com>, devicetree@vger.kernel.org, netdev@vger.kernel.org, linux-leds@vger.kernel.org, linux-arm-kernel@lists.infradead.org, linux-kernel@vger.kernel.org, bcm-kernel-feedback-list@broadcom.com, "Rafał Miłecki" <rafal@milecki.pl> Subject: [PATCH 3/4] dt-bindings: leds: add Ethernet triggered LEDs to example Date: Tue, 3 May 2022 17:36:12 +0200 [thread overview] Message-ID: <20220503153613.15320-3-zajec5@gmail.com> (raw) In-Reply-To: <20220503153613.15320-1-zajec5@gmail.com> From: Rafał Miłecki <rafal@milecki.pl> This adds 3 entries to existing example: 1. LED triggered by switch port in 10 / 100 Mbps link state 2. LED triggered by switch port in 1000 Mbps link 3. LED triggered by Ethernet interface (any speed) Signed-off-by: Rafał Miłecki <rafal@milecki.pl> --- .../devicetree/bindings/leds/common.yaml | 21 +++++++++++++++++++ 1 file changed, 21 insertions(+) diff --git a/Documentation/devicetree/bindings/leds/common.yaml b/Documentation/devicetree/bindings/leds/common.yaml index 328952d7acbb..6c72121a1656 100644 --- a/Documentation/devicetree/bindings/leds/common.yaml +++ b/Documentation/devicetree/bindings/leds/common.yaml @@ -168,6 +168,7 @@ examples: - | #include <dt-bindings/gpio/gpio.h> #include <dt-bindings/leds/common.h> + #include <dt-bindings/net/eth.h> led-controller { compatible = "gpio-leds"; @@ -183,6 +184,26 @@ examples: gpios = <&gpio0 1 GPIO_ACTIVE_HIGH>; trigger-sources = <&ohci_port1>, <&ehci_port1>; }; + + led-2 { + function = LED_FUNCTION_WAN; + color = <LED_COLOR_ID_AMBER>; + gpios = <&gpio0 2 GPIO_ACTIVE_LOW>; + trigger-sources = <&wan_port (SPEED_10 | SPEED_100)>; + }; + + led-3 { + function = LED_FUNCTION_WAN; + color = <LED_COLOR_ID_GREEN>; + gpios = <&gpio0 3 GPIO_ACTIVE_LOW>; + trigger-sources = <&wan_port SPEED_1000>; + }; + + led-4 { + function = LED_FUNCTION_LAN; + gpios = <&gpio0 4 GPIO_ACTIVE_LOW>; + trigger-sources = <&gmac 0>; + }; }; - | -- 2.34.1 _______________________________________________ linux-arm-kernel mailing list linux-arm-kernel@lists.infradead.org http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
next prev parent reply other threads:[~2022-05-03 15:36 UTC|newest] Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top 2022-05-03 15:36 [PATCH 1/4] dt-bindings: net: add bitfield defines for Ethernet speeds Rafał Miłecki 2022-05-03 15:36 ` Rafał Miłecki 2022-05-03 15:36 ` [PATCH 2/4] dt-bindings: net: allow Ethernet devices as LED triggers Rafał Miłecki 2022-05-03 15:36 ` Rafał Miłecki 2022-05-03 15:36 ` Rafał Miłecki [this message] 2022-05-03 15:36 ` [PATCH 3/4] dt-bindings: leds: add Ethernet triggered LEDs to example Rafał Miłecki 2022-05-03 15:36 ` [PATCH 4/4] ARM: dts: BCM5301X: Add triggers for Luxul XWR-1200 network LEDs Rafał Miłecki 2022-05-03 15:36 ` Rafał Miłecki 2022-05-04 21:23 ` [PATCH 1/4] dt-bindings: net: add bitfield defines for Ethernet speeds Andrew Lunn 2022-05-04 21:23 ` Andrew Lunn 2022-05-05 5:19 ` Rafał Miłecki 2022-05-05 5:19 ` Rafał Miłecki 2022-05-05 12:17 ` Andrew Lunn 2022-05-05 12:17 ` Andrew Lunn 2022-05-05 13:46 ` Rafał Miłecki 2022-05-05 13:46 ` Rafał Miłecki 2022-05-05 14:11 ` Andrew Lunn 2022-05-05 14:11 ` Andrew Lunn
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=20220503153613.15320-3-zajec5@gmail.com \ --to=zajec5@gmail.com \ --cc=bcm-kernel-feedback-list@broadcom.com \ --cc=davem@davemloft.net \ --cc=devicetree@vger.kernel.org \ --cc=f.fainelli@gmail.com \ --cc=hauke@hauke-m.de \ --cc=jacek.anaszewski@gmail.com \ --cc=krzysztof.kozlowski+dt@linaro.org \ --cc=kuba@kernel.org \ --cc=linux-arm-kernel@lists.infradead.org \ --cc=linux-kernel@vger.kernel.org \ --cc=linux-leds@vger.kernel.org \ --cc=netdev@vger.kernel.org \ --cc=pabeni@redhat.com \ --cc=pavel@ucw.cz \ --cc=rafal@milecki.pl \ --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: linkBe sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes, see mirroring instructions on how to clone and mirror all data and code used by this external index.