From: Bryan Huntsman <bryanh@codeaurora.org>
To: Mark Brown <broonie@opensource.wolfsonmicro.com>
Cc: Len Brown <lenb@kernel.org>,
Linux Power Management List <linux-pm@lists.osdl.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
linux-arm-msm@vger.kernel.org
Subject: Re: [linux-pm] Notes from the Boston Linux Power Management Mini-summit - August 9th, 2010
Date: Mon, 16 Aug 2010 18:09:17 -0700 [thread overview]
Message-ID: <4C69E13D.3020809@codeaurora.org> (raw)
In-Reply-To: <20100816144914.GB10354@sirena.org.uk>
Mark Brown wrote:
> On Sun, Aug 15, 2010 at 01:36:33AM -0400, Len Brown wrote:
>
>> A gap:
>>
>> On OMAP, bus control is independent of CPU frequency control,
>> so cpufreq and cpuidle don't quite fit the bill.
>>
>> Perhaps a "bus-idle" analogous to "cpu-idle" may be appropriate?
>
> FWIW this applies to a bunch of other embedded processors too - OMAP
> isn't particularly unique here, though it's one of the furthest along in
> terms of exploting this in mainline Linux.
This capability would benefit MSM as well. We're looking into a
soc-specific implementation using Pat Pannuto's "pseudo" platform bus
extensions (discussed here http://lkml.org/lkml/2010/8/10/389). After
we have something working, I would be curious to see if some common
functionality could be extracted into a more generic mechanism.
- Bryan
--
Sent by an employee of the Qualcomm Innovation Center, Inc.
The Qualcomm Innovation Center, Inc. is a member of the Code Aurora Forum.
prev parent reply other threads:[~2010-08-17 1:09 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-08-15 5:36 Notes from the Boston Linux Power Management Mini-summit - August 9th, 2010 Len Brown
2010-08-16 14:49 ` [linux-pm] " Mark Brown
2010-08-17 1:09 ` Bryan Huntsman [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=4C69E13D.3020809@codeaurora.org \
--to=bryanh@codeaurora.org \
--cc=broonie@opensource.wolfsonmicro.com \
--cc=lenb@kernel.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pm@lists.osdl.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 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.