On Thu, Jul 07, 2005 at 08:43:02PM -0700, [email protected] wrote: > > Some PCI devices lose all configuration (including BARs) when > > transitioning from D3hot->D0. This leaves such a device in an > Hmm, I wonder if I missed something in previous email, but exactly > why isn't this the responsibility of the driver for that device? It certainly could be handled that way. Of course, that could mean replicating essentially identical code across dozens (or more) drivers. Plus, many of those drivers might only need such changes for one variation of a device or for devices under a handful of BIOSen. Those drivers probably won't get fixed anytime soon unless some kernel hacker happens to stumble into such a situation. In the meantime, those drivers fail to work when they "should" be working. In my mind, this is a documented behaviour that should not be unexpected. It is not some random quirk of some oddball device. A few simple steps taken when this situation is recognized can allow drivers to remain unaware of this detail of PCI PM. That seems worthwhile to me. John -- John W. Linville [email protected] - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [email protected] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
- References:
- Re: [RFC] firmware leaves device in D3hot at boot
- From: "John W. Linville" <[email protected]>
- [patch 2.6.12 (repost w/ corrected subject)] pci: restore BAR values in pci_enable_device_bars
- From: "John W. Linville" <[email protected]>
- Re: [patch 2.6.12 (repost w/ corrected subject)] pci: restore BAR values in pci_enable_device_bars
- From: Grant Grundler <[email protected]>
- Re: [patch 2.6.12 (repost w/ corrected subject)] pci: restore BAR values in pci_enable_device_bars
- From: Russell King <[email protected]>
- Re: [patch 2.6.12 (repost w/ corrected subject)] pci: restore BAR values in pci_enable_device_bars
- From: Matthew Wilcox <[email protected]>
- Re: [patch 2.6.12 (repost w/ corrected subject)] pci: restore BAR values in pci_enable_device_bars
- From: Russell King <[email protected]>
- Re: [patch 2.6.12 (repost w/ corrected subject)] pci: restore BAR values in pci_enable_device_bars
- From: Ivan Kokshaysky <[email protected]>
- Re: [patch 2.6.12 (repost w/ corrected subject)] pci: restore BAR values in pci_enable_device_bars
- From: "John W. Linville" <[email protected]>
- [patch 2.6.13-rc2] pci: restore BAR values in pci_set_power_state for D3hot->D0
- From: "John W. Linville" <[email protected]>
- Re: [linux-pm] [patch 2.6.13-rc2] pci: restore BAR values in pci_set_power_state for D3hot->D0
- From: [email protected]
- Re: [RFC] firmware leaves device in D3hot at boot
- Prev by Date: [PATCH] Provide better printk() support for SMP machines [try #2]
- Next by Date: Re: share/private/slave a subtree
- Previous by thread: Re: [linux-pm] [patch 2.6.13-rc2] pci: restore BAR values in pci_set_power_state for D3hot->D0
- Next by thread: Re: [patch 2.6.12 (repost w/ corrected subject)] pci: restore BAR values in pci_enable_device_bars
- Index(es):
