1. 10 8月, 2008 2 次提交
  2. 07 8月, 2008 3 次提交
  3. 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
  4. 22 7月, 2008 2 次提交
  5. 10 7月, 2008 1 次提交
  6. 22 6月, 2008 1 次提交
  7. 03 6月, 2008 1 次提交
  8. 22 5月, 2008 1 次提交
  9. 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
  10. 18 5月, 2008 1 次提交
  11. 19 4月, 2008 1 次提交
  12. 10 4月, 2008 3 次提交
  13. 28 3月, 2008 1 次提交
  14. 06 3月, 2008 1 次提交
  15. 04 2月, 2008 1 次提交
  16. 26 1月, 2008 1 次提交
  17. 08 12月, 2007 1 次提交
  18. 27 11月, 2007 1 次提交
  19. 23 10月, 2007 2 次提交
  20. 19 10月, 2007 2 次提交
  21. 16 10月, 2007 1 次提交
  22. 13 10月, 2007 1 次提交
  23. 12 7月, 2007 3 次提交
  24. 21 5月, 2007 1 次提交
  25. 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
  26. 16 5月, 2007 1 次提交
  27. 01 5月, 2007 2 次提交
    • J
      power management: implement pm_ops.valid for everybody · e8c9c502
      Johannes Berg 提交于
      Almost all users of pm_ops only support mem sleep, don't check in .valid and
      don't reject any others in .prepare so users can be confused if they check
      /sys/power/state, especially when new states are added (these would then
      result in s-t-r although they're supposed to be something different).
      
      This patch implements a generic pm_valid_only_mem function that is then
      exported for users and puts it to use in almost all existing pm_ops.
      Signed-off-by: NJohannes Berg <johannes@sipsolutions.net>
      Cc: David Brownell <david-b@pacbell.net>
      Acked-by: NPavel Machek <pavel@ucw.cz>
      Cc: linux-pm@lists.linux-foundation.org
      Cc: Len Brown <lenb@kernel.org>
      Acked-by: NRussell King <rmk@arm.linux.org.uk>
      Cc: Greg KH <greg@kroah.com>
      Cc: "Rafael J. Wysocki" <rjw@sisk.pl>
      Cc: Paul Mundt <lethal@linux-sh.org>
      Signed-off-by: NAndrew Morton <akpm@linux-foundation.org>
      Signed-off-by: NLinus Torvalds <torvalds@linux-foundation.org>
      e8c9c502
    • J
      rework pm_ops pm_disk_mode, kill misuse · fe0c935a
      Johannes Berg 提交于
      This patch series cleans up some misconceptions about pm_ops.  Some users of
      the pm_ops structure attempt to use it to stop the user from entering suspend
      to disk, this, however, is not possible since the user can always use
      "shutdown" in /sys/power/disk and then the pm_ops are never invoked.  Also,
      platforms that don't support suspend to disk simply should not allow
      configuring SOFTWARE_SUSPEND (read the help text on it, it only selects
      suspend to disk and nothing else, all the other stuff depends on PM).
      
      The pm_ops structure is actually intended to provide a way to enter
      platform-defined sleep states (currently supported states are "standby" and
      "mem" (suspend to ram)) and additionally (if SOFTWARE_SUSPEND is configured)
      allows a platform to support a platform specific way to enter low-power mode
      once everything has been saved to disk.  This is currently only used by ACPI
      (S4).
      
      This patch:
      
      The pm_ops.pm_disk_mode is used in totally bogus ways since nobody really
      seems to understand what it actually does.
      
      This patch clarifies the pm_disk_mode description.
      
      It also removes all the arm and sh users that think they can veto suspend to
      disk via pm_ops; not so since the user can always do echo shutdown >
      /sys/power/disk, they need to find a better way involving Kconfig or such.
      
      ACPI is the only user left with a non-zero pm_disk_mode.
      
      The patch also sets the default mode to shutdown again, but when a new pm_ops
      is registered its pm_disk_mode is selected as default, that way the default
      stays for ACPI where it is apparently required.
      Signed-off-by: NJohannes Berg <johannes@sipsolutions.net>
      Cc: David Brownell <david-b@pacbell.net>
      Acked-by: NPavel Machek <pavel@ucw.cz>
      Cc: <linux-pm@lists.linux-foundation.org>
      Cc: Len Brown <lenb@kernel.org>
      Acked-by: NRussell King <rmk@arm.linux.org.uk>
      Cc: Greg KH <greg@kroah.com>
      Cc: "Rafael J. Wysocki" <rjw@sisk.pl>
      Acked-by: NPaul Mundt <lethal@linux-sh.org>
      Signed-off-by: NAndrew Morton <akpm@linux-foundation.org>
      Signed-off-by: NLinus Torvalds <torvalds@linux-foundation.org>
      fe0c935a
  28. 22 4月, 2007 1 次提交