From: Heiko Stuebner <heiko-4mtYJXux2i+zQB+pC5nmwQ@public.gmane.org>
To: "Leonidas P. Papadakos"
<papadakospan-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
Cc: linux-rockchip-IAPFreCvJWM7uuMidbF8XUB+6BGkLq7r@public.gmane.org,
Rob Herring <robh+dt-DgEjT+Ai2ygdnm+yROfE0A@public.gmane.org>
Subject: Re: [PATCH] arm64: dts: rockchip: give some life to the rk3328-roc-cc leds
Date: Sat, 02 Mar 2019 01:31:11 +0100 [thread overview]
Message-ID: <1918569.2zEEYki6OE@phil> (raw)
In-Reply-To: <20190301225813.19834-1-papadakospan-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
Am Freitag, 1. März 2019, 23:58:13 CET schrieb Leonidas P. Papadakos:
> Assign the LED's to heartbeat and sdcard io, as in other RK boards.
>
> https://github.com/armbian/build/commit/f1affad5c7be62d6e93832af3556c7609edd0858
>
> Signed-off-by: Leonidas P. Papadakos <papadakospan-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
> ---
> .../arm64/boot/dts/rockchip/rk3328-roc-cc.dts | 27 +++++++++++++++++++
> 1 file changed, 27 insertions(+)
>
> diff --git a/arch/arm64/boot/dts/rockchip/rk3328-roc-cc.dts b/arch/arm64/boot/dts/rockchip/rk3328-roc-cc.dts
> index 33c44e857..a881d4c8d 100644
> --- a/arch/arm64/boot/dts/rockchip/rk3328-roc-cc.dts
> +++ b/arch/arm64/boot/dts/rockchip/rk3328-roc-cc.dts
> @@ -81,6 +81,33 @@
> regulator-always-on;
> regulator-boot-on;
> };
> +
> + leds {
> + compatible = "gpio-leds";
> + power {
> + label = "firefly:blue:power";
> + linux,default-trigger = "heartbeat";
> + gpios = <&rk805 1 GPIO_ACTIVE_LOW>;
> + default-state = "on";
> + mode = <0x23>;
> + };
> +
> + user {
> + label = "firefly:yellow:user";
> + linux,default-trigger = "mmc1";
> + gpios = <&rk805 0 GPIO_ACTIVE_LOW>;
> + default-state = "off";
> + mode = <0x05>;
> + };
> +
> + ir {
> + status = "disabled";
please explain that. Is this an IR transmitting LED? And why are you
adding a disabled property?
Similar to how the kernel should not contain commented out code
having a disabled node in the actual board file is strange.
Heiko
> + /* gpios = <&gpio2 GPIO_C2 GPIO_ACTIVE_HIGH>; */
> + linux,default-trigger = "ir";
> + default-state = "off";
> + mode = <0x00>;
> + };
> + };
> };
>
> &cpu0 {
>
next prev parent reply other threads:[~2019-03-02 0:31 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-03-01 22:58 [PATCH] arm64: dts: rockchip: give some life to the rk3328-roc-cc leds Leonidas P. Papadakos
[not found] ` <20190301225813.19834-1-papadakospan-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
2019-03-02 0:31 ` Heiko Stuebner [this message]
2019-03-02 2:51 ` Leonidas P. Papadakos
2019-03-02 10:54 ` Heiko Stuebner
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=1918569.2zEEYki6OE@phil \
--to=heiko-4mtyjxux2i+zqb+pc5nmwq@public.gmane.org \
--cc=linux-rockchip-IAPFreCvJWM7uuMidbF8XUB+6BGkLq7r@public.gmane.org \
--cc=papadakospan-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org \
--cc=robh+dt-DgEjT+Ai2ygdnm+yROfE0A@public.gmane.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 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.