Jeff Garzik wrote:
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.
A lot of a lot of things could have been avoided, if they just did it
right the first time.
I think it's more valuable to users to get a basic network driver that
pings or a basic ATA driver that reads/writes, than peripheral issues
like suspend/resume.
Certainly we should ask for it, but it shouldn't be a merge-stopper.
Jeff
I would disagree that it's a peripheral issue, it's pretty core these
days, at least for any hardware that you can stuff in a laptop (though a
fair number of desktops get suspended and resumed these days too). One
driver on a system which doesn't suspend or resume properly can ruin the
entire process, causing a ton of user frustration. Certainly I would
consider a driver without suspend/resume support to be incomplete.
The trouble with deferring adding this support is that it's a lot harder
to add this support in after the fact than if it was considered during
the original driver development.
I would be in favor of not merging drivers lacking suspend unless
there's a very good reason they're lacking it.
It also kind of bothers me that if a driver has no suspend/resume
functions, and you suspend and resume the system, we don't complain
about it even though there's a very good chance that device is not going
to function properly. How about something in dmesg like:
Warning: driver for device XXXX has no suspend or resume support.
Device may not function properly after resume.
so that users know who to complain to. Maybe there are some devices that
truly don't need any handling for suspend, but if so I suspect the
number of those is small enough that adding empty functions would be a
good-enough solution.
--
Robert Hancock Saskatoon, SK, Canada
To email, remove "nospam" from [email protected]
Home Page: http://www.roberthancock.com/
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [email protected]
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
[Index of Archives]
[Kernel Newbies]
[Netfilter]
[Bugtraq]
[Photo]
[Stuff]
[Gimp]
[Yosemite News]
[MIPS Linux]
[ARM Linux]
[Linux Security]
[Linux RAID]
[Video 4 Linux]
[Linux for the blind]
[Linux Resources]
