From: Chanwoo Choi <cwchoi00@gmail.com>
To: Johnson Wang <johnson.wang@mediatek.com>,
cw00.choi@samsung.com, krzk+dt@kernel.org, robh+dt@kernel.org,
kyungmin.park@samsung.com
Cc: khilman@kernel.org, linux-pm@vger.kernel.org,
linux-kernel@vger.kernel.org, devicetree@vger.kernel.org,
linux-arm-kernel@lists.infradead.org,
linux-mediatek@lists.infradead.org, jia-wei.chang@mediatek.com,
Project_Global_Chrome_Upstream_Group@mediatek.com
Subject: Re: [PATCH v3 2/2] PM / devfreq: mediatek: Introduce MediaTek CCI devfreq driver
Date: Sat, 7 May 2022 03:57:34 +0900 [thread overview]
Message-ID: <0846a062-2ea2-e6d4-03c8-992c2f2e24a0@gmail.com> (raw)
In-Reply-To: <20220425125546.4129-3-johnson.wang@mediatek.com>
Hi Johnson,
On 22. 4. 25. 21:55, Johnson Wang wrote:
> We introduce a devfreq driver for the MediaTek Cache Coherent Interconnect
> (CCI) used by some MediaTek SoCs.
>
> In this driver, we use the passive devfreq driver to get target frequencies
> and adjust voltages accordingly. In MT8183 and MT8186, the MediaTek CCI
> is supplied by the same regulators with the little core CPUs.
>
> Signed-off-by: Johnson Wang <johnson.wang@mediatek.com>
> Signed-off-by: Jia-Wei Chang <jia-wei.chang@mediatek.com>
> ---
> This patch depends on "devfreq-testing"[1].
> [1]https://git.kernel.org/pub/scm/linux/kernel/git/chanwoo/linux.git/log/?h=devfreq-testing
> ---
> drivers/devfreq/Kconfig | 10 +
> drivers/devfreq/Makefile | 1 +
> drivers/devfreq/mtk-cci-devfreq.c | 474 ++++++++++++++++++++++++++++++
> 3 files changed, 485 insertions(+)
> create mode 100644 drivers/devfreq/mtk-cci-devfreq.c
Acked-by: Chanwoo Choi <cw00.choi@samsung.com>
I updated the passive governor on devfreq-testing[1] branch
[1]
https://git.kernel.org/pub/scm/linux/kernel/git/chanwoo/linux.git/log/?h=devfreq-testing
Could you please test your patches based on devfreq-testing[1] branch?
--
Best Regards,
Samsung Electronics
Chanwoo Choi
prev parent reply other threads:[~2022-05-06 18:57 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-04-25 12:55 [PATCH v3 0/2] Introduce MediaTek CCI devfreq driver Johnson Wang
2022-04-25 12:55 ` [PATCH v3 1/2] dt-bindings: interconnect: Add MediaTek CCI dt-bindings Johnson Wang
2022-04-25 17:56 ` Krzysztof Kozlowski
2022-04-26 3:18 ` Chen-Yu Tsai
2022-05-09 12:14 ` Johnson Wang
2022-05-11 10:48 ` Chen-Yu Tsai
2022-05-12 13:04 ` Johnson Wang
2022-05-13 3:31 ` Chen-Yu Tsai
2022-05-09 12:09 ` Chanwoo Choi
2022-05-09 12:43 ` Chanwoo Choi
2022-05-10 2:59 ` Johnson Wang
2022-05-10 4:27 ` Chanwoo Choi
2022-04-25 12:55 ` [PATCH v3 2/2] PM / devfreq: mediatek: Introduce MediaTek CCI devfreq driver Johnson Wang
2022-04-26 12:45 ` kernel test robot
2022-04-27 7:09 ` kernel test robot
2022-04-27 9:25 ` kernel test robot
2022-04-27 10:11 ` Johnson Wang
2022-04-28 11:39 ` [kbuild-all] " Chen, Rong A
2022-05-06 12:03 ` Chen-Yu Tsai
2022-05-09 2:53 ` Chanwoo Choi
2022-05-06 11:38 ` Johnson Wang
2022-05-07 13:53 ` Chanwoo Choi
2022-05-09 5:57 ` Johnson Wang
2022-05-09 11:51 ` Chanwoo Choi
2022-05-11 5:14 ` Johnson Wang
2022-05-11 7:08 ` Chanwoo Choi
2022-05-06 18:57 ` Chanwoo Choi [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=0846a062-2ea2-e6d4-03c8-992c2f2e24a0@gmail.com \
--to=cwchoi00@gmail.com \
--cc=Project_Global_Chrome_Upstream_Group@mediatek.com \
--cc=cw00.choi@samsung.com \
--cc=devicetree@vger.kernel.org \
--cc=jia-wei.chang@mediatek.com \
--cc=johnson.wang@mediatek.com \
--cc=khilman@kernel.org \
--cc=krzk+dt@kernel.org \
--cc=kyungmin.park@samsung.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=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).