1. 25 11月, 2008 1 次提交
    • D
      wusb: whci-hcd shouldn't do ASL/PZL updates while channel is inactive · 56968d0c
      David Vrabel 提交于
      ASL/PZL updates while the WUSB channel is inactive (i.e., the PZL and
      ASL are stopped) may not complete.  This causes hangs when removing the
      whci-hcd module if a device is still connected (removing the device
      does an endpoint_disable which results in an ASL update to remove the
      qset).
      
      If the WUSB channel is inactive the update can simply be skipped as the
      WHC doesn't care about the state of the ASL/PZL.
      Signed-off-by: NDavid Vrabel <david.vrabel@csr.com>
      56968d0c
  2. 20 11月, 2008 8 次提交
  3. 19 11月, 2008 1 次提交
    • D
      uwb: add basic radio manager · 6fae35f9
      David Vrabel 提交于
      The UWB radio manager coordinates the use of the radio between the
      PALs that may be using it.  PALs request use of the radio with
      uwb_radio_start() and the radio manager will start beaconing if its
      not already doing so.  When the last PAL has called uwb_radio_stop()
      beaconing will be stopped.
      
      In the future, the radio manager will have a more sophisticated channel
      selection algorithm, probably following the Channel Selection Policy
      from the WiMedia Alliance when it is finalized.  For now, channel 9
      (BG1, TFC1) is selected.
      
      The user may override the channel selected by the radio manager and may
      force the radio to stop beaconing.
      
      The WUSB Host Controller PAL makes use of this and there are two new
      debug PAL commands that can be used for testing.
      Signed-off-by: NDavid Vrabel <david.vrabel@csr.com>
      6fae35f9
  4. 14 11月, 2008 23 次提交
  5. 12 11月, 2008 2 次提交
  6. 02 11月, 2008 1 次提交
    • A
      saner FASYNC handling on file close · 233e70f4
      Al Viro 提交于
      As it is, all instances of ->release() for files that have ->fasync()
      need to remember to evict file from fasync lists; forgetting that
      creates a hole and we actually have a bunch that *does* forget.
      
      So let's keep our lives simple - let __fput() check FASYNC in
      file->f_flags and call ->fasync() there if it's been set.  And lose that
      crap in ->release() instances - leaving it there is still valid, but we
      don't have to bother anymore.
      Signed-off-by: NAl Viro <viro@zeniv.linux.org.uk>
      Signed-off-by: NLinus Torvalds <torvalds@linux-foundation.org>
      233e70f4
  7. 31 10月, 2008 2 次提交
  8. 30 10月, 2008 2 次提交