From: Matthias Brugger <matthias.bgg@gmail.com>
To: "Garmin.Chang" <Garmin.Chang@mediatek.com>,
Rob Herring <robh+dt@kernel.org>,
Krzysztof Kozlowski <krzysztof.kozlowski+dt@linaro.org>
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,
linux-clk@vger.kernel.org, netdev@vger.kernel.org
Subject: Re: [PATCH v3 0/2] Add power domain support for MT8188
Date: Thu, 19 Jan 2023 17:18:25 +0100 [thread overview]
Message-ID: <3c30c805-243b-5ca9-06a3-2807fd76e3b2@gmail.com> (raw)
In-Reply-To: <20221223080553.9397-1-Garmin.Chang@mediatek.com>
Both applied, thanks!
Matthias
On 23/12/2022 09:05, Garmin.Chang wrote:
> Base on tag: next-20221220, linux-next/master
>
> changes since v2:
> - add MTK_SCPD_DOMAIN_SUPPLY cap to MFG1
> - add MTK_SCPD_ALWAYS_ON cap to ADSP_INFRA
>
> Garmin.Chang (2):
> dt-bindings: power: Add MT8188 power domains
> soc: mediatek: pm-domains: Add support for mt8188
>
> .../power/mediatek,power-controller.yaml | 2 +
> drivers/soc/mediatek/mt8188-pm-domains.h | 623 ++++++++++++++++++
> drivers/soc/mediatek/mtk-pm-domains.c | 5 +
> .../dt-bindings/power/mediatek,mt8188-power.h | 44 ++
> include/linux/soc/mediatek/infracfg.h | 121 ++++
> 5 files changed, 795 insertions(+)
> create mode 100644 drivers/soc/mediatek/mt8188-pm-domains.h
> create mode 100644 include/dt-bindings/power/mediatek,mt8188-power.h
>
prev parent reply other threads:[~2023-01-19 16:19 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20221223080553.9397-1-Garmin.Chang@mediatek.com>
2023-01-06 9:47 ` [PATCH v3 0/2] Add power domain support for MT8188 Garmin Chang (張家銘)
[not found] ` <20221223080553.9397-3-Garmin.Chang@mediatek.com>
2023-01-19 11:25 ` [PATCH v3 2/2] soc: mediatek: pm-domains: Add support for mt8188 AngeloGioacchino Del Regno
2023-01-19 16:18 ` 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=3c30c805-243b-5ca9-06a3-2807fd76e3b2@gmail.com \
--to=matthias.bgg@gmail.com \
--cc=Garmin.Chang@mediatek.com \
--cc=Project_Global_Chrome_Upstream_Group@mediatek.com \
--cc=devicetree@vger.kernel.org \
--cc=krzysztof.kozlowski+dt@linaro.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-clk@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mediatek@lists.infradead.org \
--cc=netdev@vger.kernel.org \
--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).