Re: [PATCH v10 5/8] dt-bindings: media: add TI DS90UB960 FPD-Link III Deserializer

Wolfram Sang
2023-04-18T13:06:37Z

[-- Attachment #1: Type: text/plain, Size: 1023 bytes --]

> + i2c-alias-pool:
> + $ref: /schemas/types.yaml#/definitions/uint16-array
> + description:
> + I2C alias pool is a pool of I2C addresses on the main I2C bus that can be
> + used to access the remote peripherals on the serializer's I2C bus. The
> + addresses must be available, not used by any other peripheral. Each
> + remote peripheral is assigned an alias from the pool, and transactions to
> + that address will be forwarded to the remote peripheral, with the address
> + translated to the remote peripheral's real address. This property is not
> + needed if there are no I2C addressable remote peripherals.

After some initial discussion with Tomi on IRC, this question is
probably more for Luca:

Why is "i2c-alias-pool" in the drivers binding and not a regular i2c
binding? Same question for the implementation of the alias-pool
handling. Shouldn't this be in the i2c-atr library? I'd think managing
the list of aliases would look all the same in the drivers otherwise?

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]