diff options
author | Daniel Scally <[email protected]> | 2021-06-03 23:40:06 +0100 |
---|---|---|
committer | Hans de Goede <[email protected]> | 2021-06-16 17:49:53 +0200 |
commit | 5de691bffe57fd0fc2b4dcdcf13815c56d11db10 (patch) | |
tree | f7c03b1d956b7224c50984c9731f9b783b2e313e /tools/perf/scripts/python/export-to-sqlite.py | |
parent | c8d9c3674cba2e420f31e64e4f1ec52db5cc0bb5 (diff) |
platform/x86: Add intel_skl_int3472 driver
ACPI devices with _HID INT3472 are currently matched to the tps68470
driver, however this does not cover all situations in which that _HID
occurs. We've encountered three possibilities:
1. On Chrome OS devices, an ACPI device with _HID INT3472 (representing
a physical TPS68470 device) that requires a GPIO and OpRegion driver
2. On devices designed for Windows, an ACPI device with _HID INT3472
(again representing a physical TPS68470 device) which requires GPIO,
Clock and Regulator drivers.
3. On other devices designed for Windows, an ACPI device with _HID
INT3472 which does **not** represent a physical TPS68470, and is instead
used as a dummy device to group some system GPIO lines which are meant
to be consumed by the sensor that is dependent on this entry.
This commit adds a new module, registering a platform driver to deal
with the 3rd scenario plus an i2c driver to deal with #1 and #2, by
querying the CLDB buffer found against INT3472 entries to determine
which is most appropriate.
Suggested-by: Laurent Pinchart <[email protected]>
Signed-off-by: Daniel Scally <[email protected]>
Link: https://lore.kernel.org/r/[email protected]
[[email protected] Make skl_int3472_tps68470_calc_type() static]
Signed-off-by: Hans de Goede <[email protected]>
Diffstat (limited to 'tools/perf/scripts/python/export-to-sqlite.py')
0 files changed, 0 insertions, 0 deletions