You might want to read what I wrote in #112 because it might be that you're not getting all the power savings you should.

@Lekensteyn Any thoughts on this patch? Maybe we could first ship it this way an tell people who want to that they can try it, and if no issue arise, either make it the default or mix it with current way of doing things (in case they are some corner cases for this new method).

@Lekensteyn: as @smunaut noticed, my patch does fix the corruption issue, but the card is only put in D3 and not powered off, at least on recent Lenovo firmware versions. For that, one need to put the PCIe root in D3 (which Linux does not do automatically). @smunaut has a working hack that does it.
(#112). I say a hack because it turns the PCIe root off without telling the linux driver about it ....

Sorry for the delay, I could not give a meaningful response before. Now I looked into the details again and your (and @smunaut) observations are correct, _DSM cannot be used for turning it off. See also #115 (comment) for an initial analysis.

_PS3 only brings a device in D3hot state, so it is indeed not fully off (and the reported value by bbswitch is correct, it is indeed still ON). For the device to be put in fully off state (D3cold), the power resources have to be disabled (see the earlier comment for a reference to the ACPI specification).

If I remember correctly, the pci-set_power_state functions do correctly call _PS3 (bbswitch should probably use PCI_D3hot instead of PCI_D3cold for normal cases). Your patch tries to make bbswitch report OFF when the device is (hopefully) in D3hot, right? I think that we need something like #112 (have yet to review that, but if the idea is to put the parent PCIe port in OFF state, I think it is a good direction).

Yes. This PR is obsolete now that we @smunaut found the real underlying issue.