From: Matthias Brugger <matthias.bgg@gmail.com>
To: Rex-BC Chen <rex-bc.chen@mediatek.com>,
rafael@kernel.org, viresh.kumar@linaro.org, robh+dt@kernel.org,
krzk+dt@kernel.org
Cc: jia-wei.chang@mediatek.com, roger.lu@mediatek.com,
hsinyi@google.com, khilman@baylibre.com,
angelogioacchino.delregno@collabora.com,
linux-pm@vger.kernel.org, devicetree@vger.kernel.org,
linux-kernel@vger.kernel.org,
linux-arm-kernel@lists.infradead.org,
linux-mediatek@lists.infradead.org,
Project_Global_Chrome_Upstream_Group@mediatek.com
Subject: Re: [PATCH v7 0/3] cpufreq: mediatek: Cleanup and support MT8183 and MT8186
Date: Tue, 17 May 2022 12:09:25 +0200 [thread overview]
Message-ID: <3e9f0936-efee-cedf-6e2b-4dd9de79fc4e@gmail.com> (raw)
In-Reply-To: <20220516111130.13325-1-rex-bc.chen@mediatek.com>
On 16/05/2022 13:11, Rex-BC Chen wrote:
> Cpufreq is a DVFS driver used for power saving to scale the clock frequency
> and supply the voltage for CPUs. This series do some cleanup for MediaTek
> cpufreq drivers and add support for MediaTek SVS[2] and MediaTek CCI
> devfreq[3] which are supported in MT8183 and MT8186.
>
Series applied to v5.19-next/dts64
Thanks!
> Changes for v7:
> 1. Drop all drviers patches because they are all accepted.
> 2. Correct clock/clock-name for cci in dts.
>
> Changes for v6:
> 1. Reorder patches in this series.
> 2. Add a new patch to do unregister platform device.
> 3. Modify drivers from maintainer's advice.
>
> Reference series:
> [1]: V1 of this series is present by Jia-Wei Chang.
> https://lore.kernel.org/all/20220307122151.11666-1-jia-wei.chang@mediatek.com/
>
> [2]: The MediaTek CCI devfreq driver is introduced in another series.
> https://lore.kernel.org/all/20220425125546.4129-1-johnson.wang@mediatek.com/
>
> [3]: The MediaTek SVS driver is introduced in another series.
> https://lore.kernel.org/all/20220420102044.10832-1-roger.lu@mediatek.com/
>
> Rex-BC Chen (3):
> arm64: dts: mediatek: Add opp table and clock property for MT8183
> cpufreq
> arm64: dts: mediatek: Add MediaTek CCI node for MT8183
> arm64: dts: mediatek: Add mediatek,cci property for MT8183 cpufreq
>
> arch/arm64/boot/dts/mediatek/mt8183-evb.dts | 36 +++
> .../arm64/boot/dts/mediatek/mt8183-kukui.dtsi | 4 +
> arch/arm64/boot/dts/mediatek/mt8183.dtsi | 286 ++++++++++++++++++
> 3 files changed, 326 insertions(+)
>
prev parent reply other threads:[~2022-05-17 10:11 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-05-16 11:11 [PATCH v7 0/3] cpufreq: mediatek: Cleanup and support MT8183 and MT8186 Rex-BC Chen
2022-05-16 11:11 ` [PATCH v7 1/3] arm64: dts: mediatek: Add opp table and clock property for MT8183 cpufreq Rex-BC Chen
2022-05-16 11:11 ` [PATCH v7 2/3] arm64: dts: mediatek: Add MediaTek CCI node for MT8183 Rex-BC Chen
2022-05-16 11:11 ` [PATCH v7 3/3] arm64: dts: mediatek: Add mediatek,cci property for MT8183 cpufreq Rex-BC Chen
2022-05-17 10:09 ` 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=3e9f0936-efee-cedf-6e2b-4dd9de79fc4e@gmail.com \
--to=matthias.bgg@gmail.com \
--cc=Project_Global_Chrome_Upstream_Group@mediatek.com \
--cc=angelogioacchino.delregno@collabora.com \
--cc=devicetree@vger.kernel.org \
--cc=hsinyi@google.com \
--cc=jia-wei.chang@mediatek.com \
--cc=khilman@baylibre.com \
--cc=krzk+dt@kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mediatek@lists.infradead.org \
--cc=linux-pm@vger.kernel.org \
--cc=rafael@kernel.org \
--cc=rex-bc.chen@mediatek.com \
--cc=robh+dt@kernel.org \
--cc=roger.lu@mediatek.com \
--cc=viresh.kumar@linaro.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).