From: Marco Nenciarini <mnencia@kcore.it>
To: praveenpuglia@gmail.com
Cc: miguel.vadillo@intel.com, mchehab@kernel.org,
sakari.ailus@linux.intel.com, mehdi.djait@linux.intel.com,
linux-media@vger.kernel.org, linux-kernel@vger.kernel.org,
stable@vger.kernel.org
Subject: Re: [PATCH] media: i2c: cvs: Leave the privacy LED to firmware on Synaptics SVP7xxx
Date: Thu, 8 Oct 2026 17:33:51 +0200 [thread overview]
Message-ID: <ase33z4RBKKPCkq0@spark.kcore.it> (raw)
In-Reply-To: <20261008-cvs-privacy-led-v1-1-b78d5c512cba@gmail.com>
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256
Tested-by: Marco Nenciarini <mnencia@kcore.it>
Tested on a Dell Pro Max 16 Premium (MA16250) with Debian v7.2.6. I
built intel_cvs.ko with this one-line change applied and have run it
for 3 days. The kernel log shows quirks 0x3a, the privacy LED turns
on while streaming, and the stream is unaffected.
-----BEGIN PGP SIGNATURE-----
iQIzBAEBCAAdFiEEfCO4BD5l0pgKIbbiWJ8D8BulUDgFAmrHt88ACgkQWJ8D8Bul
UDiC3A//ThtRB5yWW3wiRv8hbttq6zZOleyfqhf++uT8qgLMAFgDtWPCrc05CrzI
DGroF+1zEQtfZIVW5hjy6/K7j2gUDrEA+lR1EMMiyt0xaMgdUyFWdGx5fAhcHwgZ
GRTcnkMoQOuRxg1FJ/w54wvj81lheoAPDOtjVjvmzf7F/16I1NQdJdd8Y8oOczQ9
n/o7BNpfnwNmXZPHQ8wsdX+dC694htZd/3gkjU8VnPcUaxb9WCQTFkewCwZbnvgq
h3aVKGd5Q53yN4EW3Wf4j6ITxxOxcaIEwYOqXpC+WgC6XJIj4wHDS8R6DDC+9JR5
7NWRcTFx91BL6iAWW+rinjpUoBDcIrUd2BC08H0J90UvPQcMJris5ygeK+e6HYig
8Us15j2EZNZMNSj6DnsKcmdCU3wG5j/YU6lanONHuUxWZxgqflkrthEJpE2glWcC
q+K1TNGMSIONGnYOp/1E6sR1UeaCEUXwNHjeugk1xepDlHltCkiKMyQ0Xkm5JGkb
NXie+fGUkY7mpCa0AC4ja60bh/vtCZRS/glvzdXH2tZNMeYin/0Ng3mAdasK8tV4
PCYqb/s+7Qkw8FvRnrB9UR7rYFirzCP8PeUSQUqk74LLjgWa31gqeeZkoLnJS2Eq
O9cioaU5Pq9u1DBk9vnVh//cD/pBz9OFN48NHcOCzGYQeZmIE7M=
=YAvp
-----END PGP SIGNATURE-----
next prev parent reply other threads:[~2026-10-08 15:49 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-10-08 15:09 [PATCH] media: i2c: cvs: Leave the privacy LED to firmware on Synaptics SVP7xxx Praveen Puglia via B4 Relay
2026-10-08 15:09 ` Praveen Puglia
2026-10-08 15:33 ` Marco Nenciarini [this message]
2026-10-09 10:42 ` Antti Laakso
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=ase33z4RBKKPCkq0@spark.kcore.it \
--to=mnencia@kcore.it \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-media@vger.kernel.org \
--cc=mchehab@kernel.org \
--cc=mehdi.djait@linux.intel.com \
--cc=miguel.vadillo@intel.com \
--cc=praveenpuglia@gmail.com \
--cc=sakari.ailus@linux.intel.com \
--cc=stable@vger.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 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.