From: Lukasz Luba <lukasz.luba@arm.com>
To: Chanwoo Choi <cw00.choi@samsung.com>,
k.konieczny@samsung.com, krzk@kernel.org, kgene@kernel.org
Cc: s.nawrocki@samsung.com, willy.mh.wolff.ml@gmail.com,
b.zolnierkie@samsung.com, chanwoo@kernel.org,
myungjoo.ham@samsung.com, kyungmin.park@samsung.com,
linux-pm@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-samsung-soc@vger.kernel.org,
linux-arm-kernel@lists.infradead.org
Subject: Re: [RFC PATCH 0/2] PM / devfreq: Add delayed timer for polling
Date: Wed, 8 Jul 2020 15:01:19 +0100 [thread overview]
Message-ID: <cea8d850-131f-6121-6d96-8b8dc2a33432@arm.com> (raw)
In-Reply-To: <20200703062622.11773-1-cw00.choi@samsung.com>
Hi all,
On 7/3/20 7:26 AM, Chanwoo Choi wrote:
> Add the delayed timer to devfreq framework in order to support
> the periodical polling mode without stop caused by CPU idle state.
> Some Non-CPU device must need to monitor the device status like
> utilization regardless of CPU state.
>
> - patch1 explains the detailed reason why the delayed timer is required.
> - patch2 initializes that exynos5422-dmc device use delayed timer as default
> instead of deferrable timer.
>
> Chanwoo Choi (2):
> PM / devfreq: Add support delayed timer for polling mode
> memory: samsung: exynos5422-dmc: Use delayed timer as default
>
> Documentation/ABI/testing/sysfs-class-devfreq | 12 +++
> drivers/devfreq/devfreq.c | 83 ++++++++++++++++++-
> drivers/memory/samsung/exynos5422-dmc.c | 1 +
> include/linux/devfreq.h | 9 ++
> 4 files changed, 104 insertions(+), 1 deletion(-)
>
My apologizes for being late for the party. I wasn't able to run tests
and I had to fix my setup after I messed up some scripts.
The patch set looks good to me, so you can add my (to both patches):
Reviewed-by: Lukasz Luba <lukasz.luba@arm.com>
I have run these Willy's benchmark tests and I will send some
follow up patches in a few minutes.
Regards,
Lukasz
prev parent reply other threads:[~2020-07-08 14:01 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CGME20200703061508epcas1p171aa3c0ab832b77e5837d8bd1e563742@epcas1p1.samsung.com>
2020-07-03 6:26 ` [RFC PATCH 0/2] PM / devfreq: Add delayed timer for polling Chanwoo Choi
[not found] ` <CGME20200703061509epcas1p10446471df6497b4b2d7066280daa7f87@epcas1p1.samsung.com>
2020-07-03 6:26 ` [RFC PATCH 1/2] PM / devfreq: Add support delayed timer for polling mode Chanwoo Choi
[not found] ` <CGME20200703061509epcas1p3e338b614c44f5d8b566dae92f11cc8cb@epcas1p3.samsung.com>
2020-07-03 6:26 ` [RFC PATCH 2/2] memory: samsung: exynos5422-dmc: Use delayed timer as default Chanwoo Choi
2020-07-08 12:33 ` Krzysztof Kozlowski
2020-07-09 5:44 ` Chanwoo Choi
2020-07-03 12:33 ` [RFC PATCH 0/2] PM / devfreq: Add delayed timer for polling Willy Wolff
2020-07-08 14:25 ` Lukasz Luba
2020-07-10 15:12 ` Willy Wolff
2020-07-13 8:55 ` Lukasz Luba
2020-07-08 10:52 ` Bartlomiej Zolnierkiewicz
2020-07-08 14:01 ` Lukasz Luba [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=cea8d850-131f-6121-6d96-8b8dc2a33432@arm.com \
--to=lukasz.luba@arm.com \
--cc=b.zolnierkie@samsung.com \
--cc=chanwoo@kernel.org \
--cc=cw00.choi@samsung.com \
--cc=k.konieczny@samsung.com \
--cc=kgene@kernel.org \
--cc=krzk@kernel.org \
--cc=kyungmin.park@samsung.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pm@vger.kernel.org \
--cc=linux-samsung-soc@vger.kernel.org \
--cc=myungjoo.ham@samsung.com \
--cc=s.nawrocki@samsung.com \
--cc=willy.mh.wolff.ml@gmail.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;
as well as URLs for NNTP newsgroup(s).