[PATCH 0/2] media: atomisp: Fix PipeWire/Firefox streaming for sensors without crop or frame interval support
From: Volodymyr Chapman
Date: Mon Nov 16 2026 - 12:58:26 EST
With PipeWire as the camera path, Firefox could not stream from the two
cameras of a Lenovo ThinkPad 10 (20C3) on atomisp:
- Patch 1: for sensors without crop support, VIDIOC_ENUM_FRAMESIZES lists
sizes which the preview pipeline cannot output, so format negotiation
fails when userspace picks the largest one (IMX175 3264x2448).
- Patch 2: VIDIOC_ENUM_FRAMEINTERVALS fails for sensors without
enum_frame_interval, so PipeWire advertises a 1-120 fps range, which
Firefox turns into 1 fps. atomisp now reports the sensor's current
frame interval from get_frame_interval or the pixel rate and blanking
controls.
Patch 2 has no Fixes tag: ENUM_FRAMEINTERVALS never worked for these
sensors, so this is more an improvement than a regression fix.
Tested on the ThinkPad 10 with the OV2722 front sensor and the IMX175 rear
sensor (the IMX175 driver is pending in a separate series [1]), with both
patches built out of tree against a 7.2.15 kernel: Firefox 160 streams from
both sensors at about 30 fps through PipeWire. Build-tested on media.git
next.
[1] https://lore.kernel.org/linux-media/20261116175151.20150-1-volodymyrchapman@xxxxxxxxx/
The problems were investigated and the patches drafted with the help of an
AI coding assistant (Claude); the testing was done on the hardware by the
submitter.
Volodymyr Chapman (2):
media: atomisp: Don't enumerate frame sizes the preview pipe can't
output
media: atomisp: Report frame interval for sensors without
enum_frame_interval
.../staging/media/atomisp/pci/atomisp_ioctl.c | 86 ++++++++++++++++++-
1 file changed, 83 insertions(+), 3 deletions(-)
base-commit: 3fc9303dba01676c2090768126e5327e341b7761
--
2.43.0