IPU7 camera non-functional after building vision-drivers (CVS probe failure, no libcamera IPU7 pipeline)

[filosoho]

I am testing an Intel Lunar Lake system with an IPU7 MIPI camera on Fedora 43.

The kernel IPU7 driver loads correctly, firmware is present and the camera sensor is detected at the kernel level. libcamera and libcamera IPA packages are installed.

I followed the instructions referenced from Red Hat Bugzilla
(https://bugzilla.redhat.com/show_bug.cgi?id=2413656#c2),
which point to building this repository.

The vision-drivers repository builds successfully and produces the intel_cvs kernel module, which loads, but fails during device probe. As a result, libcamera continues to fall back to SimplePipeline:

No sensor found for /dev/media0

libcamera debug logs show that only ipu3 and simple pipeline handlers are available. There is no IPU7 pipeline or IPA module present, so libcamera cannot bind to the IPU7 media device even when the kernel driver loads.

It is unclear from the documentation whether this repository is expected to provide a usable IPU7 camera HAL / libcamera pipeline or if additional userspace components (HAL, IPA, sensor tuning) are required but not yet published.

Could you clarify the current status of IPU7 camera userspace support and whether vision-drivers is intended to enable a working libcamera pipeline?

---

Hardware

• Device: Dell XPS 13 9350
• CPU: Intel Core Ultra 7 256V (Lunar Lake)
• BIOS: 1.16.1 (11/07/2025)
• Camera sensor: OmniVision OV02C10 (i2c-OVTI02C1:00)
• CVS chip: INTC10DE:00

Software

• OS: Fedora Linux 43
• Kernel: 6.17.11-300.fc43.x86_64
• IPU7: Loaded successfully
• Modules loaded: gpio_usbio, usbio, i2c_usbio, int3472-discrete

Problem

The Intel CVS driver fails to communicate with the INTC10DE chip, preventing camera initialization.

Error Messages

Intel CVS driver i2c-INTC10DE:00: magic number in dev response not supported
Intel CVS driver i2c-INTC10DE:00: cvs_find_magic_num_support:Device protocol is 1.0
Intel CVS driver i2c-INTC10DE:00: cvs_common_probe:set_host_identifier cmd failed
Intel CVS driver i2c-INTC10DE:00: probe with driver Intel CVS driver failed with error -5

Additional Related Errors

gpio_usbio.usbio-gpio usbio.usbio-gpio.0: [Firmware Bug]: GPIO 4 is not in FW pins bitmap
int3472-discrete INT3472:00: [Firmware Bug]: unknown \_SB.GPI5 pin number mismatch _DSM 39 resource 32
int3472-discrete INT3472:00: unknown \_SB.GPI5 pin 32 active-high
int3472-discrete INT3472:00: GPIO type 0x02 unknown; the sensor may not work
ov02c10 i2c-OVTI02C1:00: Error reading reg 0x300a: -121
ov02c10 i2c-OVTI02C1:00: failed to find sensor: -121

Analysis

1. The CVS driver appears unable to negotiate the reported device protocol (“magic number”), leading to probe failure.
2. Device reports protocol version 1.0 which may not be supported
3. set_host_identifier command fails with error -5 (EIO)
4. Multiple firmware bugs in GPIO and ACPI configuration

Expected Behavior

CVS driver should successfully probe and communicate with INTC10DE chip, enabling camera functionality. A libcamera IPU7 pipeline and HAL should be available.

Actual Behavior

CVS driver probe fails with error -5. libcamera only sees ipu3 and simple pipelines. Camera remains non-functional.

Attaching debug logs for reference:

• libcamera-qcam-debug.txt:
  shows libcamera starting, detecting /dev/media0, but only ipu3 and simple pipeline handlers are available. No IPU7 pipeline or IPA module is present, so libcamera cannot use the IPU7 camera.

• dmesg-ipu7.txt:
  shows intel_cvs module loading and firmware initialization. CVS probe fails with error -5, as well as sensor read errors for OV02C10.

These logs illustrate that the kernel driver loads correctly, but the userspace pipeline / HAL for IPU7 is missing or not activated. Please let me know if additional information is needed.

libcamera-debug.txt
dmesg-ipu7.txt