Re: [PATCH v10 5/8] dt-bindings: media: add TI DS90UB960 FPD-Link III Deserializer
From: Luca Ceresoli
Date: Wed Apr 19 2023 - 03:13:50 EST
Hi Wolfram, Tomi,
On Tue, 18 Apr 2023 15:06:10 +0200
Wolfram Sang <wsa@xxxxxxxxxx> wrote:
> > + 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?
I think that this _was_ the plan, as it looks obviously cleaner, but
then we agreed that we should remove the pool entirely, so I didn't
bother moving it.
Best regards,
Luca
--
Luca Ceresoli, Bootlin
Embedded Linux and Kernel engineering
https://bootlin.com