Donate to e Foundation | Murena handsets with /e/OS | Own a part of Murena! Learn more

Commit e5208ed2 authored by Hans Verkuil's avatar Hans Verkuil Committed by Mauro Carvalho Chehab
Browse files

[media] doc-rst: cec: update documentation 



Update and expand the CEC documentation. Especially w.r.t. non-blocking
mode.

Signed-off-by: default avatarHans Verkuil <hans.verkuil@cisco.com>
Signed-off-by: default avatarMauro Carvalho Chehab <mchehab@s-opensource.com>
parent ef88f10e

Documentation/media/uapi/cec/cec-func-open.rst

+4 −4
Original line number Diff line number Diff line
@@ -32,12 +32,12 @@ Arguments 
    Open flags. Access mode must be ``O_RDWR``.



    When the ``O_NONBLOCK`` flag is given, the

    :ref:`CEC_RECEIVE <CEC_RECEIVE>` ioctl will return the EAGAIN

    error code when no message is available, and ioctls

    :ref:`CEC_TRANSMIT <CEC_TRANSMIT>`,

    :ref:`CEC_RECEIVE <CEC_RECEIVE>` and :ref:`CEC_DQEVENT <CEC_DQEVENT>` ioctls

    will return the ``EAGAIN`` error code when no message or event is available, and

    ioctls :ref:`CEC_TRANSMIT <CEC_TRANSMIT>`,

    :ref:`CEC_ADAP_S_PHYS_ADDR <CEC_ADAP_S_PHYS_ADDR>` and

    :ref:`CEC_ADAP_S_LOG_ADDRS <CEC_ADAP_S_LOG_ADDRS>`

    all act in non-blocking mode.

    all return 0.



    Other flags have no effect.

Documentation/media/uapi/cec/cec-ioc-adap-g-log-addrs.rst

+35 −19
Original line number Diff line number Diff line
@@ -45,10 +45,24 @@ To query the current CEC logical addresses, applications call 
To set new logical addresses, applications fill in

:c:type:`struct cec_log_addrs` and call :ref:`ioctl CEC_ADAP_S_LOG_ADDRS <CEC_ADAP_S_LOG_ADDRS>`

with a pointer to this struct. The :ref:`ioctl CEC_ADAP_S_LOG_ADDRS <CEC_ADAP_S_LOG_ADDRS>`

is only available if ``CEC_CAP_LOG_ADDRS`` is set (ENOTTY error code is

returned otherwise). This ioctl will block until all requested logical

addresses have been claimed. The :ref:`ioctl CEC_ADAP_S_LOG_ADDRS <CEC_ADAP_S_LOG_ADDRS>` can only be called

by a file handle in initiator mode (see :ref:`CEC_S_MODE`).

is only available if ``CEC_CAP_LOG_ADDRS`` is set (the ``ENOTTY`` error code is

returned otherwise). The :ref:`ioctl CEC_ADAP_S_LOG_ADDRS <CEC_ADAP_S_LOG_ADDRS>`

can only be called by a file descriptor in initiator mode (see :ref:`CEC_S_MODE`), if not

the ``EBUSY`` error code will be returned.



To clear existing logical addresses set ``num_log_addrs`` to 0. All other fields

will be ignored in that case. The adapter will go to the unconfigured state.



If the physical address is valid (see :ref:`ioctl CEC_ADAP_S_PHYS_ADDR <CEC_ADAP_S_PHYS_ADDR>`),

then this ioctl will block until all requested logical

addresses have been claimed. If the file descriptor is in non-blocking mode then it will

not wait for the logical addresses to be claimed, instead it just returns 0.



A :ref:`CEC_EVENT_STATE_CHANGE <CEC-EVENT-STATE-CHANGE>` event is sent when the

logical addresses are claimed or cleared.



Attempting to call :ref:`ioctl CEC_ADAP_S_LOG_ADDRS <CEC_ADAP_S_LOG_ADDRS>` when

logical address types are already defined will return with error ``EBUSY``.





.. _cec-log-addrs:
@@ -63,7 +77,7 @@ by a file handle in initiator mode (see :ref:`CEC_S_MODE`). 


       -  __u8



       -  ``log_addr`` [CEC_MAX_LOG_ADDRS]

       -  ``log_addr[CEC_MAX_LOG_ADDRS]``



       -  The actual logical addresses that were claimed. This is set by the

	  driver. If no logical address could be claimed, then it is set to
@@ -136,7 +150,7 @@ by a file handle in initiator mode (see :ref:`CEC_S_MODE`). 


       -  char



       -  ``osd_name``\ [15]

       -  ``osd_name[15]``



       -  The On-Screen Display name as is returned by the

	  ``CEC_MSG_SET_OSD_NAME`` message.
@@ -145,7 +159,7 @@ by a file handle in initiator mode (see :ref:`CEC_S_MODE`). 


       -  __u8



       -  ``primary_device_type`` [CEC_MAX_LOG_ADDRS]

       -  ``primary_device_type[CEC_MAX_LOG_ADDRS]``



       -  Primary device type for each logical address. See

	  :ref:`cec-prim-dev-types` for possible types.
@@ -154,7 +168,7 @@ by a file handle in initiator mode (see :ref:`CEC_S_MODE`). 


       -  __u8



       -  ``log_addr_type`` [CEC_MAX_LOG_ADDRS]

       -  ``log_addr_type[CEC_MAX_LOG_ADDRS]``



       -  Logical address types. See :ref:`cec-log-addr-types` for

	  possible types. The driver will update this with the actual
@@ -165,25 +179,27 @@ by a file handle in initiator mode (see :ref:`CEC_S_MODE`). 


       -  __u8



       -  ``all_device_types`` [CEC_MAX_LOG_ADDRS]

       -  ``all_device_types[CEC_MAX_LOG_ADDRS]``



       -  CEC 2.0 specific: all device types. See

	  :ref:`cec-all-dev-types-flags`. Used to implement the

	  ``CEC_MSG_REPORT_FEATURES`` message. This field is ignored if

	  ``cec_version`` < :ref:`CEC_OP_CEC_VERSION_2_0 <CEC-OP-CEC-VERSION-2-0>`.

       -  CEC 2.0 specific: the bit mask of all device types. See

	  :ref:`cec-all-dev-types-flags`. It is used in the CEC 2.0

	  ``CEC_MSG_REPORT_FEATURES`` message. For CEC 1.4 you can either leave

	  this field to 0, or fill it in according to the CEC 2.0 guidelines to

	  give the CEC framework more information about the device type, even

	  though the framework won't use it directly in the CEC message.



    -  .. row 11



       -  __u8



       -  ``features`` [CEC_MAX_LOG_ADDRS][12]

       -  ``features[CEC_MAX_LOG_ADDRS][12]``



       -  Features for each logical address. Used to implement the

       -  Features for each logical address. It is used in the CEC 2.0

	  ``CEC_MSG_REPORT_FEATURES`` message. The 12 bytes include both the

	  RC Profile and the Device Features. This field is ignored if

	  ``cec_version`` < :ref:`CEC_OP_CEC_VERSION_2_0 <CEC-OP-CEC-VERSION-2-0>`.





	  RC Profile and the Device Features. For CEC 1.4 you can either leave

          this field to all 0, or fill it in according to the CEC 2.0 guidelines to

          give the CEC framework more information about the device type, even

          though the framework won't use it directly in the CEC message.



.. _cec-versions:

Documentation/media/uapi/cec/cec-ioc-adap-g-phys-addr.rst

+15 −4
Original line number Diff line number Diff line
@@ -44,10 +44,21 @@ driver stores the physical address. 
To set a new physical address applications store the physical address in

a __u16 and call :ref:`ioctl CEC_ADAP_S_PHYS_ADDR <CEC_ADAP_S_PHYS_ADDR>` with a pointer to

this integer. The :ref:`ioctl CEC_ADAP_S_PHYS_ADDR <CEC_ADAP_S_PHYS_ADDR>` is only available if

``CEC_CAP_PHYS_ADDR`` is set (ENOTTY error code will be returned

otherwise). The :ref:`ioctl CEC_ADAP_S_PHYS_ADDR <CEC_ADAP_S_PHYS_ADDR>` can only be called by a file handle

in initiator mode (see :ref:`CEC_S_MODE`), if not

EBUSY error code will be returned.

``CEC_CAP_PHYS_ADDR`` is set (the ``ENOTTY`` error code will be returned

otherwise). The :ref:`ioctl CEC_ADAP_S_PHYS_ADDR <CEC_ADAP_S_PHYS_ADDR>` can only be called

by a file descriptor in initiator mode (see :ref:`CEC_S_MODE`), if not

the ``EBUSY`` error code will be returned.



To clear an existing physical address use ``CEC_PHYS_ADDR_INVALID``.

The adapter will go to the unconfigured state.



If logical address types have been defined (see :ref:`ioctl CEC_ADAP_S_LOG_ADDRS <CEC_ADAP_S_LOG_ADDRS>`),

then this ioctl will block until all

requested logical addresses have been claimed. If the file descriptor is in non-blocking mode

then it will not wait for the logical addresses to be claimed, instead it just returns 0.



A :ref:`CEC_EVENT_STATE_CHANGE <CEC-EVENT-STATE-CHANGE>` event is sent when the physical address

changes.



The physical address is a 16-bit number where each group of 4 bits

represent a digit of the physical address a.b.c.d where the most

Documentation/media/uapi/cec/cec-ioc-dqevent.rst

+3 −1
Original line number Diff line number Diff line
@@ -38,7 +38,7 @@ Description 
CEC devices can send asynchronous events. These can be retrieved by

calling :ref:`ioctl CEC_DQEVENT <CEC_DQEVENT>`. If the file descriptor is in

non-blocking mode and no event is pending, then it will return -1 and

set errno to the EAGAIN error code.

set errno to the ``EAGAIN`` error code.



The internal event queues are per-filehandle and per-event type. If

there is no more room in a queue then the last event is overwritten with
@@ -117,6 +117,8 @@ it is guaranteed that the state did change in between the two events. 
       -  ``ts``



       -  Timestamp of the event in ns.

	  The timestamp has been taken from the ``CLOCK_MONOTONIC`` clock. To access

	  the same clock from userspace use :c:func:`clock_gettime(2)`.



       -

Documentation/media/uapi/cec/cec-ioc-g-mode.rst

+13 −13
Original line number Diff line number Diff line
@@ -108,7 +108,7 @@ Available initiator modes are: 
       -  This is an exclusive initiator and this file descriptor is the

	  only one that can transmit CEC messages and make changes to the

	  CEC adapter. If someone else is already the exclusive initiator

	  then an attempt to become one will return the EBUSY error code

	  then an attempt to become one will return the ``EBUSY`` error code

	  error.
@@ -140,7 +140,7 @@ Available follower modes are: 
       -  This is a follower and it will receive CEC messages unless there

	  is an exclusive follower. You cannot become a follower if

	  :ref:`CEC_CAP_TRANSMIT <CEC-CAP-TRANSMIT>` is not set or if :ref:`CEC_MODE_NO_INITIATOR <CEC-MODE-NO-INITIATOR>`

	  was specified, EINVAL error code is returned in that case.

	  was specified, the ``EINVAL`` error code is returned in that case.



    -  .. _`CEC-MODE-EXCL-FOLLOWER`:
@@ -151,9 +151,9 @@ Available follower modes are: 
       -  This is an exclusive follower and only this file descriptor will

	  receive CEC messages for processing. If someone else is already

	  the exclusive follower then an attempt to become one will return

	  the EBUSY error code error. You cannot become a follower if

	  the ``EBUSY`` error code. You cannot become a follower if

	  :ref:`CEC_CAP_TRANSMIT <CEC-CAP-TRANSMIT>` is not set or if :ref:`CEC_MODE_NO_INITIATOR <CEC-MODE-NO-INITIATOR>`

	  was specified, EINVAL error code is returned in that case.

	  was specified, the ``EINVAL`` error code is returned in that case.



    -  .. _`CEC-MODE-EXCL-FOLLOWER-PASSTHRU`:
@@ -166,10 +166,10 @@ Available follower modes are: 
	  CEC device into passthrough mode, allowing the exclusive follower

	  to handle most core messages instead of relying on the CEC

	  framework for that. If someone else is already the exclusive

	  follower then an attempt to become one will return the EBUSY error

	  code error. You cannot become a follower if :ref:`CEC_CAP_TRANSMIT <CEC-CAP-TRANSMIT>`

	  is not set or if :ref:`CEC_MODE_NO_INITIATOR <CEC-MODE-NO-INITIATOR>` was specified, EINVAL

	  error code is returned in that case.

	  follower then an attempt to become one will return the ``EBUSY`` error

	  code. You cannot become a follower if :ref:`CEC_CAP_TRANSMIT <CEC-CAP-TRANSMIT>`

	  is not set or if :ref:`CEC_MODE_NO_INITIATOR <CEC-MODE-NO-INITIATOR>` was specified,

	  the ``EINVAL`` error code is returned in that case.



    -  .. _`CEC-MODE-MONITOR`:
@@ -184,7 +184,7 @@ Available follower modes are: 
	  messages and directed messages for one its logical addresses) will

	  be reported. This is very useful for debugging. This is only

	  allowed if the process has the ``CAP_NET_ADMIN`` capability. If

	  that is not set, then EPERM error code is returned.

	  that is not set, then the ``EPERM`` error code is returned.



    -  .. _`CEC-MODE-MONITOR-ALL`:
@@ -193,15 +193,15 @@ Available follower modes are: 
       -  0xf0



       -  Put the file descriptor into 'monitor all' mode. Can only be used

	  in combination with :ref:`CEC_MODE_NO_INITIATOR <CEC-MODE-NO-INITIATOR>`, otherwise EINVAL

	  error code will be returned. In 'monitor all' mode all messages

	  in combination with :ref:`CEC_MODE_NO_INITIATOR <CEC-MODE-NO-INITIATOR>`, otherwise

	  the ``EINVAL`` error code will be returned. In 'monitor all' mode all messages

	  this CEC device transmits and all messages it receives, including

	  directed messages for other CEC devices will be reported. This is

	  very useful for debugging, but not all devices support this. This

	  mode requires that the :ref:`CEC_CAP_MONITOR_ALL <CEC-CAP-MONITOR-ALL>` capability is set,

	  otherwise EINVAL error code is returned. This is only allowed if

	  otherwise the ``EINVAL`` error code is returned. This is only allowed if

	  the process has the ``CAP_NET_ADMIN`` capability. If that is not

	  set, then EPERM error code is returned.

	  set, then the ``EPERM`` error code is returned.





Core message processing details: