Skip to content

R
raspberrypi-kernel

openeuler / raspberrypi-kernel

通知 13
Star 1
Fork 0
R
raspberrypi-kernel
切换分支/标签
  1. 16 11月, 2011 9 次提交
  3. 01 11月, 2011 2 次提交
  5. 18 9月, 2011 2 次提交
  7. 15 9月, 2011 1 次提交
  9. 10 9月, 2011 1 次提交
  11. 25 8月, 2011 1 次提交
  13. 23 8月, 2011 1 次提交
    • S
      usb_storage: Don't freeze in usb-stor-scan · f02fe890
      由 Seth Forshee 提交于 
      Scanning cannot be run during suspend or hibernation, but if
usb-stor-scan freezes another thread waiting on scanning to
complete may fail to freeze.

However, if usb-stor-scan is left freezable without ever actually
freezing then the freezer will wait on it to exit, and threads
waiting for scanning to finish will no longer be blocked. One
problem with this approach is that usb-stor-scan has a delay to
wait for devices to settle (which is currently the only point where
it can freeze). To work around this we can request that the freezer
send a fake signal when freezing, then use interruptible sleep to
wake the thread early when freezing happens.

To make this happen, the following changes are made to
usb-stor-scan:

 * Use set_freezable_with_signal() instead of set_freezable() to
   request a fake signal when freezing

 * Use wait_event_interruptible_timeout() instead of
   wait_event_freezable_timeout() to avoid freezing
Signed-off-by: NSeth Forshee <seth.forshee@canonical.com>
Acked-by: NAlan Stern <stern@rowland.harvard.edu>
Signed-off-by: NGreg Kroah-Hartman <gregkh@suse.de>
      f02fe890
  15. 09 8月, 2011 1 次提交
  17. 09 7月, 2011 1 次提交
  19. 02 7月, 2011 3 次提交
  21. 08 6月, 2011 1 次提交
    • A
      usb-storage: redo incorrect reads · 21c13a4f
      由 Alan Stern 提交于 
      Some USB mass-storage devices have bugs that cause them not to handle
the first READ(10) command they receive correctly.  The Corsair
Padlock v2 returns completely bogus data for its first read (possibly
it returns the data in encrypted form even though the device is
supposed to be unlocked).  The Feiya SD/SDHC card reader fails to
complete the first READ(10) command after it is plugged in or after a
new card is inserted, returning a status code that indicates it thinks
the command was invalid, which prevents the kernel from retrying the
read.

Since the first read of a new device or a new medium is for the
partition sector, the kernel is unable to retrieve the device's
partition table.  Users have to manually issue an "hdparm -z" or
"blockdev --rereadpt" command before they can access the device.

This patch (as1470) works around the problem.  It adds a new quirk
flag, US_FL_INVALID_READ10, indicating that the first READ(10) should
always be retried immediately, as should any failing READ(10) commands
(provided the preceding READ(10) command succeeded, to avoid getting
stuck in a loop).  The patch also adds appropriate unusual_devs
entries containing the new flag.
Signed-off-by: NAlan Stern <stern@rowland.harvard.edu>
Tested-by: NSven Geggus <sven-usbst@geggus.net>
Tested-by: NPaul Hartman <paul.hartman+linux@gmail.com>
CC: Matthew Dharm <mdharm-usb@one-eyed-alien.net>
CC: <stable@kernel.org>
Signed-off-by: NGreg Kroah-Hartman <gregkh@suse.de>
      21c13a4f
  23. 20 5月, 2011 1 次提交
  25. 18 5月, 2011 1 次提交
  27. 01 5月, 2011 1 次提交
  29. 26 4月, 2011 1 次提交
  31. 31 3月, 2011 1 次提交
  33. 12 3月, 2011 3 次提交
  35. 08 3月, 2011 1 次提交
  37. 03 3月, 2011 1 次提交
  39. 18 2月, 2011 2 次提交
  41. 04 2月, 2011 2 次提交
  43. 23 1月, 2011 3 次提交