devicetree.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Geert Uytterhoeven <geert@linux-m68k.org>
To: "Ricardo Cañuelo" <ricardo.canuelo@collabora.com>
Cc: Laurent Pinchart <laurent.pinchart@ideasonboard.com>,
	Collabora Kernel ML <kernel@collabora.com>,
	"open list:OPEN FIRMWARE AND FLATTENED DEVICE TREE BINDINGS" 
	<devicetree@vger.kernel.org>,
	Linux ARM <linux-arm-kernel@lists.infradead.org>,
	Rob Herring <robh+dt@kernel.org>, Wei Xu <xuwei5@hisilicon.com>
Subject: Re: [RFT PATCH 5/5] dt-bindings: drm: bridge: adi,adv7511.txt: convert to yaml
Date: Wed, 6 May 2020 09:44:19 +0200	[thread overview]
Message-ID: <CAMuHMdVbRoGAqeqePQDgRpxg4Vsr_LEfHERW-r6KdiSOCo5a6g@mail.gmail.com> (raw)
In-Reply-To: <20200501083227.10886-6-ricardo.canuelo@collabora.com>

Hi Ricardo,

On Fri, May 1, 2020 at 10:33 AM Ricardo Cañuelo
<ricardo.canuelo@collabora.com> wrote:
> Convert the ADV7511/11w/13/33/35 DT bindings to json-schema.
>
> Signed-off-by: Ricardo Cañuelo <ricardo.canuelo@collabora.com>

> --- /dev/null
> +++ b/Documentation/devicetree/bindings/display/bridge/adi,adv7511.yaml
> @@ -0,0 +1,293 @@

> +  reg-names:
> +    description:
> +      Names of maps with programmable addresses. It can contain any map
> +      needing a non-default address.
> +    minItems: 1
> +    items:
> +      - const: main
> +      - const: edid
> +      - const: cec
> +      - const: packet

Can't you avoid the need for patches
[RFT PATCH 1/5] arm64: dts: draak: Reorder hdmi-encoder@39 reg and
reg-names properties
[RFT PATCH 2/5] ARM: dts: wheat: reorder reg and reg-names properties
in hdmi bridges

by using

    items:
      enum:
        - main
        - edid
        - cec
        - packet

instead?

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

  parent reply	other threads:[~2020-05-06  7:44 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-05-01  8:32 [RFT PATCH 0/5] Convert adi,adv7511.txt DT bindings to yaml Ricardo Cañuelo
2020-05-01  8:32 ` [RFT PATCH 1/5] arm64: dts: draak: Reorder hdmi-encoder@39 reg and reg-names properties Ricardo Cañuelo
2020-05-01  8:32 ` [RFT PATCH 2/5] ARM: dts: wheat: reorder reg and reg-names properties in hdmi bridges Ricardo Cañuelo
2020-05-01  8:32 ` [RFT PATCH 3/5] ARM: dts: zynq: add port definitions to hdmi-tx@39 Ricardo Cañuelo
2020-05-01  8:32 ` [RFT PATCH 4/5] arm64: dts: hisilicon: hikey960: add missing hdmi bridge properties Ricardo Cañuelo
2020-05-01  8:32 ` [RFT PATCH 5/5] dt-bindings: drm: bridge: adi,adv7511.txt: convert to yaml Ricardo Cañuelo
2020-05-05 18:56   ` Rob Herring
2020-05-06 13:10     ` Ricardo Cañuelo
2020-05-06 18:43       ` Rob Herring
2020-05-06  7:44   ` Geert Uytterhoeven [this message]
2020-05-06  8:23     ` Ricardo Cañuelo
2020-05-06 10:57       ` Laurent Pinchart
2020-05-06 12:59         ` 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=CAMuHMdVbRoGAqeqePQDgRpxg4Vsr_LEfHERW-r6KdiSOCo5a6g@mail.gmail.com \
    --to=geert@linux-m68k.org \
    --cc=devicetree@vger.kernel.org \
    --cc=kernel@collabora.com \
    --cc=laurent.pinchart@ideasonboard.com \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=ricardo.canuelo@collabora.com \
    --cc=robh+dt@kernel.org \
    --cc=xuwei5@hisilicon.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 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).