dri-devel.lists.freedesktop.org archive mirror
 help / color / mirror / Atom feed
From: Matthias Brugger <matthias.bgg@gmail.com>
To: Rex-BC Chen <rex-bc.chen@mediatek.com>,
	chunkuang.hu@kernel.org, robh+dt@kernel.org, krzk+dt@kernel.org
Cc: devicetree@vger.kernel.org, airlied@linux.ie,
	jason-jh.lin@mediatek.com, linux-kernel@vger.kernel.org,
	dri-devel@lists.freedesktop.org,
	Project_Global_Chrome_Upstream_Group@mediatek.com,
	nancy.lin@mediatek.com, linux-mediatek@lists.infradead.org,
	yongqiang.niu@mediatek.com, linux-arm-kernel@lists.infradead.org,
	allen-kh.cheng@mediatek.com
Subject: Re: [PATCH V2 2/3] arm64: dts: mt8183: Update disp_aal node compatible
Date: Fri, 22 Apr 2022 16:19:37 +0200	[thread overview]
Message-ID: <4373b922-bd07-c02d-e43f-0426690cf47d@gmail.com> (raw)
In-Reply-To: <20220411035843.19847-3-rex-bc.chen@mediatek.com>



On 11/04/2022 05:58, Rex-BC Chen wrote:
> The driver data of MT8183 and MT8173 are different.
> The value of has_gamma for MT8173 is true while the value of MT8183 is
> false. Therefore, the compatible of disp_aal for MT8183 is not suitable
> for the compatible for MT8173.
> 
> Signed-off-by: Rex-BC Chen <rex-bc.chen@mediatek.com>
> Reviewed-by: AngeloGioacchino Del Regno <angelogioacchino.delregno@collabora.com>

Applied thanks!

> ---
>   arch/arm64/boot/dts/mediatek/mt8183.dtsi | 3 +--
>   1 file changed, 1 insertion(+), 2 deletions(-)
> 
> diff --git a/arch/arm64/boot/dts/mediatek/mt8183.dtsi b/arch/arm64/boot/dts/mediatek/mt8183.dtsi
> index 4b08691ed39e..a3616005d65c 100644
> --- a/arch/arm64/boot/dts/mediatek/mt8183.dtsi
> +++ b/arch/arm64/boot/dts/mediatek/mt8183.dtsi
> @@ -1466,8 +1466,7 @@
>   		};
>   
>   		aal0: aal@14010000 {
> -			compatible = "mediatek,mt8183-disp-aal",
> -				     "mediatek,mt8173-disp-aal";
> +			compatible = "mediatek,mt8183-disp-aal";
>   			reg = <0 0x14010000 0 0x1000>;
>   			interrupts = <GIC_SPI 233 IRQ_TYPE_LEVEL_LOW>;
>   			power-domains = <&spm MT8183_POWER_DOMAIN_DISP>;

  reply	other threads:[~2022-04-22 14:19 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-04-11  3:58 [PATCH V2 0/3] Update MediaTek disp_aal dt-binding Rex-BC Chen
2022-04-11  3:58 ` [PATCH V2 1/3] dt-bindings: display: mediatek: Update disp_aal binding for MT8183 Rex-BC Chen
2022-04-13 23:02   ` Rob Herring
2022-04-16 14:20     ` Chun-Kuang Hu
2022-04-11  3:58 ` [PATCH V2 2/3] arm64: dts: mt8183: Update disp_aal node compatible Rex-BC Chen
2022-04-22 14:19   ` Matthias Brugger [this message]
2022-04-11  3:58 ` [PATCH V2 3/3] dt-bindings: display: mediatek: Update disp_aal binding for MT8192 and MT8195 Rex-BC Chen
2022-04-13 23:02   ` Rob Herring
2022-04-16 14:21     ` Chun-Kuang Hu

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=4373b922-bd07-c02d-e43f-0426690cf47d@gmail.com \
    --to=matthias.bgg@gmail.com \
    --cc=Project_Global_Chrome_Upstream_Group@mediatek.com \
    --cc=airlied@linux.ie \
    --cc=allen-kh.cheng@mediatek.com \
    --cc=chunkuang.hu@kernel.org \
    --cc=devicetree@vger.kernel.org \
    --cc=dri-devel@lists.freedesktop.org \
    --cc=jason-jh.lin@mediatek.com \
    --cc=krzk+dt@kernel.org \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mediatek@lists.infradead.org \
    --cc=nancy.lin@mediatek.com \
    --cc=rex-bc.chen@mediatek.com \
    --cc=robh+dt@kernel.org \
    --cc=yongqiang.niu@mediatek.com \
    /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).