From: Mark Brown <broonie@opensource.wolfsonmicro.com>
To: Kukjin Kim <kgene.kim@samsung.com>
Cc: linux-samsung-soc@vger.kernel.org, cpufreq@vger.kernel.org,
davej@redhat.com, 'Jongpill Lee' <boyko.lee@samsung.com>,
'SangWook Ju' <sw.ju@samsung.com>,
'Jonghwan Choi' <jhbird.choi@samsung.com>
Subject: Re: [PATCH 4/4] [CPUFREQ] EXYNOS4210: Add Support for DVS Lock
Date: Tue, 19 Jul 2011 16:03:43 +0100 [thread overview]
Message-ID: <20110719150343.GD9652@opensource.wolfsonmicro.com> (raw)
In-Reply-To: <04a101cc4519$912ce800$b386b800$%kim@samsung.com>
On Mon, Jul 18, 2011 at 04:08:53PM +0900, Kukjin Kim wrote:
> > This feels like something cpufreq should support to at least some extent
> > in the core, especially the thing with forcing a particular mode on
> > suspend. Not that I have any particularly bright ideas for how
> > immediately.
> Basically, I agreed, but I also have no idea yet :(
> How about to use this for now then let us think the way?
Probably just as well. For the suspend stuff we should be able to
implement a generic override the governor callback for use in suspend
entry easily enough but for other things I'm drawing a blank right now.
prev parent reply other threads:[~2011-07-19 15:03 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-07-05 8:06 [PATCH 0/4] EXYNOS4210: Update exynos4210-cpufreq.c Kukjin Kim
2011-07-05 8:06 ` [PATCH 1/4] [CPUFREQ] EXYNOS4210: Remove regarding busfreq codes Kukjin Kim
2011-07-05 8:06 ` [PATCH 2/4] EXYNOS4210: Change CPU table and divider Kukjin Kim
2011-07-05 8:06 ` [PATCH 3/4] [CPUFREQ] EXYNOS4210: Cleanup sequence and unused codes Kukjin Kim
2011-07-05 8:06 ` [PATCH 4/4] [CPUFREQ] EXYNOS4210: Add Support for DVS Lock Kukjin Kim
2011-07-05 8:49 ` Kyungmin Park
2011-07-08 6:22 ` [PATCH 4/4] " Kukjin Kim
2011-07-09 3:48 ` Mark Brown
2011-07-18 7:08 ` [PATCH 4/4] [CPUFREQ] " Kukjin Kim
2011-07-19 15:03 ` Mark Brown [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=20110719150343.GD9652@opensource.wolfsonmicro.com \
--to=broonie@opensource.wolfsonmicro.com \
--cc=boyko.lee@samsung.com \
--cc=cpufreq@vger.kernel.org \
--cc=davej@redhat.com \
--cc=jhbird.choi@samsung.com \
--cc=kgene.kim@samsung.com \
--cc=linux-samsung-soc@vger.kernel.org \
--cc=sw.ju@samsung.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.