media: docs: uAPI: fix table output in LaTeX/PDF format
There are lots of tables that are not properly displayed in LaTeX/PDF. Fix the tablecolumns, add longtable where needed and LaTeX formatting macros, in order to address such issues. Signed-off-by: Mauro Carvalho Chehab <mchehab+huawei@kernel.org>
This commit is contained in:
@@ -35,7 +35,7 @@ device information, applications call the ioctl with a pointer to a
|
||||
struct :c:type:`cec_caps`. The driver fills the structure and
|
||||
returns the information to the application. The ioctl never fails.
|
||||
|
||||
.. tabularcolumns:: |p{1.2cm}|p{2.5cm}|p{13.8cm}|
|
||||
.. tabularcolumns:: |p{1.2cm}|p{2.5cm}|p{13.6cm}|
|
||||
|
||||
.. c:type:: cec_caps
|
||||
|
||||
@@ -63,7 +63,7 @@ returns the information to the application. The ioctl never fails.
|
||||
- CEC Framework API version, formatted with the ``KERNEL_VERSION()``
|
||||
macro.
|
||||
|
||||
.. tabularcolumns:: |p{4.4cm}|p{2.5cm}|p{10.6cm}|
|
||||
.. tabularcolumns:: |p{4.4cm}|p{2.5cm}|p{10.4cm}|
|
||||
|
||||
.. _cec-capabilities:
|
||||
|
||||
|
||||
@@ -39,7 +39,7 @@ provide a pointer to a cec_connector_info struct which will be populated
|
||||
by the kernel with the info provided by the adapter's driver. This ioctl
|
||||
is only available if the ``CEC_CAP_CONNECTOR_INFO`` capability is set.
|
||||
|
||||
.. tabularcolumns:: |p{1.0cm}|p{4.4cm}|p{2.5cm}|p{9.6cm}|
|
||||
.. tabularcolumns:: |p{1.0cm}|p{4.4cm}|p{2.5cm}|p{9.2cm}|
|
||||
|
||||
.. c:type:: cec_connector_info
|
||||
|
||||
@@ -59,7 +59,7 @@ is only available if the ``CEC_CAP_CONNECTOR_INFO`` capability is set.
|
||||
* - }
|
||||
-
|
||||
|
||||
.. tabularcolumns:: |p{4.4cm}|p{2.5cm}|p{10.6cm}|
|
||||
.. tabularcolumns:: |p{4.4cm}|p{2.5cm}|p{10.4cm}|
|
||||
|
||||
.. _connector-type:
|
||||
|
||||
@@ -82,7 +82,7 @@ is only available if the ``CEC_CAP_CONNECTOR_INFO`` capability is set.
|
||||
Information about the connector can be found in
|
||||
:ref:`cec-drm-connector-info`.
|
||||
|
||||
.. tabularcolumns:: |p{4.4cm}|p{2.5cm}|p{10.6cm}|
|
||||
.. tabularcolumns:: |p{4.4cm}|p{2.5cm}|p{10.4cm}|
|
||||
|
||||
.. c:type:: cec_drm_connector_info
|
||||
|
||||
|
||||
@@ -67,7 +67,7 @@ logical address types are already defined will return with error ``EBUSY``.
|
||||
|
||||
.. c:type:: cec_log_addrs
|
||||
|
||||
.. tabularcolumns:: |p{1.0cm}|p{8.0cm}|p{7.5cm}|
|
||||
.. tabularcolumns:: |p{1.0cm}|p{8.0cm}|p{8.0cm}|
|
||||
|
||||
.. cssclass:: longtable
|
||||
|
||||
@@ -150,7 +150,7 @@ logical address types are already defined will return with error ``EBUSY``.
|
||||
give the CEC framework more information about the device type, even
|
||||
though the framework won't use it directly in the CEC message.
|
||||
|
||||
.. tabularcolumns:: |p{7.8cm}|p{1.0cm}|p{8.7cm}|
|
||||
.. tabularcolumns:: |p{7.8cm}|p{1.0cm}|p{8.5cm}|
|
||||
|
||||
.. _cec-log-addrs-flags:
|
||||
|
||||
@@ -186,7 +186,7 @@ logical address types are already defined will return with error ``EBUSY``.
|
||||
|
||||
All other messages are ignored.
|
||||
|
||||
.. tabularcolumns:: |p{7.8cm}|p{1.0cm}|p{8.7cm}|
|
||||
.. tabularcolumns:: |p{7.8cm}|p{1.0cm}|p{8.5cm}|
|
||||
|
||||
.. _cec-versions:
|
||||
|
||||
@@ -211,7 +211,7 @@ logical address types are already defined will return with error ``EBUSY``.
|
||||
- 6
|
||||
- CEC version according to the HDMI 2.0 standard.
|
||||
|
||||
.. tabularcolumns:: |p{6.6cm}|p{2.2cm}|p{8.7cm}|
|
||||
.. tabularcolumns:: |p{6.6cm}|p{2.2cm}|p{8.5cm}|
|
||||
|
||||
.. _cec-prim-dev-types:
|
||||
|
||||
@@ -256,7 +256,7 @@ logical address types are already defined will return with error ``EBUSY``.
|
||||
- 7
|
||||
- Use for a video processor device.
|
||||
|
||||
.. tabularcolumns:: |p{6.6cm}|p{2.2cm}|p{8.7cm}|
|
||||
.. tabularcolumns:: |p{6.6cm}|p{2.2cm}|p{8.5cm}|
|
||||
|
||||
.. _cec-log-addr-types:
|
||||
|
||||
@@ -304,7 +304,7 @@ logical address types are already defined will return with error ``EBUSY``.
|
||||
Control).
|
||||
|
||||
|
||||
.. tabularcolumns:: |p{6.6cm}|p{2.2cm}|p{8.7cm}|
|
||||
.. tabularcolumns:: |p{6.6cm}|p{2.2cm}|p{8.5cm}|
|
||||
|
||||
.. _cec-all-dev-types-flags:
|
||||
|
||||
|
||||
@@ -44,7 +44,7 @@ two :ref:`CEC_EVENT_STATE_CHANGE <CEC-EVENT-STATE-CHANGE>` events with
|
||||
the same state). In that case the intermediate state changes were lost but
|
||||
it is guaranteed that the state did change in between the two events.
|
||||
|
||||
.. tabularcolumns:: |p{1.2cm}|p{2.9cm}|p{13.4cm}|
|
||||
.. tabularcolumns:: |p{1.2cm}|p{2.9cm}|p{13.2cm}|
|
||||
|
||||
.. c:type:: cec_event_state_change
|
||||
|
||||
@@ -74,7 +74,7 @@ it is guaranteed that the state did change in between the two events.
|
||||
|
||||
.. c:type:: cec_event_lost_msgs
|
||||
|
||||
.. tabularcolumns:: |p{1.0cm}|p{2.0cm}|p{14.5cm}|
|
||||
.. tabularcolumns:: |p{1.0cm}|p{2.0cm}|p{14.3cm}|
|
||||
|
||||
.. flat-table:: struct cec_event_lost_msgs
|
||||
:header-rows: 0
|
||||
@@ -93,7 +93,7 @@ it is guaranteed that the state did change in between the two events.
|
||||
replied to within a second according to the CEC specification,
|
||||
this is more than enough.
|
||||
|
||||
.. tabularcolumns:: |p{1.0cm}|p{4.4cm}|p{2.5cm}|p{9.6cm}|
|
||||
.. tabularcolumns:: |p{1.0cm}|p{4.4cm}|p{2.5cm}|p{9.2cm}|
|
||||
|
||||
.. c:type:: cec_event
|
||||
|
||||
@@ -128,7 +128,7 @@ it is guaranteed that the state did change in between the two events.
|
||||
* - }
|
||||
-
|
||||
|
||||
.. tabularcolumns:: |p{5.6cm}|p{0.9cm}|p{11.0cm}|
|
||||
.. tabularcolumns:: |p{5.6cm}|p{0.9cm}|p{10.8cm}|
|
||||
|
||||
.. _cec-events:
|
||||
|
||||
@@ -201,7 +201,7 @@ it is guaranteed that the state did change in between the two events.
|
||||
if the 5V is high, then an initial event will be generated for that
|
||||
filehandle.
|
||||
|
||||
.. tabularcolumns:: |p{6.0cm}|p{0.6cm}|p{10.9cm}|
|
||||
.. tabularcolumns:: |p{6.0cm}|p{0.6cm}|p{10.7cm}|
|
||||
|
||||
.. _cec-event-flags:
|
||||
|
||||
|
||||
@@ -72,7 +72,7 @@ always call :ref:`ioctl CEC_TRANSMIT <CEC_TRANSMIT>`.
|
||||
|
||||
Available initiator modes are:
|
||||
|
||||
.. tabularcolumns:: |p{5.6cm}|p{0.9cm}|p{11.0cm}|
|
||||
.. tabularcolumns:: |p{5.6cm}|p{0.9cm}|p{10.8cm}|
|
||||
|
||||
.. _cec-mode-initiator_e:
|
||||
|
||||
@@ -106,7 +106,7 @@ Available initiator modes are:
|
||||
|
||||
Available follower modes are:
|
||||
|
||||
.. tabularcolumns:: |p{6.6cm}|p{0.9cm}|p{10.0cm}|
|
||||
.. tabularcolumns:: |p{6.6cm}|p{0.9cm}|p{9.8cm}|
|
||||
|
||||
.. _cec-mode-follower_e:
|
||||
|
||||
|
||||
@@ -84,7 +84,7 @@ physical address, but the cable is still connected and CEC still works.
|
||||
In order to detect/wake up the device it is allowed to send poll and 'Image/Text
|
||||
View On' messages from initiator 0xf ('Unregistered') to destination 0 ('TV').
|
||||
|
||||
.. tabularcolumns:: |p{1.0cm}|p{3.5cm}|p{13.0cm}|
|
||||
.. tabularcolumns:: |p{1.0cm}|p{3.5cm}|p{12.8cm}|
|
||||
|
||||
.. c:type:: cec_msg
|
||||
|
||||
@@ -196,7 +196,7 @@ View On' messages from initiator 0xf ('Unregistered') to destination 0 ('TV').
|
||||
supports this, otherwise it is always 0. This counter is only
|
||||
valid if the :ref:`CEC_TX_STATUS_ERROR <CEC-TX-STATUS-ERROR>` status bit is set.
|
||||
|
||||
.. tabularcolumns:: |p{6.2cm}|p{1.0cm}|p{10.3cm}|
|
||||
.. tabularcolumns:: |p{6.2cm}|p{1.0cm}|p{10.1cm}|
|
||||
|
||||
.. _cec-msg-flags:
|
||||
|
||||
@@ -229,7 +229,7 @@ View On' messages from initiator 0xf ('Unregistered') to destination 0 ('TV').
|
||||
capability. If that is not set, then the ``EPERM`` error code is
|
||||
returned.
|
||||
|
||||
.. tabularcolumns:: |p{5.6cm}|p{0.9cm}|p{11.0cm}|
|
||||
.. tabularcolumns:: |p{5.6cm}|p{0.9cm}|p{10.8cm}|
|
||||
|
||||
.. _cec-tx-status:
|
||||
|
||||
@@ -298,7 +298,7 @@ View On' messages from initiator 0xf ('Unregistered') to destination 0 ('TV').
|
||||
- The transmit timed out. This should not normally happen and this
|
||||
indicates a driver problem.
|
||||
|
||||
.. tabularcolumns:: |p{5.6cm}|p{0.9cm}|p{11.0cm}|
|
||||
.. tabularcolumns:: |p{5.6cm}|p{0.9cm}|p{10.8cm}|
|
||||
|
||||
.. _cec-rx-status:
|
||||
|
||||
|
||||
Reference in New Issue
Block a user