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 v4 0/5] Enable cameras on Dell Latitude 5285 2-in-1
Date: Tue, 21 Apr 2026 15:52:12 -0700 [thread overview]
Message-ID: <20260421225217.12472-1-tchatard@gmail.com> (raw)
In-Reply-To: <aeMvy5aL0hSNNmEd@kekkonen.localdomain>
This series enables the front (OV5670/INT3479) and rear (OV8858/INT3477)
cameras on the Dell Latitude 5285 2-in-1 under Linux.
Changes since v3 (addressing feedback from Sakari Ailus and Hans de Goede):
- Patch 1: Fix multi-line comment style (blank opening line).
- Patch 2: Fix multi-line comment style; change n_consumers and loop
variable i from int to unsigned int; remove spurious (int) cast.
- Patch 3: Rework regulator mapping per Hans's review:
* VIO has no enable register and is always-on at hardware level; it
must never have direct software consumers. Rename
surface_go_tps68470_vio_reg_init_data to generic_tps68470_vio_reg_init_data
(used by both Surface Go and Dell 5285) and remove all VIO consumers.
* Map VSIO to dovdd/INT3477 instead of vsio/INT3477. Enabling VSIO
sets S_I2C_CTL (reg 0x43) which opens the I2C passthrough to OV8858;
since ov8858 enables dovdd before any I2C transaction, the passthrough
is guaranteed to be active in time without marking VSIO always_on.
* Remove always_on from VSIO (was a workaround; no longer needed).
* Update commit message to reflect the new design.
- Patch 5: Remove "vsio" from ov8858_supply_names[] (VSIO now maps to
"dovdd", which the driver already requests); remove ACPI_PTR() wrapper
(unnecessary when the ACPI table is declared unconditionally); update
commit message and title.
- Patches 4: Unchanged.
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
next prev parent reply other threads:[~2026-04-21 22:52 UTC|newest]
Thread overview: 38+ 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 ` [PATCH v3 0/5] Enable cameras on Dell Latitude 5285 2-in-1 Thierry Chatard
2026-04-17 16:32 ` [PATCH v3 1/5] platform/x86: intel_lpss: add resource conflict quirk for Dell Latitude 5285 Thierry Chatard
2026-04-17 17:35 ` Hans de Goede
2026-04-18 6:31 ` Sakari Ailus
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-18 6:29 ` Sakari Ailus
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-18 7:16 ` Sakari Ailus
2026-04-21 22:52 ` Thierry Chatard [this message]
2026-04-21 22:52 ` [PATCH v4 1/5] platform/x86: intel_lpss: add resource conflict quirk " Thierry Chatard
2026-04-21 22:52 ` [PATCH v4 2/5] platform/x86: int3472: tps68470: fix clock consumer registration " Thierry Chatard
2026-04-21 22:52 ` [PATCH v4 3/5] platform/x86: int3472: tps68470: add board data " Thierry Chatard
2026-04-21 22:52 ` [PATCH v4 4/5] media: ipu-bridge: add sensor configuration for OV8858 (INT3477) Thierry Chatard
2026-04-21 22:52 ` [PATCH v4 5/5] media: ov8858: add ACPI device ID INT3477 Thierry Chatard
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-18 7:18 ` Sakari Ailus
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=20260421225217.12472-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