From: Rob Herring <robh+dt@kernel.org> To: Geert Uytterhoeven <geert@linux-m68k.org> Cc: "Laurent Pinchart" <laurent.pinchart@ideasonboard.com>, "Ricardo Cañuelo" <ricardo.canuelo@collabora.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>, "Geert Uytterhoeven" <geert+renesas@glider.be>, "Wei Xu" <xuwei5@hisilicon.com> Subject: Re: [PATCH v2 6/6] dt-bindings: drm: bridge: adi,adv7511.txt: convert to yaml Date: Wed, 27 May 2020 11:29:51 -0600 [thread overview] Message-ID: <CAL_JsqJgQajnKdQ1Bt6YFX04fX0VGz44Q3kBdLLR04OzhWrH5A@mail.gmail.com> (raw) In-Reply-To: <CAMuHMdXinhY13us9rt9h7EvrT_8zhnQg6tmOBtA0nEQ=1G1O7Q@mail.gmail.com> On Tue, May 26, 2020 at 1:03 AM Geert Uytterhoeven <geert@linux-m68k.org> wrote: > > Hi Laurent, > > On Tue, May 26, 2020 at 3:44 AM Laurent Pinchart > <laurent.pinchart@ideasonboard.com> wrote: > > On Mon, May 25, 2020 at 09:43:35AM +0200, Ricardo Cañuelo wrote: > > > On jue 14-05-2020 18:22:39, Laurent Pinchart wrote: > > > > > If we want to be more strict and require the definition of all the > > > > > supplies, there will be many more DTs changes in the series, and I'm not > > > > > sure I'll be able to do that in a reasonable amount of time. I'm looking > > > > > at them and it's not always clear which regulators to use or if they are > > > > > even defined. > > > > > > > > We can decouple the two though (I think). The bindings should reflect > > > > what we consider right, and the dts files could be fixed on top. > > > > > > Do you have a suggestion on how to do this? If we decouple the two > > > tasks most of the work would be searching for DTs to fix and finding a > > > way to fix each one of them, and unless I do this _before_ the binding > > > conversion I'll get a lot of dtbs_check errors. > > > > Rob should answer this question as it will be his decision, but I've > > personally never considered non-compliant DT sources to be an obstacle > > to bindings conversion to YAML. The DT sources should be fixed, but I > > don't see it as a prerequisite (although it's a good practice). There's currently no requirement that binding schema don't introduce warnings in dts files. That should change when/if we get to a warning free state (probably per platform/family). I don't think we're close on any platform? (If we are, I'd like to start tracking that). It is good to pay attention to the warnings you get though as the schema may not be doing what you expect or the binding really doesn't match reality. > I do my best to avoid introducing regressions when the binding conversions > go upstream. Meaning you fix the dts files or massage the schema to match? If we just adjust schema to match, what's the point in this effort? We should find things wrong or ill defined. Rob
WARNING: multiple messages have this Message-ID (diff)
From: Rob Herring <robh+dt@kernel.org> To: Geert Uytterhoeven <geert@linux-m68k.org> Cc: "open list:OPEN FIRMWARE AND FLATTENED DEVICE TREE BINDINGS" <devicetree@vger.kernel.org>, "Geert Uytterhoeven" <geert+renesas@glider.be>, "Wei Xu" <xuwei5@hisilicon.com>, "Laurent Pinchart" <laurent.pinchart@ideasonboard.com>, "Collabora Kernel ML" <kernel@collabora.com>, "Ricardo Cañuelo" <ricardo.canuelo@collabora.com>, "Linux ARM" <linux-arm-kernel@lists.infradead.org> Subject: Re: [PATCH v2 6/6] dt-bindings: drm: bridge: adi, adv7511.txt: convert to yaml Date: Wed, 27 May 2020 11:29:51 -0600 [thread overview] Message-ID: <CAL_JsqJgQajnKdQ1Bt6YFX04fX0VGz44Q3kBdLLR04OzhWrH5A@mail.gmail.com> (raw) In-Reply-To: <CAMuHMdXinhY13us9rt9h7EvrT_8zhnQg6tmOBtA0nEQ=1G1O7Q@mail.gmail.com> On Tue, May 26, 2020 at 1:03 AM Geert Uytterhoeven <geert@linux-m68k.org> wrote: > > Hi Laurent, > > On Tue, May 26, 2020 at 3:44 AM Laurent Pinchart > <laurent.pinchart@ideasonboard.com> wrote: > > On Mon, May 25, 2020 at 09:43:35AM +0200, Ricardo Cañuelo wrote: > > > On jue 14-05-2020 18:22:39, Laurent Pinchart wrote: > > > > > If we want to be more strict and require the definition of all the > > > > > supplies, there will be many more DTs changes in the series, and I'm not > > > > > sure I'll be able to do that in a reasonable amount of time. I'm looking > > > > > at them and it's not always clear which regulators to use or if they are > > > > > even defined. > > > > > > > > We can decouple the two though (I think). The bindings should reflect > > > > what we consider right, and the dts files could be fixed on top. > > > > > > Do you have a suggestion on how to do this? If we decouple the two > > > tasks most of the work would be searching for DTs to fix and finding a > > > way to fix each one of them, and unless I do this _before_ the binding > > > conversion I'll get a lot of dtbs_check errors. > > > > Rob should answer this question as it will be his decision, but I've > > personally never considered non-compliant DT sources to be an obstacle > > to bindings conversion to YAML. The DT sources should be fixed, but I > > don't see it as a prerequisite (although it's a good practice). There's currently no requirement that binding schema don't introduce warnings in dts files. That should change when/if we get to a warning free state (probably per platform/family). I don't think we're close on any platform? (If we are, I'd like to start tracking that). It is good to pay attention to the warnings you get though as the schema may not be doing what you expect or the binding really doesn't match reality. > I do my best to avoid introducing regressions when the binding conversions > go upstream. Meaning you fix the dts files or massage the schema to match? If we just adjust schema to match, what's the point in this effort? We should find things wrong or ill defined. Rob _______________________________________________ linux-arm-kernel mailing list linux-arm-kernel@lists.infradead.org http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
next prev parent reply other threads:[~2020-05-27 17:30 UTC|newest] Thread overview: 66+ messages / expand[flat|nested] mbox.gz Atom feed top 2020-05-11 11:06 [PATCH v2 0/6] Convert adi,adv7511.txt DT bindings to yaml Ricardo Cañuelo 2020-05-11 11:06 ` Ricardo Cañuelo 2020-05-11 11:06 ` [PATCH v2 1/6] arm64: dts: renesas: make hdmi encoder nodes compliant with DT bindings Ricardo Cañuelo 2020-05-11 11:06 ` Ricardo Cañuelo 2020-05-11 11:51 ` Geert Uytterhoeven 2020-05-11 11:51 ` Geert Uytterhoeven 2020-05-14 1:33 ` Laurent Pinchart 2020-05-14 1:33 ` Laurent Pinchart 2020-05-11 11:06 ` [PATCH v2 2/6] ARM: " Ricardo Cañuelo 2020-05-11 11:06 ` Ricardo Cañuelo 2020-05-11 11:51 ` Geert Uytterhoeven 2020-05-11 11:51 ` Geert Uytterhoeven 2020-05-14 1:34 ` Laurent Pinchart 2020-05-14 1:34 ` Laurent Pinchart 2020-05-11 11:06 ` [PATCH v2 3/6] ARM: dts: zynq: add port definitions to hdmi-tx@39 Ricardo Cañuelo 2020-05-11 11:06 ` Ricardo Cañuelo 2020-05-11 12:24 ` Ezequiel Garcia 2020-05-11 12:24 ` Ezequiel Garcia 2020-05-11 12:52 ` Michal Simek 2020-05-11 12:52 ` Michal Simek 2020-05-14 1:36 ` Laurent Pinchart 2020-05-14 1:36 ` Laurent Pinchart 2020-05-11 11:06 ` [PATCH v2 4/6] arm64: dts: hisilicon: hikey: fixes to comply with adi,adv7533 DT binding Ricardo Cañuelo 2020-05-11 11:06 ` [PATCH v2 4/6] arm64: dts: hisilicon: hikey: fixes to comply with adi, adv7533 " Ricardo Cañuelo 2020-05-14 1:37 ` [PATCH v2 4/6] arm64: dts: hisilicon: hikey: fixes to comply with adi,adv7533 " Laurent Pinchart 2020-05-14 1:37 ` Laurent Pinchart 2020-08-04 20:57 ` [PATCH v2 4/6] arm64: dts: hisilicon: hikey: fixes to comply with adi, adv7533 " John Stultz 2020-08-04 20:57 ` John Stultz 2020-08-04 21:24 ` John Stultz 2020-08-04 21:24 ` John Stultz 2020-05-11 11:06 ` [PATCH v2 5/6] ARM: dts: iwg20d-q7-dbcm-ca: remove unneeded properties in hdmi@39 Ricardo Cañuelo 2020-05-11 11:06 ` Ricardo Cañuelo 2020-05-11 11:52 ` Geert Uytterhoeven 2020-05-11 11:52 ` Geert Uytterhoeven 2020-05-14 1:37 ` Laurent Pinchart 2020-05-14 1:37 ` Laurent Pinchart 2020-05-11 11:06 ` [PATCH v2 6/6] dt-bindings: drm: bridge: adi,adv7511.txt: convert to yaml Ricardo Cañuelo 2020-05-11 11:06 ` [PATCH v2 6/6] dt-bindings: drm: bridge: adi, adv7511.txt: " Ricardo Cañuelo 2020-05-14 1:54 ` [PATCH v2 6/6] dt-bindings: drm: bridge: adi,adv7511.txt: " Laurent Pinchart 2020-05-14 1:54 ` Laurent Pinchart 2020-05-14 9:36 ` Ricardo Cañuelo 2020-05-14 9:36 ` Ricardo Cañuelo 2020-05-14 15:22 ` Laurent Pinchart 2020-05-14 15:22 ` Laurent Pinchart 2020-05-18 21:27 ` Rob Herring 2020-05-18 21:27 ` Rob Herring 2020-05-25 7:43 ` Ricardo Cañuelo 2020-05-25 7:43 ` Ricardo Cañuelo 2020-05-26 1:44 ` Laurent Pinchart 2020-05-26 1:44 ` Laurent Pinchart 2020-05-26 7:03 ` Geert Uytterhoeven 2020-05-26 7:03 ` [PATCH v2 6/6] dt-bindings: drm: bridge: adi, adv7511.txt: " Geert Uytterhoeven 2020-05-26 10:11 ` [PATCH v2 6/6] dt-bindings: drm: bridge: adi,adv7511.txt: " Laurent Pinchart 2020-05-26 10:11 ` Laurent Pinchart 2020-05-26 10:39 ` Geert Uytterhoeven 2020-05-26 10:39 ` [PATCH v2 6/6] dt-bindings: drm: bridge: adi, adv7511.txt: " Geert Uytterhoeven 2020-05-26 19:45 ` [PATCH v2 6/6] dt-bindings: drm: bridge: adi,adv7511.txt: " Ezequiel Garcia 2020-05-26 19:45 ` Ezequiel Garcia 2020-05-27 17:29 ` Rob Herring [this message] 2020-05-27 17:29 ` [PATCH v2 6/6] dt-bindings: drm: bridge: adi, adv7511.txt: " Rob Herring 2020-05-27 18:18 ` [PATCH v2 6/6] dt-bindings: drm: bridge: adi,adv7511.txt: " Geert Uytterhoeven 2020-05-27 18:18 ` [PATCH v2 6/6] dt-bindings: drm: bridge: adi, adv7511.txt: " Geert Uytterhoeven 2020-05-28 6:36 ` [PATCH v2 6/6] dt-bindings: drm: bridge: adi,adv7511.txt: " Ricardo Cañuelo 2020-05-28 6:36 ` Ricardo Cañuelo 2020-05-11 11:55 ` [PATCH v2 0/6] Convert adi,adv7511.txt DT bindings " Geert Uytterhoeven 2020-05-11 11:55 ` Geert Uytterhoeven
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=CAL_JsqJgQajnKdQ1Bt6YFX04fX0VGz44Q3kBdLLR04OzhWrH5A@mail.gmail.com \ --to=robh+dt@kernel.org \ --cc=devicetree@vger.kernel.org \ --cc=geert+renesas@glider.be \ --cc=geert@linux-m68k.org \ --cc=kernel@collabora.com \ --cc=laurent.pinchart@ideasonboard.com \ --cc=linux-arm-kernel@lists.infradead.org \ --cc=ricardo.canuelo@collabora.com \ --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: linkBe 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.