From: Hsin-Yi Wang <hsinyi@chromium.org>
To: linux-arm-kernel@lists.infradead.org
Cc: MyungJoo Ham <myungjoo.ham@samsung.com>,
Kyungmin Park <kyungmin.park@samsung.com>,
Chanwoo Choi <cw00.choi@samsung.com>,
Matthias Brugger <matthias.bgg@gmail.com>,
linux-pm@vger.kernel.org, linux-mediatek@lists.infradead.org,
linux-kernel@vger.kernel.org,
Saravana Kannan <skannan@codeaurora.org>,
"Andrew-sh . Cheng" <andrew-sh.cheng@mediatek.com>
Subject: [PATCH RFC 0/2] Use cpufreq-map governor for MT8183 CCI
Date: Tue, 18 Jun 2019 12:14:32 +0800 [thread overview]
Message-ID: <20190618041433.245629-1-hsinyi@chromium.org> (raw)
From: Hsin-Yi Wang <hsinyi@chromium.org>
This series uses cpufreq-map governor for mt8183-cci to improve performance.
Hsin-Yi Wang (1):
devfreq: mt8183-cci: using cpufreq-map governor in cci dvfs driver
Saravana Kannan (1):
PM / devfreq: Generic CPU frequency to device frequency mapping
governor
.../bindings/devfreq/devfreq-cpufreq-map.txt | 53 ++
drivers/devfreq/Kconfig | 8 +
drivers/devfreq/Makefile | 1 +
drivers/devfreq/governor_cpufreq_map.c | 583 ++++++++++++++++++
drivers/devfreq/mt8183-cci-devfreq.c | 194 +-----
5 files changed, 649 insertions(+), 190 deletions(-)
create mode 100644 Documentation/devicetree/bindings/devfreq/devfreq-cpufreq-map.txt
create mode 100644 drivers/devfreq/governor_cpufreq_map.c
--
2.20.1
next reply other threads:[~2019-06-18 4:14 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-06-18 4:14 Hsin-Yi Wang [this message]
2019-06-18 4:14 ` [PATCH RFC 1/2] PM / devfreq: Generic CPU frequency to device frequency mapping governor Hsin-Yi Wang
2019-06-20 6:58 ` Chanwoo Choi
2019-06-20 9:32 ` Hsin-Yi Wang
2019-06-20 9:41 ` Sibi Sankar
2019-06-20 9:43 ` Hsin-Yi Wang
2019-06-26 8:12 ` Chanwoo Choi
2019-06-18 4:14 ` [PATCH RFC 2/2] devfreq: mt8183-cci: using cpufreq-map governor in cci dvfs driver Hsin-Yi Wang
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=20190618041433.245629-1-hsinyi@chromium.org \
--to=hsinyi@chromium.org \
--cc=andrew-sh.cheng@mediatek.com \
--cc=cw00.choi@samsung.com \
--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=matthias.bgg@gmail.com \
--cc=myungjoo.ham@samsung.com \
--cc=skannan@codeaurora.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).