Repository files (latest commit first)

Filename	Latest commit message	Latest commit date
Linus Torvalds f007cad159 Revert "firmware: add sanity check on shutdown/suspend" ... This reverts commit 81f9507628. It causes random failures of firmware loading at resume time (well, random for me, it seems to be more reliable for others) because the firmware disabling is not actually synchronous with any particular resume event, and at least the btusb driver that uses a workqueue to load the firmware at resume seems to occasionally hit the "firmware loading is disabled" logic because the firmware loader hasn't gotten the resume event yet. Some kind of sanity check for not trying to load firmware when it's not possible might be a good thing, but this commit was not it. Greg seems to have silently suffered the same issue, and pointed to the likely culprit, and Gabriel C verified the revert fixed it for him too. Reported-by: Linus Torvalds <torvalds@linux-foundation.org> Pointed-at-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org> Tested-by: Gabriel C <nix.or.die@gmail.com> Cc: Luis R. Rodriguez <mcgrof@kernel.org> Signed-off-by: Linus Torvalds <torvalds@linux-foundation.org>		2017-09-10 21:19:06 -07:00
..
80211
firmware	Revert "firmware: add sanity check on shutdown/suspend"	2017-09-10 21:19:06 -07:00
iio
pm
usb
basics.rst
conf.py
device-io.rst
device_link.rst
dma-buf.rst
edac.rst
frame-buffer.rst
gpio.rst
hsi.rst
i2c.rst
index.rst
infrastructure.rst
input.rst
libata.rst
message-based.rst
misc_devices.rst
miscellaneous.rst
mtdnand.rst
pci.rst
pinctl.rst
rapidio.rst
regulator.rst
s390-drivers.rst
scsi.rst
sound.rst
spi.rst
uio-howto.rst
vme.rst
w1.rst