From patchwork Fri Jun 14 08:12:39 2024 Content-Type: text/plain; charset="utf-8" MIME-Version: 1.0 Content-Transfer-Encoding: 8bit X-Patchwork-Submitter: Wolfram Sang X-Patchwork-Id: 804341 Received: from mail.zeus03.de (zeus03.de [194.117.254.33]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by smtp.subspace.kernel.org (Postfix) with ESMTPS id 0A0A11836C7 for ; Fri, 14 Jun 2024 08:12:50 +0000 (UTC) Authentication-Results: smtp.subspace.kernel.org; arc=none smtp.client-ip=194.117.254.33 ARC-Seal: i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1718352774; cv=none; b=ClOfUxeiPl3bMEHrXpWl0BWedgdW9GA3DHqr7v07JRxhw9yTqIjgRmu198JejhFxsG+OcHyKZscTp+JmWfOlDj+5NGNQ4Ab+8nWpCW78xuAM5jlpH9i26SCWu0+KjYwrr0OztXIz5008lQYZ3TyQYWSYBGvu/mmjZRO1D+Pdx7M= ARC-Message-Signature: i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1718352774; c=relaxed/simple; bh=AaeKWFy6+MhJUSVDuiArePmxqwjpDms46lje4lfg78Y=; h=From:To:Cc:Subject:Date:Message-ID:In-Reply-To:References: MIME-Version:Content-Type; b=DOJWAhyPyRLHUVxFTv++EUGikuu+SDo3fSV3BF9Fpxup46aNwRt7gxIqpQcLluFkJZ0tpuMo8Xp1EvWiH6gm4hrJWcOrv5fsay9O0xP525XONF77b1tMtBDk+fv0jWppiq07FJ1iDLzTOF6EOYgHWbY7ZecnQg8KJGmEHgA1568= ARC-Authentication-Results: i=1; smtp.subspace.kernel.org; dmarc=none (p=none dis=none) header.from=sang-engineering.com; spf=pass smtp.mailfrom=sang-engineering.com; dkim=pass (2048-bit key) header.d=sang-engineering.com header.i=@sang-engineering.com header.b=QNj1E+Ck; arc=none smtp.client-ip=194.117.254.33 Authentication-Results: smtp.subspace.kernel.org; dmarc=none (p=none dis=none) header.from=sang-engineering.com Authentication-Results: smtp.subspace.kernel.org; spf=pass smtp.mailfrom=sang-engineering.com Authentication-Results: smtp.subspace.kernel.org; dkim=pass (2048-bit key) header.d=sang-engineering.com header.i=@sang-engineering.com header.b="QNj1E+Ck" DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= sang-engineering.com; h=from:to:cc:subject:date:message-id :in-reply-to:references:mime-version:content-type :content-transfer-encoding; s=k1; bh=QxN9/peWzKBlFqRmDXEKD0iHTiZ lunJFWOblMthWaXk=; b=QNj1E+CkJ3mLavkzjyqlaUk5ZBhONnhZkCVyWtWsVkv 8IJEyytDimK6oFSAXFdmsyvTfXH/Kq05EJSKxZ+OVu7I55RqJEDYk1wl96ATg8Rc PAG9R2xLDwKm7NSy1bLsSdI+0TLAyh1BTz2MYVJw1KYOO54fpS2/S+FJnoSzSCEj z55lf+tinSvKMV+QhaU8WAlCD3xtQ6Mgm5sVmjPIHRCUY/50kMHTAxAKZDZ1c6XK cSYxaA07PQK30TwolJUF4o81ygTHz7YxR57JvWO9UTcqH1uvBAq1wYKuc5oiFQsd PDO6mSU0+vWc945iWMyyGNSjUCHNmDI0eat3ZqH9XIA== Received: (qmail 1438092 invoked from network); 14 Jun 2024 10:12:48 +0200 Received: by mail.zeus03.de with ESMTPSA (TLS_AES_256_GCM_SHA384 encrypted, authenticated); 14 Jun 2024 10:12:48 +0200 X-UD-Smtp-Session: l3s3148p1@N0RbLtUaAoIgAwDPXzjQABqqX1QYyOSW From: Wolfram Sang To: linux-i2c@vger.kernel.org Cc: Easwar Hariharan , linux-doc@vger.kernel.org, linux-kernel@vger.kernel.org, Andi Shyti , Wolfram Sang Subject: [PATCH v3 1/6] docs: i2c: summary: start sentences consistently. Date: Fri, 14 Jun 2024 10:12:39 +0200 Message-ID: <20240614081239.7128-9-wsa+renesas@sang-engineering.com> X-Mailer: git-send-email 2.43.0 In-Reply-To: <20240614081239.7128-8-wsa+renesas@sang-engineering.com> References: <20240614081239.7128-8-wsa+renesas@sang-engineering.com> Precedence: bulk X-Mailing-List: linux-i2c@vger.kernel.org List-Id: List-Subscribe: List-Unsubscribe: MIME-Version: 1.0 Change the first paragraphs to contain only one space after the end of the previous sentence like in the rest of the document. Signed-off-by: Wolfram Sang Reviewed-by: Easwar Hariharan --- Documentation/i2c/summary.rst | 12 ++++++------ 1 file changed, 6 insertions(+), 6 deletions(-) diff --git a/Documentation/i2c/summary.rst b/Documentation/i2c/summary.rst index 786c618ba3be..28ff80a2302b 100644 --- a/Documentation/i2c/summary.rst +++ b/Documentation/i2c/summary.rst @@ -4,10 +4,10 @@ Introduction to I2C and SMBus I²C (pronounce: I squared C and written I2C in the kernel documentation) is a protocol developed by Philips. It is a slow two-wire protocol (variable -speed, up to 400 kHz), with a high speed extension (3.4 MHz). It provides +speed, up to 400 kHz), with a high speed extension (3.4 MHz). It provides an inexpensive bus for connecting many types of devices with infrequent or -low bandwidth communications needs. I2C is widely used with embedded -systems. Some systems use variants that don't meet branding requirements, +low bandwidth communications needs. I2C is widely used with embedded +systems. Some systems use variants that don't meet branding requirements, and so are not advertised as being I2C but come under different names, e.g. TWI (Two Wire Interface), IIC. @@ -18,14 +18,14 @@ access the PDF. An older version of the specification (revision 6) is archived `here `_. SMBus (System Management Bus) is based on the I2C protocol, and is mostly -a subset of I2C protocols and signaling. Many I2C devices will work on an +a subset of I2C protocols and signaling. Many I2C devices will work on an SMBus, but some SMBus protocols add semantics beyond what is required to -achieve I2C branding. Modern PC mainboards rely on SMBus. The most common +achieve I2C branding. Modern PC mainboards rely on SMBus. The most common devices connected through SMBus are RAM modules configured using I2C EEPROMs, and hardware monitoring chips. Because the SMBus is mostly a subset of the generalized I2C bus, we can -use its protocols on many I2C systems. However, there are systems that don't +use its protocols on many I2C systems. However, there are systems that don't meet both SMBus and I2C electrical constraints; and others which can't implement all the common SMBus protocol semantics or messages. From patchwork Fri Jun 14 08:12:40 2024 Content-Type: text/plain; charset="utf-8" MIME-Version: 1.0 Content-Transfer-Encoding: 8bit X-Patchwork-Submitter: Wolfram Sang X-Patchwork-Id: 804340 Received: from mail.zeus03.de (zeus03.de [194.117.254.33]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by smtp.subspace.kernel.org (Postfix) with ESMTPS id 56D7C1836D3 for ; Fri, 14 Jun 2024 08:12:50 +0000 (UTC) Authentication-Results: smtp.subspace.kernel.org; arc=none smtp.client-ip=194.117.254.33 ARC-Seal: i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1718352775; cv=none; b=CMIjI2Surd4rFxIiSijVCmhh09TWRuFLt+hbVdSjmMQIBJAVuwb2fQ5hzK2WyU3su5wT95r3MJfJ6Vw6MQVkAwBy3zop+qKISTVq8yL5mOGn060GQE3y+4+BbedQHCo0TlBAsb9rfk+41tdsrjdJh5Swg6SojMYTTzner2hUYf4= ARC-Message-Signature: i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1718352775; c=relaxed/simple; bh=tLa3YjKzTjbALrEqcR62zhXe0F7RUglCnTOQTHelM9A=; h=From:To:Cc:Subject:Date:Message-ID:In-Reply-To:References: MIME-Version:Content-Type; b=G2tiV6hhT3ZkPO0pOnt0vc4DfARtzZYeo2xYeSbDkBLItDrSEMa86UVHwjPmxOlr9dMht6j6oOFFHxevr0/vRxnACBVYt35x7KN30Yb+zeKgcF4EvwtnwvHJjLtAuTNVYxso3ia/EMcFD+uYcr2SX2XriYTJv/LKfu0QJwd88JE= ARC-Authentication-Results: i=1; smtp.subspace.kernel.org; dmarc=none (p=none dis=none) header.from=sang-engineering.com; spf=pass smtp.mailfrom=sang-engineering.com; dkim=pass (2048-bit key) header.d=sang-engineering.com header.i=@sang-engineering.com header.b=Vdwrf4hU; arc=none smtp.client-ip=194.117.254.33 Authentication-Results: smtp.subspace.kernel.org; dmarc=none (p=none dis=none) header.from=sang-engineering.com Authentication-Results: smtp.subspace.kernel.org; spf=pass smtp.mailfrom=sang-engineering.com Authentication-Results: smtp.subspace.kernel.org; dkim=pass (2048-bit key) header.d=sang-engineering.com header.i=@sang-engineering.com header.b="Vdwrf4hU" DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= sang-engineering.com; h=from:to:cc:subject:date:message-id :in-reply-to:references:mime-version:content-type :content-transfer-encoding; s=k1; bh=ns0TUqgMIMc2G1ba8motoRRT6bt z+ty/Oyg8gP8SWmY=; b=Vdwrf4hUr1b2PQDAjBWcFH3KuJqYXDZLc3hkMPaxSkx scwyfv91PRPF44bhZXdieA7XWJqXJOvyl9UPamOg9oyRMatjlp65mcotuemR0+p1 XmbpCXxT6fjRkwpuE7wLH14MqRpkF0UGhnplmxkIPT1n6GLSJBFHM2FRDtexQImu iZMw6T+jb9jj4ujDR0YjA5rNmJ1qegp1HLtqMmo39BliSPHSyc1ladt5Kd04Lw0R 6ak/6gRz2drvGMICconvQHgnX4OfmBCsFudYyBMYFRuN4PvgTgLby5tSi3rVzwhn SUn1Hz78V2Ir5jZly1wDdvENjqB/StAulE0JzGKJr2w== Received: (qmail 1438126 invoked from network); 14 Jun 2024 10:12:49 +0200 Received: by mail.zeus03.de with ESMTPSA (TLS_AES_256_GCM_SHA384 encrypted, authenticated); 14 Jun 2024 10:12:49 +0200 X-UD-Smtp-Session: l3s3148p1@cn1jLtUaCoIgAwDPXzjQABqqX1QYyOSW From: Wolfram Sang To: linux-i2c@vger.kernel.org Cc: Easwar Hariharan , linux-doc@vger.kernel.org, linux-kernel@vger.kernel.org, Andi Shyti , Wolfram Sang Subject: [PATCH v3 2/6] docs: i2c: summary: update I2C specification link Date: Fri, 14 Jun 2024 10:12:40 +0200 Message-ID: <20240614081239.7128-10-wsa+renesas@sang-engineering.com> X-Mailer: git-send-email 2.43.0 In-Reply-To: <20240614081239.7128-8-wsa+renesas@sang-engineering.com> References: <20240614081239.7128-8-wsa+renesas@sang-engineering.com> Precedence: bulk X-Mailing-List: linux-i2c@vger.kernel.org List-Id: List-Subscribe: List-Unsubscribe: MIME-Version: 1.0 Luckily, the specs are directly downloadable again, so update the link. Also update its title to the original name "I²C". Signed-off-by: Wolfram Sang Reviewed-by: Easwar Hariharan --- Documentation/i2c/summary.rst | 8 +++----- 1 file changed, 3 insertions(+), 5 deletions(-) diff --git a/Documentation/i2c/summary.rst b/Documentation/i2c/summary.rst index 28ff80a2302b..e3ab1d414014 100644 --- a/Documentation/i2c/summary.rst +++ b/Documentation/i2c/summary.rst @@ -11,11 +11,9 @@ systems. Some systems use variants that don't meet branding requirements, and so are not advertised as being I2C but come under different names, e.g. TWI (Two Wire Interface), IIC. -The latest official I2C specification is the `"I2C-bus specification and user -manual" (UM10204) `_ -published by NXP Semiconductors. However, you need to log-in to the site to -access the PDF. An older version of the specification (revision 6) is archived -`here `_. +The latest official I2C specification is the `"I²C-bus specification and user +manual" (UM10204) `_ +published by NXP Semiconductors, version 7 as of this writing. SMBus (System Management Bus) is based on the I2C protocol, and is mostly a subset of I2C protocols and signaling. Many I2C devices will work on an From patchwork Fri Jun 14 08:12:42 2024 Content-Type: text/plain; charset="utf-8" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit X-Patchwork-Submitter: Wolfram Sang X-Patchwork-Id: 804339 Received: from mail.zeus03.de (zeus03.de [194.117.254.33]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by smtp.subspace.kernel.org (Postfix) with ESMTPS id 20FC5185096 for ; Fri, 14 Jun 2024 08:12:53 +0000 (UTC) Authentication-Results: smtp.subspace.kernel.org; arc=none smtp.client-ip=194.117.254.33 ARC-Seal: i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1718352776; cv=none; b=L/BLaJghcLs8AzLyoxs/9WWZYFWF4W2JYGw/qOFBUKx3vQY7mQizCdLm3whiVqhByVYMBMP4NXFUWh6aqpO32eg7NXEZRKa9LY4obADbahb1I6ff5YYjJoeMO7h80KdhaFZKArIukNUREqhJSZ/t00XdJGER4ZWa6ii6IaCOIzk= ARC-Message-Signature: i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1718352776; c=relaxed/simple; bh=tH0NOSAY7BDUS/VNB/ZGWgSpJi45DZYDHlrsL1Okdl4=; h=From:To:Cc:Subject:Date:Message-ID:In-Reply-To:References: MIME-Version; b=EsZxhXKPjK8aUcZfqlyXHcsb11GBhtdzUn1+FpfUTtRmGT2Am1e55W/iG44E0m8TnhmUZns+n1whWNW90L7l8IWc1/M9SmLjPu0+uJwd1UykNkKBGIKHtarkVmtfwQN5sr6h+BtRGSGcFRUdPvo5SFJvN0/UmsCgzHSYj2a8GbI= ARC-Authentication-Results: i=1; smtp.subspace.kernel.org; dmarc=none (p=none dis=none) header.from=sang-engineering.com; spf=pass smtp.mailfrom=sang-engineering.com; dkim=pass (2048-bit key) header.d=sang-engineering.com header.i=@sang-engineering.com header.b=eXsONqg9; arc=none smtp.client-ip=194.117.254.33 Authentication-Results: smtp.subspace.kernel.org; dmarc=none (p=none dis=none) header.from=sang-engineering.com Authentication-Results: smtp.subspace.kernel.org; spf=pass smtp.mailfrom=sang-engineering.com Authentication-Results: smtp.subspace.kernel.org; dkim=pass (2048-bit key) header.d=sang-engineering.com header.i=@sang-engineering.com header.b="eXsONqg9" DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= sang-engineering.com; h=from:to:cc:subject:date:message-id :in-reply-to:references:mime-version:content-transfer-encoding; s=k1; bh=ixLUA05ywsqk+tUJDK/loDg53P2byoU2nyRRhw8H0ik=; b=eXsONq g9QUb+CQ4DgkaBNkWvnWuLq4yVor1Lzj1BCEgEwTG3emRhyxeucfcKqlgSqCtNiO xoLRx+fnR5kNGfbw2w7Chux/LpyKy7n//O1aLDjC0PpcbVRXqiGPDCjJqTVvfqsH 2kGxG2w4fzcipDOk/h7CjkBw5hLdnIk4Bb4LAc0hP3TkYt1aybBt6A+pa+t+mUiy psNtU3TezTWrRbSUXBTRcCGcQUJaR+Dws0nKmxMtN9pg4QcajMzA4X8SV3nMVpFc OCC2UYmfTU/3BIsMKb6pv5ZE1JnIRYU+NCv0AYLukFgxxJ+15nozUGFDAczI+LiV DfgG7ZsQ02GkiOnw== Received: (qmail 1438195 invoked from network); 14 Jun 2024 10:12:50 +0200 Received: by mail.zeus03.de with ESMTPSA (TLS_AES_256_GCM_SHA384 encrypted, authenticated); 14 Jun 2024 10:12:50 +0200 X-UD-Smtp-Session: l3s3148p1@yE91LtUaJoIgAwDPXzjQABqqX1QYyOSW From: Wolfram Sang To: linux-i2c@vger.kernel.org Cc: Easwar Hariharan , linux-doc@vger.kernel.org, linux-kernel@vger.kernel.org, Andi Shyti , Wolfram Sang Subject: [PATCH v3 4/6] docs: i2c: summary: document use of inclusive language Date: Fri, 14 Jun 2024 10:12:42 +0200 Message-ID: <20240614081239.7128-12-wsa+renesas@sang-engineering.com> X-Mailer: git-send-email 2.43.0 In-Reply-To: <20240614081239.7128-8-wsa+renesas@sang-engineering.com> References: <20240614081239.7128-8-wsa+renesas@sang-engineering.com> Precedence: bulk X-Mailing-List: linux-i2c@vger.kernel.org List-Id: List-Subscribe: List-Unsubscribe: MIME-Version: 1.0 We now have the updated I2C specs and our own Code of Conduct, so we have all we need to switch over to the inclusive terminology. Define them here. Signed-off-by: Wolfram Sang --- Documentation/i2c/i2c_bus.svg | 15 ++++++++------- Documentation/i2c/summary.rst | 23 +++++++++++++++++------ 2 files changed, 25 insertions(+), 13 deletions(-) diff --git a/Documentation/i2c/i2c_bus.svg b/Documentation/i2c/i2c_bus.svg index 3170de976373..45801de4af7d 100644 --- a/Documentation/i2c/i2c_bus.svg +++ b/Documentation/i2c/i2c_bus.svg @@ -1,5 +1,6 @@ + I2CMaster + id="tspan1285">Controller Slave + id="tspan1287">Target Slave + id="tspan1287-6">Target Slave + id="tspan1287-9">Target X-Patchwork-Id: 804338 Received: from mail.zeus03.de (zeus03.de [194.117.254.33]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by smtp.subspace.kernel.org (Postfix) with ESMTPS id B220B186E44 for ; Fri, 14 Jun 2024 08:12:56 +0000 (UTC) Authentication-Results: smtp.subspace.kernel.org; arc=none smtp.client-ip=194.117.254.33 ARC-Seal: i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1718352779; cv=none; b=o9gBhhD40236D3pDYYoQx/6YcREqh/dYwvc6b+575qaOmxVi/Y+776QxDT+1dJDaIaWTvjBkYbqX+K4kAMaJSxq+sJQtML0ETpypBGSfPluPWuurqZJCd63NtbBqtrRTpzx+Fqn2Slg+4HkRErZxwZUHTsA+5DH9brJdaNYYf0w= ARC-Message-Signature: i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1718352779; c=relaxed/simple; bh=rDqQbB8WtLI0sNUuiLmLKSokCC9jWiu+CRLfqoeNG94=; h=From:To:Cc:Subject:Date:Message-ID:In-Reply-To:References: MIME-Version; b=m/jfucCJqX2jOCYHH0ZaPIpOS7e5t5u21F+KMk8U/q/LcP71axuMcUaAmaGlP6VeJ7DFmfYJVX6eodBHL7QIIS/zQZNXTF6+ZqFm2x+D0bKosZF3h6Rfk7HLcp/M6yWzyQINHl0SLtPITdsa7/n2rLiHNG7bKhf4UP7j0C2mXZU= ARC-Authentication-Results: i=1; smtp.subspace.kernel.org; dmarc=none (p=none dis=none) header.from=sang-engineering.com; spf=pass smtp.mailfrom=sang-engineering.com; dkim=pass (2048-bit key) header.d=sang-engineering.com header.i=@sang-engineering.com header.b=ZG+gE0qR; arc=none smtp.client-ip=194.117.254.33 Authentication-Results: smtp.subspace.kernel.org; dmarc=none (p=none dis=none) header.from=sang-engineering.com Authentication-Results: smtp.subspace.kernel.org; spf=pass smtp.mailfrom=sang-engineering.com Authentication-Results: smtp.subspace.kernel.org; dkim=pass (2048-bit key) header.d=sang-engineering.com header.i=@sang-engineering.com header.b="ZG+gE0qR" DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= sang-engineering.com; h=from:to:cc:subject:date:message-id :in-reply-to:references:mime-version:content-transfer-encoding; s=k1; bh=X8SjZrtr7vYauQzzWhyTb2doGzFDtsUQAd4VY9QcFf4=; b=ZG+gE0 qR4/l6m89NxA1cfDH+n/wgF34suN1R0ymF+jCl+Z6PTZbY5Tao7FqTIJy+G09vtO s598J//k8juh2k/SY7MUqEcA+miefoIMtl+yLEx10qNpmR3oy1KdO5zKrJtB504Q telfMoe47npiiefu3Vdx0YIQ2S9szU9HXhcW2R2E2CXyjtupUfnlM4CJuvbivM4G vh+5AIrIuurYeleTf6OtTn/MffD9EnaKfeHY+Hxf9ymwZoldmV6EyPApyzJlf/Ae SSzAZRPY9guvy6lFb00Z6nrSXHfRmS6LYnkXGeboAC4p0StFrV36UwWou3Vjcez8 Ahxif/tHBN8+8Ycg== Received: (qmail 1438207 invoked from network); 14 Jun 2024 10:12:50 +0200 Received: by mail.zeus03.de with ESMTPSA (TLS_AES_256_GCM_SHA384 encrypted, authenticated); 14 Jun 2024 10:12:50 +0200 X-UD-Smtp-Session: l3s3148p1@lN59LtUaKoIgAwDPXzjQABqqX1QYyOSW From: Wolfram Sang To: linux-i2c@vger.kernel.org Cc: Easwar Hariharan , linux-doc@vger.kernel.org, linux-kernel@vger.kernel.org, Andi Shyti , Wolfram Sang Subject: [PATCH v3 5/6] docs: i2c: summary: document 'local' and 'remote' targets Date: Fri, 14 Jun 2024 10:12:43 +0200 Message-ID: <20240614081239.7128-13-wsa+renesas@sang-engineering.com> X-Mailer: git-send-email 2.43.0 In-Reply-To: <20240614081239.7128-8-wsa+renesas@sang-engineering.com> References: <20240614081239.7128-8-wsa+renesas@sang-engineering.com> Precedence: bulk X-Mailing-List: linux-i2c@vger.kernel.org List-Id: List-Subscribe: List-Unsubscribe: MIME-Version: 1.0 Because Linux can be a target as well, add terminology to differentiate between Linux being the target and Linux accessing targets. Signed-off-by: Wolfram Sang --- Documentation/i2c/summary.rst | 13 +++++++++---- 1 file changed, 9 insertions(+), 4 deletions(-) diff --git a/Documentation/i2c/summary.rst b/Documentation/i2c/summary.rst index a6da1032fa06..ff8bda32b9c3 100644 --- a/Documentation/i2c/summary.rst +++ b/Documentation/i2c/summary.rst @@ -49,10 +49,15 @@ whole class of I2C adapters. Each specific adapter driver either depends on an algorithm driver in the ``drivers/i2c/algos/`` subdirectory, or includes its own implementation. -A **target** chip is a node that responds to communications when addressed -by the controller. In Linux it is called a **client**. Client drivers are kept -in a directory specific to the feature they provide, for example -``drivers/media/gpio/`` for GPIO expanders and ``drivers/media/i2c/`` for +A **target** chip is a node that responds to communications when addressed by a +controller. In the Linux kernel implementation it is called a **client**. While +targets are usually separate external chips, Linux can also act as a target +(needs hardware support) and respond to another controller on the bus. This is +then called a **local target**. In contrast, an external chip is called a +**remote target**. + +Target drivers are kept in a directory specific to the feature they provide, +for example ``drivers/gpio/`` for GPIO expanders and ``drivers/media/i2c/`` for video-related chips. For the example configuration in figure, you will need a driver for your