From: "Nancy Lin (林欣螢)" <Nancy.Lin@mediatek.com>
To: "Rex-BC Chen (陳柏辰)" <Rex-BC.Chen@mediatek.com>,
"robh@kernel.org" <robh@kernel.org>
Cc: "linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"robh+dt@kernel.org" <robh+dt@kernel.org>,
"linux-mediatek@lists.infradead.org"
<linux-mediatek@lists.infradead.org>,
"devicetree@vger.kernel.org" <devicetree@vger.kernel.org>,
"chunkuang.hu@kernel.org" <chunkuang.hu@kernel.org>,
"pavel@ucw.cz" <pavel@ucw.cz>,
"p.zabel@pengutronix.de" <p.zabel@pengutronix.de>,
"CK Hu (胡俊光)" <ck.hu@mediatek.com>,
"dri-devel@lists.freedesktop.org"
<dri-devel@lists.freedesktop.org>,
Project_Global_Chrome_Upstream_Group
<Project_Global_Chrome_Upstream_Group@mediatek.com>,
"linux-arm-kernel@lists.infradead.org"
<linux-arm-kernel@lists.infradead.org>,
"krzysztof.kozlowski+dt@linaro.org"
<krzysztof.kozlowski+dt@linaro.org>,
"matthias.bgg@gmail.com" <matthias.bgg@gmail.com>,
"airlied@linux.ie" <airlied@linux.ie>,
"angelogioacchino.delregno@collabora.com"
<angelogioacchino.delregno@collabora.com>
Subject: Re: [RESEND v5 3/3] dt-bindings: mediatek: add ethdr definition for mt8195
Date: Mon, 13 Mar 2023 07:19:11 +0000 [thread overview]
Message-ID: <915c9eebf8412fc092686626ce02e45a5d0f7841.camel@mediatek.com> (raw)
In-Reply-To: <b9f62fe5e39d23d8ce64773814fbb9f5ba1a0a21.camel@mediatek.com>
On Wed, 2022-06-08 at 23:40 +0800, Rex-BC Chen wrote:
> On Wed, 2022-06-08 at 21:45 +0800, Rob Herring wrote:
> > On Wed, 08 Jun 2022 12:38:52 +0800, Bo-Chen Chen wrote:
> > > From: "Nancy.Lin" <nancy.lin@mediatek.com>
> > >
> > > Add vdosys1 ETHDR definition.
> > >
> > > Signed-off-by: Nancy.Lin <nancy.lin@mediatek.com>
> > > Signed-off-by: Bo-Chen Chen <rex-bc.chen@mediatek.com>
> > > Reviewed-by: Chun-Kuang Hu <chunkuang.hu@kernel.org>
> > > Reviewed-by: AngeloGioacchino Del Regno <
> > > angelogioacchino.delregno@collabora.com>
> > > Reviewed-by: Krzysztof Kozlowski <krzysztof.kozlowski@linaro.org>
> > > Tested-by: AngeloGioacchino Del Regno <
> > > angelogioacchino.delregno@collabora.com>
> > > ---
> > > .../display/mediatek/mediatek,ethdr.yaml | 188
> > > ++++++++++++++++++
> > > 1 file changed, 188 insertions(+)
> > > create mode 100644
> > > Documentation/devicetree/bindings/display/mediatek/mediatek,ethdr
> > > .y
> > > aml
> > >
> >
> > 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:
> > Error:
> > Documentation/devicetree/bindings/display/mediatek/mediatek,ethdr.e
> > xa
> > mple.dts:71.40-41 syntax error
> > FATAL ERROR: Unable to parse input tree
> > make[1]: *** [scripts/Makefile.lib:383:
> > Documentation/devicetree/bindings/display/mediatek/mediatek,ethdr.e
> > xa
> > mple.dtb] Error 1
> > make[1]: *** Waiting for unfinished jobs....
> > make: *** [Makefile:1404: dt_binding_check] Error 2
> >
> > doc reference errors (make refcheckdocs):
> >
> > See https://patchwork.ozlabs.org/patch/
> >
> > This check can fail if there are any dependencies. The base for a
> > patch
> > series is generally the most recent rc1.
> >
> > If you already ran 'make dt_binding_check' and didn't see the above
> > error(s), then make sure 'yamllint' is installed and dt-schema is
> > up
> > to
> > date:
> >
> > pip3 install dtschema --upgrade
> >
> > Please check and re-submit.
> >
>
> Hello Rob,
>
> I am not sure why there is this error.
> But from my running result: line 71 in mediatek,ethdr.example.dts is
> "resets = <&vdosys1 MT8195_VDOSYS1_SW1_RST_B_HDR_VDO_FE0_DL_ASYNC>,"
>
> This reset define is in previous patch of this series.
> I don't know how to avoid this.
>
> And I also just got this:
> ./Documentation/devicetree/bindings/display/mediatek/mediatek,ethdr.e
> xa
> mple.dtb: hdr-engine@1c114000: mediatek,gce-client-reg:0:
> [4294967295,
> 7, 16384, 4096, 4294967295, 7, 20480, 4096, 4294967295, 7, 28672,
> 4096,
> 4294967295, 7, 36864, 4096, 4294967295, 7, 40960, 4096, 4294967295,
> 7,
> 45056, 4096, 4294967295, 7, 49152, 4096] is too long
> From schema:
> ./Documentation/devicetree/bindings/display/mediatek/mediatek,ethdr.y
> am
> l
> ./Documentation/devicetree/bindings/display/mediatek/mediatek,ethdr.e
> xa
> mple.dtb: hdr-engine@1c114000: mediatek,gce-client-reg: [[4294967295,
> 7, 16384, 4096, 4294967295, 7,
> 20480, 4096, 4294967295, 7, 28672, 4096, 4294967295, 7, 36864, 4096,
> 4294967295, 7, 40960, 4096, 4294967295, 7, 45056, 4096, 4294967295,
> 7,
> 49152, 4096]] is too short
> From schema:
> ./Documentation/devicetree/bindings/display/mediatek/mediatek,ethdr.y
> am
> l
>
> Is there any suggestion?
>
> BRs,
> Bo-Chen
Hi Rob,
I also got the same two messages as BO-Chen when running
dt_binding_check [1].
If I remove the following items/minItems/maxItems in the mediatek,gce-
client property, the two message disappear. I don't know what's wrong
with the original syntax. Do you have any suggestions for this?
- items:
- items:
- - description: phandle of GCE
- - description: GCE subsys id
- - description: register offset
- - description: register size
- minItems: 7
- maxItems: 7
[1].
Documentation/devicetree/bindings/display/mediatek/mediatek,ethdr.examp
le.dtb
/proj/mtk19347/cros/src/third_party/kernel/v5.10/Documentation/devicetr
ee/bindings/display/mediatek/mediatek,ethdr.example.dtb:
hdr-engine@1c114000: mediatek,gce-client-reg:0: [4294967295, 7, 16384,
4096, 4294967295, 7, 20480, 4096, 4294967295, 7, 28672, 4096,
4294967295, 7, 36864, 4096, 4294967295, 7, 40960, 4096, 4294967295, 7,
45056, 4096, 4294967295, 7, 49152, 4096] is too long
From schema:
/proj/mtk19347/cros/src/third_party/kernel/v5.10/Documentation/devicetr
ee/bindings/display/mediatek/mediatek,ethdr.yaml
/proj/mtk19347/cros/src/third_party/kernel/v5.10/Documentation/devicetr
ee/bindings/display/mediatek/mediatek,ethdr.example.dtb:
hdr-engine@1c114000: mediatek,gce-client-reg: [[4294967295, 7, 16384,
4096, 4294967295, 7, 20480, 4096, 4294967295, 7, 28672, 4096,
4294967295, 7, 36864, 4096, 4294967295, 7, 40960, 4096, 4294967295, 7,
45056, 4096, 4294967295, 7, 49152, 4096]] is too short
From schema:
/proj/mtk19347/cros/src/third_party/kernel/v5.10/Documentation/devicetr
ee/bindings/display/mediatek/mediatek,ethdr.yaml
Regards,
Nancy
>
prev parent reply other threads:[~2023-03-13 7:20 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-06-08 4:38 [RESEND v5 0/3] MediaTek MT8195 display binding Bo-Chen Chen
2022-06-08 4:38 ` [RESEND v5 1/3] dt-bindings: mediatek: add vdosys1 RDMA definition for mt8195 Bo-Chen Chen
2022-06-08 4:38 ` [RESEND v5 2/3] dt-bindings: reset: mt8195: add vdosys1 reset control bit Bo-Chen Chen
2022-06-08 4:38 ` [RESEND v5 3/3] dt-bindings: mediatek: add ethdr definition for mt8195 Bo-Chen Chen
2022-06-08 13:45 ` Rob Herring
2022-06-08 15:40 ` Rex-BC Chen
2023-03-13 7:19 ` Nancy Lin (林欣螢) [this message]
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=915c9eebf8412fc092686626ce02e45a5d0f7841.camel@mediatek.com \
--to=nancy.lin@mediatek.com \
--cc=Project_Global_Chrome_Upstream_Group@mediatek.com \
--cc=Rex-BC.Chen@mediatek.com \
--cc=airlied@linux.ie \
--cc=angelogioacchino.delregno@collabora.com \
--cc=chunkuang.hu@kernel.org \
--cc=ck.hu@mediatek.com \
--cc=devicetree@vger.kernel.org \
--cc=dri-devel@lists.freedesktop.org \
--cc=krzysztof.kozlowski+dt@linaro.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mediatek@lists.infradead.org \
--cc=matthias.bgg@gmail.com \
--cc=p.zabel@pengutronix.de \
--cc=pavel@ucw.cz \
--cc=robh+dt@kernel.org \
--cc=robh@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