1. 07 7月, 2010 4 次提交
    • R
      ACPICA: Drop acpi_set_gpe · 546eb576
      Rafael J. Wysocki 提交于
      The acpi_set_gpe() function is a little awkward, because it doesn't
      really work as advertised in the "disable" case.  Namely, if a GPE
      has been enabled with acpi_enable_gpe() and triggered a notification
      to occur, and if acpi_set_gpe() is used to disable it before
      acpi_ev_asynch_enable_gpe() runs, the GPE will be immediately enabled
      by the latter as though the acpi_set_gpe() had no effect.
      
      Thus, since it's been possible to make all of its callers use
      alternative operations to disable or enable GPEs, acpi_set_gpe() can
      be dropped.
      Signed-off-by: NRafael J. Wysocki <rjw@sisk.pl>
      Signed-off-by: NLen Brown <len.brown@intel.com>
      546eb576
    • R
      ACPICA: Remove wakeup GPE reference counting which is not used · a44061aa
      Rafael J. Wysocki 提交于
      After the previous patch that introduced acpi_gpe_wakeup() and
      modified the ACPI suspend and wakeup code to use it, the third
      argument of acpi_{enable|disable}_gpe() and the GPE wakeup
      reference counter are not necessary any more.  Remove them and
      modify all of the users of acpi_{enable|disable}_gpe()
      accordingly.  Also drop GPE type constants that aren't used
      any more.
      Signed-off-by: NRafael J. Wysocki <rjw@sisk.pl>
      Signed-off-by: NLen Brown <len.brown@intel.com>
      Signed-off-by: NBob Moore <robert.moore@intel.com>
      Signed-off-by: NLin Ming <ming.m.lin@intel.com>
      Signed-off-by: NLen Brown <len.brown@intel.com>
      a44061aa
    • R
      ACPICA: Introduce acpi_gpe_wakeup() · e8b6f970
      Rafael J. Wysocki 提交于
      ACPICA uses reference counters to avoid disabling GPEs too early in
      case they have been enabled for many times.  This is done separately
      for runtime and for wakeup, but the wakeup GPE reference counter is
      not really necessary, because GPEs are only enabled to wake up the
      system at the hardware level by acpi_enter_sleep_state().  Thus it
      only is necessary to set the corresponding bits in the wakeup enable
      masks of these GPEs' registers right before the system enters a sleep
      state.  Moreover, the GPE wakeup enable bits can only be set when the
      target sleep state of the system is known and they need to be cleared
      immediately after wakeup regardless of how many wakeup devices are
      associated with a given GPE.
      
      On the basis of the above observations, introduce function
      acpi_gpe_wakeup() to be used for setting or clearing the enable bit
      corresponding to a given GPE in its enable register's enable_for_wake
      mask.  Modify the ACPI suspend and wakeup code the use
      acpi_gpe_wakeup() instead of acpi_{enable|disable}_gpe() to set
      and clear GPE enable bits in their registers' enable_for_wake masks
      during system transitions to a sleep state and back to the working
      state, respectively.  [This will allow us to drop the third
      argument of acpi_{enable|disable}_gpe() and simplify the GPE
      handling code.]
      Signed-off-by: NRafael J. Wysocki <rjw@sisk.pl>
      Signed-off-by: NLen Brown <len.brown@intel.com>
      Signed-off-by: NBob Moore <robert.moore@intel.com>
      Signed-off-by: NLin Ming <ming.m.lin@intel.com>
      Signed-off-by: NLen Brown <len.brown@intel.com>
      e8b6f970
    • B
      ACPICA: Update version to 20100528 · ccba77eb
      Bob Moore 提交于
      Version 20100528.
      Signed-off-by: NBob Moore <robert.moore@intel.com>
      Signed-off-by: NLin Ming <ming.m.lin@intel.com>
      Signed-off-by: NLen Brown <len.brown@intel.com>
      ccba77eb
  2. 12 6月, 2010 1 次提交
  3. 06 5月, 2010 2 次提交
  4. 20 4月, 2010 5 次提交
  5. 23 2月, 2010 1 次提交
    • R
      ACPI: Use GPE reference counting to support shared GPEs · 9630bdd9
      Rafael J. Wysocki 提交于
      ACPI GPEs may map to multiple devices.  The current GPE interface
      only provides a mechanism for enabling and disabling GPEs, making
      it difficult to change the state of GPEs at runtime without extensive
      cooperation between devices.
      
      Add an API to allow devices to indicate whether or not they want
      their device's GPE to be enabled for both runtime and wakeup events.
      
      Remove the old GPE type handling entirely, which gets rid of various
      quirks, like the implicit disabling with GPE type setting. This
      requires a small amount of rework in order to ensure that non-wake
      GPEs are enabled by default to preserve existing behaviour.
      
      Based on patches from Matthew Garrett <mjg@redhat.com>.
      Signed-off-by: NMatthew Garrett <mjg@redhat.com>
      Signed-off-by: NRafael J. Wysocki <rjw@sisk.pl>
      Signed-off-by: NJesse Barnes <jbarnes@virtuousgeek.org>
      9630bdd9
  6. 23 1月, 2010 2 次提交
  7. 16 12月, 2009 1 次提交
  8. 25 11月, 2009 3 次提交
  9. 09 9月, 2009 1 次提交
  10. 29 8月, 2009 1 次提交
  11. 27 8月, 2009 4 次提交
  12. 27 5月, 2009 4 次提交
  13. 07 4月, 2009 1 次提交
    • L
      hwmon: Add Asus ATK0110 support · 2c03d07a
      Luca Tettamanti 提交于
      Asus boards have an ACPI interface for interacting with the hwmon (fan,
      temperatures, voltages) subsystem; this driver exposes the relevant
      information via the standard sysfs interface.
      
      There are two different ACPI interfaces:
      - an old one (based on RVLT/RFAN/RTMP)
      - a new one (GGRP/GITM)
      Both may be present but there a few cases (my board, sigh) where the
      new interface is just an empty stub; the driver defaults to the old one
      when both are present.
      The old interface has received a considerable testing, but I'm still
      awaiting confirmation from my tester that the new one is working as
      expected (hence the debug code is still enabled).
      
      Currently all the attributes are read-only, though a (partial) control
      should be possible with a bit more work.
      Signed-off-by: NLuca Tettamanti <kronos.it@gmail.com>
      Signed-off-by: NHans de Goede <hdegoede@redhat.com>
      Signed-off-by: NJean Delvare <khali@linux-fr.org>
      2c03d07a
  14. 28 3月, 2009 1 次提交
  15. 27 3月, 2009 5 次提交
  16. 09 2月, 2009 1 次提交
    • Y
      acpi/x86: introduce __apci_map_table, v4 · 7d97277b
      Yinghai Lu 提交于
      to prevent wrongly overwriting fixmap that still want to use.
      
      ACPI used to rely on low mappings being all linearly mapped and
      grew a habit: it never really unmapped certain kinds of tables
      after use.
      
      This can cause problems - for example the hypothetical case
      when some spurious access still references it.
      
      v2: remove prev_map and prev_size in __apci_map_table
      v3: let acpi_os_unmap_memory() call early_iounmap too, so remove extral calling to
      early_acpi_os_unmap_memory
      v4: fix typo in one acpi_get_table_with_size calling
      Signed-off-by: NYinghai Lu <yhlu.kernel@gmail.com>
      Acked-by: NLen Brown <len.brown@intel.com>
      Signed-off-by: NIngo Molnar <mingo@elte.hu>
      7d97277b
  17. 09 1月, 2009 1 次提交
  18. 31 12月, 2008 2 次提交