summaryrefslogtreecommitdiffstats
path: root/sys/dev/firewire
diff options
context:
space:
mode:
authorimp <imp@FreeBSD.org>2003-07-03 14:00:57 +0000
committerimp <imp@FreeBSD.org>2003-07-03 14:00:57 +0000
commite9df6b7a142eb6576de449a7025b728f30224161 (patch)
tree584c5d95c565a7220199ac4f80f117d25995ead7 /sys/dev/firewire
parent2d545c0325ebd6225a22298a5cffc0570a56fb16 (diff)
downloadFreeBSD-src-e9df6b7a142eb6576de449a7025b728f30224161.zip
FreeBSD-src-e9df6b7a142eb6576de449a7025b728f30224161.tar.gz
All current uses of pci_set_powerstate are bogus, at least in theory.
However, they are presently necessary due to bigger bogusness in the pci bus layer not doing the right thing on suspend/resume or on initial device probe. This is exactly the sort of thing that the BURN_BRIDGES option was invented for. Mark all of them as BURN_BRIDGES. As soon as I have the powerstate stuff properly integrated into the pci bus code, I intend to remove all these workarounds.
Diffstat (limited to 'sys/dev/firewire')
-rw-r--r--sys/dev/firewire/fwohci_pci.c2
1 files changed, 2 insertions, 0 deletions
diff --git a/sys/dev/firewire/fwohci_pci.c b/sys/dev/firewire/fwohci_pci.c
index 044621f..4166239 100644
--- a/sys/dev/firewire/fwohci_pci.c
+++ b/sys/dev/firewire/fwohci_pci.c
@@ -403,9 +403,11 @@ fwohci_pci_resume(device_t dev)
{
fwohci_softc_t *sc = device_get_softc(dev);
+#ifndef BURN_BRIDGES
device_printf(dev, "fwohci_pci_resume: power_state = 0x%08x\n",
pci_get_powerstate(dev));
pci_set_powerstate(dev, PCI_POWERSTATE_D0);
+#endif
fwohci_pci_init(dev);
fwohci_resume(sc, dev);
return 0;
OpenPOWER on IntegriCloud