[PATCH v11 08/14] media: intel: ipu-bridge: select OV2740 frequency by IPU ID

From: Maurizio Casciano

Date: Sat Nov 21 2026 - 08:33:22 EST


The OV2740 connected to the Cherry Trail AtomISP uses a 288 MHz link,
while the generic OVTI2740 configuration uses 360 MHz.

Use the bridge's existing PCI-device matching mechanism to add a
Cherry Trail-specific OVTI2740 entry before the generic fallback. This
keeps the platform distinction in the bridge and avoids adding a second
per-sensor link-frequency override path.

Suggested-by: Sakari Ailus <sakari.ailus@xxxxxxxxxxxxxxx>
Signed-off-by: Maurizio Casciano <mauriziocasciano7@xxxxxxxxx>
---
drivers/media/pci/intel/ipu-bridge.c | 7 +++++++
1 file changed, 7 insertions(+)

diff --git a/drivers/media/pci/intel/ipu-bridge.c b/drivers/media/pci/intel/ipu-bridge.c
index 5f6baac2c..5dbd74e2b 100644
--- a/drivers/media/pci/intel/ipu-bridge.c
+++ b/drivers/media/pci/intel/ipu-bridge.c
@@ -58,6 +58,11 @@ static const u16 ipu6_ov5693_ncont_clk[] = {
0
};

+static const u16 atomisp_cht_pci_ids[] = {
+ PCI_DEVICE_ID_INTEL_ISP_BSW,
+ 0
+};
+
static const struct ipu_sensor_config ipu_supported_sensors[] = {
/* GalaxyCore GC5035 */
IPU_SENSOR_CONFIG("GCTI5035", 2, 175200000, 422400000),
@@ -116,6 +121,8 @@ static const struct ipu_sensor_config ipu_supported_sensors[] = {
/* Omnivision OV2680 */
IPU_SENSOR_CONFIG("OVTI2680", 1, 331200000),
/* Omnivision OV2740 */
+ IPU_SENSOR_CONFIG_MATCH_FL("OVTI2740", atomisp_cht_pci_ids, 0,
+ 1, 288000000),
IPU_SENSOR_CONFIG("OVTI2740", 1, 360000000),
/* Omnivision OV5675 */
IPU_SENSOR_CONFIG("OVTI5675", 1, 450000000),
--
2.53.0