From: Thierry Chatard <tchatard@gmail.com>
To: linux-kernel@vger.kernel.org
Cc: hansg@kernel.org, lee@kernel.org,
platform-driver-x86@vger.kernel.org,
ilpo.jarvinen@linux.intel.com, djrscally@gmail.com,
linux-media@vger.kernel.org, mchehab@kernel.org,
sakari.ailus@linux.intel.com, jacopo.mondi@ideasonboard.com,
nicholas@rothemail.net, Thierry Chatard <tchatard@gmail.com>
Subject: [PATCH v3 0/5] Enable cameras on Dell Latitude 5285 2-in-1
Date: Fri, 17 Apr 2026 09:32:47 -0700 [thread overview]
Message-ID: <20260417163252.15603-1-tchatard@gmail.com> (raw)
In-Reply-To: <4ef5f305-0234-4193-a190-edbfe770ea04@kernel.org>
This series enables the front (OV5670/INT3479) and rear (OV8858/INT3477)
cameras on the Dell Latitude 5285 2-in-1 under Linux.
Changes since v2:
- Patch 2: Replaced the GNVS AML scanner (rejected) with a static clock
consumer list in int3472_tps68470_board_data. Adds n_clk_consumers and
clk_consumers fields to the struct; probe uses them when present instead
of for_each_acpi_consumer_dev(). All other platforms are unaffected.
- Patch 3: Adds dell_5285_clk_consumers[] (INT3477 + INT3479) and wires it
into the Dell 5285 board_data entry.
- Patches 1, 4, 5: Unchanged.
Background on the _DEP issue (patch 2):
The BIOS leaves GNVS field C0TP at zero, causing INT3479's _DEP to resolve
to PCI0 rather than the INT3472. As Hans noted, the i2c-INT3479:00 client
is created correctly by the ACPI+I2C core (PCI0 is available), so the device
itself is present. The only visible effect of the broken _DEP is that
for_each_acpi_consumer_dev() on INT3472 misses INT3479, and its clock
consumer lookup entry is never registered. The static clk_consumers list in
board_data fixes this directly. Tested without any GNVS modification: both
cameras are operational, confirming no ACPI table patching is needed.
Tested on Ubuntu 25.10, kernel 6.17.0-22-generic. Both cameras working in
Zoom, Chrome, and GNOME Camera via PipeWire.
Thierry Chatard (5):
platform/x86: intel_lpss: add resource conflict quirk for Dell Latitude 5285
platform/x86: int3472: tps68470: fix clock consumer registration for Dell Latitude 5285
platform/x86: int3472: tps68470: add board data for Dell Latitude 5285
media: ipu-bridge: add sensor configuration for OV8858 (INT3477)
media: ov8858: add ACPI device ID INT3477 and vsio power supply
drivers/clk/clk-tps68470.c | 2 +-
drivers/media/i2c/ov8858.c | 23 ++-
drivers/platform/x86/intel/int3472/tps68470.c | 35 +++--
drivers/platform/x86/intel/int3472/tps68470.h | 13 +-
drivers/platform/x86/intel/int3472/tps68470_board_data.c | 176 ++++++++++++++++++++++
drivers/platform/x86/intel/lpss/intel_lpss_acpi.c | 16 ++
media/ipu-bridge.c | 1 +
7 files changed, 254 insertions(+), 11 deletions(-)
next prev parent reply other threads:[~2026-04-17 16:33 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-03-20 0:09 [PATCH 0/5] Enable dual cameras on Dell Latitude 5285 2-in-1 Thierry Chatard
2026-03-20 0:09 ` [PATCH 1/5] platform/x86: intel_lpss: add resource conflict quirk for Dell Latitude 5285 Thierry Chatard
2026-03-20 0:09 ` [PATCH 2/5] platform/x86: int3472: tps68470: fix GNVS clock fields " Thierry Chatard
2026-03-21 9:44 ` kernel test robot
2026-03-20 0:09 ` [PATCH 3/5] platform/x86: int3472: tps68470: add board data " Thierry Chatard
2026-03-20 0:09 ` [PATCH 4/5] media: ipu-bridge: add sensor configuration for OV8858 (INT3477) Thierry Chatard
2026-03-20 0:09 ` [PATCH 5/5] media: ov8858: add ACPI device ID INT3477 and vsio power supply Thierry Chatard
2026-03-24 21:41 ` [PATCH v2 0/5] Enable dual cameras on Dell Latitude 5285 2-in-1 Thierry Chatard
2026-03-24 21:41 ` [PATCH v2 1/3] platform/x86: intel_lpss: add resource conflict quirk for Dell Latitude 5285 Thierry Chatard
2026-04-13 9:48 ` Hans de Goede
2026-03-24 21:41 ` [PATCH v2 2/3] platform/x86: int3472: tps68470: fix GNVS clock fields " Thierry Chatard
2026-04-13 11:02 ` Hans de Goede
2026-04-17 16:32 ` Thierry Chatard [this message]
2026-04-17 16:32 ` [PATCH v3 1/5] platform/x86: intel_lpss: add resource conflict quirk " Thierry Chatard
2026-04-17 17:35 ` Hans de Goede
2026-04-17 16:32 ` [PATCH v3 2/5] platform/x86: int3472: tps68470: fix clock consumer registration " Thierry Chatard
2026-04-17 17:40 ` Hans de Goede
2026-04-17 16:32 ` [PATCH v3 3/5] platform/x86: int3472: tps68470: add board data " Thierry Chatard
2026-04-17 18:54 ` Hans de Goede
2026-04-17 16:32 ` [PATCH v3 4/5] media: ipu-bridge: add sensor configuration for OV8858 (INT3477) Thierry Chatard
2026-04-17 18:56 ` Hans de Goede
2026-04-17 16:32 ` [PATCH v3 5/5] media: ov8858: add ACPI device ID INT3477 and vsio power supply Thierry Chatard
2026-04-17 18:59 ` Hans de Goede
2026-04-17 16:35 ` [PATCH v2 2/3] platform/x86: int3472: tps68470: fix GNVS clock fields for Dell Latitude 5285 tchatard
2026-03-24 21:41 ` [PATCH v2 3/3] platform/x86: int3472: tps68470: add board data " Thierry Chatard
2026-03-24 21:41 ` [PATCH v2 4/5] media: ipu-bridge: add sensor configuration for OV8858 (INT3477) Thierry Chatard
2026-03-24 21:41 ` [PATCH v2 5/5] media: ov8858: add ACPI device ID INT3477 and vsio power supply Thierry Chatard
2026-04-13 9:45 ` [PATCH v2 0/5] Enable dual cameras on Dell Latitude 5285 2-in-1 Hans de Goede
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=20260417163252.15603-1-tchatard@gmail.com \
--to=tchatard@gmail.com \
--cc=djrscally@gmail.com \
--cc=hansg@kernel.org \
--cc=ilpo.jarvinen@linux.intel.com \
--cc=jacopo.mondi@ideasonboard.com \
--cc=lee@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-media@vger.kernel.org \
--cc=mchehab@kernel.org \
--cc=nicholas@rothemail.net \
--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