From: Matthias Brugger <matthias.bgg@gmail.com>
To: Chun-Jie Chen <chun-jie.chen@mediatek.com>,
Enric Balletbo Serra <eballetbo@gmail.com>,
Nicolas Boichat <drinkcat@chromium.org>,
Rob Herring <robh+dt@kernel.org>
Cc: linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org, devicetree@vger.kernel.org,
linux-mediatek@lists.infradead.org, srv_heupstream@mediatek.com,
Project_Global_Chrome_Upstream_Group@mediatek.com
Subject: Re: [v2 0/2] Mediatek MT8186 power domain support
Date: Mon, 28 Feb 2022 12:03:52 +0100 [thread overview]
Message-ID: <1b0ad14d-5843-b8f8-ad6b-d3366a611dde@gmail.com> (raw)
In-Reply-To: <20220215104917.5726-1-chun-jie.chen@mediatek.com>
On 15/02/2022 11:49, Chun-Jie Chen wrote:
> This patch series adds power domain support for MT8186
> and depends on [1] based on 5.17-rc1.
>
Whole series applied,
Thanks.
Matthias
> change since v1:
> - change to dual license in dt-binding
>
> [1] https://patchwork.kernel.org/project/linux-mediatek/list/?series=609799
>
> Chun-Jie Chen (2):
> dt-bindings: power: Add MT8186 power domains
> soc: mediatek: pm-domains: Add support for mt8186
>
> .../power/mediatek,power-controller.yaml | 1 +
> drivers/soc/mediatek/mt8186-pm-domains.h | 344 ++++++++++++++++++
> drivers/soc/mediatek/mtk-pm-domains.c | 5 +
> include/dt-bindings/power/mt8186-power.h | 32 ++
> include/linux/soc/mediatek/infracfg.h | 48 +++
> 5 files changed, 430 insertions(+)
> create mode 100644 drivers/soc/mediatek/mt8186-pm-domains.h
> create mode 100644 include/dt-bindings/power/mt8186-power.h
>
> --
> 2.18.0
>
prev parent reply other threads:[~2022-02-28 11:03 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20220215104917.5726-1-chun-jie.chen@mediatek.com>
2022-02-15 10:49 ` [v2 1/2] dt-bindings: power: Add MT8186 power domains Chun-Jie Chen
2022-02-24 20:46 ` Rob Herring
2022-02-15 10:49 ` [v2 2/2] soc: mediatek: pm-domains: Add support for mt8186 Chun-Jie Chen
2022-02-16 2:44 ` [v2 0/2] Mediatek MT8186 power domain support Macpaul Lin
2022-02-28 11:03 ` 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=1b0ad14d-5843-b8f8-ad6b-d3366a611dde@gmail.com \
--to=matthias.bgg@gmail.com \
--cc=Project_Global_Chrome_Upstream_Group@mediatek.com \
--cc=chun-jie.chen@mediatek.com \
--cc=devicetree@vger.kernel.org \
--cc=drinkcat@chromium.org \
--cc=eballetbo@gmail.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=srv_heupstream@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).