summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorI Viswanath <viswanathiyyappan@gmail.com>2025-07-09 20:37:18 +0530
committerWolfram Sang <wsa+renesas@sang-engineering.com>2025-07-14 09:15:58 +0200
commitc3ff7f06c7876bc292cac1c7d4df3d0bfd74f3b7 (patch)
treee64d0ada3e24a1a73d930ed70a114934f7407c2f
parent6b07ea713486587c48e6dd599e6307806fdd794a (diff)
i2c: Clarify behavior of I2C_M_RD flag
Update the description of I2C_M_RD to clarify that not setting it signals a write transaction Signed-off-by: I Viswanath <viswanathiyyappan@gmail.com> Signed-off-by: Wolfram Sang <wsa+renesas@sang-engineering.com>
-rw-r--r--include/uapi/linux/i2c.h3
1 files changed, 2 insertions, 1 deletions
diff --git a/include/uapi/linux/i2c.h b/include/uapi/linux/i2c.h
index 92326ebde350..a2db2a56c8b0 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 transaction is interpreted as write.
*
* Optional:
* %I2C_M_DMA_SAFE: the buffer of this message is DMA safe. Makes only sense