Thanks for your very (!!!) fast response :-)
> > http://www.red-bean.com/~proski/linux/ymfpci_pm.diff
>
> Why not use pci_driver::{suspend,resume} ?
I'm just a bit conservative. There are several drivers that don't use this
mechanism, notably trident and maestro. Do you think it's safe to switch
all sound drivers to the mechanism you are proposing?
I'm worried about a comment in maestro.c:
/*
* we'd also like to find out about
* power level changes because some biosen
* do mean things to the maestro when they
* change their power state.
*/
If we switch to pci_driver::{suspend,resume}, will it ever be possible to
add support for any messages other than PM_SUSPEND and PM_RESUME? Probably
yes, but only in the PCI driver dispatches them.
By the way, I don't like the way how pm_unregister_all() is used in
several sound drivers. If a unit is removed its power manager callback
remains registered until the module is unloaded.
> In ACPI land the kernel should save and restore the PCI device config
> space and the PCI bus config space. It is probably that similar is
> necessary under APM.
I have never seen any sound driver doing that. I also know that PCI
settings are saved by some BIOSes on some hardware.
I'm sorry if I put it wrong. Perhaps I should have added a few IMHO.
PS. The 0x20 bit in 0x40 is not set if I load CVS ALSA drivers, even if I
set it before loading the driver. It's a problem with the kernel driver
only and should be fixed IMHO.
-- Regards, Pavel Roskin- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/