summaryrefslogtreecommitdiffstats
path: root/drivers/media/i2c/rdacm21.c
diff options
context:
space:
mode:
authorJanusz Krzysztofik <jmkrzyszt@gmail.com>2020-05-04 00:06:18 +0200
committerMauro Carvalho Chehab <mchehab@kernel.org>2022-01-28 19:32:48 +0100
commit985d2d7a482e9b64ef9643702b066da9cbd6ae8e (patch)
tree49b8d22bcd2ade157c8b008dc130f01f72cb96dd /drivers/media/i2c/rdacm21.c
parentc74052646496ffe0bc606152e6b9653137020cbf (diff)
downloadlinux-985d2d7a482e9b64ef9643702b066da9cbd6ae8e.tar.bz2
media: ov6650: Fix crop rectangle affected by set format
According to subdevice interface specification found in V4L2 API documentation, set format pad operations should not affect image geometry set in preceding image processing steps. Unfortunately, that requirement is not respected by the driver implementation of set format as it was not the case when that code was still implementing a pair of now obsolete .s_mbus_fmt() / .try_mbus_fmt() video operations before they have been merged and reused as an implementation of .set_fmt() pad operation by commit 717fd5b4907a ("[media] v4l2: replace try_mbus_fmt by set_fmt"). Exclude non-compliant crop rectangle adjustments from set format try, as well as a call to .set_selection() from set format active processing path, so only frame scaling is applied as needed and crop rectangle is no longer modified. [Sakari Ailus: Rebase on subdev state patches] Fixes: 717fd5b4907a ("[media] v4l2: replace try_mbus_fmt by set_fmt") Signed-off-by: Janusz Krzysztofik <jmkrzyszt@gmail.com> Signed-off-by: Sakari Ailus <sakari.ailus@linux.intel.com> Signed-off-by: Mauro Carvalho Chehab <mchehab@kernel.org>
Diffstat (limited to 'drivers/media/i2c/rdacm21.c')
0 files changed, 0 insertions, 0 deletions