From: Rex-BC Chen <rex-bc.chen@mediatek.com>
To: <chunkuang.hu@kernel.org>, <matthias.bgg@gmail.com>,
<robh+dt@kernel.org>
Cc: <p.zabel@pengutronix.de>, <airlied@linux.ie>, <daniel@ffwll.ch>,
<jassisinghbrar@gmail.com>, <fparent@baylibre.com>,
<yongqiang.niu@mediatek.com>, <hsinyi@chromium.org>,
<devicetree@vger.kernel.org>,
<linux-arm-kernel@lists.infradead.org>,
<linux-mediatek@lists.infradead.org>,
<linux-kernel@vger.kernel.org>, <dri-devel@lists.freedesktop.org>,
<Project_Global_Chrome_Upstream_Group@mediatek.com>,
Rex-BC Chen <rex-bc.chen@mediatek.com>
Subject: [v2,2/6] dt-bindings: display: mediatek: update supported SoC
Date: Tue, 15 Feb 2022 15:59:49 +0800 [thread overview]
Message-ID: <20220215075953.3310-3-rex-bc.chen@mediatek.com> (raw)
In-Reply-To: <20220215075953.3310-1-rex-bc.chen@mediatek.com>
Add decriptions about supported SoC: MT8186.
Signed-off-by: Rex-BC Chen <rex-bc.chen@mediatek.com>
---
.../devicetree/bindings/display/mediatek/mediatek,disp.txt | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/Documentation/devicetree/bindings/display/mediatek/mediatek,disp.txt b/Documentation/devicetree/bindings/display/mediatek/mediatek,disp.txt
index 78044c340e20..f22b3d90d45a 100644
--- a/Documentation/devicetree/bindings/display/mediatek/mediatek,disp.txt
+++ b/Documentation/devicetree/bindings/display/mediatek/mediatek,disp.txt
@@ -44,7 +44,7 @@ Required properties (all function blocks):
"mediatek,<chip>-dpi" - DPI controller, see mediatek,dpi.txt
"mediatek,<chip>-disp-mutex" - display mutex
"mediatek,<chip>-disp-od" - overdrive
- the supported chips are mt2701, mt7623, mt2712, mt8167, mt8173, mt8183 and mt8192.
+ the supported chips are mt2701, mt7623, mt2712, mt8167, mt8173, mt8183, mt8186 and mt8192.
- reg: Physical base address and length of the function block register space
- interrupts: The interrupt signal from the function block (required, except for
merge and split function blocks).
--
2.18.0
next prev parent reply other threads:[~2022-02-15 8:02 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20220215075953.3310-1-rex-bc.chen@mediatek.com>
2022-02-15 7:59 ` [v2,1/6] dt-bindings: arm: mediatek: mmsys: add support for MT8186 Rex-BC Chen
2022-02-15 7:59 ` Rex-BC Chen [this message]
2022-02-15 8:48 ` [v2,2/6] dt-bindings: display: mediatek: update supported SoC CK Hu
2022-02-15 9:07 ` Rex-BC Chen
2022-02-15 7:59 ` [v2,3/6] soc: mediatek: mmsys: add mt8186 mmsys routing table Rex-BC Chen
2022-02-15 7:59 ` [v2,4/6] soc: mediatek: add MTK mutex support for MT8186 Rex-BC Chen
2022-02-15 7:59 ` [v2,5/6] drm/mediatek: separate postmask component from mtk_disp_drv.c Rex-BC Chen
2022-02-15 9:35 ` [v2, 5/6] " CK Hu
2022-02-15 11:47 ` Rex-BC Chen
2022-02-15 7:59 ` [v2,6/6] drm/mediatek: add display support for MT8186 Rex-BC Chen
2022-02-16 1:56 ` CK 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=20220215075953.3310-3-rex-bc.chen@mediatek.com \
--to=rex-bc.chen@mediatek.com \
--cc=Project_Global_Chrome_Upstream_Group@mediatek.com \
--cc=airlied@linux.ie \
--cc=chunkuang.hu@kernel.org \
--cc=daniel@ffwll.ch \
--cc=devicetree@vger.kernel.org \
--cc=dri-devel@lists.freedesktop.org \
--cc=fparent@baylibre.com \
--cc=hsinyi@chromium.org \
--cc=jassisinghbrar@gmail.com \
--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=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