diff options
| author | Wolfram Sang <wsa+renesas@sang-engineering.com> | 2024-06-21 09:30:12 +0200 |
|---|---|---|
| committer | Wolfram Sang <wsa+renesas@sang-engineering.com> | 2024-06-22 10:11:53 +0200 |
| commit | 1e926ea19003680c423cdc3c7174b046fd462a35 (patch) | |
| tree | 1de86d9892b98ba69973b4b19208847766e1a080 /Documentation/i2c | |
| parent | d77367fff7c0d67e20393a8236b519d5c48ee875 (diff) | |
| download | linux-stable-1e926ea19003680c423cdc3c7174b046fd462a35.tar.gz linux-stable-1e926ea19003680c423cdc3c7174b046fd462a35.tar.bz2 linux-stable-1e926ea19003680c423cdc3c7174b046fd462a35.zip | |
docs: i2c: summary: document 'local' and 'remote' targets
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 <wsa+renesas@sang-engineering.com>
Reviewed-by: Easwar Hariharan <eahariha@linux.microsoft.com>
Signed-off-by: Wolfram Sang <wsa+renesas@sang-engineering.com>
Diffstat (limited to 'Documentation/i2c')
| -rw-r--r-- | Documentation/i2c/summary.rst | 13 |
1 files 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 |