* Use of V4L2_SEL_TGT_CROP_DEFAULT in i2c subdev drivers
@ 2018-09-24 10:15 Helmut Grohne
0 siblings, 0 replies; only message in thread
From: Helmut Grohne @ 2018-09-24 10:15 UTC (permalink / raw)
To: linux-media
Hi,
Documentation/media/uapi/v4l/v4l2-selection-targets.rst says that
V4L2_SEL_TGT_CROP_DEFAULT is not valid for subdev drivers. Looking into
drivers/media/i2c (which contains only subdev drivers except for
video-i2c.c), the following drivers implement V4L2_SEL_TGT_CROP_DEFAULT:
ak881x.c
mt9m111.c
mt9t112.c
ov2640.c
ov6650.c
ov772x.c
rj54n1cb0c.c
soc_camera/mt9m001.c
soc_camera/mt9t112.c
soc_camera/mt9v022.c
soc_camera/ov5642.c
soc_camera/ov772x.c
soc_camera/ov9640.c
soc_camera/ov9740.c
soc_camera/rj54n1cb0c.c
tvp5150.c
The majority of drivers behave equally for V4L2_SEL_TGT_CROP_DEFAULT and
V4L2_SEL_TGT_CROP_BOUNDS. The only exceptions are mt9t112.c and
soc_camera/mt9t112.c. Actually these two look very similar. A
significant fraction of differences is white space, case and operand
order.
Is this a bug in 16 drivers? Is this a documentation bug? Am I getting
something wrong?
Helmut
^ permalink raw reply [flat|nested] only message in thread
only message in thread, other threads:[~2018-09-24 16:17 UTC | newest]
Thread overview: (only message) (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2018-09-24 10:15 Use of V4L2_SEL_TGT_CROP_DEFAULT in i2c subdev drivers Helmut Grohne
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).