1. 22 6月, 2017 1 次提交
  2. 29 4月, 2017 1 次提交
    • H
      ACPI / PMIC: xpower: Fix power_table addresses · 2bde7c32
      Hans de Goede 提交于
      The power table addresses should be contiguous, but there was a hole
      where 0x34 was missing. On most devices this is not a problem as
      addresses above 0x34 are used for the BUC# convertors which are not
      used in the DSDTs I've access to but after the BUC# convertors
      there is a field named GPI1 in the DSTDs, which does get used in some
      cases and ended up turning BUC6 on and off due to the wrong addresses,
      resulting in turning the entire device off (or causing it to reboot).
      
      Removing the hole in the addresses fixes this, fixing one of my
      Bay Trail tablets turning off while booting the mainline kernel.
      
      While at it add comments with the field names used in the DSDTs to
      make it easier to compare the register and bits used at each address
      with the datasheet.
      Signed-off-by: NHans de Goede <hdegoede@redhat.com>
      Reviewed-by: NAndy Shevchenko <andriy.shevchenko@linux.intel.com>
      Signed-off-by: NRafael J. Wysocki <rafael.j.wysocki@intel.com>
      2bde7c32
  3. 20 4月, 2017 2 次提交
  4. 16 7月, 2016 1 次提交
    • P
      ACPI / PMIC: remove modular references from non-modular code · 6d3ef8d8
      Paul Gortmaker 提交于
      The Kconfig currently controlling compilation of these files are:
      
      drivers/acpi/Kconfig:menuconfig PMIC_OPREGION
      drivers/acpi/Kconfig:   bool "PMIC (Power Management Integrated Circuit) operation region support"
      
      drivers/acpi/Kconfig:config BXT_WC_PMIC_OPREGION
      drivers/acpi/Kconfig:   bool "ACPI operation region support for BXT WhiskeyCove PMIC"
      
      drivers/acpi/Kconfig:config XPOWER_PMIC_OPREGION
      drivers/acpi/Kconfig:   bool "ACPI operation region support for XPower AXP288 PMIC"
      
      ...meaning they currently are not being built as a module by anyone.
      
      Lets remove the couple traces of modular infrastructure use, so that
      when reading the code there is no doubt it is builtin-only.
      
      We delete the MODULE_LICENSE tag etc. since all that information
      is already contained at the top of the file in the comments.
      
      One file was using module_init.  Since module_init translates to
      device_initcall in the non-modular case, the init ordering remains
      unchanged with this commit.
      
      In one case we replace the module.h with export.h since that file
      is exporting some symbols, but does not use __init.  The other two
      are using __init and so module.h gets replaced with init.h there.
      Signed-off-by: NPaul Gortmaker <paul.gortmaker@windriver.com>
      Signed-off-by: NRafael J. Wysocki <rafael.j.wysocki@intel.com>
      6d3ef8d8
  5. 27 6月, 2016 2 次提交
  6. 24 6月, 2016 2 次提交
  7. 10 3月, 2016 1 次提交
  8. 27 3月, 2015 1 次提交
  9. 29 1月, 2015 1 次提交
  10. 27 11月, 2014 3 次提交
    • A
      ACPI / PMIC: AXP288: support virtual GPIO in ACPI table · 491cb357
      Aaron Lu 提交于
      The same virtual GPIO strategy is also used for the AXP288 PMIC in that
      various control methods that are used to do power rail handling and
      sensor reading/setting will touch GPIO fields defined under the PMIC
      device. The GPIO fileds are only defined by the ACPI code while the
      actual hardware doesn't really have a GPIO controller, but to make those
      control method execution succeed, we have to install a GPIO handler for
      the PMIC device handle. Since we do not need the virtual GPIO strategy,
      we can simply do nothing in that handler.
      Signed-off-by: NAaron Lu <aaron.lu@intel.com>
      Signed-off-by: NRafael J. Wysocki <rafael.j.wysocki@intel.com>
      491cb357
    • A
      ACPI / PMIC: support PMIC operation region for XPower AXP288 · d8139f63
      Aaron Lu 提交于
      The Baytrail-T-CR platform firmware has defined two customized operation
      regions for PMIC chip Dollar Cove XPower - one is for power resource
      handling and one is for thermal just like the CrystalCove one. This patch
      adds support for them on top of the common PMIC opregion region code.
      Signed-off-by: NAaron Lu <aaron.lu@intel.com>
      Acked-by: Lee Jones <lee.jones@linaro.org> for the MFD part
      Signed-off-by: NRafael J. Wysocki <rafael.j.wysocki@intel.com>
      d8139f63
    • A
      ACPI / PMIC: support PMIC operation region for CrystalCove · b1eea857
      Aaron Lu 提交于
      The Baytrail-T platform firmware has defined two customized operation
      regions for PMIC chip Crystal Cove - one is for power resource handling
      and one is for thermal: sensor temperature reporting, trip point setting,
      etc. This patch adds support for them on top of the existing Crystal Cove
      PMIC driver.
      
      The reason to split code into a separate file intel_pmic.c is that there
      are more PMIC drivers with ACPI operation region support coming and we can
      re-use those code. The intel_pmic_opregion_data structure is created also
      for this purpose: when we need to support a new PMIC's operation region,
      we just need to fill those callbacks and the two register mapping tables.
      Signed-off-by: NAaron Lu <aaron.lu@intel.com>
      Acked-by: Lee Jones <lee.jones@linaro.org> for the MFD part
      Signed-off-by: NRafael J. Wysocki <rafael.j.wysocki@intel.com>
      b1eea857