summaryrefslogtreecommitdiff
path: root/tools/perf/scripts/python/check-perf-trace.py
diff options
context:
space:
mode:
authorHans de Goede <hdegoede@redhat.com>2022-12-13 00:32:22 +0300
committerMauro Carvalho Chehab <mchehab@kernel.org>2023-02-08 10:01:53 +0300
commit159a61da965a3f099b35c98e9f635e6d14d87d7a (patch)
tree62bc76b2a2f849b4228c0e23d87cee752d4f4b3f /tools/perf/scripts/python/check-perf-trace.py
parent7f04875057eb68e6b371f05ff055134dba1e27d5 (diff)
downloadlinux-159a61da965a3f099b35c98e9f635e6d14d87d7a.tar.xz
media: atomisp: Remove V4L2_CID_BIN_FACTOR_HORZ/_VERT
The bin-factor-x and bin-factor-y ctrls are only used internally to get a single value to pass to atomisp_css_input_set_binning_factor(), which is supposed to tune the lens-shading correction for the binning factor. But all sensor drivers return either 0 or 1 for this, with 0 meaning unset and 1 meaning no-binning. Even though some modes do actually do binning ... Also note that the removed atomisp_get_sensor_bin_factor() would fall back to 0 if either the x and y factor differ or if the ctrls are not implemented (not all sensor drivers implement them). Simply always pass 0 to atomisp_css_input_set_binning_factor(). This is part of a patch-series which tries to remove atomisp specific / custom code from the sensor drivers, with as end goal to make the atomisp drivers regular camera sensor drivers. Reviewed-by: Andy Shevchenko <andy@kernel.org> Signed-off-by: Hans de Goede <hdegoede@redhat.com> Signed-off-by: Mauro Carvalho Chehab <mchehab@kernel.org>
Diffstat (limited to 'tools/perf/scripts/python/check-perf-trace.py')
0 files changed, 0 insertions, 0 deletions