From: Matthias Brugger <matthias.bgg@gmail.com> To: Rob Herring <robh+dt@kernel.org>, Moudy Ho <moudy.ho@mediatek.com> Cc: Krzysztof Kozlowski <krzysztof.kozlowski+dt@linaro.org>, AngeloGioacchino Del Regno <angelogioacchino.delregno@collabora.com>, Chun-Kuang Hu <chunkuang.hu@kernel.org>, linux-kernel@vger.kernel.org, devicetree@vger.kernel.org, linux-arm-kernel@lists.infradead.org, linux-mediatek@lists.infradead.org, Project_Global_Chrome_Upstream_Group@mediatek.com Subject: Re: [PATCH v4 1/8] dt-bindings: arm: mediatek: mmsys: Add support for MT8195 VPPSYS Date: Mon, 19 Dec 2022 16:17:09 +0100 [thread overview] Message-ID: <ba8ce731-2d9c-901f-e208-deafe589b723@gmail.com> (raw) In-Reply-To: <CAL_JsqKdaVmGKSwR0yiYGKc6Kp6jki632GA6CBOOjGzUmvSRWA@mail.gmail.com> On 19/12/2022 14:44, Rob Herring wrote: > On Wed, Dec 7, 2022 at 3:49 AM Moudy Ho <moudy.ho@mediatek.com> wrote: >> >> For MT8195, VPPSYS0 and VPPSYS1 are 2 display pipes with >> hardware differences in power domains, clocks and subsystem counts, >> which should be determined by compatible names. >> >> Signed-off-by: Moudy Ho <moudy.ho@mediatek.com> >> Acked-by: Krzysztof Kozlowski <krzysztof.kozlowski@linaro.org> >> --- >> .../devicetree/bindings/arm/mediatek/mediatek,mmsys.yaml | 5 ++++- >> 1 file changed, 4 insertions(+), 1 deletion(-) > > This landed in today's linux-next causing the following binding > warnings. Is this a fix? Only fixes for 6.2 should be added during the > merge window. > No it's not a fix, it's queued for the next -rc phase. I didn't know of the limitation of linux-next only allowing fixes in the merge window. Actually the patch is wrong. It shouldn't include "mediatek,mt8195-mmsys" as fallback for mediatek,mt8195-vppsys[0,1]. I'll revert the whole series from v6.2-tmp/dts64 and v6.2-tmp/soc Regards, Matthias > /builds/robherring/linux-dt/Documentation/devicetree/bindings/arm/mediatek/mediatek,mt8195-clock.example.dtb: > clock-controller@14000000: $nodename:0: 'clock-controller@14000000' > does not match '^syscon@[0-9a-f]+$' > From schema: > /builds/robherring/linux-dt/Documentation/devicetree/bindings/arm/mediatek/mediatek,mmsys.yaml > /builds/robherring/linux-dt/Documentation/devicetree/bindings/arm/mediatek/mediatek,mt8195-clock.example.dtb: > clock-controller@14000000: compatible: 'oneOf' conditional failed, one > must be fixed: > ['mediatek,mt8195-vppsys0'] is too short > 'mediatek,mt8195-vppsys0' is not one of > ['mediatek,mt2701-mmsys', 'mediatek,mt2712-mmsys', > 'mediatek,mt6765-mmsys', 'mediatek,mt6779-mmsys', > 'mediatek,mt6795-mmsys', 'mediatek,mt6797-mmsys', > 'mediatek,mt8167-mmsys', 'mediatek,mt8173-mmsys', > 'mediatek,mt8183-mmsys', 'mediatek,mt8186-mmsys', > 'mediatek,mt8188-vdosys0', 'mediatek,mt8192-mmsys', > 'mediatek,mt8365-mmsys'] > 'mediatek,mt8195-mmsys' was expected > 'mediatek,mt7623-mmsys' was expected > From schema: > /builds/robherring/linux-dt/Documentation/devicetree/bindings/arm/mediatek/mediatek,mmsys.yaml
WARNING: multiple messages have this Message-ID (diff)
From: Matthias Brugger <matthias.bgg@gmail.com> To: Rob Herring <robh+dt@kernel.org>, Moudy Ho <moudy.ho@mediatek.com> Cc: Krzysztof Kozlowski <krzysztof.kozlowski+dt@linaro.org>, AngeloGioacchino Del Regno <angelogioacchino.delregno@collabora.com>, Chun-Kuang Hu <chunkuang.hu@kernel.org>, linux-kernel@vger.kernel.org, devicetree@vger.kernel.org, linux-arm-kernel@lists.infradead.org, linux-mediatek@lists.infradead.org, Project_Global_Chrome_Upstream_Group@mediatek.com Subject: Re: [PATCH v4 1/8] dt-bindings: arm: mediatek: mmsys: Add support for MT8195 VPPSYS Date: Mon, 19 Dec 2022 16:17:09 +0100 [thread overview] Message-ID: <ba8ce731-2d9c-901f-e208-deafe589b723@gmail.com> (raw) In-Reply-To: <CAL_JsqKdaVmGKSwR0yiYGKc6Kp6jki632GA6CBOOjGzUmvSRWA@mail.gmail.com> On 19/12/2022 14:44, Rob Herring wrote: > On Wed, Dec 7, 2022 at 3:49 AM Moudy Ho <moudy.ho@mediatek.com> wrote: >> >> For MT8195, VPPSYS0 and VPPSYS1 are 2 display pipes with >> hardware differences in power domains, clocks and subsystem counts, >> which should be determined by compatible names. >> >> Signed-off-by: Moudy Ho <moudy.ho@mediatek.com> >> Acked-by: Krzysztof Kozlowski <krzysztof.kozlowski@linaro.org> >> --- >> .../devicetree/bindings/arm/mediatek/mediatek,mmsys.yaml | 5 ++++- >> 1 file changed, 4 insertions(+), 1 deletion(-) > > This landed in today's linux-next causing the following binding > warnings. Is this a fix? Only fixes for 6.2 should be added during the > merge window. > No it's not a fix, it's queued for the next -rc phase. I didn't know of the limitation of linux-next only allowing fixes in the merge window. Actually the patch is wrong. It shouldn't include "mediatek,mt8195-mmsys" as fallback for mediatek,mt8195-vppsys[0,1]. I'll revert the whole series from v6.2-tmp/dts64 and v6.2-tmp/soc Regards, Matthias > /builds/robherring/linux-dt/Documentation/devicetree/bindings/arm/mediatek/mediatek,mt8195-clock.example.dtb: > clock-controller@14000000: $nodename:0: 'clock-controller@14000000' > does not match '^syscon@[0-9a-f]+$' > From schema: > /builds/robherring/linux-dt/Documentation/devicetree/bindings/arm/mediatek/mediatek,mmsys.yaml > /builds/robherring/linux-dt/Documentation/devicetree/bindings/arm/mediatek/mediatek,mt8195-clock.example.dtb: > clock-controller@14000000: compatible: 'oneOf' conditional failed, one > must be fixed: > ['mediatek,mt8195-vppsys0'] is too short > 'mediatek,mt8195-vppsys0' is not one of > ['mediatek,mt2701-mmsys', 'mediatek,mt2712-mmsys', > 'mediatek,mt6765-mmsys', 'mediatek,mt6779-mmsys', > 'mediatek,mt6795-mmsys', 'mediatek,mt6797-mmsys', > 'mediatek,mt8167-mmsys', 'mediatek,mt8173-mmsys', > 'mediatek,mt8183-mmsys', 'mediatek,mt8186-mmsys', > 'mediatek,mt8188-vdosys0', 'mediatek,mt8192-mmsys', > 'mediatek,mt8365-mmsys'] > 'mediatek,mt8195-mmsys' was expected > 'mediatek,mt7623-mmsys' was expected > From schema: > /builds/robherring/linux-dt/Documentation/devicetree/bindings/arm/mediatek/mediatek,mmsys.yaml _______________________________________________ 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:[~2022-12-19 15:18 UTC|newest] Thread overview: 38+ messages / expand[flat|nested] mbox.gz Atom feed top 2022-12-07 9:49 [PATCH v4 0/8] add support MDP3 on MT8195 platform Moudy Ho 2022-12-07 9:49 ` Moudy Ho 2022-12-07 9:49 ` [PATCH v4 1/8] dt-bindings: arm: mediatek: mmsys: Add support for MT8195 VPPSYS Moudy Ho 2022-12-07 9:49 ` Moudy Ho 2022-12-07 10:15 ` AngeloGioacchino Del Regno 2022-12-07 10:15 ` AngeloGioacchino Del Regno 2022-12-19 13:44 ` Rob Herring 2022-12-19 13:44 ` Rob Herring 2022-12-19 15:17 ` Matthias Brugger [this message] 2022-12-19 15:17 ` Matthias Brugger 2022-12-19 15:31 ` Krzysztof Kozlowski 2022-12-19 15:31 ` Krzysztof Kozlowski 2022-12-07 9:49 ` [PATCH v4 2/8] dt-bindings: soc: mediatek: " Moudy Ho 2022-12-07 9:49 ` Moudy Ho 2022-12-07 9:49 ` [PATCH v4 3/8] arm64: dts: mediatek: mt8195: add MMSYS configuration for VPPSYS Moudy Ho 2022-12-07 9:49 ` Moudy Ho 2022-12-07 10:15 ` AngeloGioacchino Del Regno 2022-12-07 10:15 ` AngeloGioacchino Del Regno 2022-12-07 9:49 ` [PATCH v4 4/8] arm64: dts: mediatek: mt8195: add MUTEX " Moudy Ho 2022-12-07 9:49 ` Moudy Ho 2022-12-07 9:49 ` [PATCH v4 5/8] soc: mediatek: mmsys: add support for MT8195 VPPSYS Moudy Ho 2022-12-07 9:49 ` Moudy Ho 2022-12-07 9:49 ` [PATCH v4 6/8] soc: mediatek: mmsys: add config api for RSZ switching and DCM Moudy Ho 2022-12-07 9:49 ` Moudy Ho 2022-12-07 9:49 ` [PATCH v4 7/8] soc: mediatek: mutex: Add mtk_mutex_set_mod support to set MOD1 Moudy Ho 2022-12-07 9:49 ` Moudy Ho 2022-12-07 9:49 ` [PATCH v4 8/8] soc: mediatek: mutex: support MT8195 VPPSYS Moudy Ho 2022-12-07 9:49 ` Moudy Ho 2022-12-16 12:33 ` [PATCH v4 0/8] add support MDP3 on MT8195 platform Matthias Brugger 2022-12-16 12:33 ` Matthias Brugger 2022-12-19 15:17 ` Matthias Brugger 2022-12-19 15:17 ` Matthias Brugger 2022-12-20 2:14 ` Moudy Ho (何宗原) 2022-12-20 2:14 ` Moudy Ho (何宗原) 2022-12-20 3:40 ` Moudy Ho (何宗原) 2022-12-20 3:40 ` Moudy Ho (何宗原) 2022-12-20 14:55 ` Matthias Brugger 2022-12-20 14:55 ` Matthias Brugger
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=ba8ce731-2d9c-901f-e208-deafe589b723@gmail.com \ --to=matthias.bgg@gmail.com \ --cc=Project_Global_Chrome_Upstream_Group@mediatek.com \ --cc=angelogioacchino.delregno@collabora.com \ --cc=chunkuang.hu@kernel.org \ --cc=devicetree@vger.kernel.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=moudy.ho@mediatek.com \ --cc=robh+dt@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: 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.