From: "Angioli Samuele (gmail)" <angioli.samuele@gmail.com>
To: Marco Nenciarini <mnencia@kcore.it>, 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:58:19 +0200 [thread overview]
Message-ID: <c240369f-13e3-41ac-a5a6-761a5afafbbd@gmail.com> (raw)
In-Reply-To: <ajOc0H8Pvvr4exL5@spark.kcore.it>
Marco,
Agreed on all counts, and thanks for closing the loop on it.
I won't push the standalone dvdd_second_sensor quirk: a field with no
enabled board behind it is dead code, and the second_sensor mechanism is
already there for whenever a board that actually needs it shows up. The
validation stands on its own as a data point if that day comes.
I'll take the NVS topology issue to Dell through what channel I have --
the RGB-side PMIC (DSC1/LTH1/CLP1) being _STA=0 while only the IR-side
DSC0 is live looks like a factory-config decision on the Linux SKU, not
a hardware limit, since the Windows image drives the sensor fine. If
they flip the gate (or expose the rails on a live instance), the
existing int3472 paths should pick it up with no kernel change.
Thanks again to you, Hans and Sakari for the time on this one.
Samuele
Il 18/06/26 09:22, Marco Nenciarini ha scritto:
> 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
prev parent reply other threads:[~2026-06-18 7:58 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-06-01 14:06 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
2026-06-18 7:58 ` Angioli Samuele (gmail) [this message]
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=c240369f-13e3-41ac-a5a6-761a5afafbbd@gmail.com \
--to=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=mnencia@kcore.it \
--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
powered by JetHome