Re: swsusp: don't eat ide disks

[Pavel Machek <pavel@ucw.cz>]

Hi!

> > > Some disks are going to be settint their own power methods too.
> > 
> > Fine with me as long as they call idedisk_suspend() first ;-).
> 
> They may or may not do so depending upon other considerations. The new
> driver layer is supposed to handle suspend/power ordering. If it doesn't
> then it needs fixing. You can't go around hacking weird suspend shit
> into every single block driver for a final system, sure for a prototype
> but not the real thing. No way

Suspend *needs* to touch all drivers.

I do stopping at high levels already (all tasks are put into
refrigerator), but that can still me that DMA on particular driver is
in progress. Only driver itself knows if it is doing any DMA and how
to stop it. I do not see how to do it on upper layers.

[Take for example USB. It is not block device, still it does DMA which
means it has to be stopped.]
								Pavel
-- 
Worst form of spam? Adding advertisment signatures ala sourceforge.net.
What goes next? Inserting advertisment *into* email?