MAX96712 and MAX96724 have more than one GMSL2 link, and each link is
capable of connecting to a separate serializer. If these serializers
have the same CFG pins configuration, they will also have the same I2C
address, causing conflicts unless the deserializer muxes the I2C
channels. Moreover, the serializers can have the same hardware attached
to their respective I2C bus.
The MAX96712 and MAX96724 suppot I2C channel muxing via the GMSL2 link
to facilitate communication to each of the connected serializers.
Document this capability.
Signed-off-by: Cosmin Tanislav <demonsingur@xxxxxxxxx>
---
.../bindings/media/i2c/maxim,max96712.yaml | 13 +++++++++++++
1 file changed, 13 insertions(+)
diff --git a/Documentation/devicetree/bindings/media/i2c/maxim,max96712.yaml b/Documentation/devicetree/bindings/media/i2c/maxim,max96712.yaml
index bf8c861c836b..9e27568e0105 100644
--- a/Documentation/devicetree/bindings/media/i2c/maxim,max96712.yaml
+++ b/Documentation/devicetree/bindings/media/i2c/maxim,max96712.yaml
@@ -37,6 +37,19 @@ properties:
enable-gpios: true
+ i2c-mux:
+ $ref: /schemas/i2c/i2c-mux.yaml#
+ unevaluatedProperties: false
+ patternProperties:
+ '^i2c@[0-3]$':
+ $ref: /schemas/i2c/i2c-controller.yaml#
+ unevaluatedProperties: false
+ properties:
+ reg:
+ items:
+ minimum: 0
+ maximum: 3
+
ports:
$ref: /schemas/graph.yaml#/properties/ports
--
2.48.1
