linux-hotplug.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Pavel Machek <pavel@ucw.cz>
To: Todd Poynor <tpoynor@mvista.com>
Cc: Patrick Mochel <mochel@digitalimplant.org>,
	linux-hotplug-devel@lists.sourceforge.net,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH] Hotplug for device power state changes
Date: Fri, 14 May 2004 02:50:53 +0000	[thread overview]
Message-ID: <20040514025053.GA14773@elf.ucw.cz> (raw)
In-Reply-To: <40999017.4090603@mvista.com>

Hi!

> Let me throw out an example to help discuss the model best suits that 
> situation.
> An XScale PXA27x "Bulverde", a smartphone platform, has a low-power mode 
> that
> helps conserve battery power during periods of reduced activity while 
> leaving
> the CPU running at a low clock rate (and often idling) to handle any events
> that occur during that time.  In that mode, certain devices must be powered 
> off

...

> A similar request was made by another smartphone development team to handle 
> a
> dual-core CPU + DSP ARM OMAP system, where changes in DSP or network 
> activity
> (i.e., a call or other communication is starting or stopping) are to trigger
> changes in system power state.  In this case, the affected devices might 
> not be
> all-the-way powered off, but in an intermediate lower-power state.

Hey, I want linux smartphone ;-).

In case of that dual-core CPU, does linux really run on both CPUs? Do
we get sources for GSM network stack, too?

Is there some preliminary docs about such beasts available somewhere?
Dual CPU design for phone certainly looks interesting...

								Pavel
-- 
When do you have heart between your knees?


-------------------------------------------------------
This SF.Net email is sponsored by: SourceForge.net Broadband
Sign-up now for SourceForge Broadband and get the fastest
6.0/768 connection for only $19.95/mo for the first 3 months!
http://ads.osdn.com/?ad_id%62&alloc_ida84&op=click
_______________________________________________
Linux-hotplug-devel mailing list  http://linux-hotplug.sourceforge.net
Linux-hotplug-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/linux-hotplug-devel

  reply	other threads:[~2004-05-14  2:50 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20040429202654.GA9971@dhcp193.mvista.com>
2004-04-29 21:42 ` [PATCH] Hotplug for device power state changes Russell King
2004-04-29 22:36   ` Todd Poynor
2004-04-30  0:50     ` Benjamin Herrenschmidt
2004-04-30  8:30       ` Russell King
2004-04-30 19:59         ` Todd Poynor
2004-04-30 21:56           ` Greg KH
2004-05-01  1:16             ` Todd Poynor
2004-05-01  1:48               ` Greg KH
2004-05-03 21:33                 ` Todd Poynor
2004-05-01  0:03           ` Nigel Cunningham
2004-05-03 22:04             ` Todd Poynor
2004-04-30 19:07       ` Todd Poynor
2004-05-15  1:40   ` Nicolas Pitre
2004-05-15 23:34     ` Pavel Machek
     [not found] ` <Pine.LNX.4.50.0405040819490.3562-100000@monsoon.he.net>
2004-05-04 20:36   ` Todd Poynor
     [not found]     ` <Pine.LNX.4.50.0405042110440.30304-100000@monsoon.he.net>
2004-05-06  1:08       ` Todd Poynor
2004-05-14  2:50         ` Pavel Machek [this message]
2004-05-15  2:08           ` Todd Poynor

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=20040514025053.GA14773@elf.ucw.cz \
    --to=pavel@ucw.cz \
    --cc=linux-hotplug-devel@lists.sourceforge.net \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mochel@digitalimplant.org \
    --cc=tpoynor@mvista.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 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).