diff options
author | Laurent Pinchart <laurent.pinchart+renesas@ideasonboard.com> | 2014-05-27 09:41:05 -0300 |
---|---|---|
committer | Mauro Carvalho Chehab <m.chehab@samsung.com> | 2014-07-17 12:44:47 -0300 |
commit | d52e23813672c3c72f92e7b39c7408d4b9a40a96 (patch) | |
tree | a06c0a574588b3222a6795064c2ca4da37ceea91 /tools/thermal/tmon/Makefile | |
parent | b04ef7c075e8806fa18bc849e32d6a3163150cec (diff) | |
download | op-kernel-dev-d52e23813672c3c72f92e7b39c7408d4b9a40a96.zip op-kernel-dev-d52e23813672c3c72f92e7b39c7408d4b9a40a96.tar.gz |
[media] v4l: Support extending the v4l2_pix_format structure
The v4l2_pix_format structure has no reserved field. It is embedded in
the v4l2_framebuffer structure which has no reserved fields either, and
in the v4l2_format structure which has reserved fields that were not
previously required to be zeroed out by applications.
To allow extending v4l2_pix_format, inline it in the v4l2_framebuffer
structure, and use the priv field as a magic value to indicate that the
application has set all v4l2_pix_format extended fields and zeroed all
reserved fields following the v4l2_pix_format field in the v4l2_format
structure.
The availability of this API extension is reported to userspace through
the new V4L2_CAP_EXT_PIX_FORMAT capability flag. Just checking that the
priv field is still set to the magic value at [GS]_FMT return wouldn't
be enough, as older kernels don't zero the priv field on return.
To simplify the internal API towards drivers zero the extended fields
and set the priv field to the magic value for applications not aware of
the extensions.
Signed-off-by: Laurent Pinchart <laurent.pinchart+renesas@ideasonboard.com>
Signed-off-by: Mauro Carvalho Chehab <m.chehab@samsung.com>
Diffstat (limited to 'tools/thermal/tmon/Makefile')
0 files changed, 0 insertions, 0 deletions