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 35 次提交
  3. 19 11月, 2008 4 次提交
    • D
      uwb: remove unused beacon group join/leave events · 0996e638
      David Vrabel 提交于
      The UWB_NOTIF_BG_JOIN/UWB_NOTIF_BG_LEAVE events have been
      superceeded by the channel_changed callback in struct uwb_pal.
      Signed-off-by: NDavid Vrabel <david.vrabel@csr.com>
      0996e638
    • D
      e8e1594c
    • 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
    • F
      intel-iommu: fix compile warnings · b4e0f9eb
      FUJITA Tomonori 提交于
      Impact: cleanup
      
      I got the following warnings on IA64:
      
        linux-2.6/drivers/pci/intel-iommu.c: In function 'init_dmars':
        linux-2.6/drivers/pci/intel-iommu.c:1658: warning: format '%Lx' expects type 'long long unsigned int', but argument 2 has type 'u64'
        linux-2.6/drivers/pci/intel-iommu.c:1663: warning: format '%Lx' expects type 'long long unsigned int', but argument 2 has type 'u64'
      
      Another victim of int-ll64.h versus int-l64.h confusion between platforms.
      
      ->reg_base_addr has a type of u64 - which can only be printed out
      consistently if we cast its type up to LL.
      
      [ Eventually reg_base_addr should be converted to phys_addr_t, for which
        we have the %pR printk helper - but that is out of the scope of late
        -rc's. ]
      Signed-off-by: NFUJITA Tomonori <fujita.tomonori@lab.ntt.co.jp>
      Signed-off-by: NIngo Molnar <mingo@elte.hu>
      b4e0f9eb