I2C v7, SMBus 3.2, and I3C 1.1.1 specifications have replaced "master/slave" with more appropriate terms. Inspired by and following on to Wolfram's series to fix drivers/i2c/[1], fix the terminology for users of I2C_ALGOBIT bitbanging interface, now that the approved verbiage exists in the specification. Compile tested, no functionality changes intended [1]: https://lore.kernel.org/all/20240322132619.6389-1-wsa+renesas@xxxxxxxxxxxxxxxxxxxx/ Signed-off-by: Easwar Hariharan <eahariha@xxxxxxxxxxxxxxxxxxx> --- drivers/media/pci/ivtv/ivtv-i2c.c | 16 ++++++++-------- 1 file changed, 8 insertions(+), 8 deletions(-) diff --git a/drivers/media/pci/ivtv/ivtv-i2c.c b/drivers/media/pci/ivtv/ivtv-i2c.c index c052c57c6dce..967e6a025020 100644 --- a/drivers/media/pci/ivtv/ivtv-i2c.c +++ b/drivers/media/pci/ivtv/ivtv-i2c.c @@ -33,14 +33,14 @@ Some more general comments about what we are doing: The i2c bus is a 2 wire serial bus, with clock (SCL) and data (SDA) - lines. To communicate on the bus (as a master, we don't act as a slave), + lines. To communicate on the bus (as a host, we don't act as a client), we first initiate a start condition (ivtv_start). We then write the address of the device that we want to communicate with, along with a flag - that indicates whether this is a read or a write. The slave then issues + that indicates whether this is a read or a write. The client then issues an ACK signal (ivtv_ack), which tells us that it is ready for reading / writing. We then proceed with reading or writing (ivtv_read/ivtv_write), and finally issue a stop condition (ivtv_stop) to make the bus available - to other masters. + to other hosts. There is an additional form of transaction where a write may be immediately followed by a read. In this case, there is no intervening @@ -379,7 +379,7 @@ static int ivtv_waitsda(struct ivtv *itv, int val) return 0; } -/* Wait for the slave to issue an ACK */ +/* Wait for the client to issue an ACK */ static int ivtv_ack(struct ivtv *itv) { int ret = 0; @@ -407,7 +407,7 @@ static int ivtv_ack(struct ivtv *itv) return ret; } -/* Write a single byte to the i2c bus and wait for the slave to ACK */ +/* Write a single byte to the i2c bus and wait for the client to ACK */ static int ivtv_sendbyte(struct ivtv *itv, unsigned char byte) { int i, bit; @@ -471,7 +471,7 @@ static int ivtv_readbyte(struct ivtv *itv, unsigned char *byte, int nack) return 0; } -/* Issue a start condition on the i2c bus to alert slaves to prepare for +/* Issue a start condition on the i2c bus to alert clients to prepare for an address write */ static int ivtv_start(struct ivtv *itv) { @@ -534,7 +534,7 @@ static int ivtv_stop(struct ivtv *itv) return 0; } -/* Write a message to the given i2c slave. do_stop may be 0 to prevent +/* Write a message to the given i2c client. do_stop may be 0 to prevent issuing the i2c stop condition (when following with a read) */ static int ivtv_write(struct ivtv *itv, unsigned char addr, unsigned char *data, u32 len, int do_stop) { @@ -558,7 +558,7 @@ static int ivtv_write(struct ivtv *itv, unsigned char addr, unsigned char *data, return ret; } -/* Read data from the given i2c slave. A stop condition is always issued. */ +/* Read data from the given i2c client. A stop condition is always issued. */ static int ivtv_read(struct ivtv *itv, unsigned char addr, unsigned char *data, u32 len) { int retry, ret = -EREMOTEIO; -- 2.34.1
