Linux Media Controller development
 help / color / mirror / Atom feed
From: Kieran Bingham <kieran.bingham@ideasonboard.com>
To: Rob Herring <robh@kernel.org>,
	Kieran Bingham <kieran.bingham+renesas@ideasonboard.com>
Cc: linux-renesas-soc@vger.kernel.org, linux-media@vger.kernel.org,
	devicetree@vger.kernel.org, linux-kernel@vger.kernel.org,
	"Mauro Carvalho Chehab" <mchehab@kernel.org>,
	"Kieran Bingham" <kieran.bingham@ideasonboard.com>,
	"Laurent Pinchart" <laurent.pinchart@ideasonboard.com>,
	"Jacopo Mondi" <jacopo@jmondi.org>,
	"Niklas Söderlund" <niklas.soderlund@ragnatech.se>,
	"Mark Rutland" <mark.rutland@arm.com>,
	sakari.ailus@iki.fi, "Hans Verkuil" <hverkuil@xs4all.nl>,
	"Laurent Pinchart" <laurent.pinchart+renesas@ideasonboard.com>,
	"Jacopo Mondi" <jacopo+renesas@jmondi.org>,
	"Niklas Söderlund" <niklas.soderlund+renesas@ragnatech.se>
Subject: Re: [PATCH v6 1/2] dt-bindings: media: i2c: Add bindings for Maxim Integrated MAX9286
Date: Thu, 19 Dec 2019 11:46:31 +0000	[thread overview]
Message-ID: <86bbf27f-dc0c-0661-13b8-e96b28ec7529@ideasonboard.com> (raw)
In-Reply-To: <20191218181352.GA6385@bogus>

Thanks Rob,

On 18/12/2019 18:13, Rob Herring wrote:
> On Wed, Dec 11, 2019 at 12:44:58PM +0000, Kieran Bingham wrote:
>> From: Laurent Pinchart <laurent.pinchart+renesas@ideasonboard.com>
>>
>> The MAX9286 deserializes video data received on up to 4 Gigabit
>> Multimedia Serial Links (GMSL) and outputs them on a CSI-2 port using up
>> to 4 data lanes.
>>
>> Signed-off-by: Laurent Pinchart <laurent.pinchart+renesas@ideasonboard.com>
>> Signed-off-by: Jacopo Mondi <jacopo+renesas@jmondi.org>
>> Signed-off-by: Kieran Bingham <kieran.bingham+renesas@ideasonboard.com>
>> Reviewed-by: Niklas Söderlund <niklas.soderlund+renesas@ragnatech.se>
>> Signed-off-by: Niklas Söderlund <niklas.soderlund+renesas@ragnatech.se>
>> ---
>>  .../bindings/media/i2c/maxim,max9286.yaml     | 289 ++++++++++++++++++
>>  1 file changed, 289 insertions(+)
>>  create mode 100644 Documentation/devicetree/bindings/media/i2c/maxim,max9286.yaml
> 
> A couple of nits, with those fixed:

I'll fix them up :-D
Thank you very much.

Converting this to YAML picked up a few issues in our DTS - so it
certainly seems very worthwhile!

--
Kieran


> Reviewed-by: Rob Herring <robh@kernel.org>
> 
>>
>> diff --git a/Documentation/devicetree/bindings/media/i2c/maxim,max9286.yaml b/Documentation/devicetree/bindings/media/i2c/maxim,max9286.yaml
>> new file mode 100644
>> index 000000000000..d37ea2c432f6
>> --- /dev/null
>> +++ b/Documentation/devicetree/bindings/media/i2c/maxim,max9286.yaml
>> @@ -0,0 +1,289 @@
>> +# SPDX-License-Identifier: GPL-2.0-only
> 
> Dual license new bindings please:
> 
> (GPL-2.0-only OR BSD-2-Clause)

That's two of those I've got to fix up for you :D. I'll make sure all
new ones I add have this correctly presented.


>> +# Copyright (C) 2019 Renesas Electronics Corp.
>> +%YAML 1.2
>> +---
>> +$id: http://devicetree.org/schemas/media/i2c/maxim,max9286.yaml#
>> +$schema: http://devicetree.org/meta-schemas/core.yaml#
>> +
>> +title: Maxim Integrated Quad GMSL Deserializer
>> +
>> +maintainers:
>> +  - Jacopo Mondi <jacopo+renesas@jmondi.org>
>> +  - Kieran Bingham <kieran.bingham+renesas@ideasonboard.com>
>> +  - Laurent Pinchart <laurent.pinchart+renesas@ideasonboard.com>
>> +  - Niklas Söderlund <niklas.soderlund+renesas@ragnatech.se>
>> +
>> +description: -|
> 
> I usually see '|-', but I guess that works.

Oh, I'm happy to change to conform to whatever is the accepted norm...

> 
>> +  The MAX9286 deserializer receives video data on up to 4 Gigabit Multimedia
>> +  Serial Links (GMSL) and outputs them on a CSI-2 D-PHY port using up to 4 data
>> +  lanes.
>> +
>> +  In addition to video data, the GMSL links carry a bidirectional control
>> +  channel that encapsulates I2C messages. The MAX9286 forwards all I2C traffic
>> +  not addressed to itself to the other side of the links, where a GMSL
>> +  serializer will output it on a local I2C bus. In the other direction all I2C
>> +  traffic received over GMSL by the MAX9286 is output on the local I2C bus.
>> +
>> +properties:
>> +  '#address-cells':
>> +    const: 1
>> +
>> +  '#size-cells':
>> +    const: 0
>> +
>> +  compatible:
>> +    const: maxim,max9286
>> +
>> +  reg:
>> +    description: I2C device address
>> +    maxItems: 1
>> +
>> +  poc-supply:
>> +    description: Regulator providing Power over Coax to the cameras
>> +    maxItems: 1
>> +
>> +  enable-gpios:
>> +    description: GPIO connected to the \#PWDN pin with inverted polarity
>> +    maxItems: 1
>> +
>> +  ports:
>> +    type: object
>> +    description: -|
>> +      The connections to the MAX9286 GMSL and its endpoint nodes are modelled
>> +      using the OF graph bindings in accordance with the video interface
>> +      bindings defined in
>> +      Documentation/devicetree/bindings/media/video-interfaces.txt.
>> +
>> +      The following table lists the port number corresponding to each device
>> +      port.
>> +
>> +        Port            Description
>> +        ----------------------------------------
>> +        Port 0          GMSL Input 0
>> +        Port 1          GMSL Input 1
>> +        Port 2          GMSL Input 2
>> +        Port 3          GMSL Input 3
>> +        Port 4          CSI-2 Output
>> +
>> +    properties:
>> +      '#address-cells':
>> +        const: 1
>> +
>> +      '#size-cells':
>> +        const: 0
>> +
>> +      port@[0-3]:
>> +        type: object
>> +        properties:
>> +          reg:
>> +            enum: [ 0, 1, 2, 3 ]
>> +
>> +          endpoint:
>> +            type: object
>> +
>> +            properties:
>> +              remote-endpoint:
>> +                description: -|
>> +                 phandle to the remote GMSL source endpoint subnode in the
>> +                 remote node port.
>> +                maxItems: 1
> 
> This is not an array. You can just drop and assume it has a type defined 
> elsewhere.
> 

Will fix and validate.

>> +
>> +            required:
>> +              - remote-endpoint
>> +
>> +        required:
>> +          - reg
>> +          - endpoint
>> +
>> +        additionalProperties: false
>> +
>> +      port@4:
>> +        type: object
>> +        properties:
>> +          reg:
>> +            const: 4
>> +
>> +          endpoint:
>> +            type: object
>> +
>> +            properties:
>> +              remote-endpoint:
>> +                description: phandle to the remote CSI-2 sink endpoint.
>> +                maxItems: 1
> 
> And here.

Likewise.

> 
>> +
>> +              data-lanes:
>> +                description: array of physical CSI-2 data lane indexes.
>> +
>> +            required:
>> +              - remote-endpoint
>> +              - data-lanes
>> +
>> +        required:
>> +          - reg
>> +          - endpoint
>> +
>> +        additionalProperties: false
>> +
>> +    required:
>> +      - port@4
>> +
>> +  i2c-mux:
>> +    type: object
>> +    description: -|
>> +      Each GMSL link is modelled as a child bus of an i2c bus
>> +      multiplexer/switch, in accordance with bindings described in
>> +      Documentation/devicetree/bindings/i2c/i2c-mux.txt. The serializer
>> +      device on the remote end of the GMSL link shall be modelled as a child
>> +      node of the corresponding I2C bus.
>> +
>> +    properties:
>> +      '#address-cells':
>> +        const: 1
>> +
>> +      '#size-cells':
>> +        const: 0
>> +
>> +  additionalProperties: false
>> +
>> +required:
>> +  - compatible
>> +  - reg
>> +  - ports
>> +  - i2c-mux
>> +
>> +additionalProperties: false
>> +
>> +examples:
>> +  - |
>> +    #include <dt-bindings/gpio/gpio.h>
>> +
>> +    i2c@e66d8000 {
>> +      #address-cells = <1>;
>> +      #size-cells = <0>;
>> +
>> +      reg = <0 0xe66d8000 0 0x40>;
>> +
>> +      gmsl-deserializer@2c {
>> +        compatible = "maxim,max9286";
>> +        reg = <0x2c>;
>> +        poc-supply = <&camera_poc_12v>;
>> +        enable-gpios = <&gpio 13 GPIO_ACTIVE_HIGH>;
>> +
>> +        ports {
>> +          #address-cells = <1>;
>> +          #size-cells = <0>;
>> +
>> +          port@0 {
>> +            reg = <0>;
>> +
>> +            max9286_in0: endpoint {
>> +              remote-endpoint = <&rdacm20_out0>;
>> +            };
>> +          };
>> +
>> +          port@1 {
>> +            reg = <1>;
>> +
>> +            max9286_in1: endpoint {
>> +              remote-endpoint = <&rdacm20_out1>;
>> +            };
>> +          };
>> +
>> +          port@2 {
>> +            reg = <2>;
>> +
>> +            max9286_in2: endpoint {
>> +              remote-endpoint = <&rdacm20_out2>;
>> +            };
>> +          };
>> +
>> +          port@3 {
>> +            reg = <3>;
>> +
>> +            max9286_in3: endpoint {
>> +              remote-endpoint = <&rdacm20_out3>;
>> +            };
>> +          };
>> +
>> +          port@4 {
>> +            reg = <4>;
>> +
>> +            max9286_out: endpoint {
>> +              data-lanes = <1 2 3 4>;
>> +              remote-endpoint = <&csi40_in>;
>> +            };
>> +          };
>> +        };
>> +
>> +        i2c-mux {
>> +          #address-cells = <1>;
>> +          #size-cells = <0>;
>> +
>> +          i2c@0 {
>> +            #address-cells = <1>;
>> +            #size-cells = <0>;
>> +
>> +            reg = <0>;
>> +
>> +            camera@51 {
>> +              reg = <0x51>;
>> +
>> +              port {
>> +                rdacm20_out0: endpoint {
>> +                  remote-endpoint = <&max9286_in0>;
>> +                };
>> +              };
>> +
>> +            };
>> +          };
>> +
>> +          i2c@1 {
>> +            #address-cells = <1>;
>> +            #size-cells = <0>;
>> +            reg = <1>;
>> +
>> +            camera@52 {
>> +              reg = <0x52>;
>> +
>> +              port {
>> +                rdacm20_out1: endpoint {
>> +                  remote-endpoint = <&max9286_in1>;
>> +                };
>> +              };
>> +            };
>> +          };
>> +
>> +          i2c@2 {
>> +            #address-cells = <1>;
>> +            #size-cells = <0>;
>> +            reg = <2>;
>> +
>> +            camera@53 {
>> +              reg = <0x53>;
>> +
>> +              port {
>> +                rdacm20_out2: endpoint {
>> +                  remote-endpoint = <&max9286_in2>;
>> +                };
>> +              };
>> +            };
>> +          };
>> +
>> +          i2c@3 {
>> +            #address-cells = <1>;
>> +            #size-cells = <0>;
>> +            reg = <3>;
>> +
>> +            camera@54 {
>> +              reg = <0x54>;
>> +
>> +              port {
>> +                rdacm20_out3: endpoint {
>> +                  remote-endpoint = <&max9286_in3>;
>> +                };
>> +              };
>> +            };
>> +          };
>> +        };
>> +      };
>> +    };
>> -- 
>> 2.20.1
>>


-- 
Regards
--
Kieran

  reply	other threads:[~2019-12-19 11:46 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-12-11 12:44 [PATCH v6 0/2] MAX9286 GMSL Support Kieran Bingham
2019-12-11 12:44 ` [PATCH v6 1/2] dt-bindings: media: i2c: Add bindings for Maxim Integrated MAX9286 Kieran Bingham
2019-12-18 18:13   ` Rob Herring
2019-12-19 11:46     ` Kieran Bingham [this message]
2019-12-11 12:44 ` [PATCH v6 2/2] media: i2c: Add MAX9286 driver Kieran Bingham

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=86bbf27f-dc0c-0661-13b8-e96b28ec7529@ideasonboard.com \
    --to=kieran.bingham@ideasonboard.com \
    --cc=devicetree@vger.kernel.org \
    --cc=hverkuil@xs4all.nl \
    --cc=jacopo+renesas@jmondi.org \
    --cc=jacopo@jmondi.org \
    --cc=kieran.bingham+renesas@ideasonboard.com \
    --cc=laurent.pinchart+renesas@ideasonboard.com \
    --cc=laurent.pinchart@ideasonboard.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-media@vger.kernel.org \
    --cc=linux-renesas-soc@vger.kernel.org \
    --cc=mark.rutland@arm.com \
    --cc=mchehab@kernel.org \
    --cc=niklas.soderlund+renesas@ragnatech.se \
    --cc=niklas.soderlund@ragnatech.se \
    --cc=robh@kernel.org \
    --cc=sakari.ailus@iki.fi \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox