public inbox for linux-pm@vger.kernel.org
 help / color / mirror / Atom feed
From: Pavel Machek <pavel@ucw.cz>
To: Michael Trimarchi <trimarchi@gandalf.sssup.it>
Cc: linux-pm@lists.linux-foundation.org,
	Nigel Cunningham <ncunningham@crca.org.au>
Subject: Re: [RFC Disable suspend on a specific device] This is	a little change in linux power scheme
Date: Tue, 7 Apr 2009 10:06:11 +0200	[thread overview]
Message-ID: <20090407080611.GF1408@ucw.cz> (raw)
In-Reply-To: <49DC6442.3040506@gandalf.sssup.it>

Hi!

> > I think this is a rather fundamental issue and it requires some more thought.
> >
> > What platform is your device based on, BTW?

> I'm working on an openmoko freerunner gta02 and do some work on android 
> framework.
> It's a smartphone
> http://wiki.openmoko.org/wiki/Main_Page
> 
> The bluetooth device for example in the Freerunner has a direct I2S connection to
> the WM8753.  Audio from a bluetooth headset is decoded by and sent digitially 
> to the WM8753 which does the digital to analogue conversion and 
> routes it out via the appropriate outputs.
> Analogue problem has the ti-caplyso when the audio is routed for a phone call.

I still believe it should be done in the driver... at least
today. Perhaps driver should just keep i2s/bluetooth powered up when
it is in use.

Perhaps we need new state 'sleep but keep working' for cases like
that; echo mem > state should force machine to drop calls etc. There
should be another value where stuff that is in use keeps being powered
up; I also suspect that that's what android wants to use. 

> Is the correct answer to you question?
 
Yes :-).

-- 
(english) http://www.livejournal.com/~pavelmachek
(cesky, pictures) http://atrey.karlin.mff.cuni.cz/~pavel/picture/horses/blog.html

  reply	other threads:[~2009-04-07  8:06 UTC|newest]

Thread overview: 32+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-04-07 10:29 [RFC Disable suspend on a specific device] This is a little change in linux power scheme Michael Trimarchi
2009-04-07 13:45 ` Rafael J. Wysocki
2009-04-07 15:39   ` Michael Trimarchi
2009-04-07 18:55     ` Rafael J. Wysocki
2009-04-07 19:01       ` Michael Trimarchi
2009-04-07 20:40         ` Pavel Machek
2009-04-07 20:57         ` Rafael J. Wysocki
2009-04-07 21:31           ` Alan Stern
2009-04-07 21:38             ` Pavel Machek
2009-04-07 22:25               ` Nigel Cunningham
2009-04-08  5:59                 ` Michael Trimarchi
2009-04-08  8:13                   ` Rafael J. Wysocki
2009-04-08  8:24                     ` Michael Trimarchi
2009-04-08  8:34                       ` Rafael J. Wysocki
2009-04-08  8:45                         ` Michael Trimarchi
2009-04-07  8:06                           ` Pavel Machek [this message]
2009-04-20 12:46                             ` Mark Brown
2009-04-20 12:55                               ` Michael Trimarchi
2009-04-08 11:42                         ` Mark Brown
2009-04-08 16:44                           ` Igor Stoppa
2009-04-08 18:23                             ` Mark Brown
2009-04-08 19:53                               ` Igor Stoppa
2009-04-09 14:33                                 ` Mark Brown
2009-04-07 21:40             ` Rafael J. Wysocki
2009-04-08 11:53               ` Mark Brown
2009-04-08 16:45                 ` Igor Stoppa
2009-04-10 11:17                 ` Pavel Machek
2009-04-08 20:37               ` Alan Stern
2009-04-08 21:25                 ` Michael Trimarchi
2009-04-08 21:56                 ` Rafael J. Wysocki
2009-04-09 18:27                   ` Alan Stern
2009-04-09 22:33                     ` Rafael J. Wysocki

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=20090407080611.GF1408@ucw.cz \
    --to=pavel@ucw.cz \
    --cc=linux-pm@lists.linux-foundation.org \
    --cc=ncunningham@crca.org.au \
    --cc=trimarchi@gandalf.sssup.it \
    /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