1. 23 10月, 2008 2 次提交
    • S
      dock: make dock driver not a module · 898b054f
      Shaohua Li 提交于
      To avoid dock driver is loaded after other drivers like libata, let's
      make dock driver not a module.
      Signed-off-by: NShaohua Li <shaohua.li@intel.com>
      Signed-off-by: NLen Brown <len.brown@intel.com>
      898b054f
    • R
      ACPI suspend: Fix CONFIG_ACPI_SLEEP dependence and some compilation warnings · 5d1e072b
      Rafael J. Wysocki 提交于
      Initially CONFIG_PM_SLEEP was defined as
      CONFIG_SUSPEND || CONFIG_HIBERNATION and some ACPI code, most
      importantly the code in drivers/acpi/main.c, was written with this
      assumption.  Currently, however, CONFIG_PM_SLEEP is also set when
      CONFIG_XEN_SAVE_RESTORE is set.
      
      This causes some compilation warnings to appear in
      drivers/acpi/main.c if both CONFIG_SUSPEND and CONFIG_HIBERNATION
      are unset and CONFIG_PM_SLEEP is set (this was impossible before).
      To fix this problem, redefine CONFIG_ACPI_SLEEP do depend directly
      on CONFIG_SUSPEND || CONFIG_HIBERNATION, as originally intended, and
      use it instead of CONFIG_PM_SLEEP in drivers/acpi/main.c, wherever
      appropriate.
      
      Additionally, move the acpi_target_sleep_state definition from under
      the #ifdef to prevent compilation from failing in some cases.
      Signed-off-by: NRafael J. Wysocki <rjw@sisk.pl>
      Signed-off-by: NLen Brown <len.brown@intel.com>
      5d1e072b
  2. 13 10月, 2008 1 次提交
  3. 11 10月, 2008 1 次提交
    • R
      toshiba_acpi: depends on INPUT · b3cef8f6
      Randy Dunlap 提交于
      CONFIG_ACPI_TOSHIBA can =y when CONFIG_INPUT=m, so prevent that
      combination and its subsequent build errors:
      
      toshiba_acpi.c:(.text+0x3e877): undefined reference to `input_event'
      toshiba_acpi.c:(.text+0x3e98a): undefined reference to `input_unregister_polled_device'
      toshiba_acpi.c:(.text+0x3e994): undefined reference to `input_free_polled_device'
      toshiba_acpi.c:(.init.text+0x21b4): undefined reference to `input_allocate_polled_device'
      toshiba_acpi.c:(.init.text+0x2263): undefined reference to `input_register_polled_device'
      make[1]: *** [.tmp_vmlinux1] Error 1
      Signed-off-by: NRandy Dunlap <randy.dunlap@oracle.com>
      Signed-off-by: NLen Brown <len.brown@intel.com>
      b3cef8f6
  4. 24 9月, 2008 1 次提交
  5. 06 9月, 2008 1 次提交
  6. 11 7月, 2008 1 次提交
  7. 11 6月, 2008 1 次提交
  8. 10 6月, 2008 1 次提交
  9. 29 4月, 2008 1 次提交
  10. 16 3月, 2008 1 次提交
    • L
      ACPI: Remove ACPI_CUSTOM_DSDT_INITRD option · 9a9e0d68
      Linus Torvalds 提交于
      This essentially reverts commit 71fc47a9
      ("ACPI: basic initramfs DSDT override support"), because the code simply
      isn't ready.
      
      It did ugly things to the init sequence to populate the rootfs image
      early, but that just ended up showing other problems with the whole
      approach.  The fact is, the VFS layer simply isn't initialized this
      early, and the relevant ACPI code should either run much later, or this
      shouldn't be done at all.
      
      For 2.6.25, we'll just pick the latter option.  We can revisit this
      concept later if necessary.
      
      Cc: Dave Hansen <haveblue@us.ibm.com>
      Cc: Tilman Schmidt <tilman@imap.cc>
      Cc: Andrew Morton <akpm@linux-foundation.org>
      Cc: Thomas Renninger <trenn@suse.de>
      Cc: Eric Piel <eric.piel@tremplin-utc.net>
      Cc: Len Brown <len.brown@intel.com>
      Cc: Christoph Hellwig <hch@infradead.org>
      Cc: Markus Gaugusch <dsdt@gaugusch.at>
      Signed-off-by: NLinus Torvalds <torvalds@linux-foundation.org>
      9a9e0d68
  11. 23 2月, 2008 1 次提交
  12. 08 2月, 2008 2 次提交
  13. 07 2月, 2008 3 次提交
  14. 06 2月, 2008 1 次提交
    • C
      ACPI: WMI: Add ACPI-WMI mapping driver · bff431e4
      Carlos Corbacho 提交于
      The following is an implementation of the Windows Management
      Instrumentation (WMI) ACPI interface mapper (PNP0C14).
      
      What it does:
      
      Parses the _WDG method and exports functions to process WMI method calls,
      data block query/ set commands (both based on GUID) and does basic event
      handling.
      
      How: WMI presents an in kernel interface here (essentially, a minimal
      wrapper around ACPI)
      
      (const char *guid assume the 36 character ASCII representation of
      a GUID - e.g. 67C3371D-95A3-4C37-BB61-DD47B491DAAB)
      
      wmi_evaluate_method(const char *guid, u8 instance, u32 method_id,
      const struct acpi_buffer *in, struct acpi_buffer *out)
      
      wmi_query_block(const char *guid, u8 instance,
      struct acpi_buffer *out)
      
      wmi_set_block(const char *guid, u38 instance,
      const struct acpi_buffer *in)
      
      wmi_install_notify_handler(acpi_notify_handler handler);
      
      wmi_remove_notify_handler(void);
      
      wmi_get_event_data(u32 event, struct acpi_buffer *out)
      
      wmi_has_guid(const char guid*)
      
      wmi_has_guid() is a helper function to find if a GUID exists or not on the
      system (a quick and easy way for WMI dependant drivers to see if the
      the method/ block they want exists, since GUIDs are supposed to be unique).
      
      Event handling - allow a WMI based driver to register a notifier handler
      for each GUID with WMI. When a notification is sent to a GUID in WMI, the
      handler registered with WMI is then called (it is left to the caller to
      ask for the WMI event data associated with the GUID, if needed).
      
      What it won't do:
      
      Unicode - The MS article[1] calls for converting between ASCII and Unicode (or
      vice versa) if a GUID is marked as "string". This is left up to the calling
      driver.
      
      Handle a MOF[1] - the WMI mapper just exports methods, data and events to
      userspace. MOF handling is down to userspace.
      
      Userspace interface - this will be added later.
      
      [1] http://www.microsoft.com/whdc/system/pnppwr/wmi/wmi-acpi.mspx
      
      ===
      ChangeLog
      ==
      
      v1 (2007-10-02):
      
      * Initial release
      
      v2 (2007-10-05):
      
      * Cleaned up code - split up super "wmi_evaluate_block" -> each external
        symbol now handles its own ACPI calls, rather than handing off to
        a "super" method (and in turn, is a lot simpler to read)
      * Added a find_guid() symbol - return true if a given GUID exists on
        the system
      * wmi_* functions now return type acpi_status (since they are just
        fancy wrappers around acpi_evaluate_object())
      * Removed extra debug code
      
      v3 (2007-10-27)
      
      * More code clean up - now passes checkpatch.pl
      * Change data block calls - ref MS spec, method ID is not required for
        them, so drop it from the function parameters.
      * Const'ify guid in the function call parameters.
      * Fix _WDG buffer handling - copy the data to our own private structure.
      * Change WMI from tristate to bool - otherwise the external functions are
        not exported in linux/acpi.h if you try to build WMI as a module.
      * Fix more flag comparisons.
      * Add a maintainers entry - since I wrote this, I should take the blame
        for it.
      
      v4 (2007-10-30)
      
      * Add missing brace from after fixing checkpatch errors.
      * Rewrote event handling - allow external drivers to register with WMI to
        handle WMI events
      * Clean up flags and sanitise flag handling
      
      v5 (2007-11-03)
      
      * Add sysfs interface for userspace. Export events over netlink again.
      * Remove module left overs, fully convert to built-in driver.
      * Tweak in-kernel API to use u8 for instance, since this is what the GUID
        blocks use (so instance cannot be greater than u8).
      * Export wmi_get_event_data() for in kernel WMI drivers.
      
      v6 (2007-11-07)
      
      * Split out userspace into a different patch
      
      v7 (2007-11-20)
      
      * Fix driver to handle multiple PNP0C14 devices - store all GUIDs using
        the kernel's built in list functions, and just keep adding to the list
        every time we handle a PNP0C14 devices - GUIDs will always be unique,
        and WMI callers do not know or care about different devices.
      * Change WMI event handler registration to use its' own event handling
        struct; we should not pass an acpi_handle down to any WMI based drivers
        - they should be able to function with only the calls provided in WMI.
      * Update my e-mail address
      
      v8 (2007-11-28)
      
      * Convert back to a module.
      * Update Kconfig to default to building as a module.
      * Remove an erroneous printk.
      * Simply comments for string flag (since we now leave the handling to the
        caller).
      
      v9 (2007-12-07)
      
      * Add back missing MODULE_DEVICE_TABLE for autoloading
      * Checkpatch fixes
      
      v10 (2007-12-12)
      
      * Workaround broken GUIDs declared expensive without a WCxx method.
      * Minor cleanups
      
      v11 (2007-12-17)
      
      * More fixing for broken GUIDs declared expensive without a WCxx method.
      * Add basic EmbeddedControl region handling.
      
      v12 (2007-12-18)
      
      * Changed EC region handling code, as per Alexey's comments.
      
      v13 (2007-12-27)
      
      * Changed event handling so that we can have one event handler registered
        per GUID, as per Matthew Garrett's suggestion.
      
      v14 (2008-01-12)
      
      * Remove ACPI debug statements
      
      v15 (2008-02-01)
      
      * Replace two remaining 'x == NULL' type tests with '!x'
      
      v16 (2008-02-05)
      
      * Change MAINTAINERS entry, as I am not, and never have been, paid to work
        on WMI
      * Remove 'default' line from Kconfig
      Signed-off-by: NCarlos Corbacho <carlos@strangeworlds.co.uk>
      CC: Matthew Garrett <mjg59@srcf.ucam.org>
      CC: Alexey Starikovskiy <aystarik@gmail.com>
      Signed-off-by: NLen Brown <len.brown@intel.com>
      bff431e4
  15. 02 2月, 2008 1 次提交
    • Z
      ACPI: register ACPI thermal zone as generic thermal zone devices · 3f655ef8
      Zhang Rui 提交于
      Register ACPI thermal zone as thermal zone device.
      
      the new sys I/F for ACPI thermal zone will be like this:
      
      /sys/class/thermal:
      |thermal_zone1:
      	|-----type:			"ACPI thermal zone". RO
      	|-----temp:			the current temperature. RO
      	|-----mode:			the current working mode. RW.
      					the default value is "kernel"  which means  thermal
      					management is done by ACPI thermal driver.
      					"echo user > mode" prevents all the ACPI thermal driver
      					actions upon any trip points.
      	|-----trip_point_0_temp:	the threshold of trip point 0. RO.
      	|-----trip_point_0_type:	"critical". RO.
      					the type of trip point 0
      					This may be one of critical/hot/passive/active[x]
      					for an ACPI thermal zone.
      	...
      	|-----trip_point_3_temp:
      	|-----trip_point_3_type:	"active[1]"
      Signed-off-by: NZhang Rui <rui.zhang@intel.com>
      Signed-off-by: NThomas Sujith <sujith.thomas@intel.com>
      Signed-off-by: NLen Brown <len.brown@intel.com>
      3f655ef8
  16. 02 1月, 2008 1 次提交
  17. 20 11月, 2007 3 次提交
  18. 15 11月, 2007 1 次提交
  19. 11 11月, 2007 1 次提交
  20. 30 10月, 2007 2 次提交
  21. 20 10月, 2007 1 次提交
  22. 28 9月, 2007 3 次提交
  23. 19 9月, 2007 1 次提交
  24. 28 8月, 2007 1 次提交
    • H
      reverse CONFIG_ACPI_PROC_EVENT default · 721ebe00
      Hugh Dickins 提交于
      Sigh.  Again an ACPI assault on the Thinkpad's Fn+F4 to suspend to RAM.
      The default and text for CONFIG_THINKPAD_ACPI_INPUT_ENABLED were fixed
      in -rc3, but now commit 14e04fb3 ("ACPI:
      Schedule /proc/acpi/event for removal") introduces the ACPI_PROC_EVENT
      config entry, and defaults it to 'n' to disable it again.
      
      Change default to y, and add comment to make it clearer that n is for
      future distros.
      Signed-off-by: NHugh Dickins <hugh@veritas.com>
      Cc: Andrew Morton <akpm@linux-foundation.org>
      Cc: Len Brown <len.brown@intel.com>
      Signed-off-by: NLinus Torvalds <torvalds@linux-foundation.org>
      721ebe00
  25. 24 8月, 2007 1 次提交
    • L
      ACPI: Schedule /proc/acpi/event for removal · 14e04fb3
      Len Brown 提交于
      Schedule /proc/acpi/event for removal in 6 months.
      
      Re-name acpi_bus_generate_event() to acpi_bus_generate_proc_event()
      to make sure there is no confusion that it is for /proc/acpi/event only.
      
      Add CONFIG_ACPI_PROC_EVENT to allow removal of /proc/acpi/event.
      There is no functional change if CONFIG_ACPI_PROC_EVENT=y
      Signed-off-by: NLen Brown <len.brown@intel.com>
      14e04fb3
  26. 01 8月, 2007 1 次提交
  27. 30 7月, 2007 2 次提交
    • L
      ACPI: restore CONFIG_ACPI_SLEEP · 673d5b43
      Len Brown 提交于
      Restore the 2.6.22 CONFIG_ACPI_SLEEP build option, but now shadowing the
      new CONFIG_PM_SLEEP option.
      Signed-off-by: NLen Brown <len.brown@intel.com>
      [ Modified to work with the PM config setup changes. ]
      Signed-off-by: NLinus Torvalds <torvalds@linux-foundation.org>
      673d5b43
    • R
      Introduce CONFIG_SUSPEND for suspend-to-Ram and standby · 296699de
      Rafael J. Wysocki 提交于
      Introduce CONFIG_SUSPEND representing the ability to enter system sleep
      states, such as the ACPI S3 state, and allow the user to choose SUSPEND
      and HIBERNATION independently of each other.
      
      Make HOTPLUG_CPU be selected automatically if SUSPEND or HIBERNATION has
      been chosen and the kernel is intended for SMP systems.
      
      Also, introduce CONFIG_PM_SLEEP which is automatically selected if
      CONFIG_SUSPEND or CONFIG_HIBERNATION is set and use it to select the
      code needed for both suspend and hibernation.
      
      The top-level power management headers and the ACPI code related to
      suspend and hibernation are modified to use the new definitions (the
      changes in drivers/acpi/sleep/main.c are, mostly, moving code to reduce
      the number of ifdefs).
      
      There are many other files in which CONFIG_PM can be replaced with
      CONFIG_PM_SLEEP or even with CONFIG_SUSPEND, but they can be updated in
      the future.
      Signed-off-by: NRafael J. Wysocki <rjw@sisk.pl>
      Signed-off-by: NLinus Torvalds <torvalds@linux-foundation.org>
      296699de
  28. 27 7月, 2007 1 次提交
  29. 25 7月, 2007 1 次提交
  30. 24 7月, 2007 1 次提交
    • L
      ACPI: Kconfig: always enable CONFIG_ACPI_SLEEP on X86 · 7c5aa664
      Len Brown 提交于
      The SMP dependency on HOTPLUG_CPU and SUSPEND_SMP
      caused more harm than good -- making ACPI sleep
      support vanish for configs missing those options.
      So simply select them on the (ACPI && SMP && X86) systems
      that need them.
      
      Also, remove the prompt for ACPI_SLEEP,
      virtually nobody (intentionally) enables ACPI without it.
      Signed-off-by: NLen Brown <len.brown@intel.com>
      7c5aa664