[lkml]   [2005]   [Aug]   [1]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
Messages in this thread
SubjectRe: revert yenta free_irq on suspend

> > You said earlier we only should fix drivers that need fixing, but they
> > all need fixing
> I think you're still talking from a theoretical standpoing, while all my
> arguments are practical.
> In _practice_, I hope that
> (a) we don't see that very much (ie the people for whom things work
> already are a strong argument that this is less of a problem in
> practice than people try to make it appear)
> (b) drivers, _especially_ on notebooks, are already able to handle an
> incoming interrupt with the device in D3 state and returning 0xff
> for all reads.
> In particular, this is exactly the same thing that you get on a
> surprise device removal too.

Not all devices that we want power-managed are hot-pluggable, even on
notebooks. If I need to go all over the tree fixing drivers, I'd much
rather add free_irq/request_irq than mess with interrupt routines on
hardware I don't have...
if you have sharp zaurus hardware you don't need... you know my address
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to
More majordomo info at
Please read the FAQ at

 \ /
  Last update: 2005-08-01 09:20    [W:0.075 / U:0.236 seconds]
©2003-2018 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site