From: viresh.kumar@linaro.org (Viresh Kumar)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH V3 0/3] cpufreq: dt: Allow platforms to provide suspend/resume hooks
Date: Tue, 24 Apr 2018 15:09:44 +0530 [thread overview]
Message-ID: <cover.1524561482.git.viresh.kumar@linaro.org> (raw)
Hi Rafael,
These patches are already tested by Miquel and are ready to get merged.
Please pick them as part of 4.18 stuff whenever you do that.
I have updated the cpufreq-dt driver to allow platform specific
suspend/resume hooks and done some minor cleanup in the driver. I have
updated Miquel's patch and applied that on top of all this.
Thanks.
V2->V3:
- Don't double put the clock.
- Fix commit log of 3/3.
- Add tested-by from Miquel.
- There was no V2 of 1-2/3 but only 3/3 on the lists. All are marked as
V3 to clear things out.
--
viresh
[1] https://lkml.kernel.org/r/20180421141943.25705-1-miquel.raynal at bootlin.com
Miquel Raynal (1):
cpufreq: add suspend/resume support in Armada 37xx DVFS driver
Viresh Kumar (2):
cpufreq: dt: Allow platform specific suspend/resume callbacks
cpufreq: armada: Free resources on error paths
drivers/cpufreq/armada-37xx-cpufreq.c | 100 +++++++++++++++++++++++++++++-----
drivers/cpufreq/cpufreq-dt.c | 10 +++-
drivers/cpufreq/cpufreq-dt.h | 5 ++
3 files changed, 100 insertions(+), 15 deletions(-)
--
2.15.0.194.g9af6a3dea062
next reply other threads:[~2018-04-24 9:39 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-04-24 9:39 Viresh Kumar [this message]
2018-04-24 9:39 ` [PATCH V3 2/3] cpufreq: armada: Free resources on error paths Viresh Kumar
2018-04-24 9:39 ` [PATCH V3 3/3] cpufreq: add suspend/resume support in Armada 37xx DVFS driver Viresh Kumar
2018-04-26 9:32 ` kbuild test robot
2018-04-26 10:12 ` Viresh Kumar
2018-04-26 10:12 ` [PATCH V4 " Viresh Kumar
2018-05-02 15:52 ` Gregory CLEMENT
2018-05-03 4:36 ` Viresh Kumar
2018-05-13 8:48 ` [PATCH V3 0/3] cpufreq: dt: Allow platforms to provide suspend/resume hooks Rafael J. Wysocki
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=cover.1524561482.git.viresh.kumar@linaro.org \
--to=viresh.kumar@linaro.org \
--cc=linux-arm-kernel@lists.infradead.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).