linux.git/Documentation/userspace-api/media, branch v5.8

Documentation: media: convert to use i2c_new_client_device()

2020-06-19T07:20:25+00:00

Move away from the deprecated API and advertise the new one.

Signed-off-by: Wolfram Sang 
Reviewed-by: Mauro Carvalho Chehab 
Signed-off-by: Wolfram Sang

media: v4l2-ctrl: Document V4L2_CID_CAMERA_SENSOR_ROTATION

2020-05-18T13:33:48+00:00

Add documentation for the V4L2_CID_CAMERA_SENSOR_ROTATION camera
control. The newly added read-only control reports the rotation
correction to be applied to images before displaying them to the user.

Signed-off-by: Jacopo Mondi 
Signed-off-by: Hans Verkuil 
Signed-off-by: Mauro Carvalho Chehab

media: v4l2-ctrl: Document V4L2_CID_CAMERA_ORIENTATION

2020-05-18T13:33:26+00:00

Add documentation for the V4L2_CID_CAMERA_ORIENTATION camera
control. The newly added read-only control reports the camera device
orientation relative to the usage orientation of the system the camera
is installed on.

Signed-off-by: Jacopo Mondi 
Signed-off-by: Hans Verkuil 
Signed-off-by: Mauro Carvalho Chehab

media: v4l: document VIDIOC_SUBDEV_QUERYCAP

2020-05-12T15:06:18+00:00

Add documentation for the new VIDIOC_SUBDEV_QUERYCAP ioctl.

Acked-by: Sakari Ailus 
Signed-off-by: Hans Verkuil 
Signed-off-by: Jacopo Mondi 
Signed-off-by: Mauro Carvalho Chehab

media: Documentation: media: Document read-only subdevice

2020-05-12T15:03:26+00:00

Document a new kAPI function to register subdev device nodes in read only
mode and for each affected ioctl report how access is restricted.

Acked-by: Sakari Ailus 
Signed-off-by: Jacopo Mondi 
Signed-off-by: Hans Verkuil 
Signed-off-by: Mauro Carvalho Chehab

media: vidioc-enum-fmt.rst: make the ENUM_FMT text clearer

2020-05-06T12:49:37+00:00

Rework the documentation to make it easier for the reader to understand
the differences in behavior of this ioctl between MC and non-MC drivers.

Note the addition of the 'video-node-centric' and 'MC-centric' terms to
help understand what the IO_MC capability really means.

Also mention in the beginning that mbus_code is one of the fields that
application should initialize, and add META_OUTPUT as one of the types that
this ioctl supports (that was never added here when the META_OUTPUT buffer
type was added).

Finally document that EINVAL will be returned if mbus_code is unsupported.

Fixes: e5b6b07a1b45 ("media: v4l2: Extend VIDIOC_ENUM_FMT to support MC-centric devices")
Signed-off-by: Hans Verkuil 
Signed-off-by: Mauro Carvalho Chehab

media: v4l2: Extend VIDIOC_ENUM_FMT to support MC-centric devices

2020-05-06T10:09:04+00:00

The VIDIOC_ENUM_FMT ioctl enumerates all formats supported by a video
node. For MC-centric devices, its behaviour has always been ill-defined,
with drivers implementing one of the following behaviours:

- No support for VIDIOC_ENUM_FMT at all
- Enumerating all formats supported by the video node, regardless of the
  configuration of the pipeline
- Enumerating formats supported by the video node for the active
  configuration of the connected subdevice

The first behaviour is obviously useless for applications. The second
behaviour provides the most information, but doesn't offer a way to find
what formats are compatible with a given pipeline configuration. The
third behaviour fixes that, but with the drawback that applications
can't enumerate all supported formats anymore, and have to modify the
active configuration of the pipeline to enumerate formats.

The situation is messy as none of the implemented behaviours are ideal,
and userspace can't predict what will happen as the behaviour is
driver-specific.

To fix this, let's extend the VIDIOC_ENUM_FMT with a missing capability:
enumerating pixel formats for a given media bus code. The media bus code
is passed through the v4l2_fmtdesc structure in a new mbus_code field
(repurposed from the reserved fields). With this capability in place,
applications can enumerate pixel formats for a given media bus code
without modifying the active configuration of the device.

The current behaviour of the ioctl is preserved when the new mbus_code
field is set to 0, ensuring compatibility with existing userspace. The
API extension is documented as mandatory for MC-centric devices (as
advertised through the V4L2_CAP_IO_MC capability), allowing applications
and compliance tools to easily determine the availability of the
VIDIOC_ENUM_FMT extension.

Signed-off-by: Laurent Pinchart 
Acked-by: Sakari Ailus 
Signed-off-by: Niklas Söderlund 
Signed-off-by: Hans Verkuil 
Signed-off-by: Mauro Carvalho Chehab

media: v4l2-dev/ioctl: Add V4L2_CAP_IO_MC

2020-05-06T10:08:25+00:00

Add a video device capability flag to indicate that its inputs and/or
outputs are controlled by the Media Controller instead of the V4L2 API.
When this flag is set, ioctl for enum inputs and outputs are
automatically enabled and programmed to call a helper function.

Suggested-by: Hans Verkuil 
Signed-off-by: Helen Koike 
Signed-off-by: Niklas Söderlund 
Reviewed-by: Laurent Pinchart 
Signed-off-by: Hans Verkuil 
Signed-off-by: Mauro Carvalho Chehab

media: vidioc-reqbufs/create-bufs.rst: fix typo

2020-04-29T10:03:56+00:00

any others capabilities -> any other capabilities

Signed-off-by: Hans Verkuil 
Signed-off-by: Mauro Carvalho Chehab

media: uapi: h264: Add new profile and levels

2020-04-21T11:26:43+00:00

Add H264 profile "Contrained High" and H264 levels "5.2",
"6.0", "6.1" and "6.2".

Signed-off-by: Maheshwar Ajja 
Signed-off-by: Mauro Carvalho Chehab