Update I2C_M_RD Documentation to clarify that not setting it signals a i2c_write Signed-off-by: Viswanath <viswanathiyyappan@xxxxxxxxx> --- include/uapi/linux/i2c.h | 3 ++- 1 file changed, 2 insertions(+), 1 deletion(-) diff --git a/include/uapi/linux/i2c.h b/include/uapi/linux/i2c.h index aa751389de07..07cc80e9e854 100644 --- a/include/uapi/linux/i2c.h +++ b/include/uapi/linux/i2c.h @@ -21,7 +21,8 @@ * * @flags: * Supported by all adapters: - * %I2C_M_RD: read data (from slave to master). Guaranteed to be 0x0001! + * %I2C_M_RD: read data (from slave to master). Guaranteed to be 0x0001! If + * not set, the action is taken to be write data (from slave to master). * * Optional: * %I2C_M_DMA_SAFE: the buffer of this message is DMA safe. Makes sense only -- 2.43.0