public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: Ricardo Ribalda <ribalda@chromium.org>
Cc: Laurent Pinchart <laurent.pinchart@ideasonboard.com>,
	Hans de Goede <hansg@kernel.org>,
	Mauro Carvalho Chehab <mchehab@kernel.org>,
	linux-media@vger.kernel.org, linux-kernel@vger.kernel.org,
	linux-usb@vger.kernel.org
Subject: Re: [PATCH 4/4] media: uvcvideo: Introduce allow_privacy_override
Date: Tue, 18 Nov 2025 06:14:09 -0500	[thread overview]
Message-ID: <2025111817-wages-anyone-e39a@gregkh> (raw)
In-Reply-To: <20251117-uvcdynctrl-v1-4-aed70eadf3d8@chromium.org>

On Mon, Nov 17, 2025 at 08:14:19PM +0000, Ricardo Ribalda wrote:
> Some camera modules have XU controls that can configure the behaviour of
> the privacy LED.
> 
> Block mapping of those controls, unless the module is configured with
> a new parameter: allow_privacy_override.

This is not the 1990's, please do not add new module parameters, they do
not scale, nor work properly at all for modern hardware where you can
have multiple devices in the same system.

This isn't an agreement that we should do this feature at all, just that
if you do, it should NOT be a module parameter.

thanks,

greg k-h

  parent reply	other threads:[~2025-11-18 11:14 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-11-17 20:14 [PATCH 0/4] media: uvcvideo: Map known XU controls Ricardo Ribalda
2025-11-17 20:14 ` [PATCH 1/4] media: uvcvideo: Remove nodrop parameter Ricardo Ribalda
2025-11-19  4:20   ` Laurent Pinchart
2025-11-17 20:14 ` [PATCH 2/4] media: uvcvideo: Import standard controls from uvcdynctrl Ricardo Ribalda
2025-11-19  4:21   ` Laurent Pinchart
2025-11-17 20:14 ` [PATCH 3/4] media: uvcvideo: Announce deprecation intentions for UVCIOC_CTRL_MAP Ricardo Ribalda
2025-11-19  4:21   ` Laurent Pinchart
2025-11-17 20:14 ` [PATCH 4/4] media: uvcvideo: Introduce allow_privacy_override Ricardo Ribalda
2025-11-17 21:10   ` Gergo Koteles
2025-11-18  6:21     ` Ricardo Ribalda
2025-11-18  8:48       ` Gergo Koteles
2025-11-18  9:25         ` Ricardo Ribalda
2025-11-18 11:14           ` Gergo Koteles
2025-11-18 14:26             ` Hans de Goede
2025-11-18 15:36               ` Gergo Koteles
2025-11-18 18:30                 ` Ricardo Ribalda
2025-11-19 21:34                   ` Gergo Koteles
2025-11-19  4:19           ` Laurent Pinchart
2025-11-18 11:14   ` Greg Kroah-Hartman [this message]
2025-11-18 14:09     ` Mauro Carvalho Chehab
2025-11-18 16:01       ` Michal Pecio
2025-11-18 18:28       ` Ricardo Ribalda
2025-11-19  4:19       ` Laurent Pinchart

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=2025111817-wages-anyone-e39a@gregkh \
    --to=gregkh@linuxfoundation.org \
    --cc=hansg@kernel.org \
    --cc=laurent.pinchart@ideasonboard.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-media@vger.kernel.org \
    --cc=linux-usb@vger.kernel.org \
    --cc=mchehab@kernel.org \
    --cc=ribalda@chromium.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