From: Marco Nenciarini <mnencia@kcore.it>
To: angioli.samuele@gmail.com, linux-media@vger.kernel.org
Cc: hansg@kernel.org, ilpo.jarvinen@linux.intel.com,
sakari.ailus@linux.intel.com, linux-kernel@vger.kernel.org,
platform-driver-x86@vger.kernel.org
Subject: Re: [BUG] OV02C10 on Dell 16 Premium DA16250 (ARL): INT3472 handshake-derived "dvdd" regulator registered but never linked to sensor, sensor probe fails with -EREMOTEIO
Date: Thu, 18 Jun 2026 09:22:56 +0200 [thread overview]
Message-ID: <ajOc0H8Pvvr4exL5@spark.kcore.it> (raw)
In-Reply-To: <dee36707-3fc9-486e-b18b-d6a246edb67c@gmail.com>
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256
Samuele,
The _STA dump settles it, thanks for running it down. With DSC1/LTH1/CLP1 all
_STA=0 and only DSC0 (INT3472:0c) live, the OV02C10 has no live PMIC instance on
the DA16250, and the gate is a BIOS/NVS config (CL01/C1TP read but never
assigned, no _OSI branch), so acpi_osi spoofing can't reach it. avdd/dovdd/reset/
clock have no live provider to key to.
That closes the kernel angle: there is nothing for int3472 to fix here, and the
dvdd re-key, though correct, can't bring the sensor up. This is a Dell firmware
matter (the RGB-side PMIC topology left disabled in NVS), worth reporting to them
if you have a channel.
On the standalone dvdd second_sensor quirk: I'd hold off. The second_sensor
mechanism already exists; a dvdd_second_sensor field with no enabled board behind
it would be unused code, and the kernel doesn't carry a quirk that has no
consumer. If a board turns up that actually benefits, the field and its DMI entry
can land together in that series, with the consumer that justifies them. Until
then there is nothing to upstream.
Thanks again for the thorough work on this one.
Marco
-----BEGIN PGP SIGNATURE-----
iQIzBAEBCAAdFiEEfCO4BD5l0pgKIbbiWJ8D8BulUDgFAmoznMEACgkQWJ8D8Bul
UDhpbQ//dT58F+M5aB3CZ6PCvL4SpGMkDD9LQKKMOH/xr4fZGGoDLu0cyrjbDAIk
/+4/rOi0UgjLoA1WkEZnitqxYQX88X+gVFs6Nedj/ajDV4lJO1CNDMmoQhYVkevy
feUvvPRTnM2rSWTxDdVIIy4/SmBSbGqruVfI8yWgPj3ifNBjbIRPudqWG2iBMgyH
2CsId6CabIAATEsG5sptxemYIKyQqu1svc2c/rvAWJfVDtsYYMYpZq6nrIydoNKU
zL91JiXuyLgS17nSYREC0lmXnRYraTL63nYR8eZGHV1oT7PMcWCizCoL/dHImuH/
dH/K6aiX7VC8aWmpd7JQ4Y9OGLRTikx49q2pmlnYCOjSzOs5M/oT6SH7wTx/pmby
0U3kczdXQ6xzooS9obcL/ufUMAEygHwZ2qZA0dbR92zm0XvN6LDSrMjdm7ZBmT8L
3equQOTlfm4sHEmOzYZGVK+f69d6tVeaZhJfubMHHCxfaOITnmr5Z61D8TzoOKuI
Pz+MokXBZ5KLJMVz3NvdLnVBqGK5DW5dszUqIJzITtbHIrQjBmV9GzeXGej3Dmrc
a03X9jwvcnPfgoxQNQPt++hEzXn2ANqf8Zda45KVILW9aQUrT+NYAEMpCEHUytt6
F4KWtNPNt19JZKHFdTbCd9ra3U/oKZQa0s34VY+NDY8SKkTnvwk=
=jGY+
-----END PGP SIGNATURE-----
next prev parent reply other threads:[~2026-06-18 7:23 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-06-01 14:06 [BUG] OV02C10 on Dell 16 Premium DA16250 (ARL): INT3472 handshake-derived "dvdd" regulator registered but never linked to sensor, sensor probe fails with -EREMOTEIO Angioli Samuele (gmail)
2026-06-03 7:26 ` Marco Nenciarini
2026-06-12 16:09 ` Angioli Samuele (gmail)
2026-06-13 17:01 ` Marco Nenciarini
2026-06-14 14:29 ` Angioli Samuele (gmail)
2026-06-14 20:23 ` Marco Nenciarini
2026-06-15 8:21 ` Angioli Samuele (gmail)
2026-06-15 10:25 ` Marco Nenciarini
2026-06-15 13:00 ` Angioli Samuele (gmail)
2026-06-18 7:22 ` Marco Nenciarini [this message]
2026-06-18 7:58 ` Angioli Samuele (gmail)
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=ajOc0H8Pvvr4exL5@spark.kcore.it \
--to=mnencia@kcore.it \
--cc=angioli.samuele@gmail.com \
--cc=hansg@kernel.org \
--cc=ilpo.jarvinen@linux.intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-media@vger.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