From patchwork Tue Apr 30 17:38:07 2024 Content-Type: text/plain; charset="utf-8" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit X-Patchwork-Submitter: Easwar Hariharan X-Patchwork-Id: 793934 Received: from linux.microsoft.com (linux.microsoft.com [13.77.154.182]) by smtp.subspace.kernel.org (Postfix) with ESMTP id BACD6199EA6; Tue, 30 Apr 2024 17:39:46 +0000 (UTC) Authentication-Results: smtp.subspace.kernel.org; arc=none smtp.client-ip=13.77.154.182 ARC-Seal: i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1714498788; cv=none; b=TNY4vY7MnAmBHRgKywEaJMYTPJgnCp1V6HvqBRnXfmHQE1cmrJ98te/iOar4HK9qwEUl/ovteGS79zbHhlPE6pusH2YPGFQXDyqr03COG7Q2Y0yEpxqeY48oypH7uxEts473cpOLWcDId1E0MrJwM98IfV/+CQWe9VefbHYpksU= ARC-Message-Signature: i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1714498788; c=relaxed/simple; bh=eoHl763OrMxhawtO0Qsze5bzx3YTluOQBkDXFpypQ2c=; h=From:To:Cc:Subject:Date:Message-Id:In-Reply-To:References: MIME-Version; b=XvzrQNtZZF941di2n3lh8R8pF9IC7sj2hZcGpPO8rjjpB2cI3+VeLpcbObbap+xZzOYyRFRCtKz3h5yxjBhDsCjPYAkV6Agyg1SCSP19e3opBDLXMJ778YVu7nBlk2s/fSnu/GfeYTedPZihEJFEDueQHq0lGyinyve2uO56uT4= ARC-Authentication-Results: i=1; smtp.subspace.kernel.org; dmarc=pass (p=none dis=none) header.from=linux.microsoft.com; spf=pass smtp.mailfrom=linux.microsoft.com; dkim=pass (1024-bit key) header.d=linux.microsoft.com header.i=@linux.microsoft.com header.b=VE4UX4xy; arc=none smtp.client-ip=13.77.154.182 Authentication-Results: smtp.subspace.kernel.org; dmarc=pass (p=none dis=none) header.from=linux.microsoft.com Authentication-Results: smtp.subspace.kernel.org; spf=pass smtp.mailfrom=linux.microsoft.com Authentication-Results: smtp.subspace.kernel.org; dkim=pass (1024-bit key) header.d=linux.microsoft.com header.i=@linux.microsoft.com header.b="VE4UX4xy" Received: from rrs24-12-35.corp.microsoft.com (unknown [131.107.174.176]) by linux.microsoft.com (Postfix) with ESMTPSA id 51A80210FBDE; Tue, 30 Apr 2024 10:39:46 -0700 (PDT) DKIM-Filter: OpenDKIM Filter v2.11.0 linux.microsoft.com 51A80210FBDE DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=linux.microsoft.com; s=default; t=1714498786; bh=u7TOJ/936gc3y5DAMsiZbDvXVRCiqMrBgS62kL0MAbk=; h=From:To:Cc:Subject:Date:In-Reply-To:References:From; b=VE4UX4xyCE61UBMu1Xd/VzjcGPFnY6eGs9r9p2t8kzRlXwsxFbTHGmvfEp/9y0K7X 79SWXhO6dU3tSgIYj5pU9t0kloxtqQm0hDbK6ouYCtSqaBdhjY3CS9BYZa7AolCCUN P2HKf214ZeDL376BreR6Uyu/Xv5cldFa/EcCTkhE= From: Easwar Hariharan To: Andy Walls , Mauro Carvalho Chehab , linux-media@vger.kernel.org (open list:IVTV VIDEO4LINUX DRIVER), linux-kernel@vger.kernel.org (open list) Cc: Wolfram Sang , amd-gfx@lists.freedesktop.org (open list:RADEON and AMDGPU DRM DRIVERS), dri-devel@lists.freedesktop.org (open list:DRM DRIVERS), linux-kernel@vger.kernel.org (open list), intel-gfx@lists.freedesktop.org (open list:INTEL DRM DISPLAY FOR XE AND I915 DRIVERS), intel-xe@lists.freedesktop.org (open list:INTEL DRM DISPLAY FOR XE AND I915 DRIVERS), nouveau@lists.freedesktop.org (open list:DRM DRIVER FOR NVIDIA GEFORCE/QUADRO GPUS), linux-i2c@vger.kernel.org (open list:I2C SUBSYSTEM HOST DRIVERS), linux-media@vger.kernel.org (open list:BTTV VIDEO4LINUX DRIVER), linux-fbdev@vger.kernel.org (open list:FRAMEBUFFER LAYER), Easwar Hariharan Subject: [PATCH v1 08/12] media: ivtv: Make I2C terminology more inclusive Date: Tue, 30 Apr 2024 17:38:07 +0000 Message-Id: <20240430173812.1423757-9-eahariha@linux.microsoft.com> X-Mailer: git-send-email 2.34.1 In-Reply-To: <20240430173812.1423757-1-eahariha@linux.microsoft.com> References: <20240430173812.1423757-1-eahariha@linux.microsoft.com> Precedence: bulk X-Mailing-List: linux-media@vger.kernel.org List-Id: List-Subscribe: List-Unsubscribe: MIME-Version: 1.0 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@sang-engineering.com/ Signed-off-by: Easwar Hariharan --- 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;