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,
dan.scally@ideasonboard.com, linux-media@vger.kernel.org,
mchehab@kernel.org, sakari.ailus@linux.intel.com,
jacopo.mondi@ideasonboard.com, nicholas@rothemail.net,
andriy.shevchenko@intel.com, v.vitovt@gmail.com,
dmanresa@gmail.com, Thierry Chatard <tchatard@gmail.com>
Subject: [PATCH v11 0/9] Enable cameras on Dell Latitude 5285 2-in-1
Date: Wed, 30 Sep 2026 14:43:12 -0700 [thread overview]
Message-ID: <20260930214321.600863-1-tchatard@gmail.com> (raw)
This series enables the front (OV5670/INT3479) and rear (OV8858/INT3477)
cameras on the Dell Latitude 5285 2-in-1 under Linux.
Per Documentation/process/coding-assistants.rst, every patch carries an
Assisted-by tag; this work was developed with help from an AI coding
assistant. I have reviewed and tested it on the hardware and take
responsibility for the result.
The series is interdependent and touches three subsystems:
- mfd: patches 1-2 (intel-lpss resource-conflict quirk)
- platform/x86: patches 3-7 (int3472/tps68470)
- media: patches 8-9 (ipu-bridge, ov8858)
Per Sakari's suggestion it is probably best merged as one set - e.g. the
mfd/platform-drivers-x86 patches via one tree with an immutable branch that
the media tree can pull. Lee, an Acked-by on the mfd patches (1-2) would
help enable that; I'm happy to follow whichever approach the maintainers
prefer.
Patch 2 (from D. Manresa) extends the intel-lpss quirk to the Dell Latitude
7275, which has the same BIOS bug; it is carried here at the maintainers'
request. The companion 7275 board-data patch is posted separately by
D. Manresa.
Changes since v10:
- New patch 2 (D. Manresa): add the Dell Latitude 7275 to the intel-lpss
resource-conflict quirk (Reviewed-by: Hans de Goede, Sakari Ailus).
- Patch 9 (ov8858): use ACPI_PTR() for the ACPI match table (Sakari).
- Collected Reviewed-by tags: Andy Shevchenko on patches 1, 7 and 8.
- Patch 5 (static clock consumer): kept the inline if/else as-is, per
Sakari (Andy had suggested a helper).
Earlier changelogs are in the v10 posting:
https://lore.kernel.org/all/20260831160754.9857-1-tchatard@gmail.com/
Tested on Ubuntu 25.10 (kernel 6.17.0-22-generic) and Ubuntu 26.04 (kernel
7.0.0-31-generic): both cameras working in Zoom, Chrome, and GNOME Camera
via PipeWire. Also independently tested on the closely-related Dell Latitude
5290 2-in-1 by Vitalii Tytskyi:
https://github.com/vitovt/dell-5290-camera-kernel/tree/master/patches
D. Manresa (1):
mfd: intel-lpss: add Dell Latitude 7275 to the resource conflict quirk
Thierry Chatard (8):
mfd: intel-lpss: add resource conflict quirk for Dell Latitude 5285
platform/x86: int3472: tps68470: use unsigned int for GPIO lookup loop
counters
platform/x86: int3472: tps68470: move Windows MFD setup below the
device-type switch
platform/x86: int3472: tps68470: add static clock consumer support
platform/x86: int3472: tps68470: use a common always-on VIO regulator
init_data
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
drivers/media/i2c/ov8858.c | 8 +
drivers/media/pci/intel/ipu-bridge.c | 2 +
drivers/mfd/intel-lpss-acpi.c | 38 ++++
drivers/platform/x86/intel/int3472/tps68470.c | 116 ++++++-----
drivers/platform/x86/intel/int3472/tps68470.h | 8 +
.../x86/intel/int3472/tps68470_board_data.c | 181 ++++++++++++++++--
6 files changed, 290 insertions(+), 63 deletions(-)
base-commit: cee9395acd8043be0644b25c34bfa86623f2b935
--
2.53.0
next reply other threads:[~2026-09-30 21:43 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-30 21:43 Thierry Chatard [this message]
2026-09-30 21:43 ` [PATCH v11 1/9] mfd: intel-lpss: add resource conflict quirk for Dell Latitude 5285 Thierry Chatard
2026-09-30 21:43 ` [PATCH v11 2/9] mfd: intel-lpss: add Dell Latitude 7275 to the resource conflict quirk Thierry Chatard
2026-09-30 21:43 ` [PATCH v11 3/9] platform/x86: int3472: tps68470: use unsigned int for GPIO lookup loop counters Thierry Chatard
2026-09-30 21:43 ` [PATCH v11 4/9] platform/x86: int3472: tps68470: move Windows MFD setup below the device-type switch Thierry Chatard
2026-09-30 21:43 ` [PATCH v11 5/9] platform/x86: int3472: tps68470: add static clock consumer support Thierry Chatard
2026-09-30 21:43 ` [PATCH v11 6/9] platform/x86: int3472: tps68470: use a common always-on VIO regulator init_data Thierry Chatard
2026-09-30 21:43 ` [PATCH v11 7/9] platform/x86: int3472: tps68470: add board data for Dell Latitude 5285 Thierry Chatard
2026-09-30 21:43 ` [PATCH v11 8/9] media: ipu-bridge: add sensor configuration for OV8858 (INT3477) Thierry Chatard
2026-09-30 21:43 ` [PATCH v11 9/9] media: ov8858: add ACPI device ID INT3477 Thierry Chatard
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=20260930214321.600863-1-tchatard@gmail.com \
--to=tchatard@gmail.com \
--cc=andriy.shevchenko@intel.com \
--cc=dan.scally@ideasonboard.com \
--cc=djrscally@gmail.com \
--cc=dmanresa@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 \
--cc=v.vitovt@gmail.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
all inboxes | Powered by JetHome®