All of lore.kernel.org
 help / color / mirror / Atom feed
From: Rob Herring <robh@kernel.org>
To: Enric Balletbo i Serra <enric.balletbo@collabora.com>
Cc: "Ricardo Cañuelo" <ricardo.canuelo@collabora.com>,
	devicetree@vger.kernel.org, kernel@collabora.com,
	dri-devel@lists.freedesktop.org
Subject: Re: [PATCH v3] dt-bindings: display: anx7814.txt: convert to yaml
Date: Mon, 11 May 2020 18:15:54 -0500	[thread overview]
Message-ID: <20200511231554.GA12152@bogus> (raw)
In-Reply-To: <676aaa45-b4cb-104e-de37-2508f0ab634d@collabora.com>

On Mon, Apr 27, 2020 at 03:52:44PM +0200, Enric Balletbo i Serra wrote:
> Hi Ricardo,
> 
> Thank you for your patch.
> 
> On 27/4/20 12:09, Ricardo Cañuelo wrote:
> > This converts the Analogix ANX7814 bridge DT binding to yaml. Port
> > definitions and descriptions were expanded, apart from that it's a
> > direct translation from the original binding.
> > 
> > Signed-off-by: Ricardo Cañuelo <ricardo.canuelo@collabora.com>
> > Acked-by: Sam Ravnborg <sam@ravnborg.org>
> > ---
> > Changes in v3 (suggested by Sam Ravnborg):
> >   - Rename example node i2c0 to i2c.
> > 
> > Changes in v2 (suggested by Enric Balletbo):
> >   - File name change: use full compatible string.
> >   - Binding description removed.
> >   - #address-cells and #size-cells properties removed from ports node.
> >   - Example node renamed: anx7814 -> bridge.
> > 
> > Tested with:
> > make dt_binding_check ARCH=arm64 DT_SCHEMA_FILES=<.../analogix,anx7814.yaml>
> > make dtbs_check ARCH=arm64 DT_SCHEMA_FILES=<.../analogix,anx7814.yaml>
> > 
> >  .../display/bridge/analogix,anx7814.yaml      | 124 ++++++++++++++++++
> >  .../bindings/display/bridge/anx7814.txt       |  42 ------
> >  2 files changed, 124 insertions(+), 42 deletions(-)
> >  create mode 100644 Documentation/devicetree/bindings/display/bridge/analogix,anx7814.yaml
> >  delete mode 100644 Documentation/devicetree/bindings/display/bridge/anx7814.txt
> > 
> > diff --git a/Documentation/devicetree/bindings/display/bridge/analogix,anx7814.yaml b/Documentation/devicetree/bindings/display/bridge/analogix,anx7814.yaml
> > new file mode 100644
> > index 000000000000..13f0b52edefd
> > --- /dev/null
> > +++ b/Documentation/devicetree/bindings/display/bridge/analogix,anx7814.yaml
> > @@ -0,0 +1,124 @@
> > +# SPDX-License-Identifier: (GPL-2.0-only OR BSD-2-Clause)
> > +%YAML 1.2
> > +---
> > +$id: http://devicetree.org/schemas/display/bridge/analogix,anx7814.yaml#
> > +$schema: http://devicetree.org/meta-schemas/core.yaml#
> > +
> > +title: Analogix ANX7814 SlimPort (Full-HD Transmitter)
> > +
> > +maintainers:
> > +  - Enric Balletbo i Serra <enric.balletbo@collabora.com>
> > +
> > +properties:
> > +  compatible:
> > +    enum:
> > +      - analogix,anx7808
> > +      - analogix,anx7812
> > +      - analogix,anx7814
> > +      - analogix,anx7818
> > +
> > +  reg:
> > +    maxItems: 1
> > +    description: I2C address of the device.
> > +
> > +  interrupts:
> > +    maxItems: 1
> > +    description: Should contain the INTP interrupt.
> > +
> > +  hpd-gpios:
> > +    maxItems: 1
> > +    description: Which GPIO to use for hpd.
> > +
> > +  pd-gpios:
> > +    maxItems: 1
> > +    description: Which GPIO to use for power down.
> > +
> > +  reset-gpios:
> > +    maxItems: 1
> > +    description: Which GPIO to use for reset.
> > +
> > +  dvdd10-supply:
> > +    maxItems: 1
> > +    description: Regulator for 1.0V digital core power.
> > +
> > +  ports:
> > +    type: object
> > +    description:
> > +      A node containing input and output port nodes with endpoint
> > +      definitions as documented in
> > +      Documentation/devicetree/bindings/media/video-interfaces.txt
> > +      Documentation/devicetree/bindings/graph.txt
> > +
> > +    properties:
> > +      port@0:
> > +        type: object
> > +        description: Video port for HDMI input.
> > +
> > +        properties:
> > +          reg:
> > +            const: 0
> > +
> > +      port@1:
> > +        type: object
> > +        description:
> > +          Video port for SlimPort, DisplayPort, eDP or MyDP output.
> > +
> > +        properties:
> > +          reg:
> > +            const: 1
> > +
> > +    required:
> > +      - port@0
> > +      - port@1
> > +
> > +required:
> > +  - compatible
> > +  - reg
> > +  - interrupts
> 
> See below ...
> 
> > +  - hpd-gpios
> > +  - pd-gpios
> > +  - reset-gpios
> 
> I know that these gpio attributes were required in the old binding and the
> driver handles these gpios as required, but assuming that we should really
> describe the hardware _not_ the driver, strictly talking, none of these gpios
> are really required. The same happens with the interrupt, you can left the pin
> floating and poll the registers.
> 
> So I am wondering if you should remove interrupts, *-gpios from required. Maybe
> Rob Herring can give us more light on this?

Agreed.

One step further is hpd-gpios should be deprecated as it should be in a 
connector node.

> 
> Other than that:
> 
> Reviewed-by: Enric Balletbo i Serra <enric.balletbo@collabora.com>
> 
> Thanks,
>  Enric
> 
> > +  - ports
> > +
> > +additionalProperties: false
> > +
> > +examples:
> > +  - |
> > +    #include <dt-bindings/interrupt-controller/arm-gic.h>
> > +    #include <dt-bindings/gpio/gpio.h>
> > +
> > +    i2c {
> > +        #address-cells = <1>;
> > +        #size-cells = <0>;
> > +
> > +        anx7814: bridge@38 {
> > +            compatible = "analogix,anx7814";
> > +            reg = <0x38>;
> > +            interrupt-parent = <&gpio0>;
> > +            interrupts = <99 IRQ_TYPE_LEVEL_LOW>;   /* INTP */
> > +            hpd-gpios = <&pio 36 GPIO_ACTIVE_HIGH>;
> > +            pd-gpios = <&pio 33 GPIO_ACTIVE_HIGH>;
> > +            reset-gpios = <&pio 98 GPIO_ACTIVE_HIGH>;
> > +
> > +            ports {
> > +                #address-cells = <1>;
> > +                #size-cells = <0>;
> > +
> > +                port@0 {
> > +                    reg = <0>;
> > +                    anx7814_in: endpoint {
> > +                        remote-endpoint = <&hdmi0_out>;
> > +                    };
> > +                };
> > +
> > +                port@1 {
> > +                    reg = <1>;
> > +                    anx7814_out: endpoint {
> > +                        remote-endpoint = <&edp_out>;
> > +                    };
> > +                };
> > +            };
> > +        };
> > +    };
> > +
> > +...

WARNING: multiple messages have this Message-ID (diff)
From: Rob Herring <robh@kernel.org>
To: Enric Balletbo i Serra <enric.balletbo@collabora.com>
Cc: devicetree@vger.kernel.org, kernel@collabora.com,
	"Ricardo Cañuelo" <ricardo.canuelo@collabora.com>,
	dri-devel@lists.freedesktop.org
Subject: Re: [PATCH v3] dt-bindings: display: anx7814.txt: convert to yaml
Date: Mon, 11 May 2020 18:15:54 -0500	[thread overview]
Message-ID: <20200511231554.GA12152@bogus> (raw)
In-Reply-To: <676aaa45-b4cb-104e-de37-2508f0ab634d@collabora.com>

On Mon, Apr 27, 2020 at 03:52:44PM +0200, Enric Balletbo i Serra wrote:
> Hi Ricardo,
> 
> Thank you for your patch.
> 
> On 27/4/20 12:09, Ricardo Cañuelo wrote:
> > This converts the Analogix ANX7814 bridge DT binding to yaml. Port
> > definitions and descriptions were expanded, apart from that it's a
> > direct translation from the original binding.
> > 
> > Signed-off-by: Ricardo Cañuelo <ricardo.canuelo@collabora.com>
> > Acked-by: Sam Ravnborg <sam@ravnborg.org>
> > ---
> > Changes in v3 (suggested by Sam Ravnborg):
> >   - Rename example node i2c0 to i2c.
> > 
> > Changes in v2 (suggested by Enric Balletbo):
> >   - File name change: use full compatible string.
> >   - Binding description removed.
> >   - #address-cells and #size-cells properties removed from ports node.
> >   - Example node renamed: anx7814 -> bridge.
> > 
> > Tested with:
> > make dt_binding_check ARCH=arm64 DT_SCHEMA_FILES=<.../analogix,anx7814.yaml>
> > make dtbs_check ARCH=arm64 DT_SCHEMA_FILES=<.../analogix,anx7814.yaml>
> > 
> >  .../display/bridge/analogix,anx7814.yaml      | 124 ++++++++++++++++++
> >  .../bindings/display/bridge/anx7814.txt       |  42 ------
> >  2 files changed, 124 insertions(+), 42 deletions(-)
> >  create mode 100644 Documentation/devicetree/bindings/display/bridge/analogix,anx7814.yaml
> >  delete mode 100644 Documentation/devicetree/bindings/display/bridge/anx7814.txt
> > 
> > diff --git a/Documentation/devicetree/bindings/display/bridge/analogix,anx7814.yaml b/Documentation/devicetree/bindings/display/bridge/analogix,anx7814.yaml
> > new file mode 100644
> > index 000000000000..13f0b52edefd
> > --- /dev/null
> > +++ b/Documentation/devicetree/bindings/display/bridge/analogix,anx7814.yaml
> > @@ -0,0 +1,124 @@
> > +# SPDX-License-Identifier: (GPL-2.0-only OR BSD-2-Clause)
> > +%YAML 1.2
> > +---
> > +$id: http://devicetree.org/schemas/display/bridge/analogix,anx7814.yaml#
> > +$schema: http://devicetree.org/meta-schemas/core.yaml#
> > +
> > +title: Analogix ANX7814 SlimPort (Full-HD Transmitter)
> > +
> > +maintainers:
> > +  - Enric Balletbo i Serra <enric.balletbo@collabora.com>
> > +
> > +properties:
> > +  compatible:
> > +    enum:
> > +      - analogix,anx7808
> > +      - analogix,anx7812
> > +      - analogix,anx7814
> > +      - analogix,anx7818
> > +
> > +  reg:
> > +    maxItems: 1
> > +    description: I2C address of the device.
> > +
> > +  interrupts:
> > +    maxItems: 1
> > +    description: Should contain the INTP interrupt.
> > +
> > +  hpd-gpios:
> > +    maxItems: 1
> > +    description: Which GPIO to use for hpd.
> > +
> > +  pd-gpios:
> > +    maxItems: 1
> > +    description: Which GPIO to use for power down.
> > +
> > +  reset-gpios:
> > +    maxItems: 1
> > +    description: Which GPIO to use for reset.
> > +
> > +  dvdd10-supply:
> > +    maxItems: 1
> > +    description: Regulator for 1.0V digital core power.
> > +
> > +  ports:
> > +    type: object
> > +    description:
> > +      A node containing input and output port nodes with endpoint
> > +      definitions as documented in
> > +      Documentation/devicetree/bindings/media/video-interfaces.txt
> > +      Documentation/devicetree/bindings/graph.txt
> > +
> > +    properties:
> > +      port@0:
> > +        type: object
> > +        description: Video port for HDMI input.
> > +
> > +        properties:
> > +          reg:
> > +            const: 0
> > +
> > +      port@1:
> > +        type: object
> > +        description:
> > +          Video port for SlimPort, DisplayPort, eDP or MyDP output.
> > +
> > +        properties:
> > +          reg:
> > +            const: 1
> > +
> > +    required:
> > +      - port@0
> > +      - port@1
> > +
> > +required:
> > +  - compatible
> > +  - reg
> > +  - interrupts
> 
> See below ...
> 
> > +  - hpd-gpios
> > +  - pd-gpios
> > +  - reset-gpios
> 
> I know that these gpio attributes were required in the old binding and the
> driver handles these gpios as required, but assuming that we should really
> describe the hardware _not_ the driver, strictly talking, none of these gpios
> are really required. The same happens with the interrupt, you can left the pin
> floating and poll the registers.
> 
> So I am wondering if you should remove interrupts, *-gpios from required. Maybe
> Rob Herring can give us more light on this?

Agreed.

One step further is hpd-gpios should be deprecated as it should be in a 
connector node.

> 
> Other than that:
> 
> Reviewed-by: Enric Balletbo i Serra <enric.balletbo@collabora.com>
> 
> Thanks,
>  Enric
> 
> > +  - ports
> > +
> > +additionalProperties: false
> > +
> > +examples:
> > +  - |
> > +    #include <dt-bindings/interrupt-controller/arm-gic.h>
> > +    #include <dt-bindings/gpio/gpio.h>
> > +
> > +    i2c {
> > +        #address-cells = <1>;
> > +        #size-cells = <0>;
> > +
> > +        anx7814: bridge@38 {
> > +            compatible = "analogix,anx7814";
> > +            reg = <0x38>;
> > +            interrupt-parent = <&gpio0>;
> > +            interrupts = <99 IRQ_TYPE_LEVEL_LOW>;   /* INTP */
> > +            hpd-gpios = <&pio 36 GPIO_ACTIVE_HIGH>;
> > +            pd-gpios = <&pio 33 GPIO_ACTIVE_HIGH>;
> > +            reset-gpios = <&pio 98 GPIO_ACTIVE_HIGH>;
> > +
> > +            ports {
> > +                #address-cells = <1>;
> > +                #size-cells = <0>;
> > +
> > +                port@0 {
> > +                    reg = <0>;
> > +                    anx7814_in: endpoint {
> > +                        remote-endpoint = <&hdmi0_out>;
> > +                    };
> > +                };
> > +
> > +                port@1 {
> > +                    reg = <1>;
> > +                    anx7814_out: endpoint {
> > +                        remote-endpoint = <&edp_out>;
> > +                    };
> > +                };
> > +            };
> > +        };
> > +    };
> > +
> > +...
_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/dri-devel

  reply	other threads:[~2020-05-11 23:15 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-04-27 10:09 [PATCH v3] dt-bindings: display: anx7814.txt: convert to yaml Ricardo Cañuelo
2020-04-27 10:09 ` Ricardo Cañuelo
2020-04-27 13:52 ` Enric Balletbo i Serra
2020-04-27 13:52   ` Enric Balletbo i Serra
2020-05-11 23:15   ` Rob Herring [this message]
2020-05-11 23:15     ` Rob Herring

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=20200511231554.GA12152@bogus \
    --to=robh@kernel.org \
    --cc=devicetree@vger.kernel.org \
    --cc=dri-devel@lists.freedesktop.org \
    --cc=enric.balletbo@collabora.com \
    --cc=kernel@collabora.com \
    --cc=ricardo.canuelo@collabora.com \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.