1. 26 9月, 2008 1 次提交
  2. 06 9月, 2008 1 次提交
  3. 10 8月, 2008 2 次提交
  4. 07 8月, 2008 3 次提交
  5. 27 7月, 2008 2 次提交
    • D
      [ARM] 5179/1: Replace obsolete IRQT_* and __IRQT_* values with IRQ_TYPE_* · 6cab4860
      Dmitry Baryshkov 提交于
      IRQT_* and __IRQT_* were obsoleted long ago by patch [3692/1].
      Remove them completely. Sed script for the reference:
      
      s/__IRQT_RISEDGE/IRQ_TYPE_EDGE_RISING/g
      s/__IRQT_FALEDGE/IRQ_TYPE_EDGE_FALLING/g
      s/__IRQT_LOWLVL/IRQ_TYPE_LEVEL_LOW/g
      s/__IRQT_HIGHLVL/IRQ_TYPE_LEVEL_HIGH/g
      s/IRQT_RISING/IRQ_TYPE_EDGE_RISING/g
      s/IRQT_FALLING/IRQ_TYPE_EDGE_FALLING/g
      s/IRQT_BOTHEDGE/IRQ_TYPE_EDGE_BOTH/g
      s/IRQT_LOW/IRQ_TYPE_LEVEL_LOW/g
      s/IRQT_HIGH/IRQ_TYPE_LEVEL_HIGH/g
      s/IRQT_PROBE/IRQ_TYPE_PROBE/g
      s/IRQT_NOEDGE/IRQ_TYPE_NONE/g
      Signed-off-by: NDmitry Baryshkov <dbaryshkov@gmail.com>
      Signed-off-by: NRussell King <rmk+kernel@arm.linux.org.uk>
      6cab4860
    • F
      dma-mapping: add the device argument to dma_mapping_error() · 8d8bb39b
      FUJITA Tomonori 提交于
      Add per-device dma_mapping_ops support for CONFIG_X86_64 as POWER
      architecture does:
      
      This enables us to cleanly fix the Calgary IOMMU issue that some devices
      are not behind the IOMMU (http://lkml.org/lkml/2008/5/8/423).
      
      I think that per-device dma_mapping_ops support would be also helpful for
      KVM people to support PCI passthrough but Andi thinks that this makes it
      difficult to support the PCI passthrough (see the above thread).  So I
      CC'ed this to KVM camp.  Comments are appreciated.
      
      A pointer to dma_mapping_ops to struct dev_archdata is added.  If the
      pointer is non NULL, DMA operations in asm/dma-mapping.h use it.  If it's
      NULL, the system-wide dma_ops pointer is used as before.
      
      If it's useful for KVM people, I plan to implement a mechanism to register
      a hook called when a new pci (or dma capable) device is created (it works
      with hot plugging).  It enables IOMMUs to set up an appropriate
      dma_mapping_ops per device.
      
      The major obstacle is that dma_mapping_error doesn't take a pointer to the
      device unlike other DMA operations.  So x86 can't have dma_mapping_ops per
      device.  Note all the POWER IOMMUs use the same dma_mapping_error function
      so this is not a problem for POWER but x86 IOMMUs use different
      dma_mapping_error functions.
      
      The first patch adds the device argument to dma_mapping_error.  The patch
      is trivial but large since it touches lots of drivers and dma-mapping.h in
      all the architecture.
      
      This patch:
      
      dma_mapping_error() doesn't take a pointer to the device unlike other DMA
      operations.  So we can't have dma_mapping_ops per device.
      
      Note that POWER already has dma_mapping_ops per device but all the POWER
      IOMMUs use the same dma_mapping_error function.  x86 IOMMUs use device
      argument.
      
      [akpm@linux-foundation.org: fix sge]
      [akpm@linux-foundation.org: fix svc_rdma]
      [akpm@linux-foundation.org: build fix]
      [akpm@linux-foundation.org: fix bnx2x]
      [akpm@linux-foundation.org: fix s2io]
      [akpm@linux-foundation.org: fix pasemi_mac]
      [akpm@linux-foundation.org: fix sdhci]
      [akpm@linux-foundation.org: build fix]
      [akpm@linux-foundation.org: fix sparc]
      [akpm@linux-foundation.org: fix ibmvscsi]
      Signed-off-by: NFUJITA Tomonori <fujita.tomonori@lab.ntt.co.jp>
      Cc: Muli Ben-Yehuda <muli@il.ibm.com>
      Cc: Andi Kleen <andi@firstfloor.org>
      Cc: Thomas Gleixner <tglx@linutronix.de>
      Cc: Ingo Molnar <mingo@elte.hu>
      Cc: Avi Kivity <avi@qumranet.com>
      Signed-off-by: NAndrew Morton <akpm@linux-foundation.org>
      Signed-off-by: NLinus Torvalds <torvalds@linux-foundation.org>
      8d8bb39b
  6. 22 7月, 2008 2 次提交
  7. 10 7月, 2008 1 次提交
  8. 22 6月, 2008 1 次提交
  9. 03 6月, 2008 1 次提交
  10. 22 5月, 2008 1 次提交
  11. 19 5月, 2008 1 次提交
    • R
      [ARM] pxa: corgibl_limit_intensity build errors · 02a8e769
      Russell King 提交于
      If CONFIG_BACKLIGHT_CORGI is not selected, then corgibl_limit_intensity()
      is not present.  However, both corgi_pm.c and sharp_pm.c reference this
      symbol, resulting in a link error.
      
      Wrap the references with the relevant ifdefs, and avoid the resulting
      NULL pointer dereference by making the code in sharpsl_pm.c also
      conditional on the config symbol.
      Signed-off-by: NRussell King <rmk+kernel@arm.linux.org.uk>
      02a8e769
  12. 18 5月, 2008 1 次提交
  13. 19 4月, 2008 1 次提交
  14. 10 4月, 2008 3 次提交
  15. 28 3月, 2008 1 次提交
  16. 06 3月, 2008 1 次提交
  17. 04 2月, 2008 1 次提交
  18. 26 1月, 2008 1 次提交
  19. 08 12月, 2007 1 次提交
  20. 27 11月, 2007 1 次提交
  21. 23 10月, 2007 2 次提交
  22. 19 10月, 2007 2 次提交
  23. 16 10月, 2007 1 次提交
  24. 13 10月, 2007 1 次提交
  25. 12 7月, 2007 3 次提交
  26. 21 5月, 2007 1 次提交
  27. 17 5月, 2007 1 次提交
    • R
      [ARM] gic: Fix gic cascade irq handling · 0f347bb9
      Russell King 提交于
      No need for the cascade irq function to have a "fastcall" annotation.
      Fix the range checking for valid IRQ numbers - comparing the value
      returned by the GIC with NR_IRQS is meaningless since we translate
      the GIC irq number to a Linux IRQ number afterwards.
      
      Check the GIC returned IRQ number is within limits first, then add
      the IRQ offset, and only then compare with NR_IRQS.
      Signed-off-by: NRussell King <rmk+kernel@arm.linux.org.uk>
      0f347bb9
  28. 16 5月, 2007 1 次提交
  29. 01 5月, 2007 1 次提交