Lines Matching refs:CEC
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
49 adapter operations which are called by the CEC framework and that you
57 the name of the CEC adapter. Note: this name will be copied.
60 capabilities of the CEC adapter. These capabilities determine the
95 Implementing the Low-Level CEC Adapter
125 The seven low-level ops deal with various aspects of controlling the CEC adapter
133 This callback enables or disables the CEC hardware. Enabling the CEC hardware
136 capability is not set, then the physical address can change while the CEC
137 hardware is enabled. CEC drivers should not set CEC_CAP_NEEDS_HPD unless
140 state of the CEC adapter after calling cec_allocate_adapter() is disabled.
161 If enabled, then the adapter should be put in a mode to also monitor CEC pin
176 should return -ENXIO. Once a logical address is programmed the CEC hardware
210 To log the current CEC hardware status::
214 This optional callback can be used to show the status of the CEC hardware.
244 arbitration was lost: another CEC initiator
245 took control of the CEC line and you lost the arbitration.
252 low drive was detected on the CEC bus. This indicates that
290 When a CEC message was received:
300 Typically the CEC hardware provides interrupts that signal when a transmit
302 when a CEC message was received.
304 The CEC driver should always process the transmit interrupts first before
312 If the CEC adapter supports Error Injection functionality, then that can
325 /* High-level CEC message callback */
335 This basic parsing is done in the CEC Framework. It is up to the driver to decide
371 Implementing the High-Level CEC Adapter
375 CEC protocol driven. The following high-level callbacks are available:
386 /* High-level CEC message callback */
391 received CEC message::
395 If the driver wants to process a CEC message, then it can implement this
397 -ENOMSG, otherwise the CEC framework assumes it processed this message and
401 CEC framework functions
404 CEC Adapter drivers can call the following CEC framework functions:
410 Transmit a CEC message. If block is true, then wait until the message has been
418 the physical address has become valid, then the CEC framework will start
422 When the physical address is set to a valid value the CEC adapter will
424 then the CEC adapter will be disabled. If you change a valid physical address
440 Claim the CEC logical addresses. Should never be called if CEC_CAP_LOG_ADDRS
449 CEC Pin framework
452 Most CEC hardware operates on full CEC messages where the software provides
453 the message and the hardware handles the low-level CEC protocol. But some
454 hardware only drives the CEC pin and software has to handle the low-level
455 CEC protocol. The CEC pin framework was created to handle such devices.
463 a cheap CEC analyser, especially if interrupts can be used to detect
464 CEC pin transitions from low to high or vice versa.
468 CEC Notifier framework
471 Most drm HDMI implementations have an integrated CEC implementation and no
472 notifier support is needed. But some have independent CEC implementations
474 completely separate chip that deals with the CEC pin. For those cases a
476 CEC driver about changes in the physical address.