public inbox for linux-pm@vger.kernel.org
 help / color / mirror / Atom feed
From: David Brownell <david-b@pacbell.net>
To: linux-pm@lists.linux-foundation.org
Cc: linux-pm <linux-pm@lists.osdl.org>, Pavel Machek <pavel@ucw.cz>
Subject: Re: [RFC] dynamic device power management proposal
Date: Thu, 22 Mar 2007 12:20:09 -0700	[thread overview]
Message-ID: <200703221220.09679.david-b@pacbell.net> (raw)
In-Reply-To: <20070321213909.GB6057@elf.ucw.cz>

On Wednesday 21 March 2007 2:39 pm, Pavel Machek wrote:

> > > USB gets the dependencies right, just copy that.
> > Does USB include all kinds of dependence, eg non parent-children
> > dependence?
> 
> No, probably not, as USB was designed properly.

It was designed to work with as few wires as possible:  "minimalist"
design.  That's not the same as "proper"; not everything works with
the same design constraints.


> How common are those cross dependencies?

Common.  SOC audio setups are relatively simple examples, which
I know have been making trouble on Linux for some time.  One hopes
that the new ALSA SOC stuff helps sort this out:

  - SOC serial controller (I2S, AC97, McBSP, SII, etc) manages
    encoded data bitsteams (e.g. N channels, PCM or uLaw, etc)
    for input, output, or both.

  - External codec interprets those bitstreams.

  - That codec is controlled using I2C, SPI, or some other bus
    for control, e.g. "set volume", "enter stereo mode".

  - The codec and serial controllers have separate power controls.

Think of this as separate control, data, and power channels;
which are not multiplexed like USB.

At the hardware level it probably looks like two different driver
model devices (I2S/etc, and codec) that could have semi-generic
drivers (I think this is what the ALSA SOC stuff is aiming for),
plus board-specific "power codec on/off" interfaces.  Then there
are the /dev interfaces ALSA creates for each functionality.


> Do we really want to solve them generically? 

What we need to be generic is:  PM not preventing good solutions.
I'm not sure we're there yet.

- Dave

  parent reply	other threads:[~2007-03-22 19:20 UTC|newest]

Thread overview: 42+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-03-19  9:08 [RFC] dynamic device power management proposal Shaohua Li
2007-03-19 15:44 ` Alan Stern
2007-03-20  1:06   ` Shaohua Li
2007-03-20 14:58     ` Alan Stern
2007-03-21  1:43       ` Shaohua Li
2007-03-21 14:44         ` Alan Stern
2007-03-22  4:42   ` Len Brown
2007-03-22 11:56     ` Jim Gettys
2007-03-22 19:28       ` David Brownell
2007-03-22 13:20     ` Pavel Machek
2007-03-22 13:44       ` Oliver Neukum
2007-03-22 13:56         ` Pavel Machek
2007-03-22 14:18           ` Oliver Neukum
2007-03-22 14:22             ` Pavel Machek
2007-03-22 14:26               ` Oliver Neukum
2007-03-22 14:35                 ` Pavel Machek
2007-03-22 19:41     ` David Brownell
2007-03-22 19:58   ` David Brownell
2007-03-20 18:30 ` Pavel Machek
2007-03-21  1:34   ` Shaohua Li
2007-03-21 15:21     ` Amit Kucheria
2007-03-21 21:49       ` Dmitry Krivoschekov
2007-03-21 22:54         ` Pavel Machek
2007-03-21 21:39     ` Pavel Machek
2007-03-22  3:09       ` Shaohua Li
2007-03-22 13:13         ` Pavel Machek
2007-03-22 19:20       ` David Brownell [this message]
2007-03-22 20:32         ` Alan Stern
2007-03-22 20:02 ` David Brownell
2007-03-22 22:10   ` Greg KH
  -- strict thread matches above, loose matches on Subject: below --
2007-03-21 20:19 Scott E. Preece
2007-03-21 21:45 ` Pavel Machek
2007-03-26 13:53 ` Amit Kucheria
2007-03-22 13:39 Scott E. Preece
2007-03-22 13:48 ` Oliver Neukum
2007-03-22 14:01 ` Pavel Machek
2007-03-22 14:45 ` Alan Stern
2007-03-22 18:53   ` David Brownell
2007-03-22 19:05 Scott E. Preece
2007-03-27 12:05 ` Pavel Machek
2007-03-27 12:19   ` Oliver Neukum
2007-03-22 19:18 Scott E. Preece

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=200703221220.09679.david-b@pacbell.net \
    --to=david-b@pacbell.net \
    --cc=linux-pm@lists.linux-foundation.org \
    --cc=linux-pm@lists.osdl.org \
    --cc=pavel@ucw.cz \
    /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