1. 10 7月, 2008 1 次提交
  2. 22 6月, 2008 1 次提交
  3. 03 6月, 2008 1 次提交
  4. 22 5月, 2008 1 次提交
  5. 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
  6. 18 5月, 2008 1 次提交
  7. 19 4月, 2008 1 次提交
  8. 10 4月, 2008 3 次提交
  9. 28 3月, 2008 1 次提交
  10. 06 3月, 2008 1 次提交
  11. 04 2月, 2008 1 次提交
  12. 26 1月, 2008 1 次提交
  13. 08 12月, 2007 1 次提交
  14. 27 11月, 2007 1 次提交
  15. 23 10月, 2007 2 次提交
  16. 19 10月, 2007 2 次提交
  17. 16 10月, 2007 1 次提交
  18. 13 10月, 2007 1 次提交
  19. 12 7月, 2007 3 次提交
  20. 21 5月, 2007 1 次提交
  21. 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
  22. 16 5月, 2007 1 次提交
  23. 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
  24. 22 4月, 2007 1 次提交
  25. 08 3月, 2007 1 次提交
  26. 20 2月, 2007 1 次提交
  27. 15 2月, 2007 1 次提交
  28. 13 2月, 2007 1 次提交
  29. 12 2月, 2007 2 次提交
  30. 10 2月, 2007 1 次提交
  31. 08 2月, 2007 2 次提交