linux6.18: CONFIG_VIDEO_OV02C10 (and CONFIG_INTEL_VSC) not enabled, breaks camera on Samsung Galaxy Book and other IPU6/OVTI02C1 laptops

[louiszn]

Is this a new report?

Yes

System Info

Void 6.18.48_1 x86_64 GenuineIntel notuptodate rr

Package(s) Affected

linux6.18-6.18.48_1

Does a report exist for this bug with the project's home (upstream) and/or another distro?

Upstream (intel/ipu6-drivers), related tracking issues for OV02C10 support/quality, though not specifically about kernel config being disabled:

• OV02C10 sensor on Samsung Galaxy Book4 Pro 360 (DMI: 960QGK) - grey/washed image quality and ~20fps cap via Software ISP intel/ipu6-drivers#431 (image quality/calibration tracking for OV02C10)
• Support for Raptor Lake ( and OV02C10? ) Sensor module not seen by ipu6 modules. intel/ipu6-drivers#171 (Raptor Lake + OV02C10 support discussion, similar Samsung Galaxy Book 3 Pro 360 hardware)
• Ubuntu does not see OV02C10. intel/ipu6-drivers#227 (Samsung Galaxy Book 3 Ultra, sensor not detected)

Other distros confirms driver works once properly enabled/built, but these are packaging-level fixes on other distros, not a report about Void's config specifically:

• https://bbs.archlinux.org/viewtopic.php?id=277462 (Arch: build/link issues with ov02c10 + Intel VSC dependency)
• Intel IPU6 MIPI camera Raptor Lake not working omacom/omarchy#5676 (Omarchy/Arch-based: OV02C10 on Raptor Lake, notes same calibration limitation)

Expected behaviour

CONFIG_VIDEO_OV02C10=m enabled in linux6.18, so the OV02C10 sensor is detected and usable without an out-of-tree DKMS build.

Actual behaviour

Camera does not work. No sensor entity appears in the media graph (media-ctl -p -d /dev/media0 only shows IPU6 capture/CSI2 nodes, no ov02c10 entity), because CONFIG_VIDEO_OV02C10 is not set.

Steps to reproduce

1. Install Void on a laptop that has an Intel IPU6 camera with an OmniVision OV02C10 sensor (ACPI HID OVTI02C1), for example a Samsung Galaxy Book 940XFG.
2. Check that the sensor is actually present on the system by running ls /sys/bus/i2c/devices/ and grepping for OVTI. You should see i2c-OVTI02C1:00 listed.
3. Check the running kernel config with zcat /proc/config.gz and grep for OV02C10 and IPU6. You will see that CONFIG_VIDEO_INTEL_IPU6 is enabled as a module, but CONFIG_VIDEO_OV02C10 is not set.
4. Run media-ctl -p -d /dev/media0 to look at the camera media graph. You will only see IPU6 ISYS Capture nodes and CSI2 receiver entities, but no entity for the sensor itself.
5. Try to use the camera in any application. It will not work, since there is no sensor driver bound to produce a usable video stream.

[louiszn]

@Duncaen Thanks for merging the OV02C10 support! I tested it on my Samsung NP940XFG and found two additional things needed for the camera to work.

First, CONFIG_IPU_BRIDGE=m is still missing. With CONFIG_VIDEO_INTEL_IPU6=m and CONFIG_VIDEO_OV02C10=m, both modules load, but the sensor remains stuck at:

ov02c10 i2c-OVTI02C1:00: deferred probe pending: ov02c10: waiting for fwnode graph endpoint

This appears to be a known issue on other distributions as well:

• https://bugzilla.altlinux.org/show_bug.cgi?id=59770
• Support for Raptor Lake ( and OV02C10? ) Sensor module not seen by ipu6 modules. intel/ipu6-drivers#171

Could CONFIG_IPU_BRIDGE=m be enabled for the relevant kernel configurations, including newer kernels such as 7.0?

Second, the NP940XFG's OV02C10 uses a 26 MHz external clock, which the current driver rejects:

ov02c10 i2c-OVTI02C1:00: error -EINVAL: external clock 26000000 is not supported
ov02c10 i2c-OVTI02C1:00: probe with driver ov02c10 failed with error -22

There is already precedent for 26 MHz OV02C10 support on other Galaxy Book systems:

• https://github.com/abdallah-alkanani/galaxybook3-ov02c10-fix
• https://github.com/Andycodeman/samsung-galaxy-book-linux-fixes/tree/main/ov02c10-26mhz-fix

I have a small patch to allow both 19.2 MHz and 26 MHz:

--- a/drivers/media/i2c/ov02c10.c
+++ b/drivers/media/i2c/ov02c10.c
@@ -15,7 +15,8 @@
 #include <media/v4l2-fwnode.h>

 #define OV02C10_LINK_FREQ_400MHZ	400000000ULL
-#define OV02C10_MCLK			19200000
+#define OV02C10_MCLK_19_2MHZ	19200000UL
+#define OV02C10_MCLK_26MHZ		26000000UL
 #define OV02C10_RGB_DEPTH		10

 #define OV02C10_REG_CHIP_ID		CCI_REG16(0x300a)
@@ -857,6 +858,11 @@
 	}
 }

+static bool ov02c10_mclk_supported(unsigned long freq)
+{
+	return freq == OV02C10_MCLK_19_2MHZ || freq == OV02C10_MCLK_26MHZ;
+}
+
 static int ov02c10_probe(struct i2c_client *client)
 {
 	struct ov02c10 *ov02c10;
@@ -875,7 +881,7 @@
 				     "failed to get imaging clock\n");

 	freq = clk_get_rate(ov02c10->img_clk);
-	if (freq != OV02C10_MCLK)
+	if (!ov02c10_mclk_supported(freq))
 		return dev_err_probe(ov02c10->dev, -EINVAL,
 				     "external clock %lu is not supported",
 				     freq);

I haven't pushed this patch yet, but I can push it if useful.

The existing Galaxy Book fixes also suggest that 26 MHz support needs some care beyond simply bypassing the clock check, since the sensor timing was originally configured around a 19.2 MHz MCLK. I'd therefore prefer to carry the proper 26 MHz handling rather than only relaxing the validation. This is particularly relevant for getting the 24 Hz camera mode working correctly on the NP940XFG.

Could these changes be carried forward to the newer kernel versions, including 7.0? I'm happy to test any patch or interim workaround on the NP940XFG if that helps.

[louiszn]

I tried the temp patch for unblocking 26 mhz device with the following config changes:

CONFIG_IPU_BRIDGE=m
CONFIG_VIDEO_OV02C10=m
CONFIG_VIDEO_ATOMISP=n

and it worked on my Samsung NP940XFG. The IPU6 now detects and connects the camera:

intel-ipu6 0000:00:05.0: Found supported sensor OVTI02C1:00
intel-ipu6 0000:00:05.0: Connected 1 cameras

The OV02C10 sensor also appears correctly in the media graph:

entity 233: ov02c10 15-0036 (1 pad, 1 link, 0 routes)
        <- "ov02c10 15-0036":0 [ENABLED,IMMUTABLE]

So CONFIG_IPU_BRIDGE=m appears to be the missing piece for the FWNODE graph issue on this system. CONFIG_VIDEO_ATOMISP=n was also added to avoid the new config prompt during the build.