From: Josua Mayer <josua@solid-run.com>
To: Frank Li <Frank.Li@nxp.com>, Rob Herring <robh@kernel.org>,
Krzysztof Kozlowski <krzk+dt@kernel.org>,
Conor Dooley <conor+dt@kernel.org>,
Shawn Guo <shawnguo@kernel.org>,
Carlos Song <carlos.song@nxp.com>
Cc: Mikhail Anikin <mikhail.anikin@solid-run.com>,
Yazan Shhady <yazan.shhady@solid-run.com>,
Rabeeh Khoury <rabeeh@solid-run.com>,
"linux-arm-kernel@lists.infradead.org"
<linux-arm-kernel@lists.infradead.org>,
"devicetree@vger.kernel.org" <devicetree@vger.kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH v5 10/10] arm64: dts: lx2162a-clearfog: set sfp connector leds function and source
Date: Sun, 15 Mar 2026 12:29:51 +0000 [thread overview]
Message-ID: <80962490-5f42-4e0e-8b53-8e5d54751d50@solid-run.com> (raw)
In-Reply-To: <20260314-lx2160-sd-cd-v5-10-83de721585e3@solid-run.com>
On 3/14/26 14:05, Josua Mayer wrote:
> LX2162A Clearfog has four LEDs attached physically to the 4-port SFP
> connector. They are intended to show information relating to network
> interface status.
>
> Select "netdev" as default trigger for each LED, and link each one to
> the respective dpmac instance as trigger-source.
>
> Signed-off-by: Josua Mayer <josua@solid-run.com>
> ---
> arch/arm64/boot/dts/freescale/fsl-lx2162a-clearfog.dts | 8 ++++++++
> 1 file changed, 8 insertions(+)
>
> diff --git a/arch/arm64/boot/dts/freescale/fsl-lx2162a-clearfog.dts b/arch/arm64/boot/dts/freescale/fsl-lx2162a-clearfog.dts
> index 8920326a06735..9d50d3e2761da 100644
> --- a/arch/arm64/boot/dts/freescale/fsl-lx2162a-clearfog.dts
> +++ b/arch/arm64/boot/dts/freescale/fsl-lx2162a-clearfog.dts
> @@ -41,21 +41,29 @@ leds {
> led_sfp_at: led-sfp-at {
> gpios = <&gpio2 5 GPIO_ACTIVE_HIGH>; /* PROC_IRQ5 */
> default-state = "off";
> + linux,default-trigger = "netdev";
> + trigger-sources = <&dpmac3>;
Linking a dpmac as trigger-source doesn't actually work currently,
but the bindings allow it.
Any opinions on whether or not it is better to omit for now?
Note there are complications due to dpaa2 driver binding netdevs
to software-only dpni objects which are not listed in device-tree.
The dpmac objects however are hard-wired to specific physical signals,
and therefore suitable for mapping LEDs correctly.
Vendor BSP does this with udev rules for now:
SUBSYSTEM=="net", ACTION=="add",
ENV{OF_FULLNAME}=="/soc/fsl-mc@80c000000/dpmacs/ethernet@3",
RUN+="/bin/sh -c 'echo %k > /sys/class/leds/led-sfp-at/device_name &&
echo 1 > /sys/class/leds/led-sfp-at/link'"
SUBSYSTEM=="net", ACTION=="add",
ENV{OF_FULLNAME}=="/soc/fsl-mc@80c000000/dpmacs/ethernet@4",
RUN+="/bin/sh -c 'echo %k > /sys/class/leds/led-sfp-ab/device_name &&
echo 1 > /sys/class/leds/led-sfp-ab/link'"
SUBSYSTEM=="net", ACTION=="add",
ENV{OF_FULLNAME}=="/soc/fsl-mc@80c000000/dpmacs/ethernet@5",
RUN+="/bin/sh -c 'echo %k > /sys/class/leds/led-sfp-bt/device_name &&
echo 1 > /sys/class/leds/led-sfp-bt/link'"
SUBSYSTEM=="net", ACTION=="add",
ENV{OF_FULLNAME}=="/soc/fsl-mc@80c000000/dpmacs/ethernet@6",
RUN+="/bin/sh -c 'echo %k > /sys/class/leds/led-sfp-bb/device_name &&
echo 1 > /sys/class/leds/led-sfp-bb/link'"
> };
>
> led_sfp_ab: led-sfp-ab {
> gpios = <&gpio2 11 GPIO_ACTIVE_HIGH>; /* PROC_IRQ11 */
> default-state = "off";
> + linux,default-trigger = "netdev";
> + trigger-sources = <&dpmac4>;
> };
>
> led_sfp_bt: led-sfp-bt {
> gpios = <&gpio2 13 GPIO_ACTIVE_HIGH>; /* EVT1_B */
> default-state = "off";
> + linux,default-trigger = "netdev";
> + trigger-sources = <&dpmac5>;
> };
>
> led_sfp_bb: led-sfp-bb {
> gpios = <&gpio2 14 GPIO_ACTIVE_HIGH>; /* EVT2_B */
> default-state = "off";
> + linux,default-trigger = "netdev";
> + trigger-sources = <&dpmac6>;
> };
> };
>
>
prev parent reply other threads:[~2026-03-15 12:30 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-03-14 12:05 [PATCH v5 00/10] arm64: dts: lx2160a: fix pinmux issues, update SolidRun boards Josua Mayer
2026-03-14 12:05 ` [PATCH v5 01/10] arm64: dts: lx2160a-cex7/lx2162a-sr-som: fix usd-cd & gpio pinmux Josua Mayer
2026-03-14 12:11 ` Josua Mayer
2026-03-14 12:05 ` [PATCH v5 02/10] arm64: dts: lx2160a: change i2c0 (iic1) pinmux mask to one bit Josua Mayer
2026-03-14 12:05 ` [PATCH v5 03/10] arm64: dts: lx2160a: remove duplicate pinmux nodes Josua Mayer
2026-03-14 12:05 ` [PATCH v5 04/10] arm64: dts: lx2160a: rename pinmux nodes for readability Josua Mayer
2026-03-17 0:36 ` Frank Li
2026-03-17 17:20 ` Josua Mayer
2026-03-18 13:48 ` Frank Li
2026-03-24 12:40 ` Josua Mayer
2026-03-14 12:05 ` [PATCH v5 05/10] arm64: dts: lx2160a: add sda gpio references for i2c bus recovery Josua Mayer
2026-03-14 12:05 ` [PATCH v5 06/10] arm64: dts: lx2160a: change zeros to hexadecimal in pinmux nodes Josua Mayer
2026-03-14 12:05 ` [PATCH v5 07/10] arm64: dts: lx2160a: complete pinmux for rcwsr12 configuration word Josua Mayer
2026-03-14 12:05 ` [PATCH v5 08/10] arm64: dts: lx2160a-cex7: add rtc alias Josua Mayer
2026-03-14 12:05 ` [PATCH v5 09/10] arm64: dts: lx2162a-sr-som: add crypto & rtc aliases, model Josua Mayer
2026-03-14 12:05 ` [PATCH v5 10/10] arm64: dts: lx2162a-clearfog: set sfp connector leds function and source Josua Mayer
2026-03-15 12:29 ` Josua Mayer [this message]
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=80962490-5f42-4e0e-8b53-8e5d54751d50@solid-run.com \
--to=josua@solid-run.com \
--cc=Frank.Li@nxp.com \
--cc=carlos.song@nxp.com \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=krzk+dt@kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mikhail.anikin@solid-run.com \
--cc=rabeeh@solid-run.com \
--cc=robh@kernel.org \
--cc=shawnguo@kernel.org \
--cc=yazan.shhady@solid-run.com \
/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