1. 28 6月, 2008 2 次提交
    • K
      pciehp: use get_service_data · b9708940
      Kenji Kaneshige 提交于
      Current pciehp driver saves its private data pointer into pci_dev
      structure using pci_set_drvdata()/pci_get_drvdata(). But because
      pciehp is not a pci device driver but a PCI Express service driver, it
      should save its private data pointer into pcie_device structure using
      set_service_data()/get_service_data().
      Signed-off-by: NKenji Kaneshige <kaneshige.kenji@jp.fujitsu.com>
      Signed-off-by: NJesse Barnes <jbarnes@virtuousgeek.org>
      b9708940
    • K
      pciehp: fix interrupt initialization · c4635eb0
      Kenji Kaneshige 提交于
      Current pciehp driver's intialization sequence is as follows:
      
      (1) initialize controller data structure
      (2) install interrupt handler
      (3) enable software notification
      (4) initialize controller specific slot data structure
      (5) initialize generic slot data structure and register it to pci hotplug core
      
      The interrupt handler of pciehp assumes that controller specific slot
      data structure is already initialized. However, it is installed at (2)
      before initializing controller specific slot data structure at
      (4). Because of this, pciehp driver cannot handle the following cases
      properly.
      
      - If devices that shares IRQ with pciehp raise interrupts between (2) and (4).
      - If hotplug events (e.g. MRL open) happen between (3) and (4).
      
      We already have a workaround for this problem ("pciehp: fix NULL
      dereference in interrupt handler: dbd79aed).
      But we still need fundamental fix.
      
      This patch fix the problem by changing the initilization sequence as follows:
      
      (1) initialize controller data structure
      (2) initialize controller specific slot data structure
      (3) install interrupt handler
      (4) enable software notification
      (5) initialize generic slot data structure and register it to pci hotplug core
      Signed-off-by: NKenji Kaneshige <kaneshige.kenji@jp.fujitsu.com>
      Acked-by: NAlex Chiang <achiang@hp.com>
      Signed-off-by: NJesse Barnes <jbarnes@virtuousgeek.org>
      c4635eb0
  2. 11 6月, 2008 4 次提交
  3. 28 5月, 2008 1 次提交
  4. 26 4月, 2008 2 次提交
  5. 21 4月, 2008 1 次提交
  6. 18 3月, 2008 1 次提交
    • M
      pciehp: don't enable slot unless forced · 9e585824
      Mark Lord 提交于
      This fixes a 2.6.25 regression reported by Alex Chiang.
      
      Invoke pciehp_enable_slot() at startup only when pciehp_force=1.
      Some HP equipment apparently cannot cope with it otherwise.
      
      This restores the (previously working) 2.6.24 behaviour here,
      while allowing machines that need a kick to use pciehp_force=1.
      
      This was the original design back in October 2007,
      but Kristen suggested we try without it first:
      
         Kristen Carlson Accardi wrote:
         >I think it would be ok to try allowing the slot to be enabled when not
         >using pciehp_force mode.  We can wrap it later if it proves to break things
      
      This ended up breaking one of Alex's setups,
      so it's time to put the wrapper back in now.
      Signed-off-by: NMark Lord <mlord@pobox.com>
      Acked-by: NAlex Chiang <achiang@hp.com>
      Acked-by: NKristen Carlson Accardi <kristen.c.accardi@intel.com>
      Signed-off-by: NLinus Torvalds <torvalds@linux-foundation.org>
      9e585824
  7. 02 2月, 2008 4 次提交
  8. 13 10月, 2007 2 次提交
  9. 03 5月, 2007 3 次提交
  10. 08 2月, 2007 7 次提交
  11. 02 12月, 2006 1 次提交
  12. 19 10月, 2006 1 次提交
  13. 20 6月, 2006 1 次提交
  14. 24 3月, 2006 2 次提交
  15. 10 1月, 2006 2 次提交
  16. 11 11月, 2005 6 次提交