1. 13 Feb, 2020 1 commit
  2. 27 Dec, 2019 1 commit
  3. 29 Nov, 2019 1 commit
  4. 07 Nov, 2019 1 commit
  5. 25 Oct, 2019 2 commits
    • Hans de Goede's avatar
      ACPI / PMIC: Add Cherry Trail Crystal Cove PMIC OpRegion driver · cefe6aac
      Hans de Goede authored
      We have no docs for the CHT Crystal Cove PMIC. The Asus Zenfone-2 kernel
      code has 2 Crystal Cove regulator drivers, one calls the PMIC a "Crystal
      Cove Plus" PMIC and talks about Cherry Trail, so presuambly that one
      could be used to get register info for the regulators if we need to
      implement regulator support in the future.
      
      For now the sole purpose of this driver is to make
      intel_soc_pmic_exec_mipi_pmic_seq_element work on devices with a
      CHT Crystal Cove PMIC.
      
      Specifically this fixes the following MIPI PMIC sequence related errors
      on e.g. an Asus T100HA:
      
      [  178.211801] intel_soc_pmic_exec_mipi_pmic_seq_element: No PMIC registered
      [  178.211897] [drm:intel_dsi_dcs_init_backlight_funcs [i915]] *ERROR* mipi_exec_pmic failed, error: -6
      Signed-off-by: default avatarHans de Goede <hdegoede@redhat.com>
      Reviewed-by: default avatarAndy Shevchenko <andriy.shevchenko@linux.intel.com>
      Signed-off-by: default avatarRafael J. Wysocki <rafael.j.wysocki@intel.com>
      cefe6aac
    • Hans de Goede's avatar
      ACPI / PMIC: Add byt prefix to Crystal Cove PMIC OpRegion driver · ed852cde
      Hans de Goede authored
      Our current Crystal Cove OpRegion driver is only valid for the
      Crystal Cove PMIC variant found on Bay Trail (BYT) boards,
      Cherry Trail (CHT) based boards use another variant.
      
      At least the regulator registers are different on CHT and these registers
      are one of the things controlled by the custom PMIC OpRegion.
      
      Commit 4d9ed62a ("mfd: intel_soc_pmic: Export separate mfd-cell
      configs for BYT and CHT") has disabled the intel_pmic_crc.c code for CHT
      devices by removing the "crystal_cove_pmic" MFD cell on CHT devices.
      
      This commit renames the intel_pmic_crc.c driver and the cell to be
      prefixed with "byt" to indicate that this code is for BYT devices only.
      
      This is a preparation patch for adding a separate PMIC OpRegion
      driver for the CHT variant of the Crystal Cove PMIC (sometimes called
      Crystal Cove Plus in Android kernel sources).
      Signed-off-by: default avatarHans de Goede <hdegoede@redhat.com>
      Reviewed-by: default avatarAndy Shevchenko <andriy.shevchenko@linux.intel.com>
      Signed-off-by: default avatarRafael J. Wysocki <rafael.j.wysocki@intel.com>
      ed852cde
  6. 16 Aug, 2019 2 commits
  7. 22 Jun, 2019 1 commit
  8. 08 Jun, 2019 1 commit
  9. 04 Apr, 2019 1 commit
  10. 14 Jan, 2019 1 commit
  11. 02 Jan, 2019 1 commit
    • Sinan Kaya's avatar
      ACPI: Fix build failure when CONFIG_NLS is set to 'n' · 2e61069b
      Sinan Kaya authored
      Observing link failure as follows when CONFIG_ACPI is set but
      both CONFIG_NLS and CONFIG_PCI are no set:
      
      drivers/acpi/device_sysfs.o: In function `description_show':
      device_sysfs.c:(.text+0x48a): undefined reference to `utf16s_to_utf8s'
      
      This issue was previously addressed implicitly by commit 8a226e00
      (PCI: pci-label: Fix build failure when CONFIG_NLS is set to 'm' by
      allmodconfig) causing PCI_LABEL to be selected when ACPI was set
      which caused NLS to be selected too in that case.
      
      However, after commit 5d32a665 (PCI/ACPI: Allow ACPI to be built
      without CONFIG_PCI set) it is possible to build ACPI support without
      PCI, so make ACPI select NLS directly to cover that case.
      
      Fixes: 5d32a665 (PCI/ACPI: Allow ACPI to be built without CONFIG_PCI set)
      Signed-off-by: default avatarSinan Kaya <okaya@kernel.org>
      [ rjw: Changelog ]
      Signed-off-by: default avatarRafael J. Wysocki <rafael.j.wysocki@intel.com>
      2e61069b
  12. 20 Dec, 2018 2 commits
  13. 13 Dec, 2018 1 commit
  14. 08 Nov, 2018 1 commit
    • Arnd Bergmann's avatar
      ACPI / PMIC: xpower: fix IOSF_MBI dependency · 017ce359
      Arnd Bergmann authored
      We still get a link failure with IOSF_MBI=m when the xpower driver
      is built-in:
      
      drivers/acpi/pmic/intel_pmic_xpower.o: In function `intel_xpower_pmic_update_power':
      intel_pmic_xpower.c:(.text+0x4f2): undefined reference to `iosf_mbi_block_punit_i2c_access'
      intel_pmic_xpower.c:(.text+0x5e2): undefined reference to `iosf_mbi_unblock_punit_i2c_access'
      
      This makes the dependency stronger, so we can only build when IOSF_MBI
      is built-in.
      
      Fixes: 6a9b593d (ACPI / PMIC: xpower: Add depends on IOSF_MBI to Kconfig entry)
      Signed-off-by: default avatarArnd Bergmann <arnd@arndb.de>
      Signed-off-by: default avatarRafael J. Wysocki <rafael.j.wysocki@intel.com>
      017ce359
  15. 25 Oct, 2018 1 commit
  16. 16 Oct, 2018 1 commit
  17. 12 Oct, 2018 1 commit
    • Bartlomiej Zolnierkiewicz's avatar
      ACPI: remove redundant 'default n' from Kconfig · 56f57c07
      Bartlomiej Zolnierkiewicz authored
      'default n' is the default value for any bool or tristate Kconfig
      setting so there is no need to write it explicitly.
      
      Also since commit f467c564 ("kconfig: only write '# CONFIG_FOO
      is not set' for visible symbols") the Kconfig behavior is the same
      regardless of 'default n' being present or not:
      
          ...
          One side effect of (and the main motivation for) this change is making
          the following two definitions behave exactly the same:
      
              config FOO
                      bool
      
              config FOO
                      bool
                      default n
      
          With this change, neither of these will generate a
          '# CONFIG_FOO is not set' line (assuming FOO isn't selected/implied).
          That might make it clearer to people that a bare 'default n' is
          redundant.
          ...
      Signed-off-by: default avatarBartlomiej Zolnierkiewicz <b.zolnierkie@samsung.com>
      Signed-off-by: default avatarRafael J. Wysocki <rafael.j.wysocki@intel.com>
      56f57c07
  18. 23 Aug, 2018 1 commit
  19. 24 Jul, 2018 1 commit
    • Arnd Bergmann's avatar
      arm64: fix ACPI dependencies · 2c870e61
      Arnd Bergmann authored
      Kconfig reports a warning on x86 builds after the ARM64 dependency
      was added.
      
      drivers/acpi/Kconfig:6:error: recursive dependency detected!
      drivers/acpi/Kconfig:6:       symbol ACPI depends on EFI
      
      This rephrases the dependency to keep the ARM64 details out of the
      shared Kconfig file, so Kconfig no longer gets confused by it.
      
      For consistency, all three architectures that support ACPI now
      select ARCH_SUPPORTS_ACPI in exactly the configuration in which
      they allow it. We still need the 'default x86', as each one
      wants a different default: default-y on x86, default-n on arm64,
      and always-y on ia64.
      
      Fixes: 5bcd4408 ("drivers: acpi: add dependency of EFI for arm64")
      Reviewed-by: default avatarRafael J. Wysocki <rafael.j.wysocki@intel.com>
      Acked-by: default avatarWill Deacon <will.deacon@arm.com>
      Signed-off-by: default avatarArnd Bergmann <arnd@arndb.de>
      Signed-off-by: default avatarWill Deacon <will.deacon@arm.com>
      2c870e61
  20. 23 Jul, 2018 1 commit
  21. 17 May, 2018 1 commit
  22. 20 Mar, 2018 1 commit
    • Rafael J. Wysocki's avatar
      ACPI: Add Time and Alarm Device (TAD) driver · 95c513ec
      Rafael J. Wysocki authored
      Introduce a driver for the ACPI Time and Alarm Device (TAD) based on
      Section 9.18 of ACPI 6.2.
      
      This driver only supports the system wakeup capabilities of the TAD
      which are mandatory.  Support for the RTC capabilities of the TAD
      will be added to it in the future.
      
      This driver is entirely sysfs-based.  It provides attributes (under
      the TAD platform device) to allow user space to manage the AC and DC
      wakeup timers of the TAD: set and read their values, set and check
      their expire timer wake policies, check and clear their status and
      check the capabilities of the TAD reported by AML.  The DC timer
      attributes are only present if the TAD supports a separate DC alarm
      timer.
      
      The wakeup events handling and power management of the TAD is
      expected to be taken care of by the ACPI PM domain attached to its
      platform device.
      Signed-off-by: default avatarRafael J. Wysocki <rafael.j.wysocki@intel.com>
      Reviewed-by: default avatarMika Westerberg <mika.westerberg@linux.intel.com>
      Tested-by: default avatarMika Westerberg <mika.westerberg@linux.intel.com>
      95c513ec
  23. 18 Mar, 2018 1 commit
  24. 07 Feb, 2018 1 commit
  25. 14 Jan, 2018 1 commit
  26. 02 Nov, 2017 1 commit
    • Greg Kroah-Hartman's avatar
      License cleanup: add SPDX GPL-2.0 license identifier to files with no license · b2441318
      Greg Kroah-Hartman authored
      Many source files in the tree are missing licensing information, which
      makes it harder for compliance tools to determine the correct license.
      
      By default all files without license information are under the default
      license of the kernel, which is GPL version 2.
      
      Update the files which contain no license information with the 'GPL-2.0'
      SPDX license identifier.  The SPDX identifier is a legally binding
      shorthand, which can be used instead of the full boiler plate text.
      
      This patch is based on work done by Thomas Gleixner and Kate Stewart and
      Philippe Ombredanne.
      
      How this work was done:
      
      Patches were generated and checked against linux-4.14-rc6 for a subset of
      the use cases:
       - file had no licensing information it it.
       - file was a */uapi/* one with no licensing information in it,
       - file was a */uapi/* one with existing licensing information,
      
      Further patches will be generated in subsequent months to fix up cases
      where non-standard license headers were used, and references to license
      had to be inferred by heuristics based on keywords.
      
      The analysis to determine which SPDX License Identifier to be applied to
      a file was done in a spreadsheet of side by side results from of the
      output of two independent scanners (ScanCode & Windriver) producing SPDX
      tag:value files created by Philippe Ombredanne.  Philippe prepared the
      base worksheet, and did an initial spot review of a few 1000 files.
      
      The 4.13 kernel was the starting point of the analysis with 60,537 files
      assessed.  Kate Stewart did a file by file comparison of the scanner
      results in the spreadsheet to determine which SPDX license identifier(s)
      to be applied to the file. She confirmed any determination that was not
      immediately clear with lawyers working with the Linux Foundation.
      
      Criteria used to select files for SPDX license identifier tagging was:
       - Files considered eligible had to be source code files.
       - Make and config files were included as candidates if they contained >5
         lines of source
       - File already had some variant of a license header in it (even if <5
         lines).
      
      All documentation files were explicitly excluded.
      
      The following heuristics were used to determine which SPDX license
      identifiers to apply.
      
       - when both scanners couldn't find any license traces, file was
         considered to have no license information in it, and the top level
         COPYING file license applied.
      
         For non */uapi/* files that summary was:
      
         SPDX license identifier                            # files
         ---------------------------------------------------|-------
         GPL-2.0                                              11139
      
         and resulted in the first patch in this series.
      
         If that file was a */uapi/* path one, it was "GPL-2.0 WITH
         Linux-syscall-note" otherwise it was "GPL-2.0".  Results of that was:
      
         SPDX license identifier                            # files
         ---------------------------------------------------|-------
         GPL-2.0 WITH Linux-syscall-note                        930
      
         and resulted in the second patch in this series.
      
       - if a file had some form of licensing information in it, and was one
         of the */uapi/* ones, it was denoted with the Linux-syscall-note if
         any GPL family license was found in the file or had no licensing in
         it (per prior point).  Results summary:
      
         SPDX license identifier                            # files
         ---------------------------------------------------|------
         GPL-2.0 WITH Linux-syscall-note                       270
         GPL-2.0+ WITH Linux-syscall-note                      169
         ((GPL-2.0 WITH Linux-syscall-note) OR BSD-2-Clause)    21
         ((GPL-2.0 WITH Linux-syscall-note) OR BSD-3-Clause)    17
         LGPL-2.1+ WITH Linux-syscall-note                      15
         GPL-1.0+ WITH Linux-syscall-note                       14
         ((GPL-2.0+ WITH Linux-syscall-note) OR BSD-3-Clause)    5
         LGPL-2.0+ WITH Linux-syscall-note                       4
         LGPL-2.1 WITH Linux-syscall-note                        3
         ((GPL-2.0 WITH Linux-syscall-note) OR MIT)              3
         ((GPL-2.0 WITH Linux-syscall-note) AND MIT)             1
      
         and that resulted in the third patch in this series.
      
       - when the two scanners agreed on the detected license(s), that became
         the concluded license(s).
      
       - when there was disagreement between the two scanners (one detected a
         license but the other didn't, or they both detected different
         licenses) a manual inspection of the file occurred.
      
       - In most cases a manual inspection of the information in the file
         resulted in a clear resolution of the license that should apply (and
         which scanner probably needed to revisit its heuristics).
      
       - When it was not immediately clear, the license identifier was
         confirmed with lawyers working with the Linux Foundation.
      
       - If there was any question as to the appropriate license identifier,
         the file was flagged for further research and to be revisited later
         in time.
      
      In total, over 70 hours of logged manual review was done on the
      spreadsheet to determine the SPDX license identifiers to apply to the
      source files by Kate, Philippe, Thomas and, in some cases, confirmation
      by lawyers working with the Linux Foundation.
      
      Kate also obtained a third independent scan of the 4.13 code base from
      FOSSology, and compared selected files where the other two scanners
      disagreed against that SPDX file, to see if there was new insights.  The
      Windriver scanner is based on an older version of FOSSology in part, so
      they are related.
      
      Thomas did random spot checks in about 500 files from the spreadsheets
      for the uapi headers and agreed with SPDX license identifier in the
      files he inspected. For the non-uapi files Thomas did random spot checks
      in about 15000 files.
      
      In initial set of patches against 4.14-rc6, 3 files were found to have
      copy/paste license identifier errors, and have been fixed to reflect the
      correct identifier.
      
      Additionally Philippe spent 10 hours this week doing a detailed manual
      inspection and review of the 12,461 patched files from the initial patch
      version early this week with:
       - a full scancode scan run, collecting the matched texts, detected
         license ids and scores
       - reviewing anything where there was a license detected (about 500+
         files) to ensure that the applied SPDX license was correct
       - reviewing anything where there was no detection but the patch license
         was not GPL-2.0 WITH Linux-syscall-note to ensure that the applied
         SPDX license was correct
      
      This produced a worksheet with 20 files needing minor correction.  This
      worksheet was then exported into 3 different .csv files for the
      different types of files to be modified.
      
      These .csv files were then reviewed by Greg.  Thomas wrote a script to
      parse the csv files and add the proper SPDX tag to the file, in the
      format that the file expected.  This script was further refined by Greg
      based on the output to detect more types of files automatically and to
      distinguish between header and source .c files (which need different
      comment types.)  Finally Greg ran the script using the .csv files to
      generate the patches.
      Reviewed-by: default avatarKate Stewart <kstewart@linuxfoundation.org>
      Reviewed-by: default avatarPhilippe Ombredanne <pombredanne@nexb.com>
      Reviewed-by: default avatarThomas Gleixner <tglx@linutronix.de>
      Signed-off-by: default avatarGreg Kroah-Hartman <gregkh@linuxfoundation.org>
      b2441318
  27. 13 Oct, 2017 1 commit
  28. 11 Oct, 2017 1 commit
    • Srinivas Pandruvada's avatar
      ACPI / LPIT: Add Low Power Idle Table (LPIT) support · eeb2d80d
      Srinivas Pandruvada authored
      Add functionality to read LPIT table, which provides:
      
       - Sysfs interface to read residency counters via
         /sys/devices/system/cpu/cpuidle/low_power_idle_cpu_residency_us
         /sys/devices/system/cpu/cpuidle/low_power_idle_system_residency_us
      
      Here the count "low_power_idle_cpu_residency_us" shows the time spent
      by CPU package in low power state.  This is read via MSR interface,
      which points to MSR for PKG C10.
      
      Here the count "low_power_idle_system_residency_us" show the count the
      system was in low power state. This is read via MMIO interface. This
      is mapped to SLP_S0 residency on modern Intel systems. This residency
      is achieved only when CPU is in PKG C10 and all functional blocks are
      in low power state.
      
      It is possible that none of the above counters present or anyone of the
      counter present or all counters present.
      
      For example: On my Kabylake system both of the above counters present.
      After suspend to idle these counts updated and prints:
      
       6916179
       6998564
      
      This counter can be read by tools like turbostat to display. Or it can
      be used to debug, if modern systems are reaching desired low power state.
      
       - Provides an interface to read residency counter memory address
      
         This address can be used to get the base address of PMC memory
         mapped IO.  This is utilized by intel_pmc_core driver to print
         more debug information.
      
      In addition, to avoid code duplication to read iomem, removed the read of
      iomem from acpi_os_read_memory() in osl.c and made a common function
      acpi_os_read_iomem(). This new function is used for reading iomem in
      in both osl.c and acpi_lpit.c.
      
      Link: http://www.uefi.org/sites/default/files/resources/Intel_ACPI_Low_Power_S0_Idle.pdfSigned-off-by: default avatarSrinivas Pandruvada <srinivas.pandruvada@linux.intel.com>
      Signed-off-by: default avatarRafael J. Wysocki <rafael.j.wysocki@intel.com>
      eeb2d80d
  29. 03 Oct, 2017 1 commit
    • Rajmohan Mani's avatar
      ACPI / PMIC: Add TI PMIC TPS68470 operation region driver · e13452ac
      Rajmohan Mani authored
      The Kabylake platform coreboot (Chrome OS equivalent of
      BIOS) has defined 4 operation regions for the TI TPS68470 PMIC.
      These operation regions are to enable/disable voltage
      regulators, configure voltage regulators, enable/disable
      clocks and to configure clocks.
      
      This config adds ACPI operation region support for TI TPS68470 PMIC.
      TPS68470 device is an advanced power management unit that powers
      a Compact Camera Module (CCM), generates clocks for image sensors,
      drives a dual LED for flash and incorporates two LED drivers for
      general purpose indicators.
      
      This driver enables ACPI operation region support to control voltage
      regulators and clocks for the TPS68470 PMIC.
      Signed-off-by: default avatarRajmohan Mani <rajmohan.mani@intel.com>
      Acked-by: default avatarSakari Ailus <sakari.ailus@linux.intel.com>
      Signed-off-by: default avatarRafael J. Wysocki <rafael.j.wysocki@intel.com>
      e13452ac
  30. 27 Apr, 2017 1 commit
  31. 20 Apr, 2017 2 commits
  32. 10 Apr, 2017 2 commits
    • Borislav Petkov's avatar
      EDAC: Remove EDAC_MM_EDAC · e3c4ff6d
      Borislav Petkov authored
      Move all the EDAC core functionality behind CONFIG_EDAC and get rid of
      that indirection. Update defconfigs which had it.
      
      While at it, fix dependencies such that EDAC depends on RAS for the
      tracepoints.
      Signed-off-by: default avatarBorislav Petkov <bp@suse.de>
      Cc: linux-arm-kernel@lists.infradead.org
      Cc: linuxppc-dev@lists.ozlabs.org
      Cc: Chris Metcalf <cmetcalf@mellanox.com>
      Cc: linux-edac@vger.kernel.org
      e3c4ff6d
    • Borislav Petkov's avatar
      ACPI/extlog: Add EDAC dependency · 9613916b
      Borislav Petkov authored
      We are calling EDAC functions - make the proper dependencies explicit.
      Signed-off-by: default avatarBorislav Petkov <bp@suse.de>
      Cc: linux-acpi@vger.kernel.org
      9613916b
  33. 07 Apr, 2017 1 commit
  34. 05 Apr, 2017 1 commit
  35. 14 Dec, 2016 1 commit