[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CAL_JsqK-LpDQWh9RsLsGPEQ53n6s0+Q7ioVikSm1jZuoCWAgnA@mail.gmail.com>
Date: Thu, 20 May 2021 14:43:34 -0500
From: Rob Herring <robh@...nel.org>
To: Sudeep Holla <sudeep.holla@....com>,
Viresh Kumar <viresh.kumar@...aro.org>
Cc: "linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
Bjorn Andersson <bjorn.andersson@...aro.org>,
Hector Yuan <hector.yuan@...iatek.com>,
Manivannan Sadhasivam <manivannan.sadhasivam@...aro.org>,
devicetree@...r.kernel.org
Subject: Re: [PATCH v4] dt-bindings: dvfs: Add support for generic performance domains
On Wed, May 19, 2021 at 6:20 AM Sudeep Holla <sudeep.holla@....com> wrote:
>
> Hi Rob,
>
> On Mon, May 17, 2021 at 03:45:11PM -0500, Rob Herring wrote:
>
> [...]
>
> > My bot found errors running 'make DT_CHECKER_FLAGS=-m dt_binding_check'
> > on your patch (DT_CHECKER_FLAGS is new in v5.13):
> >
> > yamllint warnings/errors:
> >
> > dtschema/dtc warnings/errors:
> > Documentation/devicetree/bindings/dvfs/performance-domain.example.dt.yaml:0:0: /example-0/performance-controller@...40000: failed to match any schema with compatible: ['qcom,cpufreq-hw']
> >
> > See https://patchwork.ozlabs.org/patch/1479615
>
> IIUC, such errors due to the fact that the compatible used in the example
> is not in any yaml schema(as it is still in the old txt format). I also
> assume such errors are allowed until the transition is complete and I
> need not fix anything as part of this patch ?
Not allowed because I can't turn this check on by default until we get
rid of the existing 80 or so. But it is a new check and Viresh already
applied, so oh well.
BTW, one of the 80 is 'operating-points-v2' compatible. Hint, hint.
Rob
Powered by blists - more mailing lists