On Sat, Jan 01, 2022 at 08:27:57PM +0200, Laurent Pinchart wrote: > The I2C speed on the remote side (the I2C master bus of the connected > serializers) is configurable, and doesn't need to match the speed of the > local bus (the slave bus of the MAX9286). All remote buses must use the > same speed, and the MAX9286 needs to be programmed accordingly. Add a > new DT property to select the speed to make it configurable. > > Signed-off-by: Laurent Pinchart <laurent.pinchart+renesas@xxxxxxxxxxxxxxxx> > --- > .../devicetree/bindings/media/i2c/maxim,max9286.yaml | 7 +++++++ > 1 file changed, 7 insertions(+) > > diff --git a/Documentation/devicetree/bindings/media/i2c/maxim,max9286.yaml b/Documentation/devicetree/bindings/media/i2c/maxim,max9286.yaml > index c20557b52e45..5d3e99027a79 100644 > --- a/Documentation/devicetree/bindings/media/i2c/maxim,max9286.yaml > +++ b/Documentation/devicetree/bindings/media/i2c/maxim,max9286.yaml > @@ -50,6 +50,13 @@ properties: > '#gpio-cells': > const: 2 > > + maxim,i2c-clock-frequency: Use '-hz'. I don't see much reason to align with 'clock-frequency'. Actually, I'd make this 'maxim,i2c-remote-bus-hz' or similar to be a bit more self-describing. > + enum: [ 8470, 28300, 84700, 105000, 173000, 339000, 533000, 837000 ] > + default: 105000 > + description: | > + The I2C clock frequency for the remote I2C buses. The value must match > + the configuration of the remote serializers. > + > maxim,reverse-channel-microvolt: > minimum: 30000 > maximum: 200000 > -- > Regards, > > Laurent Pinchart > >
