From: Hans de Goede <hdegoede@redhat.com>
To: "Gergo Koteles" <soyer@irl.hu>,
"Krzysztof Kozlowski" <krzysztof.kozlowski@linaro.org>,
"Ike Panhc" <ike.pan@canonical.com>,
"Ilpo Järvinen" <ilpo.jarvinen@linux.intel.com>,
"Pavel Machek" <pavel@ucw.cz>, "Lee Jones" <lee@kernel.org>,
"Rob Herring" <robh@kernel.org>,
"Krzysztof Kozlowski" <krzysztof.kozlowski+dt@linaro.org>,
"Conor Dooley" <conor+dt@kernel.org>
Cc: platform-driver-x86@vger.kernel.org,
linux-kernel@vger.kernel.org, linux-leds@vger.kernel.org,
devicetree@vger.kernel.org
Subject: Re: [PATCH 1/3] dt-bindings: leds: add LED_FUNCTION_FNLOCK
Date: Wed, 3 Apr 2024 10:33:00 +0200 [thread overview]
Message-ID: <283b5056-29df-486f-8a4a-5271af8a5b8c@redhat.com> (raw)
In-Reply-To: <2710283677cf12ca6b826565ec39652f560a43d8.camel@irl.hu>
Hi George,
On 4/2/24 8:50 PM, Gergo Koteles wrote:
> Hi Krzysztof,
>
> On Tue, 2024-04-02 at 20:08 +0200, Krzysztof Kozlowski wrote:
>> On 02/04/2024 16:36, Gergo Koteles wrote:
>>> Hi Krzysztof,
>>>
>>> On Tue, 2024-04-02 at 15:55 +0200, Krzysztof Kozlowski wrote:
>>>>
>>>> Do we really need to define all these possible LED functions? Please
>>>> link to DTS user for this.
>>>>
>>>
>>> I think for userspace it's easier to support an LED with a specified
>>> name than to use various sysfs attributes. LED devices are easy to find
>>> because they available are in the /sys/class/leds/ directory.
>>> So I think it's a good thing to define LED names somewhere.
>>
>> You did not add anything for user-space, but DT bindings. We do not keep
>> here anything for user-space.
>>
>
> The LED_FUNCTION_KBD_BACKLIGHT confused me. Ok, this shouldn't be here,
> I will remove it from v2.
I don't believe that is necessary, see my direct reply to Krzysztof first
email about this. According to Documentation/leds/leds-class.rst
you did exactly the right thing.
Also thank you for your interesting contribution. I have only briefly
looked over your other 2 patches, but I like the concept.
I'll hopefully have time to do a full review coming Monday.
Regards,
Hans
next prev parent reply other threads:[~2024-04-03 8:33 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-04-02 13:20 [PATCH 0/3] add FnLock LED class device to ideapad laptops Gergo Koteles
2024-04-02 13:21 ` [PATCH 1/3] dt-bindings: leds: add LED_FUNCTION_FNLOCK Gergo Koteles
2024-04-02 13:55 ` Krzysztof Kozlowski
2024-04-02 14:36 ` Gergo Koteles
2024-04-02 18:08 ` Krzysztof Kozlowski
2024-04-02 18:50 ` Gergo Koteles
2024-04-03 8:33 ` Hans de Goede [this message]
2024-04-03 8:31 ` Hans de Goede
2024-04-03 8:36 ` Krzysztof Kozlowski
2024-04-03 8:39 ` Hans de Goede
2024-04-03 8:46 ` Krzysztof Kozlowski
2024-04-03 8:51 ` Hans de Goede
2024-04-11 7:13 ` Lee Jones
2024-04-02 13:21 ` [PATCH 2/3] platform/x86: ideapad-laptop: add fn_lock_get/set functions Gergo Koteles
2024-04-08 15:49 ` Hans de Goede
2024-04-08 15:49 ` Hans de Goede
2024-04-02 13:21 ` [PATCH 3/3] platform/x86: ideapad-laptop: add FnLock LED class device Gergo Koteles
2024-04-08 15:50 ` Hans de Goede
2024-04-15 13:35 ` [PATCH 0/3] add FnLock LED class device to ideapad laptops Hans de Goede
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=283b5056-29df-486f-8a4a-5271af8a5b8c@redhat.com \
--to=hdegoede@redhat.com \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=ike.pan@canonical.com \
--cc=ilpo.jarvinen@linux.intel.com \
--cc=krzysztof.kozlowski+dt@linaro.org \
--cc=krzysztof.kozlowski@linaro.org \
--cc=lee@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-leds@vger.kernel.org \
--cc=pavel@ucw.cz \
--cc=platform-driver-x86@vger.kernel.org \
--cc=robh@kernel.org \
--cc=soyer@irl.hu \
/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
all inboxes | Powered by JetHome®