From: Matthias Brugger <matthias.bgg@gmail.com>
To: Allen-KH Cheng <allen-kh.cheng@mediatek.com>,
Rob Herring <robh+dt@kernel.org>,
Krzysztof Kozlowski <krzysztof.kozlowski@canonical.com>
Cc: Project_Global_Chrome_Upstream_Group@mediatek.com,
devicetree@vger.kernel.org, linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org, linux-mediatek@lists.infradead.org,
Chen-Yu Tsai <wenst@chromium.org>
Subject: Re: [PATCH v3 0/5] Complete driver nodes for MT8192 SoC
Date: Mon, 29 Aug 2022 16:50:51 +0200 [thread overview]
Message-ID: <cd178f8c-76f0-4494-71c4-a658ee517b70@gmail.com> (raw)
In-Reply-To: <20220712114046.15574-1-allen-kh.cheng@mediatek.com>
Whole series applied.
Thanks!
On 12/07/2022 13:40, Allen-KH Cheng wrote:
> This series are based on matthias.bgg/linux.git, for-next.
>
> I remove vcodec lat and core nodes PATCH from series and will comfirm
> clocks usage then resend PATCH.
>
> Also should reference below PATCH for dsi in chunkuang.hu/linux.git
> dt-bindings: display: mediatek: dsi: Convert dsi_dtbinding to .yaml
>
> changes since v2:
> - add mmsys #reset-cells PATCH
> - add missing fallback compatible
> - add display aliases
> - remove vcodec lat and core nodes PATCH
>
> changes since v1:
> - add Reviewed-by Tag
> - rename dsi-phy from dsi-dphy
> - add missing power-domains in disp mutex
> - Add remove mt8192 display rdma compatible PATCH in series
> - use "mediatek,mt8183-disp-rdma" as fallback
> - remove mediatek,larb from rdma node
> - remove syscon-dsi and add power-domains in dsi
> - add reset property in dsi and mt8192-resets.h
> - correct Typo: s/ndoe/node in commit message
>
> Allen-KH Cheng (5):
> arm64: dts: mt8192: Add pwm node
> arm64: dts: mt8192: Add mipi_tx node
> arm64: dts: mediatek: Add mmsys #reset-cells property for mt8192
> arm64: dts: mt8192: Add display nodes
> arm64: dts: mt8192: Add dsi node
>
> arch/arm64/boot/dts/mediatek/mt8192.dtsi | 188 +++++++++++++++++++++++
> 1 file changed, 188 insertions(+)
>
prev parent reply other threads:[~2022-08-29 14:50 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-07-12 11:40 [PATCH v3 0/5] Complete driver nodes for MT8192 SoC Allen-KH Cheng
2022-07-12 11:40 ` [PATCH v3 1/5] arm64: dts: mt8192: Add pwm node Allen-KH Cheng
2022-07-12 11:40 ` [PATCH v3 2/5] arm64: dts: mt8192: Add mipi_tx node Allen-KH Cheng
2022-07-12 11:40 ` [PATCH v3 3/5] arm64: dts: mediatek: Add mmsys #reset-cells property for mt8192 Allen-KH Cheng
2022-07-13 8:10 ` AngeloGioacchino Del Regno
2022-07-18 23:18 ` Nícolas F. R. A. Prado
2022-07-12 11:40 ` [PATCH v3 4/5] arm64: dts: mt8192: Add display nodes Allen-KH Cheng
2022-07-13 8:10 ` AngeloGioacchino Del Regno
2022-07-18 23:19 ` Nícolas F. R. A. Prado
2022-07-12 11:40 ` [PATCH v3 5/5] arm64: dts: mt8192: Add dsi node Allen-KH Cheng
2022-07-18 23:23 ` [PATCH v3 0/5] Complete driver nodes for MT8192 SoC Nícolas F. R. A. Prado
2022-07-25 6:45 ` Chen-Yu Tsai
2022-08-29 14:50 ` 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=cd178f8c-76f0-4494-71c4-a658ee517b70@gmail.com \
--to=matthias.bgg@gmail.com \
--cc=Project_Global_Chrome_Upstream_Group@mediatek.com \
--cc=allen-kh.cheng@mediatek.com \
--cc=devicetree@vger.kernel.org \
--cc=krzysztof.kozlowski@canonical.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 \
--cc=wenst@chromium.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).