Lines Matching full:cec
3 CEC Pin Framework Error Injection
6 The CEC Pin Framework is a core CEC framework for CEC hardware that only
7 has low-level support for the CEC bus. Most hardware today will have
8 high-level CEC support where the hardware deals with driving the CEC bus,
10 allows you to connect the CEC pin to a GPIO on e.g. a Raspberry Pi and
11 you have now made a CEC adapter.
15 test how well CEC adapters can handle error conditions.
17 Currently only the cec-gpio driver (when the CEC line is directly
22 through debugfs. Specifically, in ``/sys/kernel/debug/cec/cecX/`` there is
33 $ cat /sys/kernel/debug/cec/cec0/error-inj
45 # <op>[,<mode>] rx-add-byte add a spurious byte to the received CEC message
46 # <op>[,<mode>] rx-remove-byte remove the last byte from the received CEC message
69 # <op> CEC message opcode (0-255) or 'any'
71 # <bit> CEC message bit (0-159)
73 # <poll> CEC poll message used to test arbitration lost (0x00-0xff, default 0x0f)
91 receiving CEC messages and those relating to transmitting CEC messages. In
93 to create custom pulses on the CEC bus.
95 Most error injection commands can be executed for specific CEC opcodes or for
103 So '``any rx-nack``' will NACK the next received CEC message,
104 '``any,always rx-nack``' will NACK all received CEC messages and
154 NACK broadcast messages and messages directed to this CEC adapter.
160 a specific CEC opcode then the bit position must be at least 18,
168 Add a spurious 0x55 byte to the received CEC message, provided
173 Remove the last byte from the received CEC message, provided it
180 As soon as a start bit has been received the CEC adapter will switch
185 the remote CEC transmitter. Arbitration happens when two CEC adapters
191 This does not work if the remote CEC transmitter has logical address
198 This setting changes the behavior of transmitting CEC messages. Normally
202 recommended behavior since there is no point in keeping the CEC bus busy
226 two byte message (e.g. a Get CEC Version message) and add 2 bytes, then
227 the full message received by the remote CEC adapter is
240 an Ack bit. If <op> specifies a specific CEC opcode then the bit position
244 done by reducing the time the CEC bus is high. This bit period is less
255 an Ack bit. If <op> specifies a specific CEC opcode then the bit position
259 done by increasing the time the CEC bus is high.
263 return to Idle state. Unfortunately the CEC specification is silent about
275 the time the CEC bus is high. This start bit period is less than is
282 the time the CEC bus is high. This start bit period is more than is
287 return to Idle state. Unfortunately the CEC specification is silent about
291 Just stop transmitting after this bit. If <op> specifies a specific CEC
299 specific CEC opcode then the bit position must be at least 18, otherwise
310 the CEC line low. The default is 1000 microseconds.
314 CEC line high (unless another CEC adapter pulls it low in that time).
320 be an Ack bit. If <op> specifies a specific CEC opcode then the bit
327 Transmit a single custom pulse as soon as the CEC bus is idle.