Re: Shutting down PCI devices on suspend

[Arjen Verweij <a.verweij-oe7qfRrRQfeEZXFvZSAUrfP6llvjuJOh@public.gmane.org>]

Matthew,

I asked a similar question some time ago, to figure out what is needed 
to add Wake-on-Lan support. The NIC needs to be put into D3 state, but 
this doesn't happen automagically. Currently I use pci-config from the 
scyld website to accomplish this right before powerdown.

Hopefully someone can comment on how it should work (tm), my guess is 
that device drivers need to be signalled, and hence it will only work if 
the driver supports it. I know from the ATi forum that the linux driver 
does not support this (yet).

Maybe you can use pci-config as a work around.
http://www.scyld.com/diag/index.html
ftp://ftp.scyld.com/pub/diag/pci-config.c
http://atlas.et.tudelft.nl/verwei90/nforce2/scyld/pci-config.c (mirror)
Compile with: gcc-2.95 -O pci-config.c -o pci-config

Regards,

Arjen

Matthew Garrett wrote:

>The default PCI suspend/resume calls (used if the driver doesn't
>implement them itself) don't alter the device power state. This seems to
>cause problems on some Thinkpads - going into S3 doesn't seem to result
>in the on-board Radeon being put into D3, and as a result the battery is
>drained at a higher rate than it should be. Who should be responsible
>for making sure that devices are properly put to sleep:
>
>1) The drivers (not immensely helpful in the case where we don't
>necessarily have drivers registered for every device)
>2) The kernel
>3) The hardware itself?
>
>I seem to remember someone mentioning something about Linux not checking
>for hints from the hardware as to what state devices should be put in,
>but I know little about this.
>  
>


-------------------------------------------------------
SF email is sponsored by - The IT Product Guide
Read honest & candid reviews on hundreds of IT Products from real users.
Discover which products truly live up to the hype. Start reading now. 
http://productguide.itmanagersjournal.com/