public inbox for linux-pm@vger.kernel.org
 help / color / mirror / Atom feed
From: David Brownell <david-b@pacbell.net>
To: linux-pm@lists.osdl.org
Cc: Pavel Machek <pavel@ucw.cz>
Subject: Re: [RFC] Linux Power Management
Date: Mon, 9 May 2005 09:41:49 -0700	[thread overview]
Message-ID: <200505090941.49405.david-b@pacbell.net> (raw)
In-Reply-To: <20050509094904.GA19790@atrey.karlin.mff.cuni.cz>

[-- Attachment #1: Type: text/plain, Size: 1491 bytes --]

On Monday 09 May 2005 2:49 am, Pavel Machek wrote:
> > > ... However, I don't think this will be common, ...
> > 
> > When you "don't think this will be common" you're basically assuming
> > Linux won't be used on embedded hardware.   Unhealthy assumption!!
> > 
> > It's **really easy** and in fact natural for hardware designers to
> > provide power management relationships that don't directly match
> > the logical bus structure that software likes to use. ...
> 
> Well, people can mess up hardware any way they like, but don't expect
> us to mess up linux to match...

Hardly.  On the other hand, if Linux can't handle such simple
and common hardware models, it's already been messed up.


> If they use GPIO lines on chip that eats so much power that it must be
> power-managed... yes, I'd call that broken hardware.

By virtue of being in the driver model, it _is_ managed no
matter how much power it uses (or doesn't use).  The issue
isn't how much power it uses.  It's the expectation that all
power signals only flow parallel to data and control busses,
as they would on daughtercard based designs.

I'd tend to agree with hardware guys on this one:  this is
such a simple case that only broken _software_ should have
trouble handling it.


> Of course, current pm core *is* inadequate for even simple uses...

Right, and GPIO based power switching is a "simple use".
Luckily the init sequence tweaks I described make Linux
work with it, until selective suspend kicks in.

- Dave

[-- Attachment #2: Type: text/plain, Size: 0 bytes --]



  reply	other threads:[~2005-05-09 16:41 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-05-03  4:32 [RFC] Linux Power Management Adam Belay
2005-05-03  6:06 ` Nigel Cunningham
2005-05-03 15:52 ` Alan Stern
2005-05-05  4:39   ` Adam Belay
2005-05-08 18:35     ` David Brownell
2005-05-09  9:49       ` Pavel Machek
2005-05-09 16:41         ` David Brownell [this message]
2005-05-09 19:30           ` Pavel Machek
2005-05-03 21:40 ` Pavel Machek
2005-05-05  4:12   ` Adam Belay
2005-05-05  9:38     ` Pavel Machek
2005-05-08 18:39       ` David Brownell
2005-05-09  8:35         ` Pavel Machek
2005-05-08 18:31 ` David Brownell
2005-05-09  3:26   ` Adam Belay
2005-05-09 16:02     ` David Brownell

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=200505090941.49405.david-b@pacbell.net \
    --to=david-b@pacbell.net \
    --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