From: Matthias Brugger <matthias.bgg@gmail.com>
To: AngeloGioacchino Del Regno
<angelogioacchino.delregno@collabora.com>,
robh+dt@kernel.org
Cc: devicetree@vger.kernel.org, linux-arm-kernel@lists.infradead.org,
linux-mediatek@lists.infradead.org, linux-kernel@vger.kernel.org,
kernel@collabora.com
Subject: Re: [PATCH] arm64: dts: mediatek: mt8173: Add gce-client-reg to display od/ufo
Date: Wed, 17 Nov 2021 18:49:21 +0100 [thread overview]
Message-ID: <003d475d-2dcd-ec24-0b9e-0cfd021f9da4@gmail.com> (raw)
In-Reply-To: <20211104135254.580257-1-angelogioacchino.delregno@collabora.com>
On 04/11/2021 14:52, AngeloGioacchino Del Regno wrote:
> In order to use CMDQ commands on these two IPs, we need to declare
> the appropriate mediatek,gce-client-reg for them.
>
> Signed-off-by: AngeloGioacchino Del Regno <angelogioacchino.delregno@collabora.com>
Now applied to v5.16-next/dts64 thanks!
> ---
> arch/arm64/boot/dts/mediatek/mt8173.dtsi | 2 ++
> 1 file changed, 2 insertions(+)
>
> diff --git a/arch/arm64/boot/dts/mediatek/mt8173.dtsi b/arch/arm64/boot/dts/mediatek/mt8173.dtsi
> index dee66e5f054c..2b7d331a4588 100644
> --- a/arch/arm64/boot/dts/mediatek/mt8173.dtsi
> +++ b/arch/arm64/boot/dts/mediatek/mt8173.dtsi
> @@ -1212,6 +1212,7 @@ ufoe@1401a000 {
> interrupts = <GIC_SPI 191 IRQ_TYPE_LEVEL_LOW>;
> power-domains = <&spm MT8173_POWER_DOMAIN_MM>;
> clocks = <&mmsys CLK_MM_DISP_UFOE>;
> + mediatek,gce-client-reg = <&gce SUBSYS_1401XXXX 0xa000 0x1000>;
> };
>
> dsi0: dsi@1401b000 {
> @@ -1316,6 +1317,7 @@ od@14023000 {
> compatible = "mediatek,mt8173-disp-od";
> reg = <0 0x14023000 0 0x1000>;
> clocks = <&mmsys CLK_MM_DISP_OD>;
> + mediatek,gce-client-reg = <&gce SUBSYS_1402XXXX 0x3000 0x1000>;
> };
>
> hdmi0: hdmi@14025000 {
>
prev parent reply other threads:[~2021-11-17 17:49 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-11-04 13:52 [PATCH] arm64: dts: mediatek: mt8173: Add gce-client-reg to display od/ufo AngeloGioacchino Del Regno
2021-11-17 17:49 ` 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=003d475d-2dcd-ec24-0b9e-0cfd021f9da4@gmail.com \
--to=matthias.bgg@gmail.com \
--cc=angelogioacchino.delregno@collabora.com \
--cc=devicetree@vger.kernel.org \
--cc=kernel@collabora.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mediatek@lists.infradead.org \
--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: 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