Searched refs:CEC (Results 1 – 25 of 70) sorted by relevance
123
/Linux-v4.19/Documentation/media/uapi/cec/ |
D | cec-ioc-adap-g-log-addrs.rst | 38 To query the current CEC logical addresses, applications call 53 values (CEC version 2.0, no vendor ID and an empty OSD name). 60 A :ref:`CEC_EVENT_STATE_CHANGE <CEC-EVENT-STATE-CHANGE>` event is sent when the 92 - The CEC version that this adapter shall use. See 95 Note that :ref:`CEC_OP_CEC_VERSION_1_3A <CEC-OP-CEC-VERSION-1-3A>` is not allowed by the CEC 104 ignored. Note that the CEC 2.0 standard allows for a maximum of 2 108 what was requested. If this field is set to 0, then the CEC 133 to :ref:`CEC_LOG_ADDR_TYPE_UNREGISTERED <CEC-LOG-ADDR-TYPE-UNREGISTERED>`). 136 - CEC 2.0 specific: the bit mask of all device types. See 137 :ref:`cec-all-dev-types-flags`. It is used in the CEC 2.0 [all …]
|
D | cec-ioc-g-mode.rst | 11 CEC_G_MODE, CEC_S_MODE - Get or set exclusive use of the CEC adapter 29 Pointer to CEC mode. 36 obtain exclusive access to the CEC adapter. This ioctl sets the 39 used to initiate messages, i.e. it commands other CEC devices. The 40 follower is the filehandle that receives messages sent to the CEC 44 When a CEC message is received, then the CEC framework will decide how 47 is waiting for it. In addition the CEC framework will process it. 49 If the message is not a reply, then the CEC framework will process it 57 The CEC framework will process core messages unless requested otherwise 59 case, the CEC framework will pass on most core messages without [all …]
|
D | cec-intro.rst | 8 HDMI cable to communicate. The protocol for CEC version 1.4 is defined 9 in supplements 1 (CEC) and 2 (HEAC or HDMI Ethernet and Audio Return 11 extensions added to CEC version 2.0 are defined in chapter 11 of the 19 CEC, need to be handled by the kernel, others can be handled either by 22 In addition, CEC can be implemented in HDMI receivers, transmitters and 24 control just the CEC pin. 26 Drivers that support CEC will create a CEC device node (/dev/cecX) to 27 give userspace access to the CEC adapter. The 32 provides three tools to handle CEC: 34 - cec-ctl: the Swiss army knife of CEC. Allows you to configure, transmit [all …]
|
D | cec-ioc-adap-g-caps.rst | 51 - The name of this CEC adapter. The combination ``driver`` and 55 - The capabilities of the CEC adapter, see 59 - CEC Framework API version, formatted with the ``KERNEL_VERSION()`` 67 .. flat-table:: CEC Capabilities Flags 72 * .. _`CEC-CAP-PHYS-ADDR`: 81 * .. _`CEC-CAP-LOG-ADDRS`: 89 * .. _`CEC-CAP-TRANSMIT`: 93 - Userspace can transmit CEC messages by calling 97 capability isn't set, then the kernel will handle all CEC 98 transmits and process all CEC messages it receives. [all …]
|
D | cec-ioc-dqevent.rst | 12 CEC_DQEVENT - Dequeue a CEC event 33 CEC devices can send asynchronous events. These can be retrieved by 43 two :ref:`CEC_EVENT_STATE_CHANGE <CEC-EVENT-STATE-CHANGE>` events with 86 replied to within a second according to the CEC specification, 108 - :cspan:`1` The CEC event type, see :ref:`cec-events`. 119 - The new adapter state as sent by the :ref:`CEC_EVENT_STATE_CHANGE <CEC-EVENT-STATE-CHANGE>` 124 - The number of lost messages as sent by the :ref:`CEC_EVENT_LOST_MSGS <CEC-EVENT-LOST-MSGS>` 132 .. flat-table:: CEC Events Types 137 * .. _`CEC-EVENT-STATE-CHANGE`: 141 - Generated when the CEC Adapter's state changes. When open() is [all …]
|
D | cec-pin-error-inj.rst | 1 CEC Pin Framework Error Injection 4 The CEC Pin Framework is a core CEC framework for CEC hardware that only 5 has low-level support for the CEC bus. Most hardware today will have 6 high-level CEC support where the hardware deals with driving the CEC bus, 8 allows you to connect the CEC pin to a GPIO on e.g. a Raspberry Pi and 9 you have now made a CEC adapter. 13 test how well CEC adapters can handle error conditions. 15 Currently only the cec-gpio driver (when the CEC line is directly 43 # <op>[,<mode>] rx-add-byte add a spurious byte to the received CEC message 44 # <op>[,<mode>] rx-remove-byte remove the last byte from the received CEC message [all …]
|
D | cec-ioc-receive.rst | 13 CEC_RECEIVE, CEC_TRANSMIT - Receive or transmit a CEC message 37 To receive a CEC message the application has to fill in the 48 1. a message received from another CEC device (the ``sequence`` field will 53 To send a CEC message the application has to fill in the struct 59 of 2-byte messages). Note that the CEC kernel framework will also reply 75 However, the CEC specification allows sending messages from 'Unregistered' to 81 physical address, but the cable is still connected and CEC still works. 122 - A non-zero sequence number is automatically assigned by the CEC framework 123 for all transmitted messages. It is used by the CEC framework when it queues 150 to :ref:`CEC_RX_STATUS_TIMEOUT <CEC-RX-STATUS-TIMEOUT>` or [all …]
|
D | cec-ioc-adap-g-phys-addr.rst | 33 Pointer to the CEC address. 58 A :ref:`CEC_EVENT_STATE_CHANGE <CEC-EVENT-STATE-CHANGE>` event is sent when the physical address 63 significant 4 bits represent 'a'. The CEC root device (usually the TV)
|
D | cec-header.rst | 6 CEC Header File
|
/Linux-v4.19/Documentation/media/kapi/ |
D | cec-core.rst | 1 CEC Kernel Support 4 The CEC framework provides a unified kernel interface for use with HDMI CEC 12 The CEC Protocol 15 The CEC protocol enables consumer electronic devices to communicate with each 22 The CEC framework described here is up to date with the CEC 2.0 specification. 30 CEC Adapter Interface 33 The struct cec_adapter represents the CEC adapter hardware. It is created by 46 adapter operations which are called by the CEC framework and that you 54 the name of the CEC adapter. Note: this name will be copied. 57 capabilities of the CEC adapter. These capabilities determine the [all …]
|
/Linux-v4.19/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 | 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. 13 - interrupts : AO-CEC interrupt number to the CPU. 14 - clocks : from common clock binding: handle to AO-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 | 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-v4.19/drivers/media/cec/ |
D | Kconfig | 2 bool "HDMI CEC RC integration" 6 Pass on CEC remote control messages to the RC framework. 9 bool "Enable CEC error injection support" 12 This option enables CEC error injection using debugfs.
|
/Linux-v4.19/drivers/media/platform/ |
D | Kconfig | 534 bool "CEC platform devices" 540 tristate "ChromeOS EC CEC driver" 548 ChromeOS Embedded Controller's CEC. 549 The CEC bus is present in the HDMI connector and enables communication 553 tristate "Amlogic Meson AO CEC driver" 558 This is a driver for Amlogic Meson SoCs AO CEC interface. It uses the 559 generic CEC framework interface. 560 CEC bus is present in the HDMI connector and enables communication 563 tristate "Generic GPIO-based CEC driver" 569 This is a generic GPIO-based CEC driver. [all …]
|
/Linux-v4.19/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-v4.19/drivers/media/usb/pulse8-cec/ |
D | Kconfig | 2 tristate "Pulse Eight HDMI CEC" 8 This is a cec driver for the Pulse Eight HDMI CEC device.
|
/Linux-v4.19/drivers/media/usb/rainshadow-cec/ |
D | Kconfig | 2 tristate "RainShadow Tech HDMI CEC" 8 This is a cec driver for the RainShadow Tech HDMI CEC device.
|
/Linux-v4.19/drivers/gpu/drm/bridge/adv7511/ |
D | Kconfig | 26 bool "ADV7511/33 HDMI CEC driver" 31 When selected the HDMI transmitter will support the CEC feature.
|
/Linux-v4.19/drivers/gpu/drm/vc4/ |
D | Kconfig | 24 bool "Broadcom VC4 HDMI CEC Support" 29 and want to use CEC.
|
/Linux-v4.19/drivers/media/platform/vivid/ |
D | Kconfig | 28 bool "Enable CEC emulation support" 33 HDMI CEC feature.
|
123