summaryrefslogtreecommitdiffstats
path: root/tools/lib/python/kdoc
diff options
context:
space:
mode:
authorHans de Goede <hansg@kernel.org>2025-10-14 19:40:24 +0200
committerHans Verkuil <hverkuil+cisco@kernel.org>2026-01-13 12:28:49 +0100
commit896f4e21af4f53719f841b647d084f4689d5ad6c (patch)
treec91348f79edef840f8dc5d35eb16ee741d25e554 /tools/lib/python/kdoc
parent299b82078696ac14325a605b3d2727ff00d6e73e (diff)
downloadlinux-896f4e21af4f53719f841b647d084f4689d5ad6c.tar.gz
linux-896f4e21af4f53719f841b647d084f4689d5ad6c.zip
media: i2c: ov01a10: Add cropping support / allow arbitrary sizes
Remove the fixed mode list and add cropping support. The main reason for doing this is to allow libcamera to select 1292x812 instead of 1280x800 so that after the extra border which the CPU debayer code needs libcamera can output 1280x720 instead of 1276x720. This in turn allows google-meet to use 720p instead of it falling back to a pretty bad 360p. This has been tested on a Dell XPS 9320, with both libcamera as well as with Intel's out-of-tree psys driver + proprietary userspace stack. Libcamera asks for 1292x812 where as the Intel stack asks for 1280x800 and neither stack explicitly sets the crop-window. Hence the need for ov01a10_set_format() to adjust the crop-window if necessary. Note the differentiating between pattern_size and border_size is done in preparation for adding support for the monochrome OV01A1B model where coordinates still need to be aligned to a multiple of 2, but there will be no need for a border (border_size=0). Link: https://bugzilla.redhat.com/show_bug.cgi?id=2337593 Signed-off-by: Hans de Goede <hansg@kernel.org> Tested-by: Mehdi Djait <mehdi.djait@linux.intel.com> # Dell XPS 9315 Reviewed-by: Mehdi Djait <mehdi.djait@linux.intel.com> Signed-off-by: Sakari Ailus <sakari.ailus@linux.intel.com> Signed-off-by: Hans Verkuil <hverkuil+cisco@kernel.org>
Diffstat (limited to 'tools/lib/python/kdoc')
0 files changed, 0 insertions, 0 deletions