devicetree.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Tomi Valkeinen <tomi.valkeinen@ideasonboard.com>
To: Laurent Pinchart <laurent.pinchart@ideasonboard.com>
Cc: linux-media@vger.kernel.org, devicetree@vger.kernel.org,
	linux-kernel@vger.kernel.org, linux-i2c@vger.kernel.org,
	"Rob Herring" <robh+dt@kernel.org>,
	"Krzysztof Kozlowski" <krzysztof.kozlowski+dt@linaro.org>,
	"Wolfram Sang" <wsa@kernel.org>,
	"Luca Ceresoli" <luca.ceresoli@bootlin.com>,
	"Andy Shevchenko" <andriy.shevchenko@intel.com>,
	"Matti Vaittinen" <Matti.Vaittinen@fi.rohmeurope.com>,
	"Mauro Carvalho Chehab" <mchehab@kernel.org>,
	"Peter Rosin" <peda@axentia.se>,
	"Liam Girdwood" <lgirdwood@gmail.com>,
	"Mark Brown" <broonie@kernel.org>,
	"Sakari Ailus" <sakari.ailus@linux.intel.com>,
	"Michael Tretter" <m.tretter@pengutronix.de>,
	"Shawn Tu" <shawnx.tu@intel.com>,
	"Hans Verkuil" <hverkuil@xs4all.nl>,
	"Mike Pagano" <mpagano@gentoo.org>,
	"Krzysztof Hałasa" <khalasa@piap.pl>,
	"Marek Vasut" <marex@denx.de>
Subject: Re: [PATCH v5 4/8] dt-bindings: media: add bindings for TI DS90UB953
Date: Tue, 13 Dec 2022 16:06:11 +0200	[thread overview]
Message-ID: <c22ff1c6-704f-affc-93a7-e2080c58c53d@ideasonboard.com> (raw)
In-Reply-To: <Y5YUoEWmHsUT8zgf@pendragon.ideasonboard.com>

On 11/12/2022 19:34, Laurent Pinchart wrote:
> Hi Tomi,
> 
> Thank you for the patch.
> 
> On Thu, Dec 08, 2022 at 12:40:02PM +0200, Tomi Valkeinen wrote:
>> Add DT bindings for TI DS90UB953 FPDLink-3 Serializer.
>>
>> Signed-off-by: Tomi Valkeinen <tomi.valkeinen@ideasonboard.com>
>> ---
>>   .../bindings/media/i2c/ti,ds90ub953.yaml      | 112 ++++++++++++++++++
>>   1 file changed, 112 insertions(+)
>>   create mode 100644 Documentation/devicetree/bindings/media/i2c/ti,ds90ub953.yaml
>>
>> diff --git a/Documentation/devicetree/bindings/media/i2c/ti,ds90ub953.yaml b/Documentation/devicetree/bindings/media/i2c/ti,ds90ub953.yaml
>> new file mode 100644
>> index 000000000000..fd7d25d93e2c
>> --- /dev/null
>> +++ b/Documentation/devicetree/bindings/media/i2c/ti,ds90ub953.yaml
>> @@ -0,0 +1,112 @@
>> +# SPDX-License-Identifier: (GPL-2.0-only OR BSD-2-Clause)
>> +%YAML 1.2
>> +---
>> +$id: http://devicetree.org/schemas/media/i2c/ti,ds90ub953.yaml#
>> +$schema: http://devicetree.org/meta-schemas/core.yaml#
>> +
>> +title: Texas Instruments DS90UB953 FPD-Link 3 Serializer
>> +
>> +maintainers:
>> +  - Tomi Valkeinen <tomi.valkeinen@ideasonboard.com>
>> +
>> +description:
>> +  The TI DS90UB953 is an FPD-Link 3 video serializer for MIPI CSI-2.
>> +
>> +properties:
>> +  compatible:
>> +    enum:
>> +      - ti,ds90ub953-q1
>> +      - ti,ds90ub971-q1
>> +
>> +  '#gpio-cells':
>> +    const: 2
> 
> I would add a description here, to tell what the cells correspond to. In
> particular, the first cell selects the GPIO_* pin number, it would be
> nice to document that its value should be in the range [0, 3].
> 
> Same comment for patch 3/8 (DS90UB913 bindings). There you could also
> mention that GPO2 and the output clock are mutually exclusive.

Yep. I have added this for ub913:
       First cell is the GPO pin number, second cell is the flags. The 
GPO pin
       number must be in range of [0, 3]. Note that GPOs 2 and 3 are not
       available in external oscillator mode.

and this for ub953:
       First cell is the GPIO pin number, second cell is the flags. The 
GPIO pin
       number must be in range of [0, 3].

>> +
>> +  gpio-controller: true
>> +
> 
> No need for clocks and clock-names for the reference input clock ? Or is
> this because you support sync mode only for now ?

Right, I don't have the clock on my hw, but it's probably better to add 
it to the binding already.

>> +  '#clock-cells':
>> +    const: 0
>> +
>> +  ports:
>> +    $ref: /schemas/graph.yaml#/properties/ports
>> +
>> +    properties:
>> +      port@0:
>> +        $ref: /schemas/graph.yaml#/$defs/port-base
>> +        unevaluatedProperties: false
>> +        description: CSI-2 input port
>> +
>> +        properties:
>> +          endpoint:
>> +            $ref: /schemas/media/video-interfaces.yaml#
>> +            unevaluatedProperties: false
> 
> Should the data-lanes property be required for the CSI-2 input ?

Yes.

>> +
>> +      port@1:
>> +        $ref: /schemas/graph.yaml#/properties/port
>> +        unevaluatedProperties: false
>> +        description: FPD-Link 3 output port
>> +
>> +  i2c:
>> +    $ref: /schemas/i2c/i2c-controller.yaml#
>> +    unevaluatedProperties: false
>> +
>> +required:
>> +  - compatible
>> +  - '#gpio-cells'
>> +  - gpio-controller
>> +  - '#clock-cells'
>> +  - ports
>> +
>> +additionalProperties: false
>> +
>> +examples:
>> +  - |
>> +    #include <dt-bindings/gpio/gpio.h>
>> +
>> +    serializer {
>> +      compatible = "ti,ds90ub953-q1";
>> +
>> +      gpio-controller;
>> +      #gpio-cells = <2>;
>> +
>> +      #clock-cells = <0>;
>> +
>> +      ports {
>> +        #address-cells = <1>;
>> +        #size-cells = <0>;
>> +
>> +        port@0 {
>> +          reg = <0>;
>> +          ub953_in: endpoint {
>> +            clock-lanes = <0>;
>> +            data-lanes = <1 2 3 4>;
>> +            remote-endpoint = <&sensor_out>;
>> +          };
>> +        };
>> +
>> +        port@1 {
>> +          reg = <1>;
>> +          endpoint {
>> +            remote-endpoint = <&deser_fpd_in>;
>> +          };
>> +        };
>> +      };
>> +
>> +      i2c {
>> +        #address-cells = <1>;
>> +        #size-cells = <0>;
>> +
>> +        sensor@1a {
>> +          compatible = "sony,imx274";
>> +          reg = <0x1a>;
>> +
>> +          reset-gpios = <&serializer 0 GPIO_ACTIVE_LOW>;
> 
> Maybe add
> 
>            clocks = <&serializer>;
> 	  clock-names = "inck";
> 
> to showcase the clock connection ?

Yes, that's a good idea.

  Tomi


  reply	other threads:[~2022-12-13 14:06 UTC|newest]

Thread overview: 57+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-12-08 10:39 [PATCH v5 0/8] i2c-atr and FPDLink Tomi Valkeinen
2022-12-08 10:39 ` [PATCH v5 1/8] i2c: core: let adapters be notified of client attach/detach Tomi Valkeinen
2022-12-08 12:30   ` Andy Shevchenko
2022-12-08 16:10     ` Tomi Valkeinen
2022-12-11 16:55   ` Laurent Pinchart
2022-12-19  8:51     ` Luca Ceresoli
2022-12-19  9:48       ` Andy Shevchenko
2022-12-26 16:54         ` Laurent Pinchart
2022-12-27 20:07           ` Andy Shevchenko
2022-12-08 10:40 ` [PATCH v5 2/8] i2c: add I2C Address Translator (ATR) support Tomi Valkeinen
2022-12-08 12:53   ` Andy Shevchenko
2022-12-08 16:01     ` Tomi Valkeinen
2022-12-08 18:09       ` Andy Shevchenko
2022-12-08 10:40 ` [PATCH v5 3/8] dt-bindings: media: add bindings for TI DS90UB913 Tomi Valkeinen
2022-12-11 17:13   ` Laurent Pinchart
2022-12-11 17:21     ` Laurent Pinchart
2022-12-13 13:36       ` Tomi Valkeinen
2022-12-26 16:46         ` Laurent Pinchart
2023-01-04  8:12           ` Tomi Valkeinen
2023-01-04 12:52             ` Laurent Pinchart
2022-12-13 13:21     ` Tomi Valkeinen
2022-12-08 10:40 ` [PATCH v5 4/8] dt-bindings: media: add bindings for TI DS90UB953 Tomi Valkeinen
2022-12-09 21:27   ` Rob Herring
2023-01-04  8:26     ` Tomi Valkeinen
2022-12-11 17:34   ` Laurent Pinchart
2022-12-13 14:06     ` Tomi Valkeinen [this message]
2022-12-08 10:40 ` [PATCH v5 5/8] dt-bindings: media: add bindings for TI DS90UB960 Tomi Valkeinen
2022-12-09 21:30   ` Rob Herring
2022-12-11 17:58   ` Laurent Pinchart
2022-12-13 14:25     ` Tomi Valkeinen
2022-12-26 16:52       ` Laurent Pinchart
2023-01-04  8:59         ` Tomi Valkeinen
2023-01-04 12:57           ` Laurent Pinchart
2023-01-04 14:05             ` Tomi Valkeinen
2023-01-05  6:54               ` Laurent Pinchart
2022-12-08 10:40 ` [PATCH v5 6/8] media: i2c: add DS90UB960 driver Tomi Valkeinen
2022-12-08 10:40 ` [PATCH v5 7/8] media: i2c: add DS90UB913 driver Tomi Valkeinen
2022-12-11 18:33   ` Laurent Pinchart
2022-12-14  6:29     ` Tomi Valkeinen
2022-12-14  6:36       ` Tomi Valkeinen
2022-12-26 16:56         ` Laurent Pinchart
2022-12-26 19:25           ` Tomi Valkeinen
2023-01-04 13:55             ` Laurent Pinchart
2023-01-04 14:13               ` Tomi Valkeinen
2023-01-04 15:32                 ` Laurent Pinchart
2023-01-04 15:43                   ` Tomi Valkeinen
2022-12-26 17:01       ` Laurent Pinchart
2022-12-27 20:09         ` Andy Shevchenko
2023-01-04 13:29           ` Laurent Pinchart
2022-12-14  6:48     ` Tomi Valkeinen
2022-12-08 10:40 ` [PATCH v5 8/8] media: i2c: add DS90UB953 driver Tomi Valkeinen
2022-12-08 10:42 ` [PATCH v5 0/8] i2c-atr and FPDLink Tomi Valkeinen
2022-12-08 12:26   ` Andy Shevchenko
2022-12-08 14:40     ` Tomi Valkeinen
2022-12-08 15:57       ` Andy Shevchenko
2022-12-08 15:58         ` Andy Shevchenko
2022-12-08 16:05           ` Tomi Valkeinen

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=c22ff1c6-704f-affc-93a7-e2080c58c53d@ideasonboard.com \
    --to=tomi.valkeinen@ideasonboard.com \
    --cc=Matti.Vaittinen@fi.rohmeurope.com \
    --cc=andriy.shevchenko@intel.com \
    --cc=broonie@kernel.org \
    --cc=devicetree@vger.kernel.org \
    --cc=hverkuil@xs4all.nl \
    --cc=khalasa@piap.pl \
    --cc=krzysztof.kozlowski+dt@linaro.org \
    --cc=laurent.pinchart@ideasonboard.com \
    --cc=lgirdwood@gmail.com \
    --cc=linux-i2c@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-media@vger.kernel.org \
    --cc=luca.ceresoli@bootlin.com \
    --cc=m.tretter@pengutronix.de \
    --cc=marex@denx.de \
    --cc=mchehab@kernel.org \
    --cc=mpagano@gentoo.org \
    --cc=peda@axentia.se \
    --cc=robh+dt@kernel.org \
    --cc=sakari.ailus@linux.intel.com \
    --cc=shawnx.tu@intel.com \
    --cc=wsa@kernel.org \
    /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;
as well as URLs for NNTP newsgroup(s).