** Description changed:
Kernel 7.3's ipu-bridge has a sensor entry for the IR sensor:
IPU_SENSOR_CONFIG("HIMX1092", 2, 180000000, 180480000)
but 7.3 ships no driver for the HM1092. ipu-bridge therefore creates a
graph endpoint for it that is never bound, and the IPU7 ISYS async
notifier waits for it forever. The comment above the table itself says
"Do not add an entry for a sensor that is not actually supported."
My setup
--------
- Ubuntu 26.10 on XPS 13 (9350), pre-installed with Ubuntu 24.04 LTS, ov02c10
camera.
+ Ubuntu 26.10 on XPS 13 (9350), pre-installed with Ubuntu 24.04 LTS, IPU7
ov02c10 camera.
Effect
------
- `isys_notifier_complete` never runs: "All sensor registration completed." is
missing from the kernel log (present on 7.0).
- /sys/kernel/debug/v4l2-async/pending_async_subdevices shows:
ipu7: [fwnode] dev=nil, node=HIMX1092-1/port@0/endpoint@0
- The RGB sensor (ov02c10 12-0036) binds through Intel CVS's sub-notifier
rather than ISYS's bound() callback, so no /dev/v4l-subdev node is created
for it while the ISYS notifier is incomplete.
- Intel's camera HAL (libcamhal-ipu7x) cannot set the sensor's format or
controls, so the picture comes out with wrong colours / exposure.
Steps to reproduce
------------------
1. Boot 7.3.0-9-generic on a Lunar Lake laptop whose ACPI tables list HIMX1092
(e.g. Dell XPS 13 9350).
2. `journalctl -k -b | grep "sensor registration"` → nothing.
3. `sudo cat /sys/kernel/debug/v4l2-async/pending_async_subdevices` → the
HIMX1092 endpoint above is pending.
4. `ls /dev/v4l-subdev*` and check for ov02c10 → no subdev for the sensor.
Temporary workaround
--------------------
Rebuilding ipu-bridge from the 7.3.0-9.9 source with only the HIMX1092 entry
removed (out-of-tree DKMS module): "All sensor registration completed."
returns, `v4l-subdev5: ov02c10 12-0036` appears, and the camera's colours are
correct. No other change was needed for this part.
AI assistance declaration
-------------------------
This bug was investigated with the help of an AI assistant. That said, I ran
the tests on my own hardware and confirmed the results above (the missing "All
sensor registration completed." message and pending HIMX1092 endpoint on the
stock kernel, and the camera working correctly with the workaround).
** Description changed:
Kernel 7.3's ipu-bridge has a sensor entry for the IR sensor:
IPU_SENSOR_CONFIG("HIMX1092", 2, 180000000, 180480000)
but 7.3 ships no driver for the HM1092. ipu-bridge therefore creates a
graph endpoint for it that is never bound, and the IPU7 ISYS async
notifier waits for it forever. The comment above the table itself says
"Do not add an entry for a sensor that is not actually supported."
My setup
--------
Ubuntu 26.10 on XPS 13 (9350), pre-installed with Ubuntu 24.04 LTS, IPU7
ov02c10 camera.
Effect
------
- - `isys_notifier_complete` never runs: "All sensor registration completed." is
- missing from the kernel log (present on 7.0).
- - /sys/kernel/debug/v4l2-async/pending_async_subdevices shows:
- ipu7: [fwnode] dev=nil, node=HIMX1092-1/port@0/endpoint@0
- The RGB sensor (ov02c10 12-0036) binds through Intel CVS's sub-notifier
rather than ISYS's bound() callback, so no /dev/v4l-subdev node is created
for it while the ISYS notifier is incomplete.
- Intel's camera HAL (libcamhal-ipu7x) cannot set the sensor's format or
controls, so the picture comes out with wrong colours / exposure.
Steps to reproduce
------------------
1. Boot 7.3.0-9-generic on a Lunar Lake laptop whose ACPI tables list HIMX1092
(e.g. Dell XPS 13 9350).
2. `journalctl -k -b | grep "sensor registration"` → nothing.
3. `sudo cat /sys/kernel/debug/v4l2-async/pending_async_subdevices` → the
HIMX1092 endpoint above is pending.
4. `ls /dev/v4l-subdev*` and check for ov02c10 → no subdev for the sensor.
Temporary workaround
--------------------
Rebuilding ipu-bridge from the 7.3.0-9.9 source with only the HIMX1092 entry
removed (out-of-tree DKMS module): "All sensor registration completed."
returns, `v4l-subdev5: ov02c10 12-0036` appears, and the camera's colours are
correct. No other change was needed for this part.
AI assistance declaration
-------------------------
This bug was investigated with the help of an AI assistant. That said, I ran
the tests on my own hardware and confirmed the results above (the missing "All
sensor registration completed." message and pending HIMX1092 endpoint on the
stock kernel, and the camera working correctly with the workaround).
** Summary changed:
- ipu-bridge lists Himax HM1092 (HIMX1092) without a driveripu-bridge: HIMX1092
entry without a driver breaks IPU7 camera (ov02c10)
+ ipu-bridge: HIMX1092 entry without a driver breaks IPU7 camera (ov02c10)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2171286
Title:
ipu-bridge: HIMX1092 entry without a driver breaks IPU7 camera
(ov02c10)
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2171286/+subscriptions
--
ubuntu-bugs mailing list
[email protected]
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
