From: Rex-BC Chen <rex-bc.chen@mediatek.com>
To: <chunkuang.hu@kernel.org>, <robh+dt@kernel.org>,
<krzk+dt@kernel.org>, <matthias.bgg@gmail.com>
Cc: <p.zabel@pengutronix.de>, <airlied@linux.ie>,
<yongqiang.niu@mediatek.com>, <jason-jh.lin@mediatek.com>,
<nancy.lin@mediatek.com>, <allen-kh.cheng@mediatek.com>,
<dri-devel@lists.freedesktop.org>,
<linux-mediatek@lists.infradead.org>,
<devicetree@vger.kernel.org>, <linux-kernel@vger.kernel.org>,
<linux-arm-kernel@lists.infradead.org>,
<Project_Global_Chrome_Upstream_Group@mediatek.com>,
Rex-BC Chen <rex-bc.chen@mediatek.com>
Subject: [PATCH V2 3/3] dt-bindings: display: mediatek: Update disp_aal binding for MT8192 and MT8195
Date: Mon, 11 Apr 2022 11:58:43 +0800 [thread overview]
Message-ID: <20220411035843.19847-4-rex-bc.chen@mediatek.com> (raw)
In-Reply-To: <20220411035843.19847-1-rex-bc.chen@mediatek.com>
Disp_aal of MT8192 and MT8195 are fully compatible with disp_aal of
MT8183. Therefore, we move the them to item "mediatek,mt8183-disp-aal".
Signed-off-by: Rex-BC Chen <rex-bc.chen@mediatek.com>
---
.../devicetree/bindings/display/mediatek/mediatek,aal.yaml | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/Documentation/devicetree/bindings/display/mediatek/mediatek,aal.yaml b/Documentation/devicetree/bindings/display/mediatek/mediatek,aal.yaml
index f118075e4a89..d4d585485e7b 100644
--- a/Documentation/devicetree/bindings/display/mediatek/mediatek,aal.yaml
+++ b/Documentation/devicetree/bindings/display/mediatek/mediatek,aal.yaml
@@ -27,12 +27,12 @@ properties:
- items:
- enum:
- mediatek,mt2712-disp-aal
- - mediatek,mt8192-disp-aal
- - mediatek,mt8195-disp-aal
- const: mediatek,mt8173-disp-aal
- items:
- enum:
- mediatek,mt8186-disp-aal
+ - mediatek,mt8192-disp-aal
+ - mediatek,mt8195-disp-aal
- const: mediatek,mt8183-disp-aal
reg:
--
2.18.0
_______________________________________________
Linux-mediatek mailing list
Linux-mediatek@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-mediatek
next prev parent reply other threads:[~2022-04-11 4:05 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
2022-04-11 3:58 ` Rex-BC Chen [this message]
2022-04-13 23:02 ` [PATCH V2 3/3] dt-bindings: display: mediatek: Update disp_aal binding for MT8192 and MT8195 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=20220411035843.19847-4-rex-bc.chen@mediatek.com \
--to=rex-bc.chen@mediatek.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=matthias.bgg@gmail.com \
--cc=nancy.lin@mediatek.com \
--cc=p.zabel@pengutronix.de \
--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).