diff options
| author | Rajat Jain <rajatja@google.com> | 2019-06-27 20:34:13 -0700 |
|---|---|---|
| committer | Andy Shevchenko <andriy.shevchenko@linux.intel.com> | 2019-07-08 16:51:30 +0300 |
| commit | b02f6a2ef0a14af5c19780521370673f55c1476d (patch) | |
| tree | a3ba6ebf863e5e9eaf58bbb914a42b87000aa1cd /scripts/kconfig/tests/err_recursive_inc/Kconfig | |
| parent | c09c6071310df430619df57d67e7ab59902f99ad (diff) | |
| download | blackbird-op-linux-b02f6a2ef0a14af5c19780521370673f55c1476d.tar.gz blackbird-op-linux-b02f6a2ef0a14af5c19780521370673f55c1476d.zip | |
platform/x86: intel_pmc_core: Attach using APCI HID "INT33A1"
Most modern platforms already have the ACPI device "INT33A1" that could
be used to attach to the driver. Switch the driver to using that and
thus make the intel_pmc_core.c a pure platform_driver.
Some of the legacy platforms though, may still not have this ACPI device
in their ACPI tables. Thus for such platforms, move the code to manually
instantiate a platform_device into a new file of its own. This would
instantiate the intel_pmc_core platform device and thus attach to
the driver, if the ACPI device for the same ("INT33A1") is not present
in a system where it should be. This was discussed here:
https://www.mail-archive.com/linux-kernel@vger.kernel.org/msg1966991.html
Signed-off-by: Rajat Jain <rajatja@google.com>
[andy: renamed to intel_pmc_core_pltdrv.c to be in align with other drivers]
Signed-off-by: Andy Shevchenko <andriy.shevchenko@linux.intel.com>
Diffstat (limited to 'scripts/kconfig/tests/err_recursive_inc/Kconfig')
0 files changed, 0 insertions, 0 deletions
