From: Sahan Nissanka <adee.sahan@gmail.com>
To: platform-driver-x86@vger.kernel.org, linux-media@vger.kernel.org
Cc: dan.scally@ideasonboard.com, sakari.ailus@linux.intel.com,
hansg@kernel.org, ilpo.jarvinen@linux.intel.com,
mchehab@kernel.org, linux-kernel@vger.kernel.org
Subject: [PATCH 3/3] media: ipu-bridge: Add sensor configuration for OV5675 (OVTI5678)
Date: Sun, 9 Aug 2026 14:25:19 +1000 [thread overview]
Message-ID: <20260809042540.15849-4-adee.sahan@gmail.com> (raw)
In-Reply-To: <20260809042540.15849-1-adee.sahan@gmail.com>
The front camera of the Dell Latitude 7320 Detachable is an OV5675
described in ACPI as OVTI5678. Without an entry here ipu-bridge creates
no software node for it, so no fwnode endpoint exists and the sensor
cannot be connected to the IPU6 even once a driver binds it:
intel-ipu6 0000:00:05.0: Found supported sensor OVTI8856:00
intel-ipu6 0000:00:05.0: Connected 1 cameras
450 MHz is OV5675_LINK_FREQ_450MHZ, the only link frequency ov5675.c
supports, and matches the two data lanes the machine's SSDB reports.
With this entry both cameras are found and the front sensor appears in
the media graph:
intel-ipu6 0000:00:05.0: Found supported sensor OVTI5678:00
intel-ipu6 0000:00:05.0: Found supported sensor OVTI8856:00
intel-ipu6 0000:00:05.0: Connected 2 cameras
Signed-off-by: Sahan Nissanka <adee.sahan@gmail.com>
---
drivers/media/pci/intel/ipu-bridge.c | 2 ++
1 file changed, 2 insertions(+)
diff --git a/drivers/media/pci/intel/ipu-bridge.c b/drivers/media/pci/intel/ipu-bridge.c
index 9cebc6a..78fe1f7 100644
--- a/drivers/media/pci/intel/ipu-bridge.c
+++ b/drivers/media/pci/intel/ipu-bridge.c
@@ -101,6 +101,8 @@ static const struct ipu_sensor_config ipu_supported_sensors[] = {
IPU_SENSOR_CONFIG("OVTIDB10", 1, 560000000),
/* Omnivision OV2680 */
IPU_SENSOR_CONFIG("OVTI2680", 1, 331200000),
+ /* Omnivision OV5675, described as OVTI5678 in ACPI */
+ IPU_SENSOR_CONFIG("OVTI5678", 1, 450000000),
/* Omnivision OV8856 */
IPU_SENSOR_CONFIG("OVTI8856", 3, 180000000, 360000000, 720000000),
/* Sony IMX471 */
--
2.53.0
prev parent reply other threads:[~2026-08-09 4:27 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-08-09 4:25 [PATCH 0/3] Enable the front camera on the Dell Latitude 7320 Detachable Sahan Nissanka
2026-08-09 4:25 ` [PATCH 1/3] platform/x86: int3472: Add TPS68470 board data for Dell " Sahan Nissanka
2026-08-10 8:32 ` Sahan Nissanka
2026-08-09 4:25 ` [PATCH 2/3] media: i2c: ov5675: Add OVTI5678 ACPI id Sahan Nissanka
2026-08-10 8:09 ` Sakari Ailus
2026-08-10 9:24 ` Sahan Nissanka
2026-08-09 4:25 ` Sahan Nissanka [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=20260809042540.15849-4-adee.sahan@gmail.com \
--to=adee.sahan@gmail.com \
--cc=dan.scally@ideasonboard.com \
--cc=hansg@kernel.org \
--cc=ilpo.jarvinen@linux.intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-media@vger.kernel.org \
--cc=mchehab@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