Hi Jacopo,
Thanks - this looks good to me, and fixes the validation.
Reviewed-by: Kieran Bingham <kieran.bingham+renesas@xxxxxxxxxxxxxxxx>
Thanks, will integrate into the current patches.
On 10/06/2020 15:44, Jacopo Mondi wrote:
> ---
> .../devicetree/bindings/media/i2c/maxim,max9286.yaml | 10 ++++++----
> 1 file changed, 6 insertions(+), 4 deletions(-)
>
> diff --git a/Documentation/devicetree/bindings/media/i2c/maxim,max9286.yaml b/Documentation/devicetree/bindings/media/i2c/maxim,max9286.yaml
> index 34e0431d0bc1..8307c41f2cae 100644
> --- a/Documentation/devicetree/bindings/media/i2c/maxim,max9286.yaml
> +++ b/Documentation/devicetree/bindings/media/i2c/maxim,max9286.yaml
> @@ -176,6 +176,8 @@ properties:
> description: The remote device compatible string.
>
> reg:
> + minItems: 2
> + maxItems: 3
> description: |
> The I2C addresses to be assigned to the remote devices through
> address reprogramming. The number of entries depends on the
> @@ -294,7 +296,7 @@ examples:
>
> camera@51 {
> compatible = "imi,rdacm20";
> - reg = <0x51 0x61>;
> + reg = <0x51>, <0x61>;
>
> port {
> rdacm20_out0: endpoint {
> @@ -312,7 +314,7 @@ examples:
>
> camera@52 {
> compatible = "imi,rdacm20";
> - reg = <0x52 0x62>;
> + reg = <0x52>, <0x62>;
>
> port {
> rdacm20_out1: endpoint {
> @@ -329,7 +331,7 @@ examples:
>
> camera@53 {
> compatible = "imi,rdacm20";
> - reg = <0x53 0x63>;
> + reg = <0x53>, <0x63>;
>
> port {
> rdacm20_out2: endpoint {
> @@ -346,7 +348,7 @@ examples:
>
> camera@54 {
> compatible = "imi,rdacm20";
> - reg = <0x54 0x64>;
> + reg = <0x54>, <0x64>;
>
> port {
> rdacm20_out3: endpoint {
> --
> 2.27.0
>
