Re: [PATCH v3 5/6] docs: i2c: summary: document 'local' and 'remote' targets

[Andi Shyti]

Hi Wolfram,

...

> -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

I am not a big fan of the use of the word client. It's not used
anywhere in the documentation and it's too generic as a name for
giving it a specific meaning.

I've seen already some confusion amongst reviewers and
maintainers when Easwar sent the patch in drm.

If it depends on me, I would stick to the only controller/target
and render obsolet the use of the word "client" in the i2c
context.

Andi

> +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
> -- 
> 2.43.0
>