Kernel/linux-stable
1
0
Fork 0
mirror of https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git synced 2025-01-04 04:06:26 +00:00
Code Issues Actions Packages Projects Releases Wiki Activity

media: Documentation: Align numbered list, make it a proper ReST

Browse Source 
Align lines for numbered list so that Sphinx produces an uniform output
for all list entries. Also indent paragraphs of such list entries for
consistency.

Also use ReST numbered list syntax for the entries.

Signed-off-by: Sakari Ailus <sakari.ailus@linux.intel.com>
Reviewed-by: Laurent Pinchart <laurent.pinchart@ideasonboard.com>
Signed-off-by: Hans Verkuil <hverkuil-cisco@xs4all.nl>
This commit is contained in:
Sakari Ailus 2023-08-02 15:11:50 +03:00 committed by Hans Verkuil
parent ef202378cc
commit 580139fa0c
1 changed files with 24 additions and 25 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

49
Documentation/userspace-api/media/v4l/dev-subdev.rst
View File

@ -579,20 +579,19 @@ is started.
There are three steps in configuring the streams: There are three steps in configuring the streams:
1) Set up links. Connect the pads between sub-devices using the :ref:`Media 1. Set up links. Connect the pads between sub-devices using the
Controller API <media_controller>` :ref:`Media Controller API <media_controller>`
2) Streams. Streams are declared and their routing is configured by 2. Streams. Streams are declared and their routing is configured by setting the
setting the routing table for the sub-device using routing table for the sub-device using :ref:`VIDIOC_SUBDEV_S_ROUTING
:ref:`VIDIOC_SUBDEV_S_ROUTING <VIDIOC_SUBDEV_G_ROUTING>` ioctl. Note that <VIDIOC_SUBDEV_G_ROUTING>` ioctl. Note that setting the routing table will
setting the routing table will reset formats and selections in the reset formats and selections in the sub-device to default values.
sub-device to default values.
3) Configure formats and selections. Formats and selections of each stream 3. Configure formats and selections. Formats and selections of each stream are
are configured separately as documented for plain sub-devices in configured separately as documented for plain sub-devices in
:ref:`format-propagation`. The stream ID is set to the same stream ID :ref:`format-propagation`. The stream ID is set to the same stream ID
associated with either sink or source pads of routes configured using the associated with either sink or source pads of routes configured using the
:ref:`VIDIOC_SUBDEV_S_ROUTING <VIDIOC_SUBDEV_G_ROUTING>` ioctl. :ref:`VIDIOC_SUBDEV_S_ROUTING <VIDIOC_SUBDEV_G_ROUTING>` ioctl.
Multiplexed streams setup example Multiplexed streams setup example
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
@ -618,11 +617,11 @@ modeled as V4L2 devices, exposed to userspace via /dev/videoX nodes.
To configure this pipeline, the userspace must take the following steps: To configure this pipeline, the userspace must take the following steps:
1) Set up media links between entities: connect the sensors to the bridge, 1. Set up media links between entities: connect the sensors to the bridge,
bridge to the receiver, and the receiver to the DMA engines. This step does bridge to the receiver, and the receiver to the DMA engines. This step does
not differ from normal non-multiplexed media controller setup. not differ from normal non-multiplexed media controller setup.
2) Configure routing 2. Configure routing
.. flat-table:: Bridge routing table .. flat-table:: Bridge routing table
:header-rows: 1 :header-rows: 1
@ -656,14 +655,14 @@ not differ from normal non-multiplexed media controller setup.
- V4L2_SUBDEV_ROUTE_FL_ACTIVE - V4L2_SUBDEV_ROUTE_FL_ACTIVE
- Pixel data stream from Sensor B - Pixel data stream from Sensor B
3) Configure formats and selections 3. Configure formats and selections
After configuring routing, the next step is configuring the formats and After configuring routing, the next step is configuring the formats and
selections for the streams. This is similar to performing this step without selections for the streams. This is similar to performing this step without
streams, with just one exception: the ``stream`` field needs to be assigned streams, with just one exception: the ``stream`` field needs to be assigned
to the value of the stream ID. to the value of the stream ID.
A common way to accomplish this is to start from the sensors and propagate the A common way to accomplish this is to start from the sensors and propagate
configurations along the stream towards the receiver, the configurations along the stream towards the receiver, using
using :ref:`VIDIOC_SUBDEV_S_FMT <VIDIOC_SUBDEV_G_FMT>` ioctls to configure each :ref:`VIDIOC_SUBDEV_S_FMT <VIDIOC_SUBDEV_G_FMT>` ioctls to configure each
stream endpoint in each sub-device. stream endpoint in each sub-device.