Hi Kieran,
On Wed, Jun 6, 2018 at 1:34 AM, Kieran Bingham
<kieran.bingham+renesas@xxxxxxxxxxxxxxxx> wrote:
> Provide device tree binding documentation for the MAX9286 Quad GMSL
> deserialiser.
>
> Signed-off-by: Kieran Bingham <kieran.bingham+renesas@xxxxxxxxxxxxxxxx>
Thanks for your patch!
> --- /dev/null
> +++ b/Documentation/devicetree/bindings/media/i2c/max9286.txt
> @@ -0,0 +1,75 @@
> +* Maxim Integrated MAX9286 GMSL Quad 1.5Gbps GMSL Deserializer
> +
> +Required Properties:
> + - compatible: Shall be "maxim,max9286"
> +
> +The following required properties are defined externally in
> +Documentation/devicetree/bindings/i2c/i2c-mux.txt:
> + - Standard I2C mux properties.
> + - I2C child bus nodes.
> +
> +A maximum of 4 I2C child nodes can be specified on the MAX9286, to
> +correspond with a maximum of 4 input devices.
> +
> +The device node must contain one 'port' child node per device input and output
> +port, in accordance with the video interface bindings defined in
> +Documentation/devicetree/bindings/media/video-interfaces.txt. The port nodes
> +are numbered as follows.
> +
> + Port Type
> + ----------------------
> + 0 sink
> + 1 sink
> + 2 sink
> + 3 sink
> + 4 source
I assume the source and at least one sink are thus mandatory?
Would it make sense to use port 0 for the source?
This would simplify extending the binding to devices with more input
ports later.
Gr{oetje,eeting}s,
Geert
--
Geert Uytterhoeven -- There's lots of Linux beyond ia32 -- geert@xxxxxxxxxxxxxx
In personal conversations with technical people, I call myself a hacker. But
when I'm talking to journalists I just say "programmer" or something like that.
-- Linus Torvalds
