From: Krzysztof Kozlowski <krzk@kernel.org>
To: Hans de Goede <hansg@kernel.org>,
Aleksandrs Vinarskis <alex@vinarskis.com>
Cc: robh@kernel.org, bryan.odonoghue@linaro.org, conor+dt@kernel.org,
devicetree@vger.kernel.org, krzk+dt@kernel.org, lee@kernel.org,
linux-kernel@vger.kernel.org, linux-leds@vger.kernel.org,
pavel@kernel.org
Subject: Re: [PATCH 1/2] dt-bindings: leds: add generic LED consumer documentation
Date: Thu, 4 Sep 2025 11:45:14 +0200 [thread overview]
Message-ID: <fdc68c54-a499-4ba6-8788-70c7ea515f2d@kernel.org> (raw)
In-Reply-To: <daf442a6-b4d6-4213-8ec0-10397d682cc4@kernel.org>
On 04/09/2025 09:26, Hans de Goede wrote:
>>>>> +maintainers:
>>>>> + - Aleksandrs Vinarskis <alex@vinarskis.com>
>>>>> +
>>>>> +description:
>>>>> + Some LED defined in DT are required by other DT consumers, for example
>>>>> + v4l2 subnode may require privacy or flash LED.
>>>>> +
>>>>> + Document LED properties that its consumers may define.
>>>>
>>>> We already have the trigger-source binding for "attaching" LEDs to
>>>> devices. Why does that not work here?
>>>
>>> I have not actually considered this, as the existing privacy-led solution
>>> from the original series is not trigger based. At least one of the reasons
>>> for that is that trigger source can be rather easily altered from user
>>> space, which would've been bad for this use case. If v4l2 acquires control
>>> over the LED it actually removes triggers and disables sysfs on that LED.
>>
>> So does that mean that v4l2 solves the problem of "trigger source can be
>> rather easily altered from user space"?
>
> Yes, currently the v4l2-core already does:
Thanks, I understand that it solves the problem described in the patch,
so the patch can be dropped.
Best regards,
Krzysztof
next prev parent reply other threads:[~2025-09-04 9:45 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20250902-leds-v1-0-4a31e125276b@vinarskis.com>
2025-09-02 11:10 ` [PATCH 1/2] dt-bindings: leds: add generic LED consumer documentation Aleksandrs Vinarskis
2025-09-02 17:57 ` Rob Herring (Arm)
2025-09-02 18:21 ` Rob Herring
2025-09-03 23:56 ` Aleksandrs Vinarskis
2025-09-04 6:41 ` Krzysztof Kozlowski
2025-09-04 7:26 ` Hans de Goede
2025-09-04 9:45 ` Krzysztof Kozlowski [this message]
2025-09-04 10:29 ` Hans de Goede
2025-09-04 10:47 ` Krzysztof Kozlowski
2025-09-04 11:47 ` Hans de Goede
2025-09-04 12:05 ` Hans de Goede
2025-09-04 14:10 ` Rob Herring
2025-09-04 22:52 ` Aleksandrs Vinarskis
2025-09-04 23:03 ` Aleksandrs Vinarskis
2025-09-02 11:10 ` [PATCH 2/2] leds: led-class: Add devicetree support to led_get() Aleksandrs Vinarskis
2025-09-02 12:25 ` Hans de Goede
2025-09-03 23:01 ` Aleksandrs Vinarskis
2025-09-04 7:08 ` Hans de Goede
2025-09-02 22:22 ` Linus Walleij
2025-09-03 6:58 ` Lee Jones
2025-09-03 3:31 ` kernel test robot
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=fdc68c54-a499-4ba6-8788-70c7ea515f2d@kernel.org \
--to=krzk@kernel.org \
--cc=alex@vinarskis.com \
--cc=bryan.odonoghue@linaro.org \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=hansg@kernel.org \
--cc=krzk+dt@kernel.org \
--cc=lee@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-leds@vger.kernel.org \
--cc=pavel@kernel.org \
--cc=robh@kernel.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 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).