From: "Heiko Stübner" <heiko@sntech.de>
To: Sebastian Kropatsch <seb-dev@mail.de>
Cc: linux-rockchip@lists.infradead.org, Rob Herring <robh@kernel.org>,
Krzysztof Kozlowski <krzk+dt@kernel.org>,
Conor Dooley <conor+dt@kernel.org>,
devicetree@vger.kernel.org, linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH 3/5] arm64: dts: rockchip: Improve LEDs on NanoPi R6C/R6S
Date: Thu, 20 Jun 2024 20:42:42 +0200 [thread overview]
Message-ID: <2564239.kdYZ1jHi8b@diego> (raw)
In-Reply-To: <20240612205056.397204-4-seb-dev@mail.de>
Am Mittwoch, 12. Juni 2024, 22:48:12 CEST schrieb Sebastian Kropatsch:
> Move led-3 node into NanoPi R6C/R6S's source files since they have
> different functionalities on each board: On the R6S this LED is used
> to signal LAN2 link up, while on the R6C this LED does not have a
> pre-defined purpose.
>
> In addition to that:
> - Remove deprecated label property
> - Add color and function properties
> - Add linux,default-trigger to trigger on Ethernet link
Again, please don't group unrelated changes together into one patch.
It makes things hard to read and hard to follow the changes.
>
> Signed-off-by: Sebastian Kropatsch <seb-dev@mail.de>
> ---
>
> DT validation doesn't like the 'linux,default-trigger = "stmmac-0:01:link"'
> properties, since "*:link" is not a valid value according to
> [Documentation/devicetree/bindings/leds/common.yaml]. These LEDs do
> have the specific purpose to show if an Ethernet link is up though.
> There is one LED for each Ethernet port and they are labeled WAN and
> LAN.
> Using the 'linux,default-trigger' like this does work perfectly fine
> with this solution. I could not find another way to achieve this. Please
> let me know if there is a better way.
> Maybe it would also be valid to add an entry to the DT bindings file to
> allow "*:link" as a value for 'linux,default-trigger'?
correct. If needed, things should be added to binding.
Heiko
next prev parent reply other threads:[~2024-06-20 18:42 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-06-12 20:48 [PATCH 0/5] Refactor, fix and improve NanoPi R6 series Sebastian Kropatsch
2024-06-12 20:48 ` [PATCH 1/5] arm64: dts: rockchip: Add common definitions for NanoPi R6C and R6S Sebastian Kropatsch
2024-06-20 18:34 ` Heiko Stübner
2024-06-12 20:48 ` [PATCH 2/5] arm64: dts: rockchip: Fix regulators, gmac and naming on NanoPi R6C/R6S Sebastian Kropatsch
2024-06-20 18:39 ` Heiko Stübner
2024-06-20 21:48 ` Sebastian Kropatsch
2024-06-12 20:48 ` [PATCH 3/5] arm64: dts: rockchip: Improve LEDs " Sebastian Kropatsch
2024-06-14 15:10 ` kernel test robot
2024-06-20 18:42 ` Heiko Stübner [this message]
2024-06-20 21:51 ` Sebastian Kropatsch
2024-06-12 20:48 ` [PATCH 4/5] arm64: dts: rockchip: Enable lower USB3 port " Sebastian Kropatsch
2024-06-12 20:48 ` [PATCH 5/5] arm64: dts: rockchip: Enable GPU " Sebastian Kropatsch
2024-06-13 17:27 ` [PATCH 0/5] Refactor, fix and improve NanoPi R6 series Rob Herring (Arm)
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=2564239.kdYZ1jHi8b@diego \
--to=heiko@sntech.de \
--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=linux-rockchip@lists.infradead.org \
--cc=robh@kernel.org \
--cc=seb-dev@mail.de \
/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).