From: "Jianjun Wang (王建军)" <Jianjun.Wang@mediatek.com>
To: "frank-w@public-files.de" <frank-w@public-files.de>
Cc: "linux-mediatek@lists.infradead.org"
<linux-mediatek@lists.infradead.org>,
"robh+dt@kernel.org" <robh+dt@kernel.org>,
"linux@fw-web.de" <linux@fw-web.de>,
"devicetree@vger.kernel.org" <devicetree@vger.kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"robh@kernel.org" <robh@kernel.org>,
"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>,
"linux-pci@vger.kernel.org" <linux-pci@vger.kernel.org>,
Ryder Lee <Ryder.Lee@mediatek.com>,
"bhelgaas@google.com" <bhelgaas@google.com>
Subject: Re: Aw: Re: [PATCH v2 1/2] dt-bindings: PCI: mediatek-gen3: add SoC based clock config
Date: Tue, 1 Nov 2022 12:06:23 +0000 [thread overview]
Message-ID: <47e696ace4cc28566fea88d73d857902434ce48e.camel@mediatek.com> (raw)
In-Reply-To: <trinity-a848b9af-2c0e-41fb-9073-97a7d05011c8-1666975323664@3c-app-gmx-bs17>
Hi Frank,
On Fri, 2022-10-28 at 18:42 +0200, Frank Wunderlich wrote:
> Hi
> > Gesendet: Freitag, 28. Oktober 2022 um 11:24 Uhr
> > Von: "Jianjun Wang" <jianjun.wang@mediatek.com>
> > An: "Frank Wunderlich" <linux@fw-web.de>,
> > linux-mediatek@lists.infradead.org
> > Cc: "Frank Wunderlich" <frank-w@public-files.de>, "Ryder Lee" <
> > ryder.lee@mediatek.com>, "Bjorn Helgaas" <bhelgaas@google.com>,
> > "Rob Herring" <robh+dt@kernel.org>, "Krzysztof Kozlowski" <
> > krzysztof.kozlowski+dt@linaro.org>, "Matthias Brugger" <
> > matthias.bgg@gmail.com>, linux-pci@vger.kernel.org,
> > devicetree@vger.kernel.org, linux-kernel@vger.kernel.org,
> > linux-arm-kernel@lists.infradead.org, "Rob Herring" <
> > robh@kernel.org>
> > Betreff: Re: [PATCH v2 1/2] dt-bindings: PCI: mediatek-gen3: add
> > SoC based clock config
> >
> > Hi Frank,
> >
> > After apply this patch, we found some dtbs_check error with the
> > following patch which adds the PCIe node for MT8195:
> >
> >
https://lore.kernel.org/linux-pci/20221020111925.30002-3-tinghan.shen@mediatek.com/
> >
> > arch/arm64/boot/dts/mediatek/mt8195-cherry-tomato-r2.dtb:
> > pcie@112f0000
> > : clock-names: 5: 'top_133m' was expected
> > From schema: Documentation/devicetree/bindings/pci/mediatek-
> > pcie-
> > gen3.yaml
> > arch/arm64/boot/dts/mediatek/mt8195-cherry-tomato-r2.dtb:
> > pcie@112f8000
> > : clock-names: 5: 'top_133m' was expected
> > From schema: Documentation/devicetree/bindings/pci/mediatek-
> > pcie-
> > gen3.yaml
> >
> > Did you get the same error when adding the PCIe node for MT7986?
>
> i'm sure i had tested the yaml and did not get any error, but on my
> retest i get same error for mt7986 too...
>
> maybe the right way is to remove the contains in the mediatek,mt8192-
> pcie if condition (to match only if this condition is no fallback),
> then it is clean for me. Can you test it with your patches?
Sorry for the late response, I have tested with the patch for MT8195,
and it works, thanks!
>
> allOf:
> - $ref: /schemas/pci/pci-bus.yaml#
> - if:
> properties:
> compatible:
> #contains:
> const: mediatek,mt8192-pcie
> then:
> properties:
> clock-names:
> items:
> - const: pl_250m
> - const: tl_26m
> - const: tl_96m
> - const: tl_32k
> - const: peri_26m
> - const: top_133m
>
>
> regards Frank
>
> regards Frank
next prev parent reply other threads:[~2022-11-01 12:57 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-10-25 7:28 [PATCH v2 0/2] rework mtk pcie-gen3 bindings and support mt7986 Frank Wunderlich
2022-10-25 7:28 ` [PATCH v2 1/2] dt-bindings: PCI: mediatek-gen3: add SoC based clock config Frank Wunderlich
2022-10-28 9:24 ` Jianjun Wang
2022-10-28 10:31 ` Frank Wunderlich
2022-10-28 16:42 ` Aw: " Frank Wunderlich
2022-11-01 12:06 ` Jianjun Wang (王建军) [this message]
2022-10-25 7:28 ` [PATCH v2 2/2] dt-bindings: PCI: mediatek-gen3: add support for mt7986 Frank Wunderlich
2022-10-25 11:10 ` AngeloGioacchino Del Regno
2022-10-26 19:46 ` Rob Herring
2022-10-26 19:46 ` 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=47e696ace4cc28566fea88d73d857902434ce48e.camel@mediatek.com \
--to=jianjun.wang@mediatek.com \
--cc=Ryder.Lee@mediatek.com \
--cc=bhelgaas@google.com \
--cc=devicetree@vger.kernel.org \
--cc=frank-w@public-files.de \
--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=linux-pci@vger.kernel.org \
--cc=linux@fw-web.de \
--cc=matthias.bgg@gmail.com \
--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