From: Hans de Goede <hansg@kernel.org>
To: Andy Shevchenko <andy.shevchenko@gmail.com>
Cc: "Ilpo Järvinen" <ilpo.jarvinen@linux.intel.com>,
"Andy Shevchenko" <andy@kernel.org>,
"Sakari Ailus" <sakari.ailus@linux.intel.com>,
"Aleksandrs Vinarskis" <alex@vinarskis.com>,
platform-driver-x86@vger.kernel.org,
"Mauro Carvalho Chehab" <mchehab@kernel.org>,
linux-media@vger.kernel.org
Subject: Re: [PATCH 0/2] v4l2-subdev/int3472: Use "privacy" as con_id for the LED lookup
Date: Tue, 9 Sep 2025 22:40:35 +0200 [thread overview]
Message-ID: <e3edf119-2dfe-4857-842d-fb2a52470eb9@kernel.org> (raw)
In-Reply-To: <CAHp75VeMMKCTDNWhdZJH2F=cmUObbpoYcDUch2jpsLBBNs_EhQ@mail.gmail.com>
Hi Andy,
On 9-Sep-25 7:27 PM, Andy Shevchenko wrote:
> On Tue, Sep 9, 2025 at 5:48 PM Hans de Goede <hansg@kernel.org> wrote:
>>
>> During DT-binding review for extending the V4L2 camera sensor privacy LED
>> support to systems using devicetree, it has come up that having a "-led"
>> suffix for the LED name / con_id is undesirable since it already is clear
>> that it is a LED:
>>
>> https://lore.kernel.org/linux-media/0e030e7d-0a1a-4a00-ba18-ed26107d07fa@oss.qualcomm.com/
>>
>> There was discussion about making an exception for "privacy-led" since
>> that is already used on x86/ACPI platforms, but I'm afraid that will set
>> a bad example which ends up being copy and pasted, so lets just drop
>> the "-led" prefix from the x86/ACPI side, which we can do since there
>> this is only an in-kernel "API".
>
> Since it's an in-kernel API, why can't these two be simply squashed?
Good question, this is only a runtime thing when running on actual
hw with a privacy LED. So having this separately will not break
the build in the middle.
As such it seems better to have this as 2 patches since it involves
2 different subsystems.
Regards,
Hans
next prev parent reply other threads:[~2025-09-09 20:40 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-09-09 14:48 [PATCH 0/2] v4l2-subdev/int3472: Use "privacy" as con_id for the LED lookup Hans de Goede
2025-09-09 14:48 ` [PATCH 1/2] media: v4l2-subdev: Use "privacy" as con_id when getting the privacy LED Hans de Goede
2025-09-09 14:48 ` [PATCH 2/2] platform/x86: int3472: Use "privacy" as con_id for the LED lookup Hans de Goede
2025-09-09 17:27 ` [PATCH 0/2] v4l2-subdev/int3472: " Andy Shevchenko
2025-09-09 20:40 ` Hans de Goede [this message]
2025-09-10 7:42 ` Sakari Ailus
2025-09-10 10:52 ` Ilpo Järvinen
2025-09-10 9:09 ` Ilpo Järvinen
2025-09-10 10:44 ` Hans de Goede
2025-09-10 10:49 ` Ilpo Järvinen
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=e3edf119-2dfe-4857-842d-fb2a52470eb9@kernel.org \
--to=hansg@kernel.org \
--cc=alex@vinarskis.com \
--cc=andy.shevchenko@gmail.com \
--cc=andy@kernel.org \
--cc=ilpo.jarvinen@linux.intel.com \
--cc=linux-media@vger.kernel.org \
--cc=mchehab@kernel.org \
--cc=platform-driver-x86@vger.kernel.org \
--cc=sakari.ailus@linux.intel.com \
/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