summaryrefslogtreecommitdiffstats
path: root/contrib/libc++/src
diff options
context:
space:
mode:
authoravg <avg@FreeBSD.org>2015-09-11 15:51:20 +0000
committeravg <avg@FreeBSD.org>2015-09-11 15:51:20 +0000
commitec0c2ca1353769d36779d0a76275d252d2661e12 (patch)
treec9dbb54888dfc178f8a99c82dc2fc8bf4a6b3426 /contrib/libc++/src
parentf992fbc2eda88c8a88d6289a122707b15279b892 (diff)
downloadFreeBSD-src-ec0c2ca1353769d36779d0a76275d252d2661e12.zip
FreeBSD-src-ec0c2ca1353769d36779d0a76275d252d2661e12.tar.gz
radeon_suspend_kms: don't mess with pci state that's managed by the bus
The pci bus driver handles the power state, it also manages configuration state saving and restoring for its child devices. Thus a PCI device driver does not have to worry about those things. In fact, I observe a hard system hang when trying to suspend a system with active radeonkms driver where both the bus driver and radeonkms driver try to do the same thing. I suspect that it could be because of an access to a PCI configuration register after the device is placed into D3 state. Reviewed by: dumbbell, jhb MFC after: 13 days Differential Revision: https://reviews.freebsd.org/D3561
Diffstat (limited to 'contrib/libc++/src')
0 files changed, 0 insertions, 0 deletions
OpenPOWER on IntegriCloud