From: Luca Weiss <luca@z3ntu.xyz>
To: Pavel Machek <pavel@ucw.cz>
Cc: linux-arm-msm@vger.kernel.org,
~postmarketos/upstreaming@lists.sr.ht,
phone-devel@vger.kernel.org,
Andr?? Almeida <andrealmeid@collabora.com>,
Andy Gross <agross@kernel.org>,
Bjorn Andersson <bjorn.andersson@linaro.org>,
Rob Herring <robh+dt@kernel.org>,
Krzysztof Kozlowski <krzysztof.kozlowski+dt@linaro.org>,
devicetree@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] ARM: dts: qcom: msm8974-hammerhead: Add notification LED
Date: Mon, 30 May 2022 22:57:43 +0200 [thread overview]
Message-ID: <2844866.mvXUDI8C0e@g550jk> (raw)
In-Reply-To: <20220530070618.GC1363@bug>
Hi Pavel,
On Montag, 30. Mai 2022 09:06:19 CEST Pavel Machek wrote:
> Hi!
>
> > From: Andr?? Almeida <andrealmeid@collabora.com>
> >
> > Nexus 5 has a RGB LED connected to the TRILED and hence channels 7, 6 and
> > 5 of the LPG. Add a node describing this.
> >
> > Signed-off-by: Luca Weiss <luca@z3ntu.xyz>
> > Signed-off-by: Andr?? Almeida <andrealmeid@collabora.com>
> >
> > --- This patch depends on the PM8941 LPG patch:
> > https://lore.kernel.org/linux-arm-msm/20220504205411.1510667-1-bjorn.ander
> > sson@linaro.org/
> How does this LED end up looking in userland? We want to make sure all the
> phone RGB status LEDs end up using same path in /sys/..
Like this, on both hammerhead and FP2 (in a separate patch):
$ ls -al /sys/class/leds/rgb:status/
total 0
drwxr-xr-x 3 root root 0 Jan 5 1970 .
drwxr-xr-x 3 root root 0 Jan 5 1970 ..
-rw-rw-r-- 1 root feedbackd 4096 Jan 5 1970 brightness
lrwxrwxrwx 1 root root 0 May 30 13:59 device -> ../../../fc4cf000.spmi:pm8941@1:lpg
-r--r--r-- 1 root root 4096 Jan 5 1970 max_brightness
-r--r--r-- 1 root root 4096 Jan 5 1970 multi_index
-rw-rw-r-- 1 root feedbackd 4096 Jan 5 1970 multi_intensity
drwxr-xr-x 2 root root 0 May 30 13:59 power
lrwxrwxrwx 1 root root 0 Jan 5 1970 subsystem -> ../../../../../../../../../class/leds
-rw-r--r-- 1 root root 0 Jan 5 1970 trigger
-rw-r--r-- 1 root root 4096 Jan 5 1970 uevent
Regards
Luca
>
> Best regards,
>
> Pavel
next prev parent reply other threads:[~2022-05-30 20:58 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-05-05 16:43 [PATCH] ARM: dts: qcom: msm8974-hammerhead: Add notification LED Luca Weiss
2022-05-06 15:10 ` kernel test robot
2022-05-30 7:06 ` Pavel Machek
2022-05-30 20:57 ` Luca Weiss [this message]
2022-07-17 3:08 ` (subset) " Bjorn Andersson
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=2844866.mvXUDI8C0e@g550jk \
--to=luca@z3ntu.xyz \
--cc=agross@kernel.org \
--cc=andrealmeid@collabora.com \
--cc=bjorn.andersson@linaro.org \
--cc=devicetree@vger.kernel.org \
--cc=krzysztof.kozlowski+dt@linaro.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=pavel@ucw.cz \
--cc=phone-devel@vger.kernel.org \
--cc=robh+dt@kernel.org \
--cc=~postmarketos/upstreaming@lists.sr.ht \
/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.