From: Garmin.Chang <Garmin.Chang@mediatek.com>
To: Matthias Brugger <matthias.bgg@gmail.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>,
Garmin.Chang <Garmin.Chang@mediatek.com>
Subject: [PATCH v2 0/2] Add power domain support for MT8188
Date: Wed, 28 Sep 2022 16:43:13 +0800 [thread overview]
Message-ID: <20220928084315.29187-1-Garmin.Chang@mediatek.com> (raw)
Base on tag: next-20220927, linux-next/master
The power domain driver manages to power up/down MediaTek MT8188 chip.
changes since v1:
- add more description to this series
- remove change-id
- align as the same indention
- remove redundant parentheses
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
--
2.18.0
next reply other threads:[~2022-09-28 9:23 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-09-28 8:43 Garmin.Chang [this message]
2022-09-28 8:43 ` [PATCH v2 1/2] dt-bindings: power: Add MT8188 power domains Garmin.Chang
2022-09-28 8:44 ` Krzysztof Kozlowski
2022-10-04 8:19 ` AngeloGioacchino Del Regno
2022-09-28 8:43 ` [PATCH v2 2/2] soc: mediatek: pm-domains: Add support for mt8188 Garmin.Chang
2022-10-04 8:19 ` AngeloGioacchino Del Regno
2022-11-25 3:27 ` Garmin Chang (張家銘)
2022-12-23 7:47 ` Garmin Chang (張家銘)
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=20220928084315.29187-1-Garmin.Chang@mediatek.com \
--to=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-kernel@vger.kernel.org \
--cc=linux-mediatek@lists.infradead.org \
--cc=matthias.bgg@gmail.com \
--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).