From: Nigel Cunningham <nigel@nigel.suspend2.net>
To: "Rafael J. Wysocki" <rjw@sisk.pl>
Cc: pm list <linux-pm@lists.osdl.org>,
LKML <linux-kernel@vger.kernel.org>,
Arjan van de Ven <arjan@infradead.org>
Subject: Re: NAK new drivers without proper power management?
Date: Sat, 10 Feb 2007 09:51:29 +1100 [thread overview]
Message-ID: <1171061489.1484.100.camel@nigel.suspend2.net> (raw)
In-Reply-To: <200702092344.14984.rjw@sisk.pl>
Hi.
On Fri, 2007-02-09 at 23:44 +0100, Rafael J. Wysocki wrote:
> On Friday, 9 February 2007 23:26, Nigel Cunningham wrote:
> > Hi.
> >
> > On Fri, 2007-02-09 at 23:17 +0100, Arjan van de Ven wrote:
> > > On Sat, 2007-02-10 at 08:57 +1100, Nigel Cunningham wrote:
> > > > Hi.
> > > >
> > > > I don't think this is already done (feel free to correct me if I'm
> > > > wrong)..
> > > >
> > > > Can we start to NAK new drivers that don't have proper power management
> > > > implemented? There really is no excuse for writing a new driver and not
> > > > putting .suspend and .resume methods in anymore, is there?
> > >
> > >
> > > to a large degree, a device driver that doesn't suspend is better than
> > > no device driver at all, right?
> >
> > I'm not sure it is. It only makes more work for everyone else: We have
> > to help people figure out what causes their computer to fail to resume
> > (which can take quite a while), then get them them complain to driver
> > author, and the driver author has to submit patches to fix it.
> >
> > All of this is avoided if they'll just do it right in the first place.
> >
> > > now.. if you want to make the core warn about it, that's very fair
> >
> > That's probably a good idea too, since I'm only suggesting this for new
> > drivers.
>
> I think if CONFIG_PM_DEBUG is set, the core should warn about drivers not
> having .suspend or .resume routines.
The only problem with that is, not everyone turns on CONFIG_PM_DEBUG.
CONFIG_PM instead?
Regards,
Nigel
next prev parent reply other threads:[~2007-02-09 22:51 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1171058269.1484.64.camel@nigel.suspend2.net>
[not found] ` <1171059433.8675.195.camel@laptopd505.fenrus.org>
[not found] ` <1171059968.1484.90.camel@nigel.suspend2.net>
2007-02-09 22:44 ` NAK new drivers without proper power management? Rafael J. Wysocki
2007-02-09 22:51 ` Nigel Cunningham [this message]
2007-02-09 23:12 ` Rafael J. Wysocki
2007-02-09 23:28 ` Nigel Cunningham
2007-02-10 0:12 ` 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=1171061489.1484.100.camel@nigel.suspend2.net \
--to=nigel@nigel.suspend2.net \
--cc=arjan@infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pm@lists.osdl.org \
--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