public inbox for linux-pm@vger.kernel.org
 help / color / mirror / Atom feed
From: Willy Tarreau <w@1wt.eu>
To: "Rafael J. Wysocki" <rjw@sisk.pl>
Cc: Robert Hancock <hancockr@shaw.ca>,
	Matthew Garrett <mjg59@srcf.ucam.org>,
	Pavel Machek <pavel@ucw.cz>, Jeff Garzik <jeff@garzik.org>,
	Daniel Barkalow <barkalow@iabervon.org>,
	pm list <linux-pm@lists.osdl.org>,
	linux-kernel <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] Re: NAK new drivers without proper power management?
Date: Sun, 11 Feb 2007 14:57:08 +0100	[thread overview]
Message-ID: <20070211135708.GC1868@1wt.eu> (raw)
In-Reply-To: <200702111450.49736.rjw@sisk.pl>

On Sun, Feb 11, 2007 at 02:50:48PM +0100, Rafael J. Wysocki wrote:
> On Sunday, 11 February 2007 14:37, Willy Tarreau wrote:
> > On Sun, Feb 11, 2007 at 01:19:57PM +0000, Matthew Garrett wrote:
> > > On Sun, Feb 11, 2007 at 02:09:43PM +0100, Willy Tarreau wrote:
> > > 
> > > > Then change the PCI layer to do the basic PM only for known compatible
> > > > drivers, and modify only the known-compatible drivers to mark them
> > > > explicitly compatible. IMHO, it generally is a bad idea to require that
> > > > any driver explicitly states what it *does not* support. It's the reason
> > > > why users encounter problem on new features with old drivers. For instance,
> > > > do you know if the old ISA NE2000 driver breaks suspend ? I don't know,
> > > > but I would at least expect it not to support it by default. It's best
> > > > to announce what *is* supported and consider everything unimplemented
> > > > otherwise explicitly stated.
> > > 
> > > This ignores the reality of the situation, which is that many drivers 
> > > support suspend and resume despite the lack of any explicit 
> > > implementation. Changing things so they're flagged as broken when 
> > > they're not would be a regression.
> > 
> > Those which are identified as OK should be flagged OK. Only those for
> > which we have no idea should be flagged broken.
> 
> I think we don't need to flag the drivers identified as OK.  Let's flag only
> the suspicious ones.
> 
> Whatever we finally come up with, I'd like to avoid modifying drivers that are
> known good.

I understand your concerns, but the problem is not *current* drivers, but
what will happen to *new* drivers. If we make it implicit that a driver
is compatible, then new drivers will be promoted as good even if nothing
has been done for this.

Regards,
Willy

  reply	other threads:[~2007-02-11 13:57 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <fa.xSKPgY66Q+DPCZ1pszFFfdrJ0To@ifi.uio.no>
     [not found] ` <45CD24F6.8090107@shaw.ca>
     [not found]   ` <1171076554.10170.5.camel@nigel.suspend2.net>
2007-02-10  9:34     ` [PATCH] Re: NAK new drivers without proper power management? Rafael J. Wysocki
2007-02-10 10:02       ` Nigel Cunningham
2007-02-10 10:30         ` Rafael J. Wysocki
2007-02-10 17:52           ` Daniel Barkalow
2007-02-10 19:50             ` Rafael J. Wysocki
2007-02-11  6:54               ` Willy Tarreau
2007-02-11 12:13                 ` Matthew Garrett
2007-02-11 13:09                   ` Willy Tarreau
2007-02-11 13:19                     ` Matthew Garrett
2007-02-11 13:37                       ` Willy Tarreau
2007-02-11 13:50                         ` Rafael J. Wysocki
2007-02-11 13:57                           ` Willy Tarreau [this message]
2007-02-11 14:36                             ` Rafael J. Wysocki
2007-02-11 15:19                               ` Pekka Enberg
2007-02-11 18:31                                 ` Rafael J. Wysocki
2007-02-11 17:27                               ` Daniel Barkalow
2007-02-11 18:53                                 ` Rafael J. Wysocki
2007-02-11 23:06                                   ` Nigel Cunningham
2007-02-11 23:10                                     ` Rafael J. Wysocki
2007-02-11 21:04                               ` Stefan Richter
2007-02-11 21:10                     ` Pavel Machek
2007-02-11 17:36                   ` Robert Hancock
2007-02-11 22:49                   ` Nigel Cunningham
2007-02-11 19:37             ` 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=20070211135708.GC1868@1wt.eu \
    --to=w@1wt.eu \
    --cc=barkalow@iabervon.org \
    --cc=hancockr@shaw.ca \
    --cc=jeff@garzik.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-pm@lists.osdl.org \
    --cc=mjg59@srcf.ucam.org \
    --cc=pavel@ucw.cz \
    --cc=rjw@sisk.pl \
    /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