From: Matthias Brugger <matthias.bgg@gmail.com>
To: Chen-Yu Tsai <wenst@chromium.org>,
AngeloGioacchino Del Regno
<angelogioacchino.delregno@collabora.com>
Cc: devicetree@vger.kernel.org, linux-arm-kernel@lists.infradead.org,
linux-mediatek@lists.infradead.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] arm64: dts: mediatek: mt8195: Correct clock order for dp_intf*
Date: Mon, 2 Sep 2024 17:50:37 +0200 [thread overview]
Message-ID: <b0d83115-db4f-4c3b-9cfe-e889b1410c44@gmail.com> (raw)
In-Reply-To: <20240802070951.1086616-1-wenst@chromium.org>
On 02/08/2024 09:09, Chen-Yu Tsai wrote:
> The clocks for dp_intf* device nodes are given in the wrong order,
> causing the binding validation to fail.
>
> Fixes: 6c2503b5856a ("arm64: dts: mt8195: Add dp-intf nodes")
> Signed-off-by: Chen-Yu Tsai <wenst@chromium.org>
Applied, thanks!
> ---
> arch/arm64/boot/dts/mediatek/mt8195.dtsi | 12 ++++++------
> 1 file changed, 6 insertions(+), 6 deletions(-)
>
> diff --git a/arch/arm64/boot/dts/mediatek/mt8195.dtsi b/arch/arm64/boot/dts/mediatek/mt8195.dtsi
> index 989e8ac545ac..e89ba384c4aa 100644
> --- a/arch/arm64/boot/dts/mediatek/mt8195.dtsi
> +++ b/arch/arm64/boot/dts/mediatek/mt8195.dtsi
> @@ -3252,10 +3252,10 @@ dp_intf0: dp-intf@1c015000 {
> compatible = "mediatek,mt8195-dp-intf";
> reg = <0 0x1c015000 0 0x1000>;
> interrupts = <GIC_SPI 657 IRQ_TYPE_LEVEL_HIGH 0>;
> - clocks = <&vdosys0 CLK_VDO0_DP_INTF0>,
> - <&vdosys0 CLK_VDO0_DP_INTF0_DP_INTF>,
> + clocks = <&vdosys0 CLK_VDO0_DP_INTF0_DP_INTF>,
> + <&vdosys0 CLK_VDO0_DP_INTF0>,
> <&apmixedsys CLK_APMIXED_TVDPLL1>;
> - clock-names = "engine", "pixel", "pll";
> + clock-names = "pixel", "engine", "pll";
> status = "disabled";
> };
>
> @@ -3522,10 +3522,10 @@ dp_intf1: dp-intf@1c113000 {
> reg = <0 0x1c113000 0 0x1000>;
> interrupts = <GIC_SPI 513 IRQ_TYPE_LEVEL_HIGH 0>;
> power-domains = <&spm MT8195_POWER_DOMAIN_VDOSYS1>;
> - clocks = <&vdosys1 CLK_VDO1_DP_INTF0_MM>,
> - <&vdosys1 CLK_VDO1_DPINTF>,
> + clocks = <&vdosys1 CLK_VDO1_DPINTF>,
> + <&vdosys1 CLK_VDO1_DP_INTF0_MM>,
> <&apmixedsys CLK_APMIXED_TVDPLL2>;
> - clock-names = "engine", "pixel", "pll";
> + clock-names = "pixel", "engine", "pll";
> status = "disabled";
> };
>
prev parent reply other threads:[~2024-09-02 15:50 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-08-02 7:09 [PATCH] arm64: dts: mediatek: mt8195: Correct clock order for dp_intf* Chen-Yu Tsai
2024-08-30 20:49 ` Nícolas F. R. A. Prado
2024-09-02 15:50 ` Matthias Brugger [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=b0d83115-db4f-4c3b-9cfe-e889b1410c44@gmail.com \
--to=matthias.bgg@gmail.com \
--cc=angelogioacchino.delregno@collabora.com \
--cc=devicetree@vger.kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mediatek@lists.infradead.org \
--cc=wenst@chromium.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;
as well as URLs for NNTP newsgroup(s).