1. 17 7月, 2012 1 次提交
  2. 14 7月, 2012 1 次提交
  3. 01 6月, 2012 2 次提交
  4. 30 3月, 2012 1 次提交
  5. 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
  6. 22 3月, 2012 3 次提交
  7. 17 1月, 2012 7 次提交
  8. 13 1月, 2012 1 次提交
  9. 14 7月, 2011 3 次提交
  10. 10 5月, 2011 1 次提交
  11. 23 3月, 2011 1 次提交
  12. 03 3月, 2011 1 次提交
  13. 19 1月, 2011 2 次提交
  14. 12 1月, 2011 5 次提交
  15. 18 10月, 2010 1 次提交
  16. 01 10月, 2010 4 次提交
  17. 29 9月, 2010 1 次提交
  18. 25 9月, 2010 1 次提交
    • R
      ACPI / ACPICA: Defer enabling of runtime GPEs (v3) · a2100801
      Rafael J. Wysocki 提交于
      The current ACPI GPEs initialization code has a problem that it
      enables some GPEs pointed to by device _PRW methods, generally
      intended for signaling wakeup events (system or device wakeup).
      These GPEs are then almost immediately disabled by the ACPI namespace
      scanning code with the help of acpi_gpe_can_wake(), but it would be
      better not to enable them at all until really necessary.
      
      Modify the initialization of GPEs so that the ones that have
      associated _Lxx or _Exx methods and are not pointed to by any _PRW
      methods will be enabled after the namespace scan is complete.
      Signed-off-by: NRafael J. Wysocki <rjw@sisk.pl>
      Signed-off-by: NLen Brown <len.brown@intel.com>
      a2100801
  19. 15 8月, 2010 1 次提交
  20. 13 7月, 2010 1 次提交
    • R
      ACPI / ACPICA: Do not execute _PRW methods during initialization · 9874647b
      Rafael J. Wysocki 提交于
      Currently, during initialization ACPICA walks the entire ACPI
      namespace in search of any device objects with assciated _PRW
      methods.  All of the _PRW methods found are executed in the process
      to extract the GPE information returned by them, so that the GPEs in
      question can be marked as "able to wakeup" (more precisely, the
      ACPI_GPE_CAN_WAKE flag is set for them).  The only purpose of this
      exercise is to avoid enabling the CAN_WAKE GPEs automatically, even
      if there are _Lxx/_Exx methods associated with them.  However, it is
      both costly and unnecessary, because the host OS has to execute the
      _PRW methods anyway to check which devices can wake up the system
      from sleep states.  Moreover, it then uses full information
      returned by _PRW, including the GPE information, so it can take care
      of disabling the GPEs if necessary.
      
      Remove the code that walks the namespace and executes _PRW from
      ACPICA and modify comments to reflect that change.  Make
      acpi_bus_set_run_wake_flags() disable GPEs for wakeup devices
      so that they don't cause spurious wakeup events to be signaled.
      This not only reduces the complexity of the ACPICA initialization
      code, but in some cases it should reduce the kernel boot time as
      well.
      
      Unfortunately, for this purpose we need a new ACPICA function,
      acpi_gpe_can_wake(), to be called by the host OS in order to disable
      the GPEs that can wake up the system and were previously enabled by
      acpi_ev_initialize_gpe_block() or acpi_ev_update_gpes() (such a GPE
      should be disabled only once, because the initialization code enables
      it only once, but it may be pointed to by _PRW for multiple devices
      and that's why the additional function is necessary).
      Signed-off-by: NRafael J. Wysocki <rjw@sisk.pl>
      Signed-off-by: NLen Brown <len.brown@intel.com>
      9874647b
  21. 07 7月, 2010 1 次提交