From: Josua Mayer <josua@solid-run.com> To: Andrew Lunn <andrew@lunn.ch> Cc: Gregory Clement <gregory.clement@bootlin.com>, Sebastian Hesselbarth <sebastian.hesselbarth@gmail.com>, Rob Herring <robh+dt@kernel.org>, Krzysztof Kozlowski <krzysztof.kozlowski+dt@linaro.org>, Conor Dooley <conor+dt@kernel.org>, Yazan Shhady <yazan.shhady@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 2/2] arm64: dts: add description for solidrun cn9130 som and clearfog boards Date: Fri, 22 Mar 2024 15:58:37 +0000 [thread overview] Message-ID: <542b7c30-a650-471a-8030-d1d6d70cb17f@solid-run.com> (raw) In-Reply-To: <a22e7861-c140-4f34-97be-a1f4e435b44b@lunn.ch> Am 22.03.24 um 16:49 schrieb Andrew Lunn: >> I (currently) can't put in the led node e.g. >> linux,default-trigger = "link100|link1000|tx|rx"; >> Right? > No. The trigger will be 'netdev'. Or 'heartbeat', or > 'kbd-numlock'. OK. > They are just LEDs, they can be used for > anything. While testing some of this code i had the keyboard numlock > indicating network packets, since it easier to see than the RJ45 > socket... The same applies the other way. The RJ45 LEDs are just Linux > LEDs, they can be used for anything... > > I do have some code adding additional properties for the blink > reason. However, it is very debatable if it belongs in DT. DT > describes hardware, not configuration of hardware. > > Do you actually have labels on the case indicating what the LEDs mean? > It could be we describe the label, which is hardware, not the > configuration of the LED, which is policy from user space. I have seen it on customer products, and I have seen it in manuals, and it can help in customer support. Personally I would want it for consistency reasons, so that even if hardware engineers confused 0 and 1 I can ensure consistent behaviour out of the box. It could be the vendor recommended or intended configuration ...
WARNING: multiple messages have this Message-ID (diff)
From: Josua Mayer <josua@solid-run.com> To: Andrew Lunn <andrew@lunn.ch> Cc: Gregory Clement <gregory.clement@bootlin.com>, Sebastian Hesselbarth <sebastian.hesselbarth@gmail.com>, Rob Herring <robh+dt@kernel.org>, Krzysztof Kozlowski <krzysztof.kozlowski+dt@linaro.org>, Conor Dooley <conor+dt@kernel.org>, Yazan Shhady <yazan.shhady@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 2/2] arm64: dts: add description for solidrun cn9130 som and clearfog boards Date: Fri, 22 Mar 2024 15:58:37 +0000 [thread overview] Message-ID: <542b7c30-a650-471a-8030-d1d6d70cb17f@solid-run.com> (raw) In-Reply-To: <a22e7861-c140-4f34-97be-a1f4e435b44b@lunn.ch> Am 22.03.24 um 16:49 schrieb Andrew Lunn: >> I (currently) can't put in the led node e.g. >> linux,default-trigger = "link100|link1000|tx|rx"; >> Right? > No. The trigger will be 'netdev'. Or 'heartbeat', or > 'kbd-numlock'. OK. > They are just LEDs, they can be used for > anything. While testing some of this code i had the keyboard numlock > indicating network packets, since it easier to see than the RJ45 > socket... The same applies the other way. The RJ45 LEDs are just Linux > LEDs, they can be used for anything... > > I do have some code adding additional properties for the blink > reason. However, it is very debatable if it belongs in DT. DT > describes hardware, not configuration of hardware. > > Do you actually have labels on the case indicating what the LEDs mean? > It could be we describe the label, which is hardware, not the > configuration of the LED, which is policy from user space. I have seen it on customer products, and I have seen it in manuals, and it can help in customer support. Personally I would want it for consistency reasons, so that even if hardware engineers confused 0 and 1 I can ensure consistent behaviour out of the box. It could be the vendor recommended or intended configuration ... _______________________________________________ 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:[~2024-03-22 15:58 UTC|newest] Thread overview: 48+ messages / expand[flat|nested] mbox.gz Atom feed top 2024-03-21 21:47 [PATCH 0/2] arm64: dts: add description for solidrun cn9130 som and clearfog boards Josua Mayer 2024-03-21 21:47 ` Josua Mayer 2024-03-21 21:47 ` [PATCH 1/2] dt-bindings: arm64: marvell: add solidrun cn9130 " Josua Mayer 2024-03-21 21:47 ` Josua Mayer 2024-03-22 2:16 ` Rob Herring 2024-03-22 2:16 ` Rob Herring 2024-03-22 10:08 ` Josua Mayer 2024-03-22 10:08 ` Josua Mayer 2024-03-25 19:34 ` Krzysztof Kozlowski 2024-03-25 19:34 ` Krzysztof Kozlowski 2024-03-25 20:12 ` Josua Mayer 2024-03-25 20:12 ` Josua Mayer 2024-03-26 6:41 ` Krzysztof Kozlowski 2024-03-26 6:41 ` Krzysztof Kozlowski 2024-03-26 19:26 ` Josua Mayer 2024-03-26 19:26 ` Josua Mayer 2024-03-27 10:19 ` Krzysztof Kozlowski 2024-03-27 10:19 ` Krzysztof Kozlowski 2024-03-27 10:55 ` Josua Mayer 2024-03-27 10:55 ` Josua Mayer 2024-03-28 9:14 ` Krzysztof Kozlowski 2024-03-28 9:14 ` Krzysztof Kozlowski 2024-03-28 9:33 ` Josua Mayer 2024-03-28 9:33 ` Josua Mayer 2024-03-28 9:41 ` Krzysztof Kozlowski 2024-03-28 9:41 ` Krzysztof Kozlowski 2024-03-28 9:46 ` Josua Mayer 2024-03-28 9:46 ` Josua Mayer 2024-03-28 16:22 ` Josua Mayer 2024-03-28 16:22 ` Josua Mayer 2024-03-21 21:47 ` [PATCH 2/2] arm64: dts: add description for solidrun cn9130 som and " Josua Mayer 2024-03-21 21:47 ` Josua Mayer 2024-03-21 21:59 ` Andrew Lunn 2024-03-21 21:59 ` Andrew Lunn 2024-03-22 9:54 ` Josua Mayer 2024-03-22 9:54 ` Josua Mayer 2024-03-22 13:11 ` Andrew Lunn 2024-03-22 13:11 ` Andrew Lunn 2024-03-22 15:38 ` Josua Mayer 2024-03-22 15:38 ` Josua Mayer 2024-03-22 15:49 ` Andrew Lunn 2024-03-22 15:49 ` Andrew Lunn 2024-03-22 15:58 ` Josua Mayer [this message] 2024-03-22 15:58 ` Josua Mayer 2024-03-22 18:14 ` Josua Mayer 2024-03-22 18:14 ` Josua Mayer 2024-03-22 18:27 ` Andrew Lunn 2024-03-22 18:27 ` 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=542b7c30-a650-471a-8030-d1d6d70cb17f@solid-run.com \ --to=josua@solid-run.com \ --cc=andrew@lunn.ch \ --cc=conor+dt@kernel.org \ --cc=devicetree@vger.kernel.org \ --cc=gregory.clement@bootlin.com \ --cc=krzysztof.kozlowski+dt@linaro.org \ --cc=linux-arm-kernel@lists.infradead.org \ --cc=linux-kernel@vger.kernel.org \ --cc=robh+dt@kernel.org \ --cc=sebastian.hesselbarth@gmail.com \ --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: 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.