From: Tim Chang <jia-wei.chang@mediatek.com>
To: MyungJoo Ham <myungjoo.ham@samsung.com>,
Kyungmin Park <kyungmin.park@samsung.com>,
Chanwoo Choi <cw00.choi@samsung.com>,
"Rob Herring" <robh+dt@kernel.org>,
Matthias Brugger <matthias.bgg@gmail.com>,
"Liam Girdwood" <lgirdwood@gmail.com>,
Mark Brown <broonie@kernel.org>,
"Jia-Wei Chang" <jia-wei.chang@mediatek.com>
Cc: <linux-pm@vger.kernel.org>, <devicetree@vger.kernel.org>,
<linux-arm-kernel@lists.infradead.org>,
<linux-mediatek@lists.infradead.org>,
<linux-kernel@vger.kernel.org>, <fan.chen@mediatek.com>,
<louis.yu@mediatek.com>, <roger.lu@mediatek.com>,
<Allen-yy.Lin@mediatek.com>,
<Project_Global_Chrome_Upstream_Group@mediatek.com>,
<hsinyi@google.com>
Subject: [PATCH 0/3] devfreq: mediatek: introduce MTK cci devfreq
Date: Mon, 7 Mar 2022 20:25:10 +0800 [thread overview]
Message-ID: <20220307122513.11822-1-jia-wei.chang@mediatek.com> (raw)
The Cache Coherent Interconnect (CCI) is the management of cache
coherency by hardware. CCI DEVFREQ is DVFS driver for power saving by
scaling clock frequency and supply voltage of CCI. CCI uses the same
input clock source and power rail as LITTLE CPUs on Mediatek SoCs.
Jia-Wei Chang (3):
dt-bindings: devfreq: mediatek: add mtk cci devfreq dt-bindings
devfreq: mediatek: add mt8183 cci devfreq driver
devfreq: mediatek: add platform data to support mt8186
.../devicetree/bindings/devfreq/mtk-cci.yaml | 73 +++
drivers/devfreq/Kconfig | 11 +-
drivers/devfreq/Makefile | 2 +-
drivers/devfreq/mtk-cci-devfreq.c | 481 ++++++++++++++++++
4 files changed, 565 insertions(+), 2 deletions(-)
create mode 100644 Documentation/devicetree/bindings/devfreq/mtk-cci.yaml
create mode 100644 drivers/devfreq/mtk-cci-devfreq.c
--
2.18.0
_______________________________________________
Linux-mediatek mailing list
Linux-mediatek@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-mediatek
next reply other threads:[~2022-03-07 12:48 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-03-07 12:25 Tim Chang [this message]
2022-03-07 12:25 ` [PATCH 1/3] dt-bindings: devfreq: mediatek: add mtk cci devfreq dt-bindings Tim Chang
2022-03-07 21:42 ` Krzysztof Kozlowski
2022-03-24 12:11 ` Jia-Wei Chang
2022-03-24 12:44 ` Krzysztof Kozlowski
2022-04-01 13:39 ` Jia-Wei Chang
2022-04-02 11:31 ` Krzysztof Kozlowski
2022-04-06 3:32 ` Jia-Wei Chang
2022-03-07 12:25 ` [PATCH 2/3] devfreq: mediatek: add mt8183 cci devfreq driver Tim Chang
2022-03-07 16:44 ` Hsin-Yi Wang
2022-04-07 21:52 ` Kevin Hilman
2022-04-08 2:53 ` Johnson Wang
2022-03-07 21:51 ` Krzysztof Kozlowski
2022-03-24 12:17 ` Jia-Wei Chang
2022-04-07 3:20 ` Chanwoo Choi
2022-04-07 11:45 ` Jia-Wei Chang
2022-03-07 12:25 ` [PATCH 3/3] devfreq: mediatek: add platform data to support mt8186 Tim Chang
2022-03-07 21:52 ` Krzysztof Kozlowski
2022-03-24 12:19 ` Jia-Wei 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=20220307122513.11822-1-jia-wei.chang@mediatek.com \
--to=jia-wei.chang@mediatek.com \
--cc=Allen-yy.Lin@mediatek.com \
--cc=Project_Global_Chrome_Upstream_Group@mediatek.com \
--cc=broonie@kernel.org \
--cc=cw00.choi@samsung.com \
--cc=devicetree@vger.kernel.org \
--cc=fan.chen@mediatek.com \
--cc=hsinyi@google.com \
--cc=kyungmin.park@samsung.com \
--cc=lgirdwood@gmail.com \
--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=louis.yu@mediatek.com \
--cc=matthias.bgg@gmail.com \
--cc=myungjoo.ham@samsung.com \
--cc=robh+dt@kernel.org \
--cc=roger.lu@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