1. 17 7月, 2012 2 次提交
  2. 14 7月, 2012 1 次提交
  3. 01 6月, 2012 5 次提交
  4. 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
  5. 30 3月, 2012 3 次提交
  6. 29 3月, 2012 1 次提交
  7. 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
  8. 22 3月, 2012 9 次提交
  9. 14 3月, 2012 1 次提交
  10. 27 1月, 2012 1 次提交
  11. 21 1月, 2012 2 次提交
    • M
      ACPI: Remove ./drivers/acpi/atomicio.[ch] · 1001a3a3
      Myron Stowe 提交于
      With the conversion of atomicio's routines in place (see commits
      6f68c91c and 700130b4), atomicio.[ch] can be removed, replacing
      the APEI specific pre-mapping capabilities with the more generalized
      versions that drivers/acpi/osl.c provides.
      Signed-off-by: NMyron Stowe <myron.stowe@redhat.com>
      Signed-off-by: NLen Brown <len.brown@intel.com>
      1001a3a3
    • M
      ACPI, APEI: Add 64-bit read/write support for APEI on i386 · e615bf5b
      Myron Stowe 提交于
      Base ACPI (CA) currently does not support atomic 64-bit reads and writes
      (acpi_read() and acpi_write() split 64-bit loads/stores into two
      32-bit transfers) yet APEI expects 64-bit transfer capability, even
      when running on 32-bit systems.
      
      This patch implements 64-bit read and write routines for APEI usage.
      
      This patch re-factors similar functionality introduced in commit
      04c25997, bringing it into the ACPI subsystem in preparation for
      removing ./drivers/acpi/atomicio.[ch].  In the implementation I have
      replicated acpi_os_read_memory() and acpi_os_write_memory(), creating
      64-bit versions for APEI to utilize, as opposed to something more
      elegant.  My thinking is that we should attempt to see if we can get
      ACPI's CA/OSL changed so that the existing acpi_read() and acpi_write()
      interfaces are natively 64-bit capable and then subsequently remove the
      replication.
      Signed-off-by: NMyron Stowe <myron.stowe@redhat.com>
      Signed-off-by: NLen Brown <len.brown@intel.com>
      e615bf5b
  12. 20 1月, 2012 1 次提交
  13. 18 1月, 2012 1 次提交
  14. 17 1月, 2012 11 次提交