From: Geert Uytterhoeven <geert@linux-m68k.org>
To: Laurent Pinchart <laurent.pinchart+renesas@ideasonboard.com>
Cc: "open list:OPEN FIRMWARE AND FLATTENED DEVICE TREE BINDINGS"
<devicetree@vger.kernel.org>,
DRI Development <dri-devel@lists.freedesktop.org>,
Linux-Renesas <linux-renesas-soc@vger.kernel.org>,
Rob Herring <robh+dt@kernel.org>,
Jacopo Mondi <jacopo+renesas@jmondi.org>,
Maxime Ripard <maxime@cerno.tech>
Subject: Re: [PATCH 4/4] dt-bindings: display: bridge: renesas,lvds: Convert binding to YAML
Date: Mon, 6 Apr 2020 10:47:37 +0200 [thread overview]
Message-ID: <CAMuHMdXJcw0eGY7J=JcGv6Hs9E_GCybsYSeKKeH5pAH8nkdTrg@mail.gmail.com> (raw)
In-Reply-To: <20200405232318.26833-5-laurent.pinchart+renesas@ideasonboard.com>
Hi Laurent,
On Mon, Apr 6, 2020 at 1:24 AM Laurent Pinchart
<laurent.pinchart+renesas@ideasonboard.com> wrote:
> Convert the Renesas R-Car LVDS encoder text binding to YAML.
>
> Signed-off-by: Laurent Pinchart <laurent.pinchart+renesas@ideasonboard.com>
Thanks for your patch!
> --- /dev/null
> +++ b/Documentation/devicetree/bindings/display/bridge/renesas,lvds.yaml
> @@ -0,0 +1,248 @@
> +# SPDX-License-Identifier: (GPL-2.0-only OR BSD-2-Clause)
> +%YAML 1.2
> +---
> +$id: http://devicetree.org/schemas/display/bridge/renesas,lvds.yaml#
> +$schema: http://devicetree.org/meta-schemas/core.yaml#
> +
> +title: Renesas R-Car LVDS Encoder
> +
> +maintainers:
> + - Laurent Pinchart <laurent.pinchart+renesas@ideasonboard.com>
> +
> +description: |
> + These DT bindings describe the LVDS encoder embedded in the Renesas R-Car
> + Gen2, R-Car Gen3 and RZ/G SoCs.
RZ/G1 and RZ/G2 (no idea what'll RZ/G3 will bring ;-)
> +
> +properties:
> + compatible:
> + enum:
> + - renesas,r8a7743-lvds # for R8A7743 (RZ/G1M) compatible LVDS encoders
> + - renesas,r8a7744-lvds # for R8A7744 (RZ/G1N) compatible LVDS encoders
> + - renesas,r8a774a1-lvds # for R8A774A1 (RZ/G2M) compatible LVDS encoders
> + - renesas,r8a774b1-lvds # for R8A774B1 (RZ/G2N) compatible LVDS encoders
> + - renesas,r8a774c0-lvds # for R8A774C0 (RZ/G2E) compatible LVDS encoders
> + - renesas,r8a7790-lvds # for R8A7790 (R-Car H2) compatible LVDS encoders
> + - renesas,r8a7791-lvds # for R8A7791 (R-Car M2-W) compatible LVDS encoders
> + - renesas,r8a7793-lvds # for R8A7793 (R-Car M2-N) compatible LVDS encoders
> + - renesas,r8a7795-lvds # for R8A7795 (R-Car H3) compatible LVDS encoders
> + - renesas,r8a7796-lvds # for R8A7796 (R-Car M3-W) compatible LVDS encoders
R8A77960 (I know you don't have support for R8A77961 yet ;-)
> + - renesas,r8a77965-lvds # for R8A77965 (R-Car M3-N) compatible LVDS encoders
> + - renesas,r8a77970-lvds # for R8A77970 (R-Car V3M) compatible LVDS encoders
> + - renesas,r8a77980-lvds # for R8A77980 (R-Car V3H) compatible LVDS encoders
> + - renesas,r8a77990-lvds # for R8A77990 (R-Car E3) compatible LVDS encoders
> + - renesas,r8a77995-lvds # for R8A77995 (R-Car D3) compatible LVDS encoders
Wouldn't it be sufficient to just have the SoC name (e.g. "R-Car D3") in
the comments?
> +if:
> + properties:
> + compatible:
> + enum:
> + - renesas,r8a774c0-lvds
> + - renesas,r8a77990-lvds
> + - renesas,r8a77995-lvds
> +then:
> + properties:
> + clocks:
> + minItems: 1
> + maxItems: 4
> + items:
> + - description: Functional clock
> + - description: EXTAL input clock
> + - description: DU_DOTCLKIN0 input clock
> + - description: DU_DOTCLKIN1 input clock
> +
> + clock-names:
> + minItems: 1
> + maxItems: 4
> + items:
> + - const: fck
> + # The LVDS encoder can use the EXTAL or DU_DOTCLKINx clocks.
> + # These clocks are optional.
> + - enum:
> + - extal
> + - dclkin.0
> + - dclkin.1
> + - enum:
> + - extal
> + - dclkin.0
> + - dclkin.1
> + - enum:
> + - extal
> + - dclkin.0
> + - dclkin.1
Can the duplication of the last 3 entries be avoided?
Perhaps like in
Documentation/devicetree/bindings/serial/renesas,scif.yaml?
> +examples:
> + - |
> + #include <dt-bindings/clock/renesas-cpg-mssr.h>
> + #include <dt-bindings/power/r8a7795-sysc.h>
> +
> + lvds@feb90000 {
> + compatible = "renesas,r8a7795-lvds";
> + reg = <0 0xfeb90000 0 0x14>;
Examples are built with #{address,size}-cells = <1>.
> + lvds0: lvds@feb90000 {
> + compatible = "renesas,r8a77990-lvds";
> + reg = <0 0xfeb90000 0 0x20>;
Likewise.
> + lvds1: lvds@feb90100 {
> + compatible = "renesas,r8a77990-lvds";
> + reg = <0 0xfeb90100 0 0x20>;
Likewise.
Gr{oetje,eeting}s,
Geert
--
Geert Uytterhoeven -- There's lots of Linux beyond ia32 -- geert@linux-m68k.org
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
_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/dri-devel
next prev parent reply other threads:[~2020-04-06 8:47 UTC|newest]
Thread overview: 37+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-04-05 23:23 [PATCH 0/4] dt-bindings: display: bridge: Convert bindings used by R-Car DU to YAML Laurent Pinchart
2020-04-05 23:23 ` [PATCH 1/4] dt-bindings: display: bridge: Reject additional properties in ports node Laurent Pinchart
2020-04-06 7:47 ` Maxime Ripard
2020-04-14 21:56 ` Rob Herring
2020-04-05 23:23 ` [PATCH 2/4] dt-bindings: display: bridge: Convert simple-bridge bindings to YAML Laurent Pinchart
2020-04-06 7:47 ` Maxime Ripard
2020-04-14 22:00 ` Rob Herring
2020-04-15 0:54 ` Laurent Pinchart
2020-04-15 0:59 ` [PATCH v1.1 " Laurent Pinchart
2020-04-15 13:51 ` Rob Herring
2020-04-05 23:23 ` [PATCH 3/4] dt-bindings: display: bridge: thc63lvd1024: Convert binding " Laurent Pinchart
2020-04-06 6:40 ` Jacopo Mondi
2020-04-06 11:15 ` Laurent Pinchart
2020-05-13 23:21 ` [PATCH 5/4] dt-bindings: display: bridge: thc63lvd1024: Document dual-output mode Laurent Pinchart
2020-05-14 7:18 ` Jacopo Mondi
2020-05-28 2:42 ` Rob Herring
2020-04-06 7:48 ` [PATCH 3/4] dt-bindings: display: bridge: thc63lvd1024: Convert binding to YAML Maxime Ripard
2020-04-14 22:01 ` Rob Herring
2020-04-05 23:23 ` [PATCH 4/4] dt-bindings: display: bridge: renesas, lvds: " Laurent Pinchart
2020-04-06 7:49 ` [PATCH 4/4] dt-bindings: display: bridge: renesas,lvds: " Maxime Ripard
2020-04-06 8:47 ` Geert Uytterhoeven [this message]
2020-04-06 11:09 ` Laurent Pinchart
2020-04-06 11:40 ` Geert Uytterhoeven
2020-04-06 19:19 ` Rob Herring
2020-05-13 23:28 ` [PATCH v1.1 4/4] dt-bindings: display: bridge: renesas, lvds: " Laurent Pinchart
2020-05-14 7:31 ` [PATCH v1.1 4/4] dt-bindings: display: bridge: renesas,lvds: " Geert Uytterhoeven
2020-05-14 15:17 ` Laurent Pinchart
2020-05-14 19:02 ` Geert Uytterhoeven
2020-05-14 21:37 ` Laurent Pinchart
2020-05-14 21:42 ` [PATCH v1.2 4/4] dt-bindings: display: bridge: renesas, lvds: " Laurent Pinchart
2020-05-28 17:50 ` Rob Herring
2020-06-29 8:10 ` Sam Ravnborg
2020-06-29 23:41 ` Laurent Pinchart
2020-05-13 23:39 ` [PATCH 6/4] dt-bindings: display: renesas: lvds: RZ/G2E needs renesas, companion too Laurent Pinchart
2020-05-14 6:44 ` [PATCH 6/4] dt-bindings: display: renesas: lvds: RZ/G2E needs renesas,companion too Geert Uytterhoeven
2020-06-29 8:11 ` Sam Ravnborg
2020-06-29 23:42 ` Laurent Pinchart
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='CAMuHMdXJcw0eGY7J=JcGv6Hs9E_GCybsYSeKKeH5pAH8nkdTrg@mail.gmail.com' \
--to=geert@linux-m68k.org \
--cc=devicetree@vger.kernel.org \
--cc=dri-devel@lists.freedesktop.org \
--cc=jacopo+renesas@jmondi.org \
--cc=laurent.pinchart+renesas@ideasonboard.com \
--cc=linux-renesas-soc@vger.kernel.org \
--cc=maxime@cerno.tech \
--cc=robh+dt@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).