From: "Rafael J. Wysocki" <rjw@sisk.pl>
To: "Mahalingam, Nithish" <nithish.mahalingam@intel.com>
Cc: Magnus Damm <magnus.damm@gmail.com>,
Alan Stern <stern@rowland.harvard.edu>, Greg KH <gregkh@suse.de>,
LKML <linux-kernel@vger.kernel.org>,
ACPI Devel Maling List <linux-acpi@vger.kernel.org>,
Linux-pm mailing list <linux-pm@lists.linux-foundation.org>,
Ingo Molnar <mingo@elte.hu>,
Arjan van de Ven <arjan@infradead.org>
Subject: Re: [linux-pm] [RFC][PATCH] PM: Introduce core framework for run-time PM of I/O devices (rev. 8)
Date: Sat, 11 Jul 2009 13:08:42 +0200 [thread overview]
Message-ID: <200907111308.44388.rjw@sisk.pl> (raw)
In-Reply-To: <175E0F9A9EFCEA46A65F5552BB057298BB5F3EA2@bgsmsx502.gar.corp.intel.com>
On Thursday 09 July 2009, Mahalingam, Nithish wrote:
> Hi,
Hi,
> I am newbee to this mailing list. Please excuse me if I am talking nonsense here.
>
>
>
> On Thu, Jul 9, 2009 at 10:48 PM, Alan Stern<stern@rowland.harvard.edu> wrote:
> >> On Thu, 9 Jul 2009, Magnus Damm wrote:
> >>
> >>> Clocks should be stopped as soon as possible without any delay. The
> >>> clock stopping is very cheap performance wise. Also, the clock
> >> stopping is done on bus level without invoking any driver callbacks.
> >>> Delaying the clock stopping does not make any sense to me.
> >>
> >> In that case the device driver or bus subsystem should manage the
> >> device's clock directly. There's no need to tie it in with the runtime
> >> PM framework. Simply start the clock before each I/O operation and
> >> stop it afterward.
>
> > It's not that easy. The clock needs to be enabled to let the hardware
> > device perform device specific stuff. For instance, the clock for the
> > LCD controller needs to be on to redraw the screen. When the driver
> > knows that it's done with the clock it can notify the bus using
> > Runtime PM.
>
> Is there any plan to look into the "Clock Framework" that was developed as
> part of OMAP and extending this to make it generic for all platforms?
I don't have any plan to do that and I heaven't heard of anyone planning to do
it.
Best,
Rafael
next prev parent reply other threads:[~2009-07-11 11:08 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-07-06 0:52 [RFC][PATCH] PM: Introduce core framework for run-time PM of I/O devices (rev. 8) Rafael J. Wysocki
2009-07-07 15:12 ` Magnus Damm
2009-07-07 22:07 ` Rafael J. Wysocki
2009-07-08 2:54 ` Alan Stern
2009-07-08 4:40 ` Magnus Damm
2009-07-08 14:26 ` Alan Stern
2009-07-08 17:50 ` [update][RFC][PATCH] PM: Introduce core framework for run-time PM of I/O devices (rev. 9) Rafael J. Wysocki
2009-07-08 5:45 ` [RFC][PATCH] PM: Introduce core framework for run-time PM of I/O devices (rev. 8) Magnus Damm
2009-07-08 19:01 ` Rafael J. Wysocki
2009-07-08 19:42 ` Alan Stern
2009-07-08 19:55 ` Rafael J. Wysocki
2009-07-08 21:09 ` Alan Stern
2009-07-08 21:29 ` Rafael J. Wysocki
2009-07-09 2:52 ` Magnus Damm
2009-07-09 13:48 ` Alan Stern
2009-07-09 15:31 ` Magnus Damm
2009-07-09 21:56 ` [linux-pm] " Mahalingam, Nithish
2009-07-11 11:08 ` Rafael J. Wysocki [this message]
2009-07-12 2:05 ` Mahalingam, Nithish
2009-07-13 1:42 ` Magnus Damm
2009-07-09 23:22 ` Pavel Machek
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=200907111308.44388.rjw@sisk.pl \
--to=rjw@sisk.pl \
--cc=arjan@infradead.org \
--cc=gregkh@suse.de \
--cc=linux-acpi@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pm@lists.linux-foundation.org \
--cc=magnus.damm@gmail.com \
--cc=mingo@elte.hu \
--cc=nithish.mahalingam@intel.com \
--cc=stern@rowland.harvard.edu \
/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