1. 21 9月, 2012 8 次提交
  2. 31 7月, 2012 1 次提交
    • L
      ACPI: delete _GTS/_BFS support · 3f6f49c7
      Len Brown 提交于
      _GTS and _BFS were added to the suspend/resume flow
      in the ACPI 2.0 specification.
      
      Linux dutifully implemented _GTS and _BFS.
      We discovered that it was rarely seen in systems
      in the field.  Further, some of those systems had
      AML so bogus that it could never work -- proof that
      no other operating system supports _GTS and _BFS.
      So we made _GTS and _BFS optional via modparam,
      and disabled them by default.
      
      But we've had to complicate some code to keep
      this support in the kernel, as these methods are defined
      to be evaluated very close to sleep entry and exit.
      Indeed, no other AML is ever evaluated with interrupts off.
      
      We have submitted a proposal for _GTS and _BFS
      to be officially removed from the ACPI specification
      on the next revision.  Here we remove it from Linux.
      Signed-off-by: NLen Brown <len.brown@intel.com>
      Acked-by: NIngo Molnar <mingo@kernel.org>
      Acked-by: NKonrad Rzeszutek Wilk <konrad.wilk@oracle.com>
      3f6f49c7
  3. 18 7月, 2012 3 次提交
  4. 17 7月, 2012 6 次提交
  5. 14 7月, 2012 1 次提交
  6. 01 7月, 2012 3 次提交
  7. 24 6月, 2012 1 次提交
  8. 23 6月, 2012 1 次提交
  9. 04 6月, 2012 3 次提交
    • T
      ACPI: Add _OST support for sysfs eject · c4753e57
      Toshi Kani 提交于
      Changed acpi_bus_hot_remove_device() to support _OST. This function is
      also changed to global so that it can be called from hotplug notify
      handlers to perform hot-remove operation.
      
      Changed acpi_eject_store(), which is the sysfs eject handler. It checks
      eject_pending to see if the request was originated from ACPI eject
      notification. If not, it calls _OST(0x103,84,) per Figure 6-37 in ACPI
      5.0 spec.
      
      Added eject_pending bit to acpi_device_flags. This bit is set when the
      kernel has received an ACPI eject notification, but does not initiate
      its hot-remove operation by itself.
      
      Added struct acpi_eject_event. This structure is used to pass extended
      information to acpi_bus_hot_remove_device(), which has a single argument
      to support asynchronous call
      Signed-off-by: NToshi Kani <toshi.kani@hp.com>
      Signed-off-by: NLen Brown <len.brown@intel.com>
      c4753e57
    • T
      ACPI: Add an interface to evaluate _OST · 275c58d7
      Toshi Kani 提交于
      Added acpi_evaluate_hotplug_opt(). All ACPI hotplug handlers must call
      this function when evaluating _OST for hotplug operations. If the
      platform does not support _OST, this function returns AE_NOT_FOUND and
      has no effect on the platform.
      
      ACPI_HOTPLUG_OST is defined when all relevant ACPI hotplug operations,
      such as CPU, memory and container hotplug, are enabled. This assures
      consistent behavior among the hotplug operations with regarding the
      _OST support. When ACPI_HOTPLUG_OST is not defined, this function is
      a no-op.
      
      ACPI PCI hotplug is not enhanced to support _OST at this time since it
      is a legacy method being replaced by PCIe native hotplug. _OST support
      for ACPI PCI hotplug may be added in future if necessary.
      
      Some platforms may require the OS to support _OST in order to support
      ACPI hotplug operations. For example, if a platform has the management
      console where user can request a hotplug operation from, this _OST
      support would be required for the management console to show the result
      of the hotplug request to user.
      
      Added macro definitions of _OST source events and status codes.
      Also renamed OSC_SB_CPUHP_OST_SUPPORT to OSC_SB_HOTPLUG_OST_SUPPORT
      since this _OSC bit is not specific to CPU hotplug. This bit is
      defined in Table 6-147 of ACPI 5.0 as follows.
      
        Bits:       3
        Field Name: Insertion / Ejection _OST Processing Support
        Definition: This bit is set if OSPM will evaluate the _OST
                    object defined under a device when processing
                    insertion and ejection source event codes.
      Signed-off-by: NToshi Kani <toshi.kani@hp.com>
      Signed-off-by: NLen Brown <len.brown@intel.com>
      275c58d7
    • L
      ACPI: fix acpi_bus.h build warnings when ACPI is not enabled · 7ae30986
      Len Brown 提交于
      introduced in Linux-3.5-rc1 by
      66886d6f
      (ACPI: Add stubs for (un)register_acpi_bus_type)
      
      Fix header file warnings when CONFIG_ACPI is not enabled:
      
      include/acpi/acpi_bus.h:443:42: warning: 'struct acpi_bus_type' declared inside parameter list
      include/acpi/acpi_bus.h:443:42: warning: its scope is only this definition or declaration, which is probably not
      include/acpi/acpi_bus.h:444:44: warning: 'struct acpi_bus_type' declared inside parameter list
      Signed-off-by: NLen Brown <len.brown@intel.com>
      7ae30986
  10. 01 6月, 2012 5 次提交
  11. 12 5月, 2012 2 次提交
  12. 05 5月, 2012 1 次提交
    • L
      ACPI: Fix D3hot v D3cold confusion · 1cc0c998
      Lin Ming 提交于
      Before this patch, ACPI_STATE_D3 incorrectly referenced D3hot
      in some places, but D3cold in other places.
      
      After this patch, ACPI_STATE_D3 always means ACPI_STATE_D3_COLD;
      and all references to D3hot use ACPI_STATE_D3_HOT.
      
      ACPI's _PR3 method is used to enter both D3hot and D3cold states.
      What distinguishes D3hot from D3cold is the presence _PR3
      (Power Resources for D3hot)  If these resources are all ON,
      then the state is D3hot.  If _PR3 is not present,
      or all _PR0 resources for the devices are OFF,
      then the state is D3cold.
      
      This patch applies after Linux-3.4-rc1.
      A future syntax cleanup may remove ACPI_STATE_D3
      to emphasize that it always means ACPI_STATE_D3_COLD.
      Signed-off-by: NLin Ming <ming.m.lin@intel.com>
      Acked-by: NRafael J. Wysocki <rjw@sisk.pl>
      Reviewed-by: NAaron Lu <aaron.lu@amd.com>
      Signed-off-by: NLen Brown <len.brown@intel.com>
      1cc0c998
  13. 30 3月, 2012 3 次提交
  14. 29 3月, 2012 1 次提交
  15. 27 3月, 2012 1 次提交
    • L
      ACPICA: Sleep/Wake interfaces: optionally execute _GTS and _BFS · 8a73b17e
      Lin Ming 提交于
      Enhanced the sleep/wake interfaces to optionally execute the
      _GTS method (Going To Sleep), and the _BFS method (Back From
      Sleep).  Windows apparently does not execute these methods, and
      therefore these methods are often untested. It has been seen on
      some systems where the execution of these methods causes errors
      and also prevents the machine from entering S5. It is therefore
      suggested that host operating systems do not execute these methods
      by default. In the future, perhaps these methods can be optionally
      executed based on the age of the system and/or what is the newest
      version of Windows that the BIOS asks for via _OSI.
      Signed-off-by: NLin Ming <ming.m.lin@intel.com>
      Signed-off-by: NBob Moore <robert.moore@intel.com>
      Signed-off-by: NLen Brown <len.brown@intel.com>
      8a73b17e