From: Richard Fitzgerald <rf@opensource.wolfsonmicro.com>
To: Mark Brown <broonie@kernel.org>
Cc: Lee Jones <lee.jones@linaro.org>,
linux-kernel@vger.kernel.org,
patches@opensource.wolfsonmicro.com
Subject: Re: [PATCH v6 1/1] mfd: arizona: Export functions to control subsystem DVFS
Date: Tue, 26 May 2015 16:45:15 +0100 [thread overview]
Message-ID: <20150526154515.GB26432@opensource.wolfsonmicro.com> (raw)
In-Reply-To: <20150526152942.GU21577@sirena.org.uk>
On Tue, May 26, 2015 at 04:29:42PM +0100, Mark Brown wrote:
> On Tue, May 26, 2015 at 02:52:05PM +0100, Lee Jones wrote:
>
> > Shouldn't this DVFS dump live in drivers/cpufreq?
>
> cpufreq is specifically for CPUs (with the governors and everything) and
> has its own problems here. There is devfreq which was crated for this
> sort of thing (though more on a SoC level) though, not sure if it's a
> good fit or not.
The only codecs that have DVFS are WM8997, WM8998 and WM5102. No newer
codecs have it so it feels like unnecessary effort to create a whole
new driver for these three codecs. In any case, all we're really doing
here is setting the state of a single bit which tells the codec whether
we're feeding it enough DCVDD for it to do its internal DVFS. Most of
the additional complexity here is around co-operating with the
runtime_suspend/resume code in the MFD driver,
next prev parent reply other threads:[~2015-05-26 15:45 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-05-19 14:57 [PATCH v6 0/1] mfd: arizona: Export functions to control subsystem DVFS Richard Fitzgerald
2015-05-19 14:57 ` [PATCH v6 1/1] " Richard Fitzgerald
2015-05-19 15:23 ` Charles Keepax
2015-05-26 13:52 ` Lee Jones
2015-05-26 15:29 ` Mark Brown
2015-05-26 15:45 ` Richard Fitzgerald [this message]
2015-05-26 16:10 ` Richard Fitzgerald
2015-05-27 8:05 ` Lee Jones
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=20150526154515.GB26432@opensource.wolfsonmicro.com \
--to=rf@opensource.wolfsonmicro.com \
--cc=broonie@kernel.org \
--cc=lee.jones@linaro.org \
--cc=linux-kernel@vger.kernel.org \
--cc=patches@opensource.wolfsonmicro.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.