lkml.org 
[lkml]   [2021]   [Jan]   [17]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
 
Messages in this thread
/
From
Subject[PATCH v2 0/7] Introduce intel_skl_int3472 driver
Date
Hello all

v1 for this series was originally 14-18 of this series:
https://lore.kernel.org/linux-media/20201130133129.1024662-1-djrscally@gmail.com/T/#m91934e12e3d033da2e768e952ea3b4a125ee3e67

At the moment in the kernel the ACPI _HID INT3472 is taken by the tps68470
MFD driver, but that driver can only handle some of the cases of that _HID
that we see. There are at least these three possibilities:

1. INT3472 devices that provide GPIOs through the usual framework and run
power and clocks through an operation region; this is the situation that
the current module handles and is seen on ChromeOS devices
2. INT3472 devices that provide GPIOs, plus clocks and regulators that are
meant to be driven through the usual frameworks, usually seen on devices
designed to run Windows
3. INT3472 devices that don't actually represent a physical tps68470, but
are being used as a convenient way of grouping a bunch of system GPIO
lines that are intended to enable power and clocks for sensors which
are called out as dependent on them. Also seen on devices designed to
run Windows.

This series introduces a new module which registers:

1. An i2c driver that determines which scenario (#1 or #2) applies to the
machine and registers platform devices to be bound to GPIO, OpRegion,
clock and regulator drivers as appropriate.
2. A platform driver that binds to the dummy INT3472 devices described in
#3

The platform driver for the dummy device registers the GPIO lines that
enable the clocks and regulators to the sensors via those frameworks so
that sensor drivers can consume them in the usual fashion. The existing
GPIO and OpRegion tps68470 drivers will work with the i2c driver that's
registered. Clock and regulator drivers are currently in the works.

The existing mfd/tps68470.c driver being thus superseded, it is removed.

This has been tested on a number of devices; but currently **not** on a
ChromeOS, which we ideally need to do to ensure no regression caused by
replacing the tps68470 MFD driver.

Thanks
Dan

Daniel Scally (7):
acpi: utils: move acpi_lpss_dep() to utils
acpi: utils: Add function to fetch dependent acpi_devices
i2c: i2c-core-base: Use format macro in i2c_dev_set_name()
i2c: i2c-core-acpi: Add i2c_acpi_dev_name()
gpio: gpiolib-acpi: Export acpi_get_gpiod()
platform: x86: Add intel_skl_int3472 driver
mfd: Remove tps68470 MFD driver

MAINTAINERS | 5 +
drivers/acpi/acpi_lpss.c | 24 -
drivers/acpi/internal.h | 1 +
drivers/acpi/pmic/Kconfig | 1 -
drivers/acpi/utils.c | 58 ++
drivers/gpio/Kconfig | 1 -
drivers/gpio/gpiolib-acpi.c | 3 +-
drivers/i2c/i2c-core-acpi.c | 16 +
drivers/i2c/i2c-core-base.c | 4 +-
drivers/mfd/Kconfig | 18 -
drivers/mfd/Makefile | 1 -
drivers/mfd/tps68470.c | 97 ----
drivers/platform/x86/Kconfig | 25 +
drivers/platform/x86/Makefile | 4 +
.../platform/x86/intel_skl_int3472_common.c | 100 ++++
.../platform/x86/intel_skl_int3472_common.h | 100 ++++
.../platform/x86/intel_skl_int3472_discrete.c | 496 ++++++++++++++++++
.../platform/x86/intel_skl_int3472_tps68470.c | 145 +++++
include/acpi/acpi_bus.h | 2 +
include/linux/acpi.h | 5 +
include/linux/i2c.h | 8 +
21 files changed, 969 insertions(+), 145 deletions(-)
delete mode 100644 drivers/mfd/tps68470.c
create mode 100644 drivers/platform/x86/intel_skl_int3472_common.c
create mode 100644 drivers/platform/x86/intel_skl_int3472_common.h
create mode 100644 drivers/platform/x86/intel_skl_int3472_discrete.c
create mode 100644 drivers/platform/x86/intel_skl_int3472_tps68470.c

--
2.25.1

\
 
 \ /
  Last update: 2021-01-18 01:37    [W:0.372 / U:2.396 seconds]
©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site