From: Anna-Maria Behnsen <anna-maria@linutronix.de>
To: linux-pm@vger.kernel.org
Cc: rafael@kernel.org, Thomas Gleixner <tglx@linutronix.de>,
Viresh Kumar <viresh.kumar@linaro.org>,
Michael Ellerman <mpe@ellerman.id.au>
Subject: cpufreq - powernv driver
Date: Mon, 27 Jun 2022 15:24:02 +0200 (CEST) [thread overview]
Message-ID: <4c99f34b-40f1-e6cc-2669-7854b615b5fd@linutronix.de> (raw)
Hi,
during my work on a timer hierarchy I stumbled over powernv cpufreq driver
which is using a timer which is deferrable and pinned. This is the only
timer in kernel which uses this combination and I would like to get rid of
it.
Only removing the pinned or deferrable flag could not be the proper
solution, right?
I'm not familiar with cpufreq. I was wondering if it's possible to rework
the powernv cpufreq driver to use cpufreq infrastructure instead handling
it's own timer for ramping down? I would be happy if someone could help me
with some pointers how this could be solved.
Thanks,
Anna-Maria
next reply other threads:[~2022-06-27 13:24 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-06-27 13:24 Anna-Maria Behnsen [this message]
2022-09-26 13:20 ` cpufreq - powernv driver Anna-Maria Behnsen
2022-09-26 13:40 ` 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=4c99f34b-40f1-e6cc-2669-7854b615b5fd@linutronix.de \
--to=anna-maria@linutronix.de \
--cc=linux-pm@vger.kernel.org \
--cc=mpe@ellerman.id.au \
--cc=rafael@kernel.org \
--cc=tglx@linutronix.de \
--cc=viresh.kumar@linaro.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).