Searched refs:CEC (Results 1 – 25 of 74) sorted by relevance
123
| /Linux-v5.4/Documentation/media/uapi/cec/ |
| D | cec-ioc-adap-g-log-addrs.rst | 45 To query the current CEC logical addresses, applications call
60 values (CEC version 2.0, no vendor ID and an empty OSD name).
67 A :ref:`CEC_EVENT_STATE_CHANGE <CEC-EVENT-STATE-CHANGE>` event is sent when the
99 - The CEC version that this adapter shall use. See
102 Note that :ref:`CEC_OP_CEC_VERSION_1_3A <CEC-OP-CEC-VERSION-1-3A>` is not allowed by the CEC
111 ignored. Note that the CEC 2.0 standard allows for a maximum of 2
115 what was requested. If this field is set to 0, then the CEC
140 to :ref:`CEC_LOG_ADDR_TYPE_UNREGISTERED <CEC-LOG-ADDR-TYPE-UNREGISTERED>`).
143 - CEC 2.0 specific: the bit mask of all device types. See
144 :ref:`cec-all-dev-types-flags`. It is used in the CEC 2.0
[all …]
|
| D | cec-ioc-g-mode.rst | 18 CEC_G_MODE, CEC_S_MODE - Get or set exclusive use of the CEC adapter
36 Pointer to CEC mode.
43 obtain exclusive access to the CEC adapter. This ioctl sets the
46 used to initiate messages, i.e. it commands other CEC devices. The
47 follower is the filehandle that receives messages sent to the CEC
51 When a CEC message is received, then the CEC framework will decide how
54 is waiting for it. In addition the CEC framework will process it.
56 If the message is not a reply, then the CEC framework will process it
64 The CEC framework will process core messages unless requested otherwise
66 case, the CEC framework will pass on most core messages without
[all …]
|
| D | cec-intro.rst | 17 HDMI cable to communicate. The protocol for CEC version 1.4 is defined
18 in supplements 1 (CEC) and 2 (HEAC or HDMI Ethernet and Audio Return
20 extensions added to CEC version 2.0 are defined in chapter 11 of the
28 CEC, need to be handled by the kernel, others can be handled either by
31 In addition, CEC can be implemented in HDMI receivers, transmitters and
33 control just the CEC pin.
35 Drivers that support CEC will create a CEC device node (/dev/cecX) to
36 give userspace access to the CEC adapter. The
41 provides three tools to handle CEC:
43 - cec-ctl: the Swiss army knife of CEC. Allows you to configure, transmit
[all …]
|
| D | cec-ioc-adap-g-caps.rst | 58 - The name of this CEC adapter. The combination ``driver`` and
62 - The capabilities of the CEC adapter, see
66 - CEC Framework API version, formatted with the ``KERNEL_VERSION()``
74 .. flat-table:: CEC Capabilities Flags
79 * .. _`CEC-CAP-PHYS-ADDR`:
88 * .. _`CEC-CAP-LOG-ADDRS`:
96 * .. _`CEC-CAP-TRANSMIT`:
100 - Userspace can transmit CEC messages by calling
104 capability isn't set, then the kernel will handle all CEC
105 transmits and process all CEC messages it receives.
[all …]
|
| D | cec-ioc-dqevent.rst | 19 CEC_DQEVENT - Dequeue a CEC event
40 CEC devices can send asynchronous events. These can be retrieved by
50 two :ref:`CEC_EVENT_STATE_CHANGE <CEC-EVENT-STATE-CHANGE>` events with
93 replied to within a second according to the CEC specification,
115 - :cspan:`1` The CEC event type, see :ref:`cec-events`.
126 - The new adapter state as sent by the :ref:`CEC_EVENT_STATE_CHANGE <CEC-EVENT-STATE-CHANGE>`
131 - The number of lost messages as sent by the :ref:`CEC_EVENT_LOST_MSGS <CEC-EVENT-LOST-MSGS>`
139 .. flat-table:: CEC Events Types
144 * .. _`CEC-EVENT-STATE-CHANGE`:
148 - Generated when the CEC Adapter's state changes. When open() is
[all …]
|
| D | cec-pin-error-inj.rst | 10 CEC Pin Framework Error Injection
13 The CEC Pin Framework is a core CEC framework for CEC hardware that only
14 has low-level support for the CEC bus. Most hardware today will have
15 high-level CEC support where the hardware deals with driving the CEC bus,
17 allows you to connect the CEC pin to a GPIO on e.g. a Raspberry Pi and
18 you have now made a CEC adapter.
22 test how well CEC adapters can handle error conditions.
24 Currently only the cec-gpio driver (when the CEC line is directly
52 # <op>[,<mode>] rx-add-byte add a spurious byte to the received CEC message
53 # <op>[,<mode>] rx-remove-byte remove the last byte from the received CEC message
[all …]
|
| D | cec-ioc-receive.rst | 20 CEC_RECEIVE, CEC_TRANSMIT - Receive or transmit a CEC message
44 To receive a CEC message the application has to fill in the
55 1. a message received from another CEC device (the ``sequence`` field will
60 To send a CEC message the application has to fill in the struct
66 of 2-byte messages). Note that the CEC kernel framework will also reply
82 However, the CEC specification allows sending messages from 'Unregistered' to
88 physical address, but the cable is still connected and CEC still works.
129 - A non-zero sequence number is automatically assigned by the CEC framework
130 for all transmitted messages. It is used by the CEC framework when it queues
157 to :ref:`CEC_RX_STATUS_TIMEOUT <CEC-RX-STATUS-TIMEOUT>` or
[all …]
|
| D | cec-ioc-adap-g-phys-addr.rst | 40 Pointer to the CEC address.
65 A :ref:`CEC_EVENT_STATE_CHANGE <CEC-EVENT-STATE-CHANGE>` event is sent when the physical address
70 significant 4 bits represent 'a'. The CEC root device (usually the TV)
|
| /Linux-v5.4/Documentation/media/kapi/ |
| D | cec-core.rst | 3 CEC Kernel Support
6 The CEC framework provides a unified kernel interface for use with HDMI CEC
14 The CEC Protocol
17 The CEC protocol enables consumer electronic devices to communicate with each
24 The CEC framework described here is up to date with the CEC 2.0 specification.
32 CEC Adapter Interface
35 The struct cec_adapter represents the CEC adapter hardware. It is created by
48 adapter operations which are called by the CEC framework and that you
56 the name of the CEC adapter. Note: this name will be copied.
59 capabilities of the CEC adapter. These capabilities determine the
[all …]
|
| /Linux-v5.4/Documentation/devicetree/bindings/media/ |
| D | cec-gpio.txt | 1 * HDMI CEC GPIO driver
3 The HDMI CEC GPIO module supports CEC implementations where the CEC line
7 Please note: the maximum voltage for the CEC line is 3.63V, for the HPD and
13 - cec-gpios: gpio that the CEC line is connected to. The line should be
16 If the CEC line is associated with an HDMI receiver/transmitter, then the
21 If the CEC line is not associated with an HDMI receiver/transmitter, then
30 Example for the Raspberry Pi 3 where the CEC line is connected to
|
| D | s5p-cec.txt | 1 * Samsung HDMI CEC driver
3 The HDMI CEC module is present is Samsung SoCs and its purpose is to
4 handle communication between HDMI connected devices over the CEC bus.
13 - interrupts : HDMI CEC interrupt number to the CPU.
14 - clocks : from common clock binding: handle to HDMI CEC clock.
21 - needs-hpd : if present the CEC support is only available when the HPD
|
| D | tegra-cec.txt | 1 * Tegra HDMI CEC hardware
3 The HDMI CEC module is present in Tegra SoCs and its purpose is to
4 handle communication between HDMI connected devices over the CEC bus.
13 - interrupts : HDMI CEC interrupt number to the CPU.
14 - clocks : from common clock binding: handle to HDMI CEC clock.
|
| D | st,stm32-cec.txt | 1 STMicroelectronics STM32 CEC driver
7 - clocks : from common clock binding: handle to CEC clocks
9 - interrupts : CEC interrupt number to the CPU.
17 clocks = <&rcc 0 STM32F7_APB1_CLOCK(CEC)>, <&rcc 1 CLK_HDMI_CEC>;
|
| D | meson-ao-cec.txt | 1 * Amlogic Meson AO-CEC driver
3 The Amlogic Meson AO-CEC module is present is Amlogic SoCs and its purpose is
4 to handle communication between HDMI connected devices over the CEC bus.
18 - interrupts : AO-CEC interrupt number to the CPU.
19 - clocks : from common clock binding: handle to AO-CEC clock.
|
| D | stih-cec.txt | 1 STMicroelectronics STIH4xx HDMI CEC driver
7 - clocks : from common clock binding: handle to HDMI CEC clock
8 - interrupts : HDMI CEC interrupt number to the CPU.
10 - pinctrl-0: Specifies the pin control groups used for CEC hardware.
|
| D | cec.txt | 1 Common bindings for HDMI CEC adapters
5 - needs-hpd: if present the CEC support is only available when the HPD
6 is high. Some boards only let the CEC pin through if the HPD is high,
|
| /Linux-v5.4/drivers/media/cec/ |
| D | Kconfig | 3 bool "HDMI CEC RC integration"
7 Pass on CEC remote control messages to the RC framework.
10 bool "Enable CEC error injection support"
13 This option enables CEC error injection using debugfs.
|
| /Linux-v5.4/drivers/media/platform/ |
| D | Kconfig | 543 bool "CEC platform devices"
549 tristate "ChromeOS EC CEC driver"
556 ChromeOS Embedded Controller's CEC.
557 The CEC bus is present in the HDMI connector and enables communication
561 tristate "Amlogic Meson AO CEC driver"
566 This is a driver for Amlogic Meson SoCs AO CEC interface. It uses the
567 generic CEC framework interface.
568 CEC bus is present in the HDMI connector and enables communication
571 tristate "Amlogic Meson G12A AO CEC driver"
579 This is a driver for Amlogic Meson G12A SoCs AO CEC interface.
[all …]
|
| /Linux-v5.4/Documentation/ABI/testing/ |
| D | debugfs-cec-error-inj | 6 The CEC Framework allows for CEC error injection commands through
35 part of the CEC documentation and must keep that documentation up to date
38 The following CEC error injection implementations exist:
|
| /Linux-v5.4/drivers/media/usb/rainshadow-cec/ |
| D | Kconfig | 3 tristate "RainShadow Tech HDMI CEC"
9 This is a cec driver for the RainShadow Tech HDMI CEC device.
|
| /Linux-v5.4/drivers/media/usb/pulse8-cec/ |
| D | Kconfig | 3 tristate "Pulse Eight HDMI CEC"
9 This is a cec driver for the Pulse Eight HDMI CEC device.
|
| /Linux-v5.4/drivers/gpu/drm/bridge/adv7511/ |
| D | Kconfig | 27 bool "ADV7511/33 HDMI CEC driver"
32 When selected the HDMI transmitter will support the CEC feature.
|
| /Linux-v5.4/drivers/gpu/drm/vc4/ |
| D | Kconfig | 25 bool "Broadcom VC4 HDMI CEC Support"
30 and want to use CEC.
|
| /Linux-v5.4/drivers/media/platform/vivid/ |
| D | Kconfig | 28 bool "Enable CEC emulation support"
33 HDMI CEC feature.
|
| /Linux-v5.4/Documentation/devicetree/bindings/display/mediatek/ |
| D | mediatek,hdmi.txt | 28 HDMI CEC
31 The HDMI CEC controller handles hotplug detection and CEC communication.
|
123
