Searched refs:NACK (Results 1 – 8 of 8) sorted by relevance
| /Linux-v5.4/Documentation/i2c/ |
| D | slave-interface.rst | 112 still shifted out. If the master sends NACK and stops reading after the byte
162 About ACK/NACK
166 device is basically present or if it mysteriously disappeared. Using NACK to
170 to NACK them. For those reasons, this API does not support NACK in the address
173 Currently, there is no slave event to report if the master did ACK or NACK a
|
| /Linux-v5.4/drivers/i2c/busses/ |
| D | i2c-qcom-geni.c | 54 NACK, enumerator
65 #define DM_I2C_CB_ERR ((BIT(NACK) | BIT(BUS_PROTO) | BIT(ARB_LOST)) \
99 [NACK] = {-ENXIO, "NACK: slv unresponsive, check its power/reset-ln"},
196 if (err != NACK && err != GENI_ABORT_DONE) { in geni_i2c_err()
228 geni_i2c_err(gi2c, NACK); in geni_i2c_irq()
|
| /Linux-v5.4/Documentation/i2c/busses/ |
| D | i2c-mlxcpld.rst | 50 Bit 4 - ACK/NACK.
|
| /Linux-v5.4/Documentation/media/uapi/cec/ |
| D | cec-pin-error-inj.rst | 50 # <op>[,<mode>] rx-nack NACK the message instead of sending an ACK
110 So '``any rx-nack``' will NACK the next received CEC message,
111 '``any,always rx-nack``' will NACK all received CEC messages and
112 '``0x82,toggle rx-nack``' will only NACK if an Active Source message was
161 NACK broadcast messages and messages directed to this CEC adapter.
|
| D | cec-ioc-receive.rst | 190 :ref:`CEC_TX_STATUS_NACK <CEC-TX-STATUS-NACK>` status bit is set.
263 * .. _`CEC-TX-STATUS-NACK`:
|
| /Linux-v5.4/Documentation/devicetree/bindings/regulator/ |
| D | qcom,rpmh-regulator.txt | 103 must wait for an ACK or a NACK from RPMh for every request
|
| /Linux-v5.4/Documentation/translations/it_IT/process/ |
| D | stable-kernel-rules.rst | 170 - La commissione per la revisione ha 48 ore per dare il proprio ACK o NACK
|
| /Linux-v5.4/Documentation/media/kapi/ |
| D | cec-core.rst | 263 The hardware must be able to differentiate between OK, NACK and 'something
|
