mirror of
https://github.com/tbsdtv/linux_media.git
synced 2025-07-23 12:43:29 +02:00
Documentation: userspace-api: correct spelling
Correct spelling problems for Documentation/userspace-api/ as reported by codespell. Signed-off-by: Randy Dunlap <rdunlap@infradead.org> Cc: Jonathan Corbet <corbet@lwn.net> Cc: linux-doc@vger.kernel.org Cc: Sean Young <sean@mess.org> Cc: Mauro Carvalho Chehab <mchehab@kernel.org> Cc: linux-media@vger.kernel.org Link: https://lore.kernel.org/r/20230129231053.20863-10-rdunlap@infradead.org Signed-off-by: Jonathan Corbet <corbet@lwn.net>
This commit is contained in:
committed by
Jonathan Corbet
parent
810edcd576
commit
c1966bd1f0
@@ -165,7 +165,7 @@ Multiple io_pagetable-s, through their iopt_area-s, can share a single
|
|||||||
iopt_pages which avoids multi-pinning and double accounting of page
|
iopt_pages which avoids multi-pinning and double accounting of page
|
||||||
consumption.
|
consumption.
|
||||||
|
|
||||||
iommufd_ioas is sharable between subsystems, e.g. VFIO and VDPA, as long as
|
iommufd_ioas is shareable between subsystems, e.g. VFIO and VDPA, as long as
|
||||||
devices managed by different subsystems are bound to a same iommufd.
|
devices managed by different subsystems are bound to a same iommufd.
|
||||||
|
|
||||||
IOMMUFD User API
|
IOMMUFD User API
|
||||||
|
@@ -18,7 +18,7 @@ The ST VGXY61 driver implements the following controls:
|
|||||||
* - HDR linearize
|
* - HDR linearize
|
||||||
- The merger outputs a long exposure capture as long as it is not
|
- The merger outputs a long exposure capture as long as it is not
|
||||||
saturated.
|
saturated.
|
||||||
* - HDR substraction
|
* - HDR subtraction
|
||||||
- This involves subtracting the short exposure frame from the long
|
- This involves subtracting the short exposure frame from the long
|
||||||
exposure frame.
|
exposure frame.
|
||||||
* - No HDR
|
* - No HDR
|
||||||
|
@@ -43,7 +43,7 @@ reduced range of reception.
|
|||||||
|
|
||||||
.. note::
|
.. note::
|
||||||
|
|
||||||
Wide band receiver might be implictly enabled if you enable
|
Wide band receiver might be implicitly enabled if you enable
|
||||||
carrier reports. In that case it will be disabled as soon as you disable
|
carrier reports. In that case it will be disabled as soon as you disable
|
||||||
carrier reports. Trying to disable wide band receiver while carrier
|
carrier reports. Trying to disable wide band receiver while carrier
|
||||||
reports are active will do nothing.
|
reports are active will do nothing.
|
||||||
|
@@ -75,7 +75,7 @@ protocol, or the manchester BPF decoder.
|
|||||||
- Command
|
- Command
|
||||||
|
|
||||||
There is a variant of rc5 called either rc5x or extended rc5
|
There is a variant of rc5 called either rc5x or extended rc5
|
||||||
where there the second stop bit is the 6th commmand bit, but inverted.
|
where there the second stop bit is the 6th command bit, but inverted.
|
||||||
This is done so it the scancodes and encoding is compatible with existing
|
This is done so it the scancodes and encoding is compatible with existing
|
||||||
schemes. This bit is stored in bit 6 of the scancode, inverted. This is
|
schemes. This bit is stored in bit 6 of the scancode, inverted. This is
|
||||||
done to keep it compatible with plain rc-5 where there are two start bits.
|
done to keep it compatible with plain rc-5 where there are two start bits.
|
||||||
|
@@ -628,7 +628,7 @@ the remote via /dev/input/event devices.
|
|||||||
|
|
||||||
- Put device into zoom/full screen mode
|
- Put device into zoom/full screen mode
|
||||||
|
|
||||||
- ZOOM / FULL SCREEN / ZOOM+ / HIDE PANNEL / SWITCH
|
- ZOOM / FULL SCREEN / ZOOM+ / HIDE PANEL / SWITCH
|
||||||
|
|
||||||
- .. row 80
|
- .. row 80
|
||||||
|
|
||||||
|
@@ -490,7 +490,7 @@ struct v4l2_mpeg_vbi_fmt_ivtv
|
|||||||
- An alternate form of the sliced VBI data payload used when 36
|
- An alternate form of the sliced VBI data payload used when 36
|
||||||
lines of sliced VBI data are present. No line masks are provided
|
lines of sliced VBI data are present. No line masks are provided
|
||||||
in this form of the payload; all valid line mask bits are
|
in this form of the payload; all valid line mask bits are
|
||||||
implcitly set.
|
implicitly set.
|
||||||
* - }
|
* - }
|
||||||
-
|
-
|
||||||
|
|
||||||
|
@@ -1213,7 +1213,7 @@ FWHT Flags
|
|||||||
- Luma AC coefficient table index.
|
- Luma AC coefficient table index.
|
||||||
* - __s8
|
* - __s8
|
||||||
- ``y_dc_delta``
|
- ``y_dc_delta``
|
||||||
- Luma DC delta vaue.
|
- Luma DC delta value.
|
||||||
* - __s8
|
* - __s8
|
||||||
- ``y2_dc_delta``
|
- ``y2_dc_delta``
|
||||||
- Y2 block DC delta value.
|
- Y2 block DC delta value.
|
||||||
|
@@ -8,7 +8,7 @@ JPEG Control Reference
|
|||||||
|
|
||||||
The JPEG class includes controls for common features of JPEG encoders
|
The JPEG class includes controls for common features of JPEG encoders
|
||||||
and decoders. Currently it includes features for codecs implementing
|
and decoders. Currently it includes features for codecs implementing
|
||||||
progressive baseline DCT compression process with Huffman entrophy
|
progressive baseline DCT compression process with Huffman entropy
|
||||||
coding.
|
coding.
|
||||||
|
|
||||||
|
|
||||||
|
@@ -47,7 +47,7 @@ Codec API was released.
|
|||||||
1998-11-08: Many minor changes. Most symbols have been renamed. Some
|
1998-11-08: Many minor changes. Most symbols have been renamed. Some
|
||||||
material changes to struct v4l2_capability.
|
material changes to struct v4l2_capability.
|
||||||
|
|
||||||
1998-11-12: The read/write directon of some ioctls was misdefined.
|
1998-11-12: The read/write direction of some ioctls was misdefined.
|
||||||
|
|
||||||
1998-11-14: ``V4L2_PIX_FMT_RGB24`` changed to ``V4L2_PIX_FMT_BGR24``,
|
1998-11-14: ``V4L2_PIX_FMT_RGB24`` changed to ``V4L2_PIX_FMT_BGR24``,
|
||||||
and ``V4L2_PIX_FMT_RGB32`` changed to ``V4L2_PIX_FMT_BGR32``. Audio
|
and ``V4L2_PIX_FMT_RGB32`` changed to ``V4L2_PIX_FMT_BGR32``. Audio
|
||||||
@@ -145,7 +145,7 @@ common Linux driver API conventions.
|
|||||||
``VIDIOC_G_INFMT``, ``VIDIOC_S_OUTFMT``, ``VIDIOC_G_OUTFMT``,
|
``VIDIOC_G_INFMT``, ``VIDIOC_S_OUTFMT``, ``VIDIOC_G_OUTFMT``,
|
||||||
``VIDIOC_S_VBIFMT`` and ``VIDIOC_G_VBIFMT``. The image format
|
``VIDIOC_S_VBIFMT`` and ``VIDIOC_G_VBIFMT``. The image format
|
||||||
struct v4l2_format was renamed to struct v4l2_pix_format, while
|
struct v4l2_format was renamed to struct v4l2_pix_format, while
|
||||||
struct v4l2_format is now the envelopping structure
|
struct v4l2_format is now the enveloping structure
|
||||||
for all format negotiations.
|
for all format negotiations.
|
||||||
|
|
||||||
5. Similar to the changes above, the ``VIDIOC_G_PARM`` and
|
5. Similar to the changes above, the ``VIDIOC_G_PARM`` and
|
||||||
|
@@ -14,7 +14,7 @@ are often referred to as greyscale formats.
|
|||||||
- In all the tables that follow, bit 7 is the most significant bit in a byte.
|
- In all the tables that follow, bit 7 is the most significant bit in a byte.
|
||||||
- Formats are described with the minimum number of pixels needed to create a
|
- Formats are described with the minimum number of pixels needed to create a
|
||||||
byte-aligned repeating pattern. `...` indicates repetition of the pattern.
|
byte-aligned repeating pattern. `...` indicates repetition of the pattern.
|
||||||
- Y'\ :sub:`x`\ [9:2] denotes bits 9 to 2 of the Y' value for pixel at colum
|
- Y'\ :sub:`x`\ [9:2] denotes bits 9 to 2 of the Y' value for pixel at column
|
||||||
`x`.
|
`x`.
|
||||||
- `0` denotes padding bits set to 0.
|
- `0` denotes padding bits set to 0.
|
||||||
|
|
||||||
|
@@ -71,7 +71,7 @@ overlay devices.
|
|||||||
- Default cropping rectangle, it shall cover the "whole picture".
|
- Default cropping rectangle, it shall cover the "whole picture".
|
||||||
Assuming pixel aspect 1/1 this could be for example a 640 × 480
|
Assuming pixel aspect 1/1 this could be for example a 640 × 480
|
||||||
rectangle for NTSC, a 768 × 576 rectangle for PAL and SECAM
|
rectangle for NTSC, a 768 × 576 rectangle for PAL and SECAM
|
||||||
centered over the active picture area. The same co-ordinate system
|
centered over the active picture area. The same coordinate system
|
||||||
as for ``bounds`` is used.
|
as for ``bounds`` is used.
|
||||||
* - struct :c:type:`v4l2_fract`
|
* - struct :c:type:`v4l2_fract`
|
||||||
- ``pixelaspect``
|
- ``pixelaspect``
|
||||||
|
@@ -274,7 +274,7 @@ value will be the injected file descriptor number.
|
|||||||
The notifying process can be preempted, resulting in the notification being
|
The notifying process can be preempted, resulting in the notification being
|
||||||
aborted. This can be problematic when trying to take actions on behalf of the
|
aborted. This can be problematic when trying to take actions on behalf of the
|
||||||
notifying process that are long-running and typically retryable (mounting a
|
notifying process that are long-running and typically retryable (mounting a
|
||||||
filesytem). Alternatively, at filter installation time, the
|
filesystem). Alternatively, at filter installation time, the
|
||||||
``SECCOMP_FILTER_FLAG_WAIT_KILLABLE_RECV`` flag can be set. This flag makes it
|
``SECCOMP_FILTER_FLAG_WAIT_KILLABLE_RECV`` flag can be set. This flag makes it
|
||||||
such that when a user notification is received by the supervisor, the notifying
|
such that when a user notification is received by the supervisor, the notifying
|
||||||
process will ignore non-fatal signals until the response is sent. Signals that
|
process will ignore non-fatal signals until the response is sent. Signals that
|
||||||
|
@@ -37,6 +37,6 @@ representation onto this fixed set.
|
|||||||
If there is no good match when mapping then a new profile name may be
|
If there is no good match when mapping then a new profile name may be
|
||||||
added. Drivers which wish to introduce new profile names must:
|
added. Drivers which wish to introduce new profile names must:
|
||||||
|
|
||||||
1. Explain why the existing profile names canot be used.
|
1. Explain why the existing profile names cannot be used.
|
||||||
2. Add the new profile name, along with a clear description of the
|
2. Add the new profile name, along with a clear description of the
|
||||||
expected behaviour, to the sysfs-platform_profile ABI documentation.
|
expected behaviour, to the sysfs-platform_profile ABI documentation.
|
||||||
|
Reference in New Issue
Block a user