From: Rex-BC Chen <rex-bc.chen@mediatek.com>
To: <robh+dt@kernel.org>, <krzysztof.kozlowski+dt@linaro.org>,
<chunkuang.hu@kernel.org>, <p.zabel@pengutronix.de>
Cc: <airlied@linux.ie>, <matthias.bgg@gmail.com>,
<angelogioacchino.delregno@collabora.com>,
<jason-jh.lin@mediatek.com>, <nancy.lin@mediatek.com>,
<devicetree@vger.kernel.org>, <linux-kernel@vger.kernel.org>,
<dri-devel@lists.freedesktop.org>,
<linux-mediatek@lists.infradead.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 0/3] MediaTek MT8195 display binding
Date: Mon, 9 May 2022 12:42:59 +0800 [thread overview]
Message-ID: <20220509044302.27878-1-rex-bc.chen@mediatek.com> (raw)
Add this series to present MediaTek display binding for MT8195.
The reason I send this series is Jason and Nancy's binding patches are
never received by devicetree mail server.
Therefore, I help them to resend binding patches.
Changes for v2:
1. This patch is based on linux next-20220506.
2. Jason's patches are accepted and I drop them.
[1]: https://lore.kernel.org/all/20220504091440.2052-2-nancy.lin@mediatek.com/
Nancy.Lin (3):
dt-bindings: mediatek: add vdosys1 RDMA definition for mt8195
dt-bindings: reset: mt8195: add vdosys1 reset control bit
dt-bindings: mediatek: add ethdr definition for mt8195
.../display/mediatek/mediatek,ethdr.yaml | 191 ++++++++++++++++++
.../display/mediatek/mediatek,mdp-rdma.yaml | 94 +++++++++
include/dt-bindings/reset/mt8195-resets.h | 45 +++++
3 files changed, 330 insertions(+)
create mode 100644 Documentation/devicetree/bindings/display/mediatek/mediatek,ethdr.yaml
create mode 100644 Documentation/devicetree/bindings/display/mediatek/mediatek,mdp-rdma.yaml
--
2.18.0
next reply other threads:[~2022-05-09 4:46 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-05-09 4:42 Rex-BC Chen [this message]
2022-05-09 4:43 ` [PATCH v2 1/3] dt-bindings: mediatek: add vdosys1 RDMA definition for mt8195 Rex-BC Chen
2022-05-09 7:31 ` Krzysztof Kozlowski
2022-05-09 8:45 ` Rex-BC Chen
2022-05-10 2:23 ` Rex-BC Chen
2022-05-10 10:28 ` Krzysztof Kozlowski
2022-05-10 10:37 ` Chen-Yu Tsai
2022-05-10 10:57 ` Krzysztof Kozlowski
2022-05-11 2:26 ` Rex-BC Chen
2022-05-11 7:21 ` Krzysztof Kozlowski
2022-05-09 12:20 ` Rob Herring
2022-05-30 7:06 ` Pavel Machek
2022-06-02 3:53 ` Rex-BC Chen
2022-05-09 4:43 ` [PATCH v2 2/3] dt-bindings: reset: mt8195: add vdosys1 reset control bit Rex-BC Chen
2022-05-09 4:43 ` [PATCH v2 3/3] dt-bindings: mediatek: add ethdr definition for mt8195 Rex-BC Chen
2022-05-09 7:35 ` Krzysztof Kozlowski
2022-05-09 8:54 ` Rex-BC Chen
2022-05-09 10:44 ` Krzysztof Kozlowski
2022-05-09 10:50 ` AngeloGioacchino Del Regno
2022-05-10 1:46 ` Rex-BC Chen
2022-05-10 11:19 ` Krzysztof Kozlowski
2022-05-11 2:29 ` Rex-BC Chen
2022-05-09 12:20 ` Rob Herring
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=20220509044302.27878-1-rex-bc.chen@mediatek.com \
--to=rex-bc.chen@mediatek.com \
--cc=Project_Global_Chrome_Upstream_Group@mediatek.com \
--cc=airlied@linux.ie \
--cc=angelogioacchino.delregno@collabora.com \
--cc=chunkuang.hu@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=dri-devel@lists.freedesktop.org \
--cc=jason-jh.lin@mediatek.com \
--cc=krzysztof.kozlowski+dt@linaro.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 \
/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).