Introduce intel_skl_int3472 driver
Subsystems (9)
v2 cover Introduce intel_skl_int3472 driver
Hello all
v1 for this series was originally 14-18 of this series:
https://lore.kernel.org/linux-media/[email protected]/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
Signature · 1 line
2.25.1
PATCH v2 1/7 acpi: utils: move acpi_lpss_dep() to utils
I need to be able to identify devices which declare themselves to be dependent on other devices through _DEP; add this function to utils.c and export it to the rest of the ACPI layer.
---
Changes in v2:
- Introduced
drivers/acpi/acpi_lpss.c | 24 ------------------------ drivers/acpi/internal.h | 1 + drivers/acpi/utils.c | 24 ++++++++++++++++++++++++ 3 files changed, 25 insertions(+), 24 deletions(-)
drivers/acpi/acpi_lpss.c +0 -24
@@ -543,30 +543,6 @@ static struct device *acpi_lpss_find_device(const char *hid, const char *uid)return bus_find_device (&pci_bus_type,NULL , &data, match_hid_uid); } -static bool acpi_lpss_dep (struct acpi_device *adev,acpi_handle handle) -{ -struct acpi_handle_list dep_devices; -acpi_status status; -int i; - -if (!acpi_has_method (adev->handle,"_DEP" )) -return false; - - status =acpi_evaluate_reference (adev->handle,"_DEP" ,NULL , - &dep_devices); -if (ACPI_FAILURE (status)) { -dev_dbg (&adev->dev,"Failed to evaluate _DEP.\n" ); -return false; - } - -for (i =0 ; i < dep_devices.count; i++) { -if (dep_devices.handles[i] == handle) -return true; - } - -return false; -} -static void acpi_lpss_link_consumer (struct device *dev1,const struct lpss_device_links *link) {
drivers/acpi/internal.h +1 -0
@@ -79,6 +79,7 @@ static inline void acpi_lpss_init(void) {}#endif void acpi_apd_init (void ); +bool acpi_lpss_dep (struct acpi_device *adev,acpi_handle handle);acpi_status acpi_hotplug_schedule (struct acpi_device *adev,u32 src);bool acpi_queue_hotplug_work (struct work_struct *work);
drivers/acpi/utils.c +24 -0
@@ -807,6 +807,30 @@ static int acpi_dev_match_cb(struct device *dev, const void *data)return hrv == match->hrv; } +bool acpi_lpss_dep (struct acpi_device *adev,acpi_handle handle) +{ +struct acpi_handle_list dep_devices; +acpi_status status; +int i; + +if (!acpi_has_method (adev->handle,"_DEP" )) +return false; + + status =acpi_evaluate_reference (adev->handle,"_DEP" ,NULL , + &dep_devices); +if (ACPI_FAILURE (status)) { +dev_dbg (&adev->dev,"Failed to evaluate _DEP.\n" ); +return false; + } + +for (i =0 ; i < dep_devices.count; i++) { +if (dep_devices.handles[i] == handle) +return true; + } + +return false; +} +/** * acpi_dev_present - Detect that a given ACPI device is present * @hid: Hardware ID of the device.
Signature · 1 line
2.25.1
Re: [PATCH v2 1/7] acpi: utils: move acpi_lpss_dep() to utils
Hi Daniel,
Thank you for the patch.
Quoted 55 lines · Daniel Scally
I need to be able to identify devices which declare themselves to be dependent on other devices through
_DEP; add this function toutils.cand export it to the rest of the ACPI layer.Suggested-by Andy Shevchenko <[email protected]>Signed-off-by Daniel Scally <[email protected]>---
Changes in v2:
- Introduceddrivers/acpi/acpi_lpss.c | 24 ------------------------ drivers/acpi/internal.h | 1 + drivers/acpi/utils.c | 24 ++++++++++++++++++++++++ 3 files changed, 25 insertions(+), 24 deletions(-)drivers/acpi/acpi_lpss.c +0
-24@@ -543,30 +543,6 @@ static struct device *acpi_lpss_find_device(const char *hid, const char *uid)return bus_find_device (&pci_bus_type,NULL , &data, match_hid_uid); } -static bool acpi_lpss_dep (struct acpi_device *adev,acpi_handle handle) -{ -struct acpi_handle_list dep_devices; -acpi_status status; -int i; - -if (!acpi_has_method (adev->handle,"_DEP" )) -return false; - - status =acpi_evaluate_reference (adev->handle,"_DEP" ,NULL , - &dep_devices); -if (ACPI_FAILURE (status)) { -dev_dbg (&adev->dev,"Failed to evaluate _DEP.\n" ); -return false; - } - -for (i =0 ; i < dep_devices.count; i++) { -if (dep_devices.handles[i] == handle) -return true; - } - -return false; -} -static void acpi_lpss_link_consumer (struct device *dev1,const struct lpss_device_links *link) {drivers/acpi/internal.h +0
-0
drivers/acpi/internal.h static inline void acpi_lpss_init(void) {} · line 82
Quoted 4 lines
drivers/acpi/internal.h +1
-0@@ -79,6 +79,7 @@ static inline void acpi_lpss_init(void) {}#endif void acpi_apd_init (void ); +bool acpi_lpss_dep (struct acpi_device *adev,acpi_handle handle);
"lpss" stands for low power subsystem, an Intel device within the PCH that handles I2C, SPI, UART, ... I think the function should be renamed, as it's now generic. acpi_dev_has_dep() is a potential candidate, I'm sure better ones exist. A bit of kerneldoc would also not hurt.
Quoted 38 lines
drivers/acpi/internal.h +0
-0acpi_status acpi_hotplug_schedule (struct acpi_device *adev,u32 src);bool acpi_queue_hotplug_work (struct work_struct *work);drivers/acpi/utils.c +24
-0@@ -807,6 +807,30 @@ static int acpi_dev_match_cb(struct device *dev, const void *data)return hrv == match->hrv; } +bool acpi_lpss_dep (struct acpi_device *adev,acpi_handle handle) +{ +struct acpi_handle_list dep_devices; +acpi_status status; +int i; + +if (!acpi_has_method (adev->handle,"_DEP" )) +return false; + + status =acpi_evaluate_reference (adev->handle,"_DEP" ,NULL , + &dep_devices); +if (ACPI_FAILURE (status)) { +dev_dbg (&adev->dev,"Failed to evaluate _DEP.\n" ); +return false; + } + +for (i =0 ; i < dep_devices.count; i++) { +if (dep_devices.handles[i] == handle) +return true; + } + +return false; +} +/** * acpi_dev_present - Detect that a given ACPI device is present * @hid: Hardware ID of the device.
Signature · 3 lines
Regards, Laurent Pinchart
Re: [PATCH v2 1/7] acpi: utils: move acpi_lpss_dep() to utils
Hi Laurent
Quoted 62 lines · Laurent Pinchart
Hi Daniel,
Thank you for the patch.
Quoted 57 lines · Daniel Scally
I need to be able to identify devices which declare themselves to be dependent on other devices through
_DEP; add this function toutils.cand export it to the rest of the ACPI layer.Suggested-by Andy Shevchenko <[email protected]>Signed-off-by Daniel Scally <[email protected]>---
Changes in v2:
- Introduceddrivers/acpi/acpi_lpss.c | 24 ------------------------ drivers/acpi/internal.h | 1 + drivers/acpi/utils.c | 24 ++++++++++++++++++++++++ 3 files changed, 25 insertions(+), 24 deletions(-)drivers/acpi/acpi_lpss.c +0
-24@@ -543,30 +543,6 @@ static struct device *acpi_lpss_find_device(const char *hid, const char *uid)return bus_find_device (&pci_bus_type,NULL , &data, match_hid_uid); } -static bool acpi_lpss_dep (struct acpi_device *adev,acpi_handle handle) -{ -struct acpi_handle_list dep_devices; -acpi_status status; -int i; - -if (!acpi_has_method (adev->handle,"_DEP" )) -return false; - - status =acpi_evaluate_reference (adev->handle,"_DEP" ,NULL , - &dep_devices); -if (ACPI_FAILURE (status)) { -dev_dbg (&adev->dev,"Failed to evaluate _DEP.\n" ); -return false; - } - -for (i =0 ; i < dep_devices.count; i++) { -if (dep_devices.handles[i] == handle) -return true; - } - -return false; -} -static void acpi_lpss_link_consumer (struct device *dev1,const struct lpss_device_links *link) {drivers/acpi/internal.h +0
-0@@ -79,6 +79,7 @@ static inline void acpi_lpss_init(void) {}#endif
Quoted 6 lines
drivers/acpi/internal.h static inline void acpi_lpss_init(void) {} · line 82
Quoted 2 lines
drivers/acpi/internal.h +1
-0void acpi_apd_init (void ); +bool acpi_lpss_dep (struct acpi_device *adev,acpi_handle handle);"lpss" stands for low power subsystem, an Intel device within the PCH that handles I2C, SPI, UART, ... I think the function should be renamed, as it's now generic.
acpi_dev_has_dep()is a potential candidate, I'm sure better ones exist. A bit of kerneldoc would also not hurt.
Okedokey; I shall add kerneldoc and think of an appropriate name, plus rename all the uses of it. How about acpi_dev_is_dep()? "has_dep" to me implies anything at all in _DEP should return true.
Quoted 38 lines
Quoted 38 lines
drivers/acpi/internal.h +0
-0acpi_status acpi_hotplug_schedule (struct acpi_device *adev,u32 src);bool acpi_queue_hotplug_work (struct work_struct *work);drivers/acpi/utils.c +24
-0@@ -807,6 +807,30 @@ static int acpi_dev_match_cb(struct device *dev, const void *data)return hrv == match->hrv; } +bool acpi_lpss_dep (struct acpi_device *adev,acpi_handle handle) +{ +struct acpi_handle_list dep_devices; +acpi_status status; +int i; + +if (!acpi_has_method (adev->handle,"_DEP" )) +return false; + + status =acpi_evaluate_reference (adev->handle,"_DEP" ,NULL , + &dep_devices); +if (ACPI_FAILURE (status)) { +dev_dbg (&adev->dev,"Failed to evaluate _DEP.\n" ); +return false; + } + +for (i =0 ; i < dep_devices.count; i++) { +if (dep_devices.handles[i] == handle) +return true; + } + +return false; +} +/** * acpi_dev_present - Detect that a given ACPI device is present * @hid: Hardware ID of the device.
Re: [PATCH v2 1/7] acpi: utils: move acpi_lpss_dep() to utils
In reply to Laurent PinchartQuoted 1 line · Laurent Pinchart
On Mon, Jan 18, 2021 at 12:34:22AM +0000, Daniel Scally wrote:
...
Quoted 6 lines
Quoted 1 line
+bool
acpi_lpss_dep(struct acpi_device *adev, acpi_handle handle);"lpss" stands for low power subsystem, an Intel device within the PCH that handles I2C, SPI, UART, ... I think the function should be renamed, as it's now generic.
acpi_dev_has_dep()is a potential candidate, I'm sure better ones exist. A bit of kerneldoc would also not hurt.
Actually a good suggestions. Please apply my tag after addressing above.
Signature · 2 lines
With Best Regards, Andy Shevchenko
Re: [PATCH v2 1/7] acpi: utils: move acpi_lpss_dep() to utils
Quoted 10 lines · Andy Shevchenko
Quoted 1 line · Laurent Pinchart
On Mon, Jan 18, 2021 at 12:34:22AM +0000, Daniel Scally wrote:
...
Quoted 5 lines
Quoted 1 line
+bool
acpi_lpss_dep(struct acpi_device *adev, acpi_handle handle);"lpss" stands for low power subsystem, an Intel device within the PCH that handles I2C, SPI, UART, ... I think the function should be renamed, as it's now generic.
acpi_dev_has_dep()is a potential candidate, I'm sure better ones exist. A bit of kerneldoc would also not hurt.Actually a good suggestions. Please apply my tag after addressing above.
Will do, thanks
Re: [PATCH v2 1/7] acpi: utils: move acpi_lpss_dep() to utils
In reply to Daniel ScallyQuoted 3 lines · Daniel Scally
I need to be able to identify devices which declare themselves to be dependent on other devices through
_DEP; add this function toutils.cand export it to the rest of the ACPI layer.
Prefix -> "ACPI / utils: "
Otherwise good to me
Quoted 96 lines
Suggested-by Andy Shevchenko <[email protected]>Signed-off-by Daniel Scally <[email protected]>---
Changes in v2:
- Introduceddrivers/acpi/acpi_lpss.c | 24 ------------------------ drivers/acpi/internal.h | 1 + drivers/acpi/utils.c | 24 ++++++++++++++++++++++++ 3 files changed, 25 insertions(+), 24 deletions(-)drivers/acpi/acpi_lpss.c +0
-24@@ -543,30 +543,6 @@ static struct device *acpi_lpss_find_device(const char *hid, const char *uid)return bus_find_device (&pci_bus_type,NULL , &data, match_hid_uid); } -static bool acpi_lpss_dep (struct acpi_device *adev,acpi_handle handle) -{ -struct acpi_handle_list dep_devices; -acpi_status status; -int i; - -if (!acpi_has_method (adev->handle,"_DEP" )) -return false; - - status =acpi_evaluate_reference (adev->handle,"_DEP" ,NULL , - &dep_devices); -if (ACPI_FAILURE (status)) { -dev_dbg (&adev->dev,"Failed to evaluate _DEP.\n" ); -return false; - } - -for (i =0 ; i < dep_devices.count; i++) { -if (dep_devices.handles[i] == handle) -return true; - } - -return false; -} -static void acpi_lpss_link_consumer (struct device *dev1,const struct lpss_device_links *link) {drivers/acpi/internal.h +1
-0@@ -79,6 +79,7 @@ static inline void acpi_lpss_init(void) {}#endif void acpi_apd_init (void ); +bool acpi_lpss_dep (struct acpi_device *adev,acpi_handle handle);acpi_status acpi_hotplug_schedule (struct acpi_device *adev,u32 src);bool acpi_queue_hotplug_work (struct work_struct *work);drivers/acpi/utils.c +24
-0@@ -807,6 +807,30 @@ static int acpi_dev_match_cb(struct device *dev, const void *data)return hrv == match->hrv; } +bool acpi_lpss_dep (struct acpi_device *adev,acpi_handle handle) +{ +struct acpi_handle_list dep_devices; +acpi_status status; +int i; + +if (!acpi_has_method (adev->handle,"_DEP" )) +return false; + + status =acpi_evaluate_reference (adev->handle,"_DEP" ,NULL , + &dep_devices); +if (ACPI_FAILURE (status)) { +dev_dbg (&adev->dev,"Failed to evaluate _DEP.\n" ); +return false; + } + +for (i =0 ; i < dep_devices.count; i++) { +if (dep_devices.handles[i] == handle) +return true; + } + +return false; +} +/** * acpi_dev_present - Detect that a given ACPI device is present * @hid: Hardware ID of the device. Signature · 1 line
2.25.1
Signature · 2 lines
With Best Regards, Andy Shevchenko
Rafael J. Wysocki
maintainerRe: [PATCH v2 1/7] acpi: utils: move acpi_lpss_dep() to utils
Quoted 7 lines · Andy Shevchenko
Quoted 3 lines · Daniel Scally
I need to be able to identify devices which declare themselves to be dependent on other devices through
_DEP; add this function toutils.cand export it to the rest of the ACPI layer.Prefix -> "ACPI / utils: "
Preferably "ACPI: utils: " for that matter and yes, please rename the function while moving it.
Quoted 105 lines
Otherwise good to me
Reviewed-by: Andy Shevchenko <andriy.shevchenko(a)linux.intel.com>Quoted 94 lines
Suggested-by Andy Shevchenko <andriy.shevchenko(a)linux.intel.com>Signed-off-by Daniel Scally <djrscally(a)gmail.com>---
Changes in v2:
- Introduceddrivers/acpi/acpi_lpss.c | 24 ------------------------ drivers/acpi/internal.h | 1 + drivers/acpi/utils.c | 24 ++++++++++++++++++++++++ 3 files changed, 25 insertions(+), 24 deletions(-)drivers/acpi/acpi_lpss.c +0
-24@@ -543,30 +543,6 @@ static struct device *acpi_lpss_find_device(const char *hid, const char *uid)return bus_find_device (&pci_bus_type,NULL , &data, match_hid_uid); } -static bool acpi_lpss_dep (struct acpi_device *adev,acpi_handle handle) -{ -struct acpi_handle_list dep_devices; -acpi_status status; -int i; - -if (!acpi_has_method (adev->handle,"_DEP" )) -return false; - - status =acpi_evaluate_reference (adev->handle,"_DEP" ,NULL , - &dep_devices); -if (ACPI_FAILURE (status)) { -dev_dbg (&adev->dev,"Failed to evaluate _DEP.\n" ); -return false; - } - -for (i =0 ; i < dep_devices.count; i++) { -if (dep_devices.handles[i] == handle) -return true; - } - -return false; -} -static void acpi_lpss_link_consumer (struct device *dev1,const struct lpss_device_links *link) {drivers/acpi/internal.h +1
-0@@ -79,6 +79,7 @@ static inline void acpi_lpss_init(void) {}#endif void acpi_apd_init (void ); +bool acpi_lpss_dep (struct acpi_device *adev,acpi_handle handle);acpi_status acpi_hotplug_schedule (struct acpi_device *adev,u32 src);bool acpi_queue_hotplug_work (struct work_struct *work);drivers/acpi/utils.c +24
-1@@ -807,6 +807,30 @@ static int acpi_dev_match_cb(struct device *dev, const void *data)return hrv == match->hrv; } +bool acpi_lpss_dep (struct acpi_device *adev,acpi_handle handle) +{ +struct acpi_handle_list dep_devices; +acpi_status status; +int i; + +if (!acpi_has_method (adev->handle,"_DEP" )) +return false; + + status =acpi_evaluate_reference (adev->handle,"_DEP" ,NULL , + &dep_devices); +if (ACPI_FAILURE (status)) { +dev_dbg (&adev->dev,"Failed to evaluate _DEP.\n" ); +return false; + } + +for (i =0 ; i < dep_devices.count; i++) { +if (dep_devices.handles[i] == handle) +return true; + } + +return false; +} +/** * acpi_dev_present - Detect that a given ACPI device is present * @hid: Hardware ID of the device. -- Quoted 2 lines
2.25.1
--
With Best Regards,
Andy Shevchenko
Re: [PATCH v2 1/7] acpi: utils: move acpi_lpss_dep() to utils
Quoted 11 lines · Rafael J. Wysocki
Quoted 7 lines · Andy Shevchenko
Quoted 3 lines · Daniel Scally
I need to be able to identify devices which declare themselves to be dependent on other devices through
_DEP; add this function toutils.cand export it to the rest of the ACPI layer.Prefix -> "ACPI / utils: "
Preferably "ACPI: utils: " for that matter
Ah, good to know! I was always bending between / and : there.
Signature · 2 lines
With Best Regards, Andy Shevchenko
PATCH v2 2/7 acpi: utils: Add function to fetch dependent acpi_devices
In reply to Daniel ScallyIn some ACPI tables we encounter, devices use the _DEP method to assert a dependence on other ACPI devices as opposed to the OpRegions that the specification intends. We need to be able to find those devices "from" the dependee, so add a function to parse all ACPI Devices and check if the include the handle of the dependee device in their _DEP buffer.
---
Changes in v2:
- Used acpi_lpss_dep() as Andy suggested.
drivers/acpi/utils.c | 34 ++++++++++++++++++++++++++++++++++ include/acpi/acpi_bus.h | 2 ++ 2 files changed, 36 insertions(+)
drivers/acpi/utils.c +34 -0
@@ -831,6 +831,18 @@ bool acpi_lpss_dep(struct acpi_device *adev, acpi_handle handle)return false; } +static int acpi_dev_match_by_dep (struct device *dev,const void *data) +{ +struct acpi_device *adev =to_acpi_device (dev); +const struct acpi_device *dependee = data; +acpi_handle handle = dependee->handle; + +if (acpi_lpss_dep (adev, handle)) +return 1 ; + +return 0 ; +} +/** * acpi_dev_present - Detect that a given ACPI device is present * @hid: Hardware ID of the device.
@@ -866,6 +878,28 @@ bool acpi_dev_present(const char *hid, const char *uid, s64 hrv) }EXPORT_SYMBOL (acpi_dev_present); +/** +* acpi_dev_get_next_dep_dev - Return next ACPI device dependent on input dev +* @adev: Pointer to the dependee device +* @prev: Pointer to the previous dependent device (or NULL for first match) +* +* Return the next ACPI device which declares itself dependent on @adev in +* the _DEP buffer. +* +* The caller is responsible to call put_device() on the returned device. +*/ +struct acpi_device *acpi_dev_get_next_dep_dev (struct acpi_device *adev, +struct acpi_device *prev) +{ +struct device *start = prev ? &prev->dev :NULL ; +struct device *dev; + + dev =bus_find_device (&acpi_bus_type, start, adev, acpi_dev_match_by_dep); + +return dev ?to_acpi_device (dev) :NULL ; +} +EXPORT_SYMBOL (acpi_dev_get_next_dep_dev); +/** * acpi_dev_get_next_match_dev - Return the next match of ACPI device * @adev: Pointer to the previous acpi_device matching this @hid, @uid and @hrv
include/acpi/acpi_bus.h +2 -0
@@ -683,6 +683,8 @@ static inline bool acpi_device_can_poweroff(struct acpi_device *adev)bool acpi_dev_hid_uid_match (struct acpi_device *adev,const char *hid2,const char *uid2); +struct acpi_device * +acpi_dev_get_next_dep_dev (struct acpi_device *adev,struct acpi_device *prev);struct acpi_device *acpi_dev_get_next_match_dev (struct acpi_device *adev,const char *hid,const char *uid,s64 hrv); struct acpi_device *
Signature · 1 line
2.25.1
Re: [PATCH v2 2/7] acpi: utils: Add function to fetch dependent acpi_devices
Hi Daniel,
Thank you for the patch.
Quoted 25 lines · Daniel Scally
In some ACPI tables we encounter, devices use the
_DEPmethod to assert a dependence on other ACPI devices as opposed to the OpRegions that the specification intends. We need to be able to find those devices "from" the dependee, so add a function to parse all ACPI Devices and check if the include the handle of the dependee device in their_DEPbuffer.Signed-off-by Daniel Scally <[email protected]>---
Changes in v2:
- Usedacpi_lpss_dep()as Andy suggested.drivers/acpi/utils.c | 34 ++++++++++++++++++++++++++++++++++ include/acpi/acpi_bus.h | 2 ++ 2 files changed, 36 insertions(+)drivers/acpi/utils.c +2
-0@@ -831,6 +831,18 @@ bool acpi_lpss_dep(struct acpi_device *adev, acpi_handle handle)return false; } +static int acpi_dev_match_by_dep (struct device *dev,const void *data) +{
drivers/acpi/utils.c bool acpi_lpss_dep(struct acpi_device *adev, acpi_handle handle) · line 845
Quoted 10 lines
drivers/acpi/utils.c +10
-0+struct acpi_device *adev =to_acpi_device (dev); +const struct acpi_device *dependee = data; +acpi_handle handle = dependee->handle; + +if (acpi_lpss_dep (adev, handle)) +return 1 ; + +return 0 ; +} +
I think I'd move this just before acpi_dev_get_next_dep_dev() to keep the two together.
drivers/acpi/utils.c bool acpi_dev_present(const char *hid, const char *uid, s64 hrv) · line 882
Quoted 9 lines
drivers/acpi/utils.c +2
-0/** * acpi_dev_present - Detect that a given ACPI device is present * @hid: Hardware ID of the device. @@ -866,6 +878,28 @@ bool acpi_dev_present(const char *hid, const char *uid, s64 hrv) }EXPORT_SYMBOL (acpi_dev_present); +/** +* acpi_dev_get_next_dep_dev - Return next ACPI device dependent on input dev
Maybe acpi_dev_get_next_dependent_dev() ? "dep" could mean either dependent or dependency.
Quoted 5 lines
drivers/acpi/utils.c +5
-0+* @adev: Pointer to the dependee device +* @prev: Pointer to the previous dependent device (or NULL for first match) +* +* Return the next ACPI device which declares itself dependent on @adev in +* the _DEP buffer.
drivers/acpi/utils.c bool acpi_dev_present(const char *hid, const char *uid, s64 hrv) · line 897
Quoted 10 lines
drivers/acpi/utils.c +10
-0+* +* The caller is responsible to call put_device() on the returned device. +*/ +struct acpi_device *acpi_dev_get_next_dep_dev (struct acpi_device *adev, +struct acpi_device *prev) +{ +struct device *start = prev ? &prev->dev :NULL ; +struct device *dev; + + dev =bus_find_device (&acpi_bus_type, start, adev, acpi_dev_match_by_dep);
Having to loop over all ACPI devices is quite inefficient, but if we need a reverse lookup, we don't really have a choice. We could create a reverse map, but I don't think it's worth it.
drivers/acpi/utils.c bool acpi_dev_present(const char *hid, const char *uid, s64 hrv) · line 901
Quoted 4 lines
drivers/acpi/utils.c +4
-0+ +return dev ?to_acpi_device (dev) :NULL ; +} +EXPORT_SYMBOL (acpi_dev_get_next_dep_dev);
I would have used EXPORT_SYMBOL_GPL. I'm not sure what the policy is in the ACPI subsystem, and it's also a personal choice.
Quoted 17 lines
drivers/acpi/utils.c +1
-0+/** * acpi_dev_get_next_match_dev - Return the next match of ACPI device * @adev: Pointer to the previous acpi_device matching this @hid, @uid and @hrv include/acpi/acpi_bus.h +2
-0@@ -683,6 +683,8 @@ static inline bool acpi_device_can_poweroff(struct acpi_device *adev)bool acpi_dev_hid_uid_match (struct acpi_device *adev,const char *hid2,const char *uid2); +struct acpi_device * +acpi_dev_get_next_dep_dev (struct acpi_device *adev,struct acpi_device *prev);struct acpi_device *acpi_dev_get_next_match_dev (struct acpi_device *adev,const char *hid,const char *uid,s64 hrv); struct acpi_device *
Signature · 3 lines
Regards, Laurent Pinchart
Re: [PATCH v2 2/7] acpi: utils: Add function to fetch dependent acpi_devices
Morning Laurent
Quoted 28 lines · Laurent Pinchart
Hi Daniel,
Thank you for the patch.
Quoted 23 lines · Daniel Scally
In some ACPI tables we encounter, devices use the
_DEPmethod to assert a dependence on other ACPI devices as opposed to the OpRegions that the specification intends. We need to be able to find those devices "from" the dependee, so add a function to parse all ACPI Devices and check if the include the handle of the dependee device in their_DEPbuffer.Signed-off-by Daniel Scally <[email protected]>---
Changes in v2:
- Usedacpi_lpss_dep()as Andy suggested.drivers/acpi/utils.c | 34 ++++++++++++++++++++++++++++++++++ include/acpi/acpi_bus.h | 2 ++ 2 files changed, 36 insertions(+)drivers/acpi/utils.c +0
-0@@ -831,6 +831,18 @@ bool acpi_lpss_dep(struct acpi_device *adev, acpi_handle handle)return false; }
Quoted 14 lines
drivers/acpi/utils.c bool acpi_lpss_dep(struct acpi_device *adev, acpi_handle handle) · line 845
Quoted 12 lines
drivers/acpi/utils.c +12
-0+static int acpi_dev_match_by_dep (struct device *dev,const void *data) +{ +struct acpi_device *adev =to_acpi_device (dev); +const struct acpi_device *dependee = data; +acpi_handle handle = dependee->handle; + +if (acpi_lpss_dep (adev, handle)) +return 1 ; + +return 0 ; +} +I think I'd move this just before
acpi_dev_get_next_dep_dev()to keep the two together.
Will do
Quoted 8 lines
Quoted 8 lines
drivers/acpi/utils.c +0
-0/** * acpi_dev_present - Detect that a given ACPI device is present * @hid: Hardware ID of the device. @@ -866,6 +878,28 @@ bool acpi_dev_present(const char *hid, const char *uid, s64 hrv) }EXPORT_SYMBOL (acpi_dev_present);
Quoted 4 lines
drivers/acpi/utils.c bool acpi_dev_present(const char *hid, const char *uid, s64 hrv) · line 882
Quoted 2 lines
drivers/acpi/utils.c +2
-0+/** +* acpi_dev_get_next_dep_dev - Return next ACPI device dependent on input dev Maybe
acpi_dev_get_next_dependent_dev()? "dep" could mean either dependent or dependency.
Yes, good point, I agree.
Quoted 20 lines
Quoted 6 lines
drivers/acpi/utils.c +5
-0+* @adev: Pointer to the dependee device +* @prev: Pointer to the previous dependent device (or NULL for first match) +* +* Return the next ACPI device which declares itself dependent on @adev in +* the _DEP buffer. drivers/acpi/utils.c bool acpi_dev_present(const char *hid, const char *uid, s64 hrv) · line 897
Quoted 10 lines
drivers/acpi/utils.c +10
-0+* +* The caller is responsible to call put_device() on the returned device. +*/ +struct acpi_device *acpi_dev_get_next_dep_dev (struct acpi_device *adev, +struct acpi_device *prev) +{ +struct device *start = prev ? &prev->dev :NULL ; +struct device *dev; + + dev =bus_find_device (&acpi_bus_type, start, adev, acpi_dev_match_by_dep);Having to loop over all ACPI devices is quite inefficient, but if we need a reverse lookup, we don't really have a choice. We could create a reverse map, but I don't think it's worth it.
Quoted 6 lines
drivers/acpi/utils.c bool acpi_dev_present(const char *hid, const char *uid, s64 hrv) · line 901
Quoted 4 lines
drivers/acpi/utils.c +4
-0+ +return dev ?to_acpi_device (dev) :NULL ; +} +EXPORT_SYMBOL (acpi_dev_get_next_dep_dev);I would have used
EXPORT_SYMBOL_GPL. I'm not sure what the policy is in the ACPI subsystem, and it's also a personal choice.
EXPORT_SYMBOL_GPL would be my usual choice, but the other functions in the file all use EXPORT_SYMBOL, so I assumed there was some policy that that be used (since basically everywhere else I've touched in the kernel so far defaults to the GPL version)
Quoted 2 lines
Reviewed-by Laurent Pinchart <[email protected]>
Thanks!
Quoted 18 lines
Quoted 18 lines
drivers/acpi/utils.c +1
-0+/** * acpi_dev_get_next_match_dev - Return the next match of ACPI device * @adev: Pointer to the previous acpi_device matching this @hid, @uid and @hrv include/acpi/acpi_bus.h +2
-0@@ -683,6 +683,8 @@ static inline bool acpi_device_can_poweroff(struct acpi_device *adev)bool acpi_dev_hid_uid_match (struct acpi_device *adev,const char *hid2,const char *uid2); +struct acpi_device * +acpi_dev_get_next_dep_dev (struct acpi_device *adev,struct acpi_device *prev);struct acpi_device *acpi_dev_get_next_match_dev (struct acpi_device *adev,const char *hid,const char *uid,s64 hrv); struct acpi_device *
Re: [PATCH v2 2/7] acpi: utils: Add function to fetch dependent acpi_devices
In reply to Daniel ScallyQuoted 5 lines · Daniel Scally
In some ACPI tables we encounter, devices use the
_DEPmethod to assert a dependence on other ACPI devices as opposed to the OpRegions that the specification intends. We need to be able to find those devices "from" the dependee, so add a function to parse all ACPI Devices and check if the include the handle of the dependee device in their_DEPbuffer.
Fix prefix to be "ACPI / utils: " and rebase on top of function name changes as suggested by Laurent.
...
Quoted 2 lines
+/**
+ *acpi_dev_get_next_dep_dev- Return next ACPI device dependent on input dev
Are you expecting some kind of for_each_*() macro to be added and used? Otherwise there is probably no need to have it "_next_" in the name as it will be a bit confusing.
Quoted 8 lines
+ * @adev: Pointer to the dependee device
+ * @prev: Pointer to the previous dependent device (or NULL for first match)
+ *
+ * Return the next ACPI device which declares itself dependent on @adev in
+ * the_DEPbuffer.
+ *
+ * The caller is responsible to callput_device()on the returned device.
+ */
Signature · 2 lines
With Best Regards, Andy Shevchenko
Re: [PATCH v2 2/7] acpi: utils: Add function to fetch dependent acpi_devices
Quoted 8 lines · Andy Shevchenko
Quoted 5 lines · Daniel Scally
In some ACPI tables we encounter, devices use the
_DEPmethod to assert a dependence on other ACPI devices as opposed to the OpRegions that the specification intends. We need to be able to find those devices "from" the dependee, so add a function to parse all ACPI Devices and check if the include the handle of the dependee device in their_DEPbuffer.Fix prefix to be "ACPI / utils: " and rebase on top of function name changes as suggested by Laurent.
OK.
Quoted 5 lines
Quoted 2 lines
+/**
+ *acpi_dev_get_next_dep_dev- Return next ACPI device dependent on input devAre you expecting some kind of for_each_*() macro to be added and used? Otherwise there is probably no need to have it "_next_" in the name as it will be a bit confusing.
I thought that somebody might want to do that in the future yes, although I've no need for it at the minute because each of the dummy INT3472 devices only has one dependent sensor that we've seen so far. But for the INT3472 devices representing a physical TPS68470, there are platforms where 2 sensors are called out as dependent on the same PMIC ACPI device (Surface Go2 for example).
It can be renamed and just cross that bridge when we come to it though, I have no problem with that.
Quoted 9 lines
Quoted 9 lines
+ * @adev: Pointer to the dependee device
+ * @prev: Pointer to the previous dependent device (or NULL for first match)
+ *
+ * Return the next ACPI device which declares itself dependent on @adev in
+ * the_DEPbuffer.
+ *
+ * The caller is responsible to callput_device()on the returned device.
+ */
Rafael J. Wysocki
maintainerRe: [PATCH v2 2/7] acpi: utils: Add function to fetch dependent acpi_devices
In reply to Daniel ScallyQuoted 6 lines · Daniel Scally
In some ACPI tables we encounter, devices use the
_DEPmethod to assert a dependence on other ACPI devices as opposed to the OpRegions that the specification intends. We need to be able to find those devices "from" the dependee, so add a function to parse all ACPI Devices and check if the include the handle of the dependee device in their_DEPbuffer.
What exactly do you need this for?
Would it be practical to look up the suppliers in acpi_dep_list instead?
Note that supplier drivers may remove entries from there, but does that matter for your use case?
Quoted 77 lines
Signed-off-by Daniel Scally <djrscally(a)gmail.com>---
Changes in v2:
- Usedacpi_lpss_dep()as Andy suggested.drivers/acpi/utils.c | 34 ++++++++++++++++++++++++++++++++++ include/acpi/acpi_bus.h | 2 ++ 2 files changed, 36 insertions(+)drivers/acpi/utils.c +34
-0@@ -831,6 +831,18 @@ bool acpi_lpss_dep(struct acpi_device *adev, acpi_handle handle)return false; } +static int acpi_dev_match_by_dep (struct device *dev,const void *data) +{ +struct acpi_device *adev =to_acpi_device (dev); +const struct acpi_device *dependee = data; +acpi_handle handle = dependee->handle; + +if (acpi_lpss_dep (adev, handle)) +return 1 ; + +return 0 ; +} +/** * acpi_dev_present - Detect that a given ACPI device is present * @hid: Hardware ID of the device. @@ -866,6 +878,28 @@ bool acpi_dev_present(const char *hid, const char *uid, s64 hrv) }EXPORT_SYMBOL (acpi_dev_present); +/** +* acpi_dev_get_next_dep_dev - Return next ACPI device dependent on input dev +* @adev: Pointer to the dependee device +* @prev: Pointer to the previous dependent device (or NULL for first match) +* +* Return the next ACPI device which declares itself dependent on @adev in +* the _DEP buffer. +* +* The caller is responsible to call put_device() on the returned device. +*/ +struct acpi_device *acpi_dev_get_next_dep_dev (struct acpi_device *adev, +struct acpi_device *prev) +{ +struct device *start = prev ? &prev->dev :NULL ; +struct device *dev; + + dev =bus_find_device (&acpi_bus_type, start, adev, acpi_dev_match_by_dep); + +return dev ?to_acpi_device (dev) :NULL ; +} +EXPORT_SYMBOL (acpi_dev_get_next_dep_dev); +/** * acpi_dev_get_next_match_dev - Return the next match of ACPI device * @adev: Pointer to the previous acpi_device matching this @hid, @uid and @hrv include/acpi/acpi_bus.h +2
-1@@ -683,6 +683,8 @@ static inline bool acpi_device_can_poweroff(struct acpi_device *adev)bool acpi_dev_hid_uid_match (struct acpi_device *adev,const char *hid2,const char *uid2); +struct acpi_device * +acpi_dev_get_next_dep_dev (struct acpi_device *adev,struct acpi_device *prev);struct acpi_device *acpi_dev_get_next_match_dev (struct acpi_device *adev,const char *hid,const char *uid,s64 hrv); struct acpi_device * --2.25.1
Re: [PATCH v2 2/7] acpi: utils: Add function to fetch dependent acpi_devices
Quoted 7 lines · Rafael J. Wysocki
Quoted 5 lines · Daniel Scally
In some ACPI tables we encounter, devices use the
_DEPmethod to assert a dependence on other ACPI devices as opposed to the OpRegions that the specification intends. We need to be able to find those devices "from" the dependee, so add a function to parse all ACPI Devices and check if the include the handle of the dependee device in their_DEPbuffer.What exactly do you need this for?
So, in our DSDT we have devices with _HID INT3472, plus sensors which refer to those INT3472's in their _DEP method. The driver binds to the INT3472 device, we need to find the sensors dependent on them.
Quoted 4 lines
Would it be practical to look up the suppliers in
acpi_dep_listinstead?Note that supplier drivers may remove entries from there, but does that matter for your use case?
Ah - that may work, yes. Thank you, let me test that.
Quoted 78 lines
Quoted 78 lines
Signed-off-by Daniel Scally <[email protected]>---
Changes in v2:
- Usedacpi_lpss_dep()as Andy suggested.drivers/acpi/utils.c | 34 ++++++++++++++++++++++++++++++++++ include/acpi/acpi_bus.h | 2 ++ 2 files changed, 36 insertions(+)drivers/acpi/utils.c +34
-0@@ -831,6 +831,18 @@ bool acpi_lpss_dep(struct acpi_device *adev, acpi_handle handle)return false; } +static int acpi_dev_match_by_dep (struct device *dev,const void *data) +{ +struct acpi_device *adev =to_acpi_device (dev); +const struct acpi_device *dependee = data; +acpi_handle handle = dependee->handle; + +if (acpi_lpss_dep (adev, handle)) +return 1 ; + +return 0 ; +} +/** * acpi_dev_present - Detect that a given ACPI device is present * @hid: Hardware ID of the device. @@ -866,6 +878,28 @@ bool acpi_dev_present(const char *hid, const char *uid, s64 hrv) }EXPORT_SYMBOL (acpi_dev_present); +/** +* acpi_dev_get_next_dep_dev - Return next ACPI device dependent on input dev +* @adev: Pointer to the dependee device +* @prev: Pointer to the previous dependent device (or NULL for first match) +* +* Return the next ACPI device which declares itself dependent on @adev in +* the _DEP buffer. +* +* The caller is responsible to call put_device() on the returned device. +*/ +struct acpi_device *acpi_dev_get_next_dep_dev (struct acpi_device *adev, +struct acpi_device *prev) +{ +struct device *start = prev ? &prev->dev :NULL ; +struct device *dev; + + dev =bus_find_device (&acpi_bus_type, start, adev, acpi_dev_match_by_dep); + +return dev ?to_acpi_device (dev) :NULL ; +} +EXPORT_SYMBOL (acpi_dev_get_next_dep_dev); +/** * acpi_dev_get_next_match_dev - Return the next match of ACPI device * @adev: Pointer to the previous acpi_device matching this @hid, @uid and @hrv include/acpi/acpi_bus.h +2
-1@@ -683,6 +683,8 @@ static inline bool acpi_device_can_poweroff(struct acpi_device *adev)bool acpi_dev_hid_uid_match (struct acpi_device *adev,const char *hid2,const char *uid2); +struct acpi_device * +acpi_dev_get_next_dep_dev (struct acpi_device *adev,struct acpi_device *prev);struct acpi_device *acpi_dev_get_next_match_dev (struct acpi_device *adev,const char *hid,const char *uid,s64 hrv); struct acpi_device * --2.25.1
Rafael J. Wysocki
maintainerRe: [PATCH v2 2/7] acpi: utils: Add function to fetch dependent acpi_devices
Quoted 8 lines · Daniel Scally
Quoted 6 lines · Rafael J. Wysocki
Quoted 5 lines · Daniel Scally
In some ACPI tables we encounter, devices use the
_DEPmethod to assert a dependence on other ACPI devices as opposed to the OpRegions that the specification intends. We need to be able to find those devices "from" the dependee, so add a function to parse all ACPI Devices and check if the include the handle of the dependee device in their_DEPbuffer.
Quoted 6 lines
Quoted 1 line
What exactly do you need this for?
So, in our DSDT we have devices with
_HIDINT3472, plus sensors which refer to those INT3472's in their_DEPmethod. The driver binds to the INT3472 device, we need to find the sensors dependent on them.
Well, this is an interesting concept. :-)
Why does _DEP need to be used for that? Isn't there any other way to look up the dependent sensors?
Quoted 7 lines
Quoted 5 lines
Would it be practical to look up the suppliers in
acpi_dep_listinstead?Note that supplier drivers may remove entries from there, but does that matter for your use case?
Ah - that may work, yes. Thank you, let me test that.
Even if that doesn't work right away, but it can be made work, I would very much prefer that to the driver parsing _DEP for every device in the namespace by itself.
Re: [PATCH v2 2/7] acpi: utils: Add function to fetch dependent acpi_devices
Quoted 9 lines · Rafael J. Wysocki
Quoted 8 lines · Daniel Scally
Quoted 7 lines · Rafael J. Wysocki
Quoted 5 lines · Daniel Scally
In some ACPI tables we encounter, devices use the
_DEPmethod to assert a dependence on other ACPI devices as opposed to the OpRegions that the specification intends. We need to be able to find those devices "from" the dependee, so add a function to parse all ACPI Devices and check if the include the handle of the dependee device in their_DEPbuffer.What exactly do you need this for?
Quoted 8 lines
Quoted 4 lines
So, in our DSDT we have devices with
_HIDINT3472, plus sensors which refer to those INT3472's in their_DEPmethod. The driver binds to the INT3472 device, we need to find the sensors dependent on them.Well, this is an interesting concept. :-)
Why does
_DEPneed to be used for that? Isn't there any other way to look up the dependent sensors?
If there is, I'm not aware of it, I don't see a reference to the sensor in the INT3472 device (named "PMI0", with the corresponding sensor being "CAM0") in DSDT [1]
Quoted 8 lines
Quoted 5 lines
Quoted 4 lines
Would it be practical to look up the suppliers in
acpi_dep_listinstead?Note that supplier drivers may remove entries from there, but does that matter for your use case?
Ah - that may work, yes. Thank you, let me test that.
Even if that doesn't work right away, but it can be made work, I would very much prefer that to the driver parsing
_DEPfor every device in the namespace by itself.
Alright; I haven't looked too closely yet, but I think an iterator over acpi_dep_list exported from the ACPI subsystem would also work in a pretty similar way to the function introduced in this patch does, without much work
Re: [PATCH v2 2/7] acpi: utils: Add function to fetch dependent acpi_devices
In reply to Rafael J. WysockiHi Rafael
Quoted 18 lines · Rafael J. Wysocki
Quoted 7 lines · Daniel Scally
Quoted 6 lines · Rafael J. Wysocki
Quoted 5 lines · Daniel Scally
In some ACPI tables we encounter, devices use the
_DEPmethod to assert a dependence on other ACPI devices as opposed to the OpRegions that the specification intends. We need to be able to find those devices "from" the dependee, so add a function to parse all ACPI Devices and check if the include the handle of the dependee device in their_DEPbuffer.Quoted 5 lines
Quoted 1 line
What exactly do you need this for?
So, in our DSDT we have devices with
_HIDINT3472, plus sensors which refer to those INT3472's in their_DEPmethod. The driver binds to the INT3472 device, we need to find the sensors dependent on them.Well, this is an interesting concept. :-)
Why does
_DEPneed to be used for that? Isn't there any other way to look up the dependent sensors?
Quoted 8 lines
Quoted 5 lines
Quoted 4 lines
Would it be practical to look up the suppliers in
acpi_dep_listinstead?Note that supplier drivers may remove entries from there, but does that matter for your use case?
Ah - that may work, yes. Thank you, let me test that.
Even if that doesn't work right away, but it can be made work, I would very much prefer that to the driver parsing
_DEPfor every device in the namespace by itself.
This does work; do you prefer it in scan.c, or in utils.c (in which case with acpi_dep_list declared as external var in internal.h)?
Rafael J. Wysocki
maintainerRe: [PATCH v2 2/7] acpi: utils: Add function to fetch dependent acpi_devices
Quoted 26 lines · Daniel Scally
Hi Rafael
Quoted 22 lines · Rafael J. Wysocki
Quoted 7 lines · Daniel Scally
Quoted 6 lines · Rafael J. Wysocki
Quoted 5 lines · Daniel Scally
In some ACPI tables we encounter, devices use the
_DEPmethod to assert a dependence on other ACPI devices as opposed to the OpRegions that the specification intends. We need to be able to find those devices "from" the dependee, so add a function to parse all ACPI Devices and check if the include the handle of the dependee device in their_DEPbuffer.Quoted 5 lines
Quoted 1 line
What exactly do you need this for?
So, in our DSDT we have devices with
_HIDINT3472, plus sensors which refer to those INT3472's in their_DEPmethod. The driver binds to the INT3472 device, we need to find the sensors dependent on them.Well, this is an interesting concept. :-)
Why does
_DEPneed to be used for that? Isn't there any other way to look up the dependent sensors?Quoted 4 lines
Quoted 4 lines
Would it be practical to look up the suppliers in
acpi_dep_listinstead?Note that supplier drivers may remove entries from there, but does that matter for your use case?
Quoted 8 lines
Quoted 4 lines
Quoted 1 line
Ah - that may work, yes. Thank you, let me test that.
Even if that doesn't work right away, but it can be made work, I would very much prefer that to the driver parsing
_DEPfor every device in the namespace by itself.This does work; do you prefer it in
scan.c, or inutils.c(in which case withacpi_dep_listdeclared as external var ininternal.h)?
Let's put it in scan.c for now, because there is the lock protecting the list in there too.
How do you want to implement this? Something like "walk the list and run a callback for the matching entries" or do you have something else in mind?
Re: [PATCH v2 2/7] acpi: utils: Add function to fetch dependent acpi_devices
Quoted 31 lines · Rafael J. Wysocki
Quoted 30 lines · Daniel Scally
Hi Rafael
Quoted 26 lines · Rafael J. Wysocki
Quoted 7 lines · Daniel Scally
Quoted 6 lines · Rafael J. Wysocki
Quoted 5 lines · Daniel Scally
In some ACPI tables we encounter, devices use the
_DEPmethod to assert a dependence on other ACPI devices as opposed to the OpRegions that the specification intends. We need to be able to find those devices "from" the dependee, so add a function to parse all ACPI Devices and check if the include the handle of the dependee device in their_DEPbuffer.Quoted 5 lines
Quoted 1 line
What exactly do you need this for?
So, in our DSDT we have devices with
_HIDINT3472, plus sensors which refer to those INT3472's in their_DEPmethod. The driver binds to the INT3472 device, we need to find the sensors dependent on them.Well, this is an interesting concept. :-)
Why does
_DEPneed to be used for that? Isn't there any other way to look up the dependent sensors?Quoted 5 lines
Quoted 4 lines
Would it be practical to look up the suppliers in
acpi_dep_listinstead?Note that supplier drivers may remove entries from there, but does that matter for your use case?
Ah - that may work, yes. Thank you, let me test that.
Even if that doesn't work right away, but it can be made work, I would very much prefer that to the driver parsing
_DEPfor every device in the namespace by itself.
Quoted 8 lines
Quoted 2 lines
This does work; do you prefer it in
scan.c, or inutils.c(in which case withacpi_dep_listdeclared as external var ininternal.h)?Let's put it in
scan.cfor now, because there is the lock protecting the list in there too.How do you want to implement this? Something like "walk the list and run a callback for the matching entries" or do you have something else in mind?
Something like this (though with a mutex_lock()). It could be simplified by dropping the prev stuff, but we have seen INT3472 devices with multiple sensors declaring themselves dependent on the same device
struct acpi_device * acpi_dev_get_next_dependent_dev(struct acpi_device *supplier, struct acpi_device *prev)
{
struct acpi_dep_data *dep;
struct acpi_device *adev;
int ret;
if (!supplier)
return ERR_PTR(-EINVAL);
if (prev) {
/*
* We need to find the previous device in the list, so we know
* where to start iterating from.
*/
list_for_each_entry(dep, &acpi_dep_list, node)
if (dep->consumer == prev->handle && dep->supplier == supplier->handle)
break;
dep = list_next_entry(dep, node);
} else {
dep = list_first_entry(&acpi_dep_list, struct acpi_dep_data, node);
}
list_for_each_entry_from(dep, &acpi_dep_list, node) { if (dep->supplier == supplier->handle) { ret = acpi_bus_get_device(dep->consumer, &adev); if (ret)
return ERR_PTR(ret);
return adev;
}
}
return NULL;
}
Rafael J. Wysocki
maintainerRe: [PATCH v2 2/7] acpi: utils: Add function to fetch dependent acpi_devices
Quoted 81 lines · Daniel Scally
Quoted 31 lines · Rafael J. Wysocki
Quoted 30 lines · Daniel Scally
Hi Rafael
Quoted 26 lines · Rafael J. Wysocki
Quoted 7 lines · Daniel Scally
Quoted 6 lines · Rafael J. Wysocki
Quoted 5 lines · Daniel Scally
In some ACPI tables we encounter, devices use the
_DEPmethod to assert a dependence on other ACPI devices as opposed to the OpRegions that the specification intends. We need to be able to find those devices "from" the dependee, so add a function to parse all ACPI Devices and check if the include the handle of the dependee device in their_DEPbuffer.Quoted 5 lines
Quoted 1 line
What exactly do you need this for?
So, in our DSDT we have devices with
_HIDINT3472, plus sensors which refer to those INT3472's in their_DEPmethod. The driver binds to the INT3472 device, we need to find the sensors dependent on them.Well, this is an interesting concept. :-)
Why does
_DEPneed to be used for that? Isn't there any other way to look up the dependent sensors?Quoted 5 lines
Quoted 4 lines
Would it be practical to look up the suppliers in
acpi_dep_listinstead?Note that supplier drivers may remove entries from there, but does that matter for your use case?
Ah - that may work, yes. Thank you, let me test that.
Even if that doesn't work right away, but it can be made work, I would very much prefer that to the driver parsing
_DEPfor every device in the namespace by itself.Quoted 8 lines
Quoted 2 lines
This does work; do you prefer it in
scan.c, or inutils.c(in which case withacpi_dep_listdeclared as external var ininternal.h)?Let's put it in
scan.cfor now, because there is the lock protecting the list in there too.How do you want to implement this? Something like "walk the list and run a callback for the matching entries" or do you have something else in mind?
Something like this (though with a
mutex_lock()). It could be simplified by dropping the prev stuff, but we have seen INT3472 devices with multiple sensors declaring themselves dependent on the same devicestruct
acpi_device* acpi_dev_get_next_dependent_dev(structacpi_device*supplier,
structacpi_device*prev){ struct acpi_dep_data *dep; struct acpi_device *adev; int ret; if (!supplier) return ERR_PTR(-EINVAL); if (prev) { /* * We need to find the previous device in the list, so we know * where to start iterating from. */ list_for_each_entry(dep, &acpi_dep_list, node) if (dep->consumer == prev->handle && dep->supplier == supplier->handle) break; dep = list_next_entry(dep, node); } else { dep = list_first_entry(&acpi_dep_list, struct acpi_dep_data, node); } list_for_each_entry_from(dep, &acpi_dep_list, node) { if (dep->supplier == supplier->handle) { ret = acpi_bus_get_device(dep->consumer, &adev); if (ret)
Quoted 8 lines
return ERR_PTR(ret);
return adev;
}
}
return NULL;
}That would work I think, but would it be practical to modify acpi_walk_dep_device_list() so that it runs a callback for every consumer found instead of or in addition to the "delete from the list and free the entry" operation?
Re: [PATCH v2 2/7] acpi: utils: Add function to fetch dependent acpi_devices
Quoted 85 lines · Rafael J. Wysocki
Quoted 84 lines · Daniel Scally
Quoted 30 lines · Rafael J. Wysocki
Quoted 29 lines · Daniel Scally
Hi Rafael
Quoted 26 lines · Rafael J. Wysocki
Quoted 7 lines · Daniel Scally
Quoted 6 lines · Rafael J. Wysocki
Quoted 5 lines · Daniel Scally
In some ACPI tables we encounter, devices use the
_DEPmethod to assert a dependence on other ACPI devices as opposed to the OpRegions that the specification intends. We need to be able to find those devices "from" the dependee, so add a function to parse all ACPI Devices and check if the include the handle of the dependee device in their_DEPbuffer.Quoted 5 lines
Quoted 1 line
What exactly do you need this for?
So, in our DSDT we have devices with
_HIDINT3472, plus sensors which refer to those INT3472's in their_DEPmethod. The driver binds to the INT3472 device, we need to find the sensors dependent on them.Well, this is an interesting concept. :-)
Why does
_DEPneed to be used for that? Isn't there any other way to look up the dependent sensors?Quoted 5 lines
Quoted 4 lines
Would it be practical to look up the suppliers in
acpi_dep_listinstead?Note that supplier drivers may remove entries from there, but does that matter for your use case?
Ah - that may work, yes. Thank you, let me test that.
Even if that doesn't work right away, but it can be made work, I would very much prefer that to the driver parsing
_DEPfor every device in the namespace by itself.Quoted 8 lines
Quoted 2 lines
This does work; do you prefer it in
scan.c, or inutils.c(in which case withacpi_dep_listdeclared as external var ininternal.h)?Let's put it in
scan.cfor now, because there is the lock protecting the list in there too.How do you want to implement this? Something like "walk the list and run a callback for the matching entries" or do you have something else in mind?
Something like this (though with a
mutex_lock()). It could be simplified by dropping the prev stuff, but we have seen INT3472 devices with multiple sensors declaring themselves dependent on the same devicestruct
acpi_device* acpi_dev_get_next_dependent_dev(structacpi_device*supplier,
structacpi_device*prev){ struct acpi_dep_data *dep; struct acpi_device *adev; int ret; if (!supplier) return ERR_PTR(-EINVAL); if (prev) { /* * We need to find the previous device in the list, so we know * where to start iterating from. */ list_for_each_entry(dep, &acpi_dep_list, node) if (dep->consumer == prev->handle && dep->supplier == supplier->handle) break; dep = list_next_entry(dep, node); } else { dep = list_first_entry(&acpi_dep_list, struct acpi_dep_data, node); } list_for_each_entry_from(dep, &acpi_dep_list, node) { if (dep->supplier == supplier->handle) { ret = acpi_bus_get_device(dep->consumer, &adev); if (ret) return ERR_PTR(ret); return adev; } }
Quoted 6 lines
Quoted 2 lines
return NULL; }That would work I think, but would it be practical to modify
acpi_walk_dep_device_list()so that it runs a callback for every consumer found instead of or in addition to the "delete from the list and free the entry" operation?
I think that this would work fine, if that's the way you want to go. We'd just need to move everything inside the if (dep->supplier == handle) block to a new callback, and for my purposes I think also add a way to stop parsing the list from the callback (so like have the callbacks return int and stop parsing on a non-zero return). Do you want to expose that ability to pass a callback outside of ACPI? Or just export helpers to call each of the callbacks (one to fetch the next dependent device, one to decrement the unmet dependencies counter)
Otherwise, I'd just need to update the 5 users of that function either to use the new helper or else to also pass the decrement dependencies callback.
Rafael J. Wysocki
maintainerRe: [PATCH v2 2/7] acpi: utils: Add function to fetch dependent acpi_devices
Quoted 96 lines · Daniel Scally
Quoted 85 lines · Rafael J. Wysocki
Quoted 84 lines · Daniel Scally
Quoted 30 lines · Rafael J. Wysocki
Quoted 29 lines · Daniel Scally
Hi Rafael
Quoted 26 lines · Rafael J. Wysocki
Quoted 7 lines · Daniel Scally
Quoted 6 lines · Rafael J. Wysocki
Quoted 5 lines · Daniel Scally
In some ACPI tables we encounter, devices use the
_DEPmethod to assert a dependence on other ACPI devices as opposed to the OpRegions that the specification intends. We need to be able to find those devices "from" the dependee, so add a function to parse all ACPI Devices and check if the include the handle of the dependee device in their_DEPbuffer.Quoted 5 lines
Quoted 1 line
What exactly do you need this for?
So, in our DSDT we have devices with
_HIDINT3472, plus sensors which refer to those INT3472's in their_DEPmethod. The driver binds to the INT3472 device, we need to find the sensors dependent on them.Well, this is an interesting concept. :-)
Why does
_DEPneed to be used for that? Isn't there any other way to look up the dependent sensors?Quoted 5 lines
Quoted 4 lines
Would it be practical to look up the suppliers in
acpi_dep_listinstead?Note that supplier drivers may remove entries from there, but does that matter for your use case?
Ah - that may work, yes. Thank you, let me test that.
Even if that doesn't work right away, but it can be made work, I would very much prefer that to the driver parsing
_DEPfor every device in the namespace by itself.Quoted 8 lines
Quoted 2 lines
This does work; do you prefer it in
scan.c, or inutils.c(in which case withacpi_dep_listdeclared as external var ininternal.h)?Let's put it in
scan.cfor now, because there is the lock protecting the list in there too.How do you want to implement this? Something like "walk the list and run a callback for the matching entries" or do you have something else in mind?
Something like this (though with a
mutex_lock()). It could be simplified by dropping the prev stuff, but we have seen INT3472 devices with multiple sensors declaring themselves dependent on the same devicestruct
acpi_device* acpi_dev_get_next_dependent_dev(structacpi_device*supplier,
structacpi_device*prev){ struct acpi_dep_data *dep; struct acpi_device *adev; int ret; if (!supplier) return ERR_PTR(-EINVAL); if (prev) { /* * We need to find the previous device in the list, so we know * where to start iterating from. */ list_for_each_entry(dep, &acpi_dep_list, node) if (dep->consumer == prev->handle && dep->supplier == supplier->handle) break; dep = list_next_entry(dep, node); } else { dep = list_first_entry(&acpi_dep_list, struct acpi_dep_data, node); } list_for_each_entry_from(dep, &acpi_dep_list, node) { if (dep->supplier == supplier->handle) { ret = acpi_bus_get_device(dep->consumer, &adev); if (ret) return ERR_PTR(ret); return adev; } }Quoted 6 lines
Quoted 2 lines
return NULL; }That would work I think, but would it be practical to modify
acpi_walk_dep_device_list()so that it runs a callback for every consumer found instead of or in addition to the "delete from the list and free the entry" operation?
Quoted 6 lines
I think that this would work fine, if that's the way you want to go. We'd just need to move everything inside the if (
dep->supplier== handle) block to a new callback, and for my purposes I think also add a way to stop parsing the list from the callback (so like have the callbacks return int and stop parsing on a non-zero return). Do you want to expose that ability to pass a callback outside of ACPI?
Yes.
Quoted 2 lines
Or just export helpers to call each of the callbacks (one to fetch the next dependent device, one to decrement the unmet dependencies counter)
If you can run a callback for every matching entry, you don't really need to have a callback to return the next matching entry. You can do stuff for all of them in one go (note that it probably is not a good idea to run the callback under the lock, so the for loop currently in there is not really suitable for that).
Quoted 3 lines
Otherwise, I'd just need to update the 5 users of that function either to use the new helper or else to also pass the decrement dependencies callback.
Or have a wrapper around it passing the decrement dependencies callback for the "typical" users.
Re: [PATCH v2 2/7] acpi: utils: Add function to fetch dependent acpi_devices
Quoted 99 lines · Rafael J. Wysocki
Quoted 92 lines · Daniel Scally
Quoted 83 lines · Rafael J. Wysocki
Quoted 82 lines · Daniel Scally
Quoted 30 lines · Rafael J. Wysocki
Quoted 29 lines · Daniel Scally
Hi Rafael
Quoted 26 lines · Rafael J. Wysocki
Quoted 7 lines · Daniel Scally
Quoted 6 lines · Rafael J. Wysocki
Quoted 5 lines · Daniel Scally
In some ACPI tables we encounter, devices use the
_DEPmethod to assert a dependence on other ACPI devices as opposed to the OpRegions that the specification intends. We need to be able to find those devices "from" the dependee, so add a function to parse all ACPI Devices and check if the include the handle of the dependee device in their_DEPbuffer.Quoted 5 lines
Quoted 1 line
What exactly do you need this for?
So, in our DSDT we have devices with
_HIDINT3472, plus sensors which refer to those INT3472's in their_DEPmethod. The driver binds to the INT3472 device, we need to find the sensors dependent on them.Well, this is an interesting concept. :-)
Why does
_DEPneed to be used for that? Isn't there any other way to look up the dependent sensors?Quoted 5 lines
Quoted 4 lines
Would it be practical to look up the suppliers in
acpi_dep_listinstead?Note that supplier drivers may remove entries from there, but does that matter for your use case?
Ah - that may work, yes. Thank you, let me test that.
Even if that doesn't work right away, but it can be made work, I would very much prefer that to the driver parsing
_DEPfor every device in the namespace by itself.Quoted 8 lines
Quoted 2 lines
This does work; do you prefer it in
scan.c, or inutils.c(in which case withacpi_dep_listdeclared as external var ininternal.h)?Let's put it in
scan.cfor now, because there is the lock protecting the list in there too.How do you want to implement this? Something like "walk the list and run a callback for the matching entries" or do you have something else in mind?
Something like this (though with a
mutex_lock()). It could be simplified by dropping the prev stuff, but we have seen INT3472 devices with multiple sensors declaring themselves dependent on the same devicestruct
acpi_device* acpi_dev_get_next_dependent_dev(structacpi_device*supplier,
structacpi_device*prev){ struct acpi_dep_data *dep; struct acpi_device *adev; int ret; if (!supplier) return ERR_PTR(-EINVAL); if (prev) { /* * We need to find the previous device in the list, so we know * where to start iterating from. */ list_for_each_entry(dep, &acpi_dep_list, node) if (dep->consumer == prev->handle && dep->supplier == supplier->handle) break; dep = list_next_entry(dep, node); } else { dep = list_first_entry(&acpi_dep_list, struct acpi_dep_data, node); } list_for_each_entry_from(dep, &acpi_dep_list, node) { if (dep->supplier == supplier->handle) { ret = acpi_bus_get_device(dep->consumer, &adev); if (ret) return ERR_PTR(ret); return adev; } }Quoted 6 lines
Quoted 2 lines
return NULL; }That would work I think, but would it be practical to modify
acpi_walk_dep_device_list()so that it runs a callback for every consumer found instead of or in addition to the "delete from the list and free the entry" operation?Quoted 6 lines
I think that this would work fine, if that's the way you want to go. We'd just need to move everything inside the if (
dep->supplier== handle) block to a new callback, and for my purposes I think also add a way to stop parsing the list from the callback (so like have the callbacks return int and stop parsing on a non-zero return). Do you want to expose that ability to pass a callback outside of ACPI?
Quoted 7 lines
Yes.
Quoted 2 lines
Or just export helpers to call each of the callbacks (one to fetch the next dependent device, one to decrement the unmet dependencies counter)
If you can run a callback for every matching entry, you don't really need to have a callback to return the next matching entry. You can do stuff for all of them in one go
Well it my case it's more to return a pointer to the dep->consumer's acpi_device for a matching entry, so my idea was where there's multiple dependents you could use this as an iterator...but it could just be extended to that if needed later; I don't actually need to do it right now.
Quoted 3 lines
note that it probably is not a good
idea to run the callback under the lock, so the for loop currently in there is not really suitable for that
No problem; I'll tweak that then
Quoted 5 lines
Quoted 3 lines
Otherwise, I'd just need to update the 5 users of that function either to use the new helper or else to also pass the decrement dependencies callback.
Or have a wrapper around it passing the decrement dependencies callback for the "typical" users.
Yeah that's what I mean by helper; I'll do that then; thanks
Re: [PATCH v2 2/7] acpi: utils: Add function to fetch dependent acpi_devices
Hi Rafael
Quoted 115 lines · Daniel Scally
Quoted 99 lines · Rafael J. Wysocki
Quoted 92 lines · Daniel Scally
Quoted 83 lines · Rafael J. Wysocki
Quoted 82 lines · Daniel Scally
Quoted 30 lines · Rafael J. Wysocki
Quoted 29 lines · Daniel Scally
Hi Rafael
Quoted 26 lines · Rafael J. Wysocki
Quoted 7 lines · Daniel Scally
Quoted 6 lines · Rafael J. Wysocki
Quoted 5 lines · Daniel Scally
In some ACPI tables we encounter, devices use the
_DEPmethod to assert a dependence on other ACPI devices as opposed to the OpRegions that the specification intends. We need to be able to find those devices "from" the dependee, so add a function to parse all ACPI Devices and check if the include the handle of the dependee device in their_DEPbuffer.Quoted 5 lines
Quoted 1 line
What exactly do you need this for?
So, in our DSDT we have devices with
_HIDINT3472, plus sensors which refer to those INT3472's in their_DEPmethod. The driver binds to the INT3472 device, we need to find the sensors dependent on them.Well, this is an interesting concept. :-)
Why does
_DEPneed to be used for that? Isn't there any other way to look up the dependent sensors?Quoted 5 lines
Quoted 4 lines
Would it be practical to look up the suppliers in
acpi_dep_listinstead?Note that supplier drivers may remove entries from there, but does that matter for your use case?
Ah - that may work, yes. Thank you, let me test that.
Even if that doesn't work right away, but it can be made work, I would very much prefer that to the driver parsing
_DEPfor every device in the namespace by itself.Quoted 8 lines
Quoted 2 lines
This does work; do you prefer it in
scan.c, or inutils.c(in which case withacpi_dep_listdeclared as external var ininternal.h)?Let's put it in
scan.cfor now, because there is the lock protecting the list in there too.How do you want to implement this? Something like "walk the list and run a callback for the matching entries" or do you have something else in mind?
Something like this (though with a
mutex_lock()). It could be simplified by dropping the prev stuff, but we have seen INT3472 devices with multiple sensors declaring themselves dependent on the same devicestruct
acpi_device* acpi_dev_get_next_dependent_dev(structacpi_device*supplier,
structacpi_device*prev){ struct acpi_dep_data *dep; struct acpi_device *adev; int ret; if (!supplier) return ERR_PTR(-EINVAL); if (prev) { /* * We need to find the previous device in the list, so we know * where to start iterating from. */ list_for_each_entry(dep, &acpi_dep_list, node) if (dep->consumer == prev->handle && dep->supplier == supplier->handle) break; dep = list_next_entry(dep, node); } else { dep = list_first_entry(&acpi_dep_list, struct acpi_dep_data, node); } list_for_each_entry_from(dep, &acpi_dep_list, node) { if (dep->supplier == supplier->handle) { ret = acpi_bus_get_device(dep->consumer, &adev); if (ret) return ERR_PTR(ret); return adev; } }Quoted 6 lines
Quoted 2 lines
return NULL; }That would work I think, but would it be practical to modify
acpi_walk_dep_device_list()so that it runs a callback for every consumer found instead of or in addition to the "delete from the list and free the entry" operation?Quoted 6 lines
I think that this would work fine, if that's the way you want to go. We'd just need to move everything inside the if (
dep->supplier== handle) block to a new callback, and for my purposes I think also add a way to stop parsing the list from the callback (so like have the callbacks return int and stop parsing on a non-zero return). Do you want to expose that ability to pass a callback outside of ACPI?Quoted 7 lines
Yes.
Quoted 2 lines
Or just export helpers to call each of the callbacks (one to fetch the next dependent device, one to decrement the unmet dependencies counter)
If you can run a callback for every matching entry, you don't really need to have a callback to return the next matching entry. You can do stuff for all of them in one go
Well it my case it's more to return a pointer to the dep->consumer's
acpi_devicefor a matching entry, so my idea was where there's multiple dependents you could use this as an iterator...but it could just be extended to that if needed later; I don't actually need to do it right now.
Quoted 5 lines
Quoted 3 lines
note that it probably is not a good
idea to run the callback under the lock, so the for loop currently in there is not really suitable for thatNo problem; I'll tweak that then
Slightly walking back my "No problem" here; as I understand this there's kinda two options:
1. Walk over the (locked) list, when a match is found unlock, run the callback and re-lock.
The problem with that idea is unless I'm mistaken there's no guarantee that the .next pointer is still valid then (even using the *_safe() methods) because either the next or the next + 1 entry could have been removed whilst the list was unlocked and the callback was being ran, so this seems a little unsafe.
2. Walk over the (locked) list twice, the first time counting matching entries and using that to allocate a temporary buffer, then walk again to store the matching entries into the buffer. Finally, run the callback for everything in the buffer, free it and return.
Obviously that's a lot less efficient than the current function, which isn't particularly palatable.
Apologies if I've missed a better option that would work fine; but failing that do you still want me to go ahead and change acpi_walk_dep_device_list() to do this (I'd choose #2 of the above), or fallback to using acpi_dev_get_next_dependent_dev() described above? If the latter, does acpi_walk_dep_device_list() maybe need re-naming to make clear it's not a generalised function?
Re: [PATCH v2 2/7] acpi: utils: Add function to fetch dependent acpi_devices
Quoted 2 lines · Daniel Scally
Quoted 1 line · Daniel Scally
On 21/01/2021 18:08, Rafael J. Wysocki wrote:
...
Quoted 5 lines
Quoted 1 line
No problem; I'll tweak that then
Slightly walking back my "No problem" here; as I understand this there's kinda two options:
Quoted 8 lines
1. Walk over the (locked) list, when a match is found unlock, run the callback and re-lock.
The problem with that idea is unless I'm mistaken there's no guarantee that the .next pointer is still valid then (even using the
*_safe()methods) because either the next or the next + 1 entry could have been removed whilst the list was unlocked and the callback was being ran, so this seems a little unsafe.
It's easy to solve.
See an example in deferred_probe_work_func().
https://elixir.bootlin.com/linux/latest/source/drivers/base/dd.c#L75
Quoted 14 lines
2. Walk over the (locked) list twice, the first time counting matching entries and using that to allocate a temporary buffer, then walk again to store the matching entries into the buffer. Finally, run the callback for everything in the buffer, free it and return.
Obviously that's a lot less efficient than the current function, which isn't particularly palatable.
Apologies if I've missed a better option that would work fine; but failing that do you still want me to go ahead and change
acpi_walk_dep_device_list()to do this (I'd choose #2 of the above), or fallback to usingacpi_dev_get_next_dependent_dev()described above? If the latter, doesacpi_walk_dep_device_list()maybe need re-naming to make clear it's not a generalised function?
Signature · 2 lines
With Best Regards, Andy Shevchenko
Rafael J. Wysocki
maintainerRe: [PATCH v2 2/7] acpi: utils: Add function to fetch dependent acpi_devices
In reply to Daniel ScallyQuoted 123 lines · Daniel Scally
Hi Rafael
Quoted 119 lines · Daniel Scally
Quoted 99 lines · Rafael J. Wysocki
Quoted 92 lines · Daniel Scally
Quoted 83 lines · Rafael J. Wysocki
Quoted 82 lines · Daniel Scally
Quoted 30 lines · Rafael J. Wysocki
Quoted 29 lines · Daniel Scally
Hi Rafael
Quoted 26 lines · Rafael J. Wysocki
Quoted 7 lines · Daniel Scally
Quoted 6 lines · Rafael J. Wysocki
Quoted 5 lines · Daniel Scally
In some ACPI tables we encounter, devices use the
_DEPmethod to assert a dependence on other ACPI devices as opposed to the OpRegions that the specification intends. We need to be able to find those devices "from" the dependee, so add a function to parse all ACPI Devices and check if the include the handle of the dependee device in their_DEPbuffer.Quoted 5 lines
Quoted 1 line
What exactly do you need this for?
So, in our DSDT we have devices with
_HIDINT3472, plus sensors which refer to those INT3472's in their_DEPmethod. The driver binds to the INT3472 device, we need to find the sensors dependent on them.Well, this is an interesting concept. :-)
Why does
_DEPneed to be used for that? Isn't there any other way to look up the dependent sensors?Quoted 5 lines
Quoted 4 lines
Would it be practical to look up the suppliers in
acpi_dep_listinstead?Note that supplier drivers may remove entries from there, but does that matter for your use case?
Ah - that may work, yes. Thank you, let me test that.
Even if that doesn't work right away, but it can be made work, I would very much prefer that to the driver parsing
_DEPfor every device in the namespace by itself.Quoted 8 lines
Quoted 2 lines
This does work; do you prefer it in
scan.c, or inutils.c(in which case withacpi_dep_listdeclared as external var ininternal.h)?Let's put it in
scan.cfor now, because there is the lock protecting the list in there too.How do you want to implement this? Something like "walk the list and run a callback for the matching entries" or do you have something else in mind?
Something like this (though with a
mutex_lock()). It could be simplified by dropping the prev stuff, but we have seen INT3472 devices with multiple sensors declaring themselves dependent on the same devicestruct
acpi_device* acpi_dev_get_next_dependent_dev(structacpi_device*supplier,
structacpi_device*prev){ struct acpi_dep_data *dep; struct acpi_device *adev; int ret; if (!supplier) return ERR_PTR(-EINVAL); if (prev) { /* * We need to find the previous device in the list, so we know * where to start iterating from. */ list_for_each_entry(dep, &acpi_dep_list, node) if (dep->consumer == prev->handle && dep->supplier == supplier->handle) break; dep = list_next_entry(dep, node); } else { dep = list_first_entry(&acpi_dep_list, struct acpi_dep_data, node); } list_for_each_entry_from(dep, &acpi_dep_list, node) { if (dep->supplier == supplier->handle) { ret = acpi_bus_get_device(dep->consumer, &adev); if (ret) return ERR_PTR(ret); return adev; } }Quoted 6 lines
Quoted 2 lines
return NULL; }That would work I think, but would it be practical to modify
acpi_walk_dep_device_list()so that it runs a callback for every consumer found instead of or in addition to the "delete from the list and free the entry" operation?Quoted 6 lines
I think that this would work fine, if that's the way you want to go. We'd just need to move everything inside the if (
dep->supplier== handle) block to a new callback, and for my purposes I think also add a way to stop parsing the list from the callback (so like have the callbacks return int and stop parsing on a non-zero return). Do you want to expose that ability to pass a callback outside of ACPI?Quoted 7 lines
Yes.
Quoted 2 lines
Or just export helpers to call each of the callbacks (one to fetch the next dependent device, one to decrement the unmet dependencies counter)
If you can run a callback for every matching entry, you don't really need to have a callback to return the next matching entry. You can do stuff for all of them in one go
Well it my case it's more to return a pointer to the dep->consumer's
acpi_devicefor a matching entry, so my idea was where there's multiple dependents you could use this as an iterator...but it could just be extended to that if needed later; I don't actually need to do it right now.Quoted 3 lines
note that it probably is not a good
idea to run the callback under the lock, so the for loop currently in there is not really suitable for that
Quoted 7 lines
Quoted 1 line
No problem; I'll tweak that then
Slightly walking back my "No problem" here; as I understand this there's kinda two options:
1. Walk over the (locked) list, when a match is found unlock, run the callback and re-lock.
That's what I was thinking about.
Quoted 5 lines
The problem with that idea is unless I'm mistaken there's no guarantee that the .next pointer is still valid then (even using the
*_safe()methods) because either the next or the next + 1 entry could have been removed whilst the list was unlocked and the callback was being ran, so this seems a little unsafe.
This can be addressed by rotating the list while walking it, but that becomes problematic if there are concurrent walkers.
OK, I guess running the callback under the lock is not really a big deal (and for the deletion case this is actually necessary), so let's do that.
PATCH v2 3/7 i2c: i2c-core-base: Use format macro in i2c_dev_set_name()
In reply to Daniel ScallySome places in the kernel allow users to map resources to a device using device name (for example, gpiod_lookup_table). Currently this involves waiting for the i2c_client to have been registered so we can use dev_name(&client->dev). We want to add a function to allow users to refer to an i2c device by name before it has been instantiated, so create a macro for the format that's accessible outside the i2c layer and use it in i2c_dev_set_name()
---
- Used format macro in i2c_dev_set_name() instead of sub func
drivers/i2c/i2c-core-base.c | 4 ++-- include/linux/i2c.h | 3 +++ 2 files changed, 5 insertions(+), 2 deletions(-)
drivers/i2c/i2c-core-base.c +2 -2
@@ -811,12 +811,12 @@ static void i2c_dev_set_name(struct i2c_adapter *adap,struct acpi_device *adev =ACPI_COMPANION (&client->dev);if (info && info->dev_name) { -dev_set_name (&client->dev,"i2c-%s" , info->dev_name); +dev_set_name (&client->dev,I2C_DEV_NAME_FORMAT , info->dev_name);return ; }if (adev) { -dev_set_name (&client->dev,"i2c-%s" ,acpi_dev_name (adev)); +dev_set_name (&client->dev,I2C_DEV_NAME_FORMAT ,acpi_dev_name (adev));return ; }
include/linux/i2c.h +3 -0
@@ -39,6 +39,9 @@ enum i2c_slave_event;typedef int (*i2c_slave_cb_t )(struct i2c_client *client,enum i2c_slave_event event,u8 *val); +/* I2C Device Name Format - to maintain consistency outside the i2c layer */ +#define I2C_DEV_NAME_FORMAT "i2c-%s" +/* I2C Frequency Modes */ #define I2C_MAX_STANDARD_MODE_FREQ 100000#define I2C_MAX_FAST_MODE_FREQ 400000
Signature · 1 line
2.25.1
Re: [PATCH v2 3/7] i2c: i2c-core-base: Use format macro in i2c_dev_set_name()
Hi Daniel,
Thank you for the patch.
Quoted 10 lines · Daniel Scally
Some places in the kernel allow users to map resources to a device using device name (for example,
gpiod_lookup_table). Currently this involves waiting for thei2c_clientto have been registered so we can usedev_name(&client->dev). We want to add a function to allow users to refer to an i2c device by name before it has been instantiated, so create a macro for the format that's accessible outside the i2c layer and use it ini2c_dev_set_name()Suggested-by Andy Shevchenko <[email protected]>Signed-off-by Daniel Scally <[email protected]>
I'd change the subject line to say "Add a format macro for I2C device names", as that's the most important part of the patch. Apart from that,
Quoted 40 lines
---
- Used format macro ini2c_dev_set_name()instead of sub funcdrivers/i2c/i2c-core-base.c | 4 ++-- include/linux/i2c.h | 3 +++ 2 files changed, 5 insertions(+), 2 deletions(-)drivers/i2c/i2c-core-base.c +2
-2@@ -811,12 +811,12 @@ static void i2c_dev_set_name(struct i2c_adapter *adap,struct acpi_device *adev =ACPI_COMPANION (&client->dev);if (info && info->dev_name) { -dev_set_name (&client->dev,"i2c-%s" , info->dev_name); +dev_set_name (&client->dev,I2C_DEV_NAME_FORMAT , info->dev_name);return ; }if (adev) { -dev_set_name (&client->dev,"i2c-%s" ,acpi_dev_name (adev)); +dev_set_name (&client->dev,I2C_DEV_NAME_FORMAT ,acpi_dev_name (adev));return ; }include/linux/i2c.h +3
-0@@ -39,6 +39,9 @@ enum i2c_slave_event;typedef int (*i2c_slave_cb_t )(struct i2c_client *client,enum i2c_slave_event event,u8 *val); +/* I2C Device Name Format - to maintain consistency outside the i2c layer */ +#define I2C_DEV_NAME_FORMAT "i2c-%s" +/* I2C Frequency Modes */ #define I2C_MAX_STANDARD_MODE_FREQ 100000#define I2C_MAX_FAST_MODE_FREQ 400000
Signature · 3 lines
Regards, Laurent Pinchart
Re: [PATCH v2 3/7] i2c: i2c-core-base: Use format macro in i2c_dev_set_name()
Quoted 4 lines · Laurent Pinchart
On Mon, Jan 18, 2021 at 12:34:24AM +0000, Daniel Scally wrote:
I'd change the subject line to say "Add a format macro for I2C device names", as that's the most important part of the patch. Apart from that,
Actually prefix can be "i2c: core: ".
Hint: look at the git history to find what was lately used mostly.
% git log --oneline -- drivers/i2c/i2c-*
Signature · 2 lines
With Best Regards, Andy Shevchenko
Re: [PATCH v2 3/7] i2c: i2c-core-base: Use format macro in i2c_dev_set_name()
In reply to Daniel ScallyHi Daniel,
Quoted 23 lines · Daniel Scally
Some places in the kernel allow users to map resources to a device using device name (for example,
gpiod_lookup_table). Currently this involves waiting for thei2c_clientto have been registered so we can usedev_name(&client->dev). We want to add a function to allow users to refer to an i2c device by name before it has been instantiated, so create a macro for the format that's accessible outside the i2c layer and use it ini2c_dev_set_name()Suggested-by Andy Shevchenko <[email protected]>Signed-off-by Daniel Scally <[email protected]>---
- Used format macro ini2c_dev_set_name()instead of sub funcdrivers/i2c/i2c-core-base.c | 4 ++-- include/linux/i2c.h | 3 +++ 2 files changed, 5 insertions(+), 2 deletions(-)drivers/i2c/i2c-core-base.c +0
-0@@ -811,12 +811,12 @@ static void i2c_dev_set_name(struct i2c_adapter *adap,struct acpi_device *adev =ACPI_COMPANION (&client->dev);
drivers/i2c/i2c-core-base.c static void i2c_dev_set_name(struct i2c_adapter *adap, · line 819
Quoted 10 lines
drivers/i2c/i2c-core-base.c +2
-2if (info && info->dev_name) { -dev_set_name (&client->dev,"i2c-%s" , info->dev_name); +dev_set_name (&client->dev,I2C_DEV_NAME_FORMAT , info->dev_name);return ; }if (adev) { -dev_set_name (&client->dev,"i2c-%s" ,acpi_dev_name (adev)); +dev_set_name (&client->dev,I2C_DEV_NAME_FORMAT ,acpi_dev_name (adev));
Over 80, please wrap.
With that,
Quoted 20 lines
drivers/i2c/i2c-core-base.c +0
-0return ; }include/linux/i2c.h +3
-0@@ -39,6 +39,9 @@ enum i2c_slave_event;typedef int (*i2c_slave_cb_t )(struct i2c_client *client,enum i2c_slave_event event,u8 *val); +/* I2C Device Name Format - to maintain consistency outside the i2c layer */ +#define I2C_DEV_NAME_FORMAT "i2c-%s" +/* I2C Frequency Modes */ #define I2C_MAX_STANDARD_MODE_FREQ 100000#define I2C_MAX_FAST_MODE_FREQ 400000Signature · 1 line
2.25.1
Signature · 1 line
Sakari Ailus
Re: [PATCH v2 3/7] i2c: i2c-core-base: Use format macro in i2c_dev_set_name()
Quoted 6 lines
drivers/i2c/i2c-core-base.c static void i2c_dev_set_name(struct i2c_adapter *adap, · line 819
Quoted 4 lines
drivers/i2c/i2c-core-base.c +1
-1if (adev) { -dev_set_name (&client->dev,"i2c-%s" ,acpi_dev_name (adev)); +dev_set_name (&client->dev,I2C_DEV_NAME_FORMAT ,acpi_dev_name (adev));Over 80, please wrap.
I am not that strict with the 80, and I don't think it will improve readability here. It can stay this time IMO.
Sakari Ailus
Reviewed-byRe: [PATCH v2 3/7] i2c: i2c-core-base: Use format macro in i2c_dev_set_name()
In reply to Sakari AilusQuoted 39 lines · Sakari Ailus
Hi Daniel,
Quoted 23 lines · Daniel Scally
Some places in the kernel allow users to map resources to a device using device name (for example,
gpiod_lookup_table). Currently this involves waiting for thei2c_clientto have been registered so we can usedev_name(&client->dev). We want to add a function to allow users to refer to an i2c device by name before it has been instantiated, so create a macro for the format that's accessible outside the i2c layer and use it ini2c_dev_set_name()Suggested-by Andy Shevchenko <[email protected]>Signed-off-by Daniel Scally <[email protected]>---
- Used format macro ini2c_dev_set_name()instead of sub funcdrivers/i2c/i2c-core-base.c | 4 ++-- include/linux/i2c.h | 3 +++ 2 files changed, 5 insertions(+), 2 deletions(-)drivers/i2c/i2c-core-base.c +0
-0@@ -811,12 +811,12 @@ static void i2c_dev_set_name(struct i2c_adapter *adap,struct acpi_device *adev =ACPI_COMPANION (&client->dev);drivers/i2c/i2c-core-base.c static void i2c_dev_set_name(struct i2c_adapter *adap, · line 819
Quoted 10 lines
drivers/i2c/i2c-core-base.c +2
-2if (info && info->dev_name) { -dev_set_name (&client->dev,"i2c-%s" , info->dev_name); +dev_set_name (&client->dev,I2C_DEV_NAME_FORMAT , info->dev_name);return ; }if (adev) { -dev_set_name (&client->dev,"i2c-%s" ,acpi_dev_name (adev)); +dev_set_name (&client->dev,I2C_DEV_NAME_FORMAT ,acpi_dev_name (adev));Over 80, please wrap.
Quoted 3 lines
With that,
Acked-by Sakari Ailus <[email protected]>
Or rather:
Quoted 24 lines
Quoted 21 lines
drivers/i2c/i2c-core-base.c +0
-0return ; }include/linux/i2c.h +3
-0@@ -39,6 +39,9 @@ enum i2c_slave_event;typedef int (*i2c_slave_cb_t )(struct i2c_client *client,enum i2c_slave_event event,u8 *val); +/* I2C Device Name Format - to maintain consistency outside the i2c layer */ +#define I2C_DEV_NAME_FORMAT "i2c-%s" +/* I2C Frequency Modes */ #define I2C_MAX_STANDARD_MODE_FREQ 100000#define I2C_MAX_FAST_MODE_FREQ 400000Signature · 1 line
2.25.1Signature · 1 line
Sakari Ailus
Signature · 1 line
Sakari Ailus
Re: [PATCH v2 3/7] i2c: i2c-core-base: Use format macro in i2c_dev_set_name()
In reply to Daniel ScallyQuoted 2 lines · Daniel Scally
Some places in the kernel allow users to map resources to a device using device name (for example,
gpiod_lookup_table). Currently
"...in the struct gpiod_lookup_table)." ?
Quoted 1 line
this involves waiting for the
i2c_clientto have been registered so we
I²C client ?
Quoted 2 lines
can use
dev_name(&client->dev). We want to add a function to allow users to refer to an i2c device by name before it has been instantiated, so
I²C device ?
Quoted 1 line
create a macro for the format that's accessible outside the i2c layer
I²C layer ?
Quoted 1 line
and use it in
i2c_dev_set_name()
Period at the end.
For the record, I do not like wrapping below to 80 limit and agree with Wolfram.
Quoted 45 lines
Suggested-by Andy Shevchenko <[email protected]>Signed-off-by Daniel Scally <[email protected]>---
- Used format macro ini2c_dev_set_name()instead of sub funcdrivers/i2c/i2c-core-base.c | 4 ++-- include/linux/i2c.h | 3 +++ 2 files changed, 5 insertions(+), 2 deletions(-)drivers/i2c/i2c-core-base.c +2
-2@@ -811,12 +811,12 @@ static void i2c_dev_set_name(struct i2c_adapter *adap,struct acpi_device *adev =ACPI_COMPANION (&client->dev);if (info && info->dev_name) { -dev_set_name (&client->dev,"i2c-%s" , info->dev_name); +dev_set_name (&client->dev,I2C_DEV_NAME_FORMAT , info->dev_name);return ; }if (adev) { -dev_set_name (&client->dev,"i2c-%s" ,acpi_dev_name (adev)); +dev_set_name (&client->dev,I2C_DEV_NAME_FORMAT ,acpi_dev_name (adev));return ; }include/linux/i2c.h +3
-0@@ -39,6 +39,9 @@ enum i2c_slave_event;typedef int (*i2c_slave_cb_t )(struct i2c_client *client,enum i2c_slave_event event,u8 *val); +/* I2C Device Name Format - to maintain consistency outside the i2c layer */ +#define I2C_DEV_NAME_FORMAT "i2c-%s" +/* I2C Frequency Modes */ #define I2C_MAX_STANDARD_MODE_FREQ 100000#define I2C_MAX_FAST_MODE_FREQ 400000Signature · 1 line
2.25.1
Signature · 2 lines
With Best Regards, Andy Shevchenko
PATCH v2 4/7 i2c: i2c-core-acpi: Add i2c_acpi_dev_name()
In reply to Daniel ScallyWe want to refer to an i2c device by name before it has been created by the kernel; add a function that constructs the name from the acpi device instead.
---
Changes in v2:
- Stopped using devm_kasprintf()
drivers/i2c/i2c-core-acpi.c | 16 ++++++++++++++++ include/linux/i2c.h | 5 +++++ 2 files changed, 21 insertions(+)
drivers/i2c/i2c-core-acpi.c +16 -0
@@ -497,6 +497,22 @@ struct i2c_client *i2c_acpi_new_device(struct device *dev, int index, }EXPORT_SYMBOL_GPL (i2c_acpi_new_device); +/** +* i2c_acpi_dev_name - Construct i2c device name for devs sourced from ACPI +* @adev: ACPI device to construct the name for +* +* Constructs the name of an i2c device matching the format used by +* i2c_dev_set_name() to allow users to refer to an i2c device by name even +* before they have been instantiated. +* +* The caller is responsible for freeing the returned pointer. +*/ +char *i2c_acpi_dev_name (struct acpi_device *adev) +{ +return kasprintf (GFP_KERNEL ,I2C_DEV_NAME_FORMAT ,acpi_dev_name (adev)); +} +EXPORT_SYMBOL_GPL (i2c_acpi_dev_name); +#ifdef CONFIG_ACPI_I2C_OPREGION static int acpi_gsb_i2c_read_bytes (struct i2c_client *client,u8 cmd,u8 *data,u8 data_len)
include/linux/i2c.h +5 -0
@@ -998,6 +998,7 @@ bool i2c_acpi_get_i2c_resource(struct acpi_resource *ares,u32 i2c_acpi_find_bus_speed (struct device *dev);struct i2c_client *i2c_acpi_new_device (struct device *dev,int index,struct i2c_board_info *info); +char *i2c_acpi_dev_name (struct acpi_device *adev);struct i2c_adapter *i2c_acpi_find_adapter_by_handle (acpi_handle handle);#else static inline bool i2c_acpi_get_i2c_resource(struct acpi_resource *ares,
@@ -1014,6 +1015,10 @@ static inline struct i2c_client *i2c_acpi_new_device(struct device *dev, {return ERR_PTR (-ENODEV ); } +static inline char *i2c_acpi_dev_name (struct acpi_device *adev) +{ +return NULL ; +}static inline struct i2c_adapter *i2c_acpi_find_adapter_by_handle (acpi_handle handle) {return NULL ;
Signature · 1 line
2.25.1
Re: [PATCH v2 4/7] i2c: i2c-core-acpi: Add i2c_acpi_dev_name()
Hi Daniel,
Thank you for the patch.
Quoted 1 line · Daniel Scally
We want to refer to an i2c device by name before it has been
s/i2c device/acpi i2c device/ ?
Quoted 24 lines
created by the kernel; add a function that constructs the name from the acpi device instead.
Signed-off-by Daniel Scally <[email protected]>---
Changes in v2:- Stopped using
devm_kasprintf()drivers/i2c/i2c-core-acpi.c | 16 ++++++++++++++++ include/linux/i2c.h | 5 +++++ 2 files changed, 21 insertions(+)drivers/i2c/i2c-core-acpi.c +3
-0@@ -497,6 +497,22 @@ struct i2c_client *i2c_acpi_new_device(struct device *dev, int index, }EXPORT_SYMBOL_GPL (i2c_acpi_new_device); +/** +* i2c_acpi_dev_name - Construct i2c device name for devs sourced from ACPI +* @adev: ACPI device to construct the name for
drivers/i2c/i2c-core-acpi.c struct i2c_client *i2c_acpi_new_device(struct device *dev, int index, · line 512
Quoted 10 lines
drivers/i2c/i2c-core-acpi.c +10
-0+* +* Constructs the name of an i2c device matching the format used by +* i2c_dev_set_name() to allow users to refer to an i2c device by name even +* before they have been instantiated. +* +* The caller is responsible for freeing the returned pointer. +*/ +char *i2c_acpi_dev_name (struct acpi_device *adev) +{ +return kasprintf (GFP_KERNEL ,I2C_DEV_NAME_FORMAT ,acpi_dev_name (adev));
There's a real danger of a memory leak, as the function name sounds very similar to dev_name() or acpi_dev_name() and those don't allocate memory. I'm not sure what a better name would be, but given that this function is only used in patch 6/7 and not in the I2C subsystem itself, I wonder if we should inline this kasprintf() call in the caller and drop this patch.
Quoted 29 lines
drivers/i2c/i2c-core-acpi.c +3
-0+} +EXPORT_SYMBOL_GPL (i2c_acpi_dev_name); +#ifdef CONFIG_ACPI_I2C_OPREGION static int acpi_gsb_i2c_read_bytes (struct i2c_client *client,u8 cmd,u8 *data,u8 data_len)include/linux/i2c.h +5
-0@@ -998,6 +998,7 @@ bool i2c_acpi_get_i2c_resource(struct acpi_resource *ares,u32 i2c_acpi_find_bus_speed (struct device *dev);struct i2c_client *i2c_acpi_new_device (struct device *dev,int index,struct i2c_board_info *info); +char *i2c_acpi_dev_name (struct acpi_device *adev);struct i2c_adapter *i2c_acpi_find_adapter_by_handle (acpi_handle handle);#else static inline bool i2c_acpi_get_i2c_resource(struct acpi_resource *ares,@@ -1014,6 +1015,10 @@ static inline struct i2c_client *i2c_acpi_new_device(struct device *dev, {return ERR_PTR (-ENODEV ); } +static inline char *i2c_acpi_dev_name (struct acpi_device *adev) +{ +return NULL ; +}static inline struct i2c_adapter *i2c_acpi_find_adapter_by_handle (acpi_handle handle) {return NULL ;
Signature · 3 lines
Regards, Laurent Pinchart
Re: [PATCH v2 4/7] i2c: i2c-core-acpi: Add i2c_acpi_dev_name()
Quoted 1 line · Laurent Pinchart
On Mon, Jan 18, 2021 at 12:34:25AM +0000, Daniel Scally wrote:
...
Quoted 12 lines
Quoted 12 lines
drivers/i2c/i2c-core-acpi.c +12
-0+/** +* i2c_acpi_dev_name - Construct i2c device name for devs sourced from ACPI +* @adev: ACPI device to construct the name for +* +* Constructs the name of an i2c device matching the format used by +* i2c_dev_set_name() to allow users to refer to an i2c device by name even +* before they have been instantiated. +* +* The caller is responsible for freeing the returned pointer. +*/ +char *i2c_acpi_dev_name (struct acpi_device *adev) +{
Quoted 8 lines
drivers/i2c/i2c-core-acpi.c struct i2c_client *i2c_acpi_new_device(struct device *dev, int index, · line 512
Quoted 1 line
drivers/i2c/i2c-core-acpi.c +1
-0+return kasprintf (GFP_KERNEL ,I2C_DEV_NAME_FORMAT ,acpi_dev_name (adev));There's a real danger of a memory leak, as the function name sounds very similar to
dev_name()oracpi_dev_name()and those don't allocate memory. I'm not sure what a better name would be, but given that this function is only used in patch 6/7 and not in the I2C subsystem itself, I wonder if we should inline thiskasprintf()call in the caller and drop this patch.
Dan, I'm fine with either choice.
Quoted 1 line
Quoted 1 line
+}
Signature · 2 lines
With Best Regards, Andy Shevchenko
Rafael J. Wysocki
maintainerRe: [PATCH v2 4/7] i2c: i2c-core-acpi: Add i2c_acpi_dev_name()
In reply to Laurent PinchartQuoted 43 lines · Laurent Pinchart
Hi Daniel,
Thank you for the patch.
Quoted 1 line · Daniel Scally
We want to refer to an i2c device by name before it has been
s/i2c device/acpi i2c device/ ?
Quoted 33 lines
created by the kernel; add a function that constructs the name from the acpi device instead.
Signed-off-by Daniel Scally <djrscally(a)gmail.com>---
Changes in v2:- Stopped using
devm_kasprintf()drivers/i2c/i2c-core-acpi.c | 16 ++++++++++++++++ include/linux/i2c.h | 5 +++++ 2 files changed, 21 insertions(+)drivers/i2c/i2c-core-acpi.c +12
-0@@ -497,6 +497,22 @@ struct i2c_client *i2c_acpi_new_device(struct device *dev, int index, }EXPORT_SYMBOL_GPL (i2c_acpi_new_device); +/** +* i2c_acpi_dev_name - Construct i2c device name for devs sourced from ACPI +* @adev: ACPI device to construct the name for +* +* Constructs the name of an i2c device matching the format used by +* i2c_dev_set_name() to allow users to refer to an i2c device by name even +* before they have been instantiated. +* +* The caller is responsible for freeing the returned pointer. +*/ +char *i2c_acpi_dev_name (struct acpi_device *adev) +{
Quoted 8 lines
drivers/i2c/i2c-core-acpi.c struct i2c_client *i2c_acpi_new_device(struct device *dev, int index, · line 512
Quoted 1 line
drivers/i2c/i2c-core-acpi.c +1
-0+return kasprintf (GFP_KERNEL ,I2C_DEV_NAME_FORMAT ,acpi_dev_name (adev));There's a real danger of a memory leak, as the function name sounds very similar to
dev_name()oracpi_dev_name()and those don't allocate memory. I'm not sure what a better name would be, but given that this function is only used in patch 6/7 and not in the I2C subsystem itself, I wonder if we should inline thiskasprintf()call in the caller and drop this patch.
IMO if this is a one-off usage, it's better to open-code it.
Re: [PATCH v2 4/7] i2c: i2c-core-acpi: Add i2c_acpi_dev_name()
Quoted 9 lines
Quoted 7 lines
There's a real danger of a memory leak, as the function name sounds very similar to
dev_name()oracpi_dev_name()and those don't allocate memory. I'm not sure what a better name would be, but given that this function is only used in patch 6/7 and not in the I2C subsystem itself, I wonder if we should inline thiskasprintf()call in the caller and drop this patch.IMO if this is a one-off usage, it's better to open-code it.
Sounds reasonable to me, too.
Re: [PATCH v2 4/7] i2c: i2c-core-acpi: Add i2c_acpi_dev_name()
Quoted 9 lines · Wolfram Sang
Quoted 7 lines
Quoted 6 lines
There's a real danger of a memory leak, as the function name sounds very similar to
dev_name()oracpi_dev_name()and those don't allocate memory. I'm not sure what a better name would be, but given that this function is only used in patch 6/7 and not in the I2C subsystem itself, I wonder if we should inline thiskasprintf()call in the caller and drop this patch.IMO if this is a one-off usage, it's better to open-code it.
Sounds reasonable to me, too.
Just to clarify; "open-code" meaning inline it in the caller like Laurent said, right?
Re: [PATCH v2 4/7] i2c: i2c-core-acpi: Add i2c_acpi_dev_name()
Quoted 3 lines
Just to clarify; "open-code" meaning inline it in the caller like Laurent said, right?
Yes.
Re: [PATCH v2 4/7] i2c: i2c-core-acpi: Add i2c_acpi_dev_name()
Quoted 4 lines · Wolfram Sang
Quoted 2 lines
Just to clarify; "open-code" meaning inline it in the caller like Laurent said, right?
Yes.
Thanks - will do that and drop this one then
Re: [PATCH v2 4/7] i2c: i2c-core-acpi: Add i2c_acpi_dev_name()
In reply to Daniel ScallyQuoted 1 line · Daniel Scally
We want to refer to an i2c device by name before it has been
I²C
Quoted 2 lines
created by the kernel; add a function that constructs the name from the acpi device instead.
acpi -> ACPI
Prefix: "i2c: core: "
With above
Quoted 63 lines
Signed-off-by Daniel Scally <[email protected]>---
Changes in v2:- Stopped using
devm_kasprintf()drivers/i2c/i2c-core-acpi.c | 16 ++++++++++++++++ include/linux/i2c.h | 5 +++++ 2 files changed, 21 insertions(+)drivers/i2c/i2c-core-acpi.c +16
-0@@ -497,6 +497,22 @@ struct i2c_client *i2c_acpi_new_device(struct device *dev, int index, }EXPORT_SYMBOL_GPL (i2c_acpi_new_device); +/** +* i2c_acpi_dev_name - Construct i2c device name for devs sourced from ACPI +* @adev: ACPI device to construct the name for +* +* Constructs the name of an i2c device matching the format used by +* i2c_dev_set_name() to allow users to refer to an i2c device by name even +* before they have been instantiated. +* +* The caller is responsible for freeing the returned pointer. +*/ +char *i2c_acpi_dev_name (struct acpi_device *adev) +{ +return kasprintf (GFP_KERNEL ,I2C_DEV_NAME_FORMAT ,acpi_dev_name (adev)); +} +EXPORT_SYMBOL_GPL (i2c_acpi_dev_name); +#ifdef CONFIG_ACPI_I2C_OPREGION static int acpi_gsb_i2c_read_bytes (struct i2c_client *client,u8 cmd,u8 *data,u8 data_len)include/linux/i2c.h +5
-0@@ -998,6 +998,7 @@ bool i2c_acpi_get_i2c_resource(struct acpi_resource *ares,u32 i2c_acpi_find_bus_speed (struct device *dev);struct i2c_client *i2c_acpi_new_device (struct device *dev,int index,struct i2c_board_info *info); +char *i2c_acpi_dev_name (struct acpi_device *adev);struct i2c_adapter *i2c_acpi_find_adapter_by_handle (acpi_handle handle);#else static inline bool i2c_acpi_get_i2c_resource(struct acpi_resource *ares,@@ -1014,6 +1015,10 @@ static inline struct i2c_client *i2c_acpi_new_device(struct device *dev, {return ERR_PTR (-ENODEV ); } +static inline char *i2c_acpi_dev_name (struct acpi_device *adev) +{ +return NULL ; +}static inline struct i2c_adapter *i2c_acpi_find_adapter_by_handle (acpi_handle handle) {return NULL ;Signature · 1 line
2.25.1
Signature · 2 lines
With Best Regards, Andy Shevchenko
Re: [PATCH v2 4/7] i2c: i2c-core-acpi: Add i2c_acpi_dev_name()
Quoted 4 lines · Andy Shevchenko
Quoted 1 line · Daniel Scally
We want to refer to an i2c device by name before it has been
I²C
Andy, are you next going to suggest renaming all the files with i2c?
$ git ls-files | grep i2c | wc -l 953
Please do not use the pedantic I²C, 7 bit ascii is just fine here.
My keyboard does not have a superscripted 2 key, and yes, I know how to use it with multiple keypresses but it's irrelevant.
Quoted 4 lines
Quoted 2 lines
created by the kernel; add a function that constructs the name from the acpi device instead.
acpi -> ACPI
Same deal with acpi filenames. Everyone already recognizes acpi is actually ACPI and there isn't any confusion in anyone's mind.
$ git ls-files | grep acpi | wc -l 533
Quoted 1 line
Prefix: "i2c: core: "
Please stop being a pedant on these trivial things. It's unimportant and has almost no value.
Re: [PATCH v2 4/7] i2c: i2c-core-acpi: Add i2c_acpi_dev_name()
Quoted 7 lines · Joe Perches
Quoted 4 lines · Andy Shevchenko
Quoted 1 line · Daniel Scally
We want to refer to an i2c device by name before it has been
I²C
Andy, are you next going to suggest renaming all the files with i2c?
Where did you get this from?
Quoted 4 lines
Please do not use the pedantic I²C, 7 bit ascii is just fine here.
My keyboard does not have a superscripted 2 key, and yes, I know how to use it with multiple keypresses but it's irrelevant.
I2C is fine for me as well.
...
Quoted 6 lines
Quoted 4 lines
Quoted 2 lines
created by the kernel; add a function that constructs the name from the acpi device instead.
acpi -> ACPI
Same deal with acpi filenames.
Where did you get about *file* names, really? Maybe you read again above?
...
Quoted 4 lines
Quoted 1 line
Prefix: "i2c: core: "
Please stop being a pedant on these trivial things. It's unimportant and has almost no value.
This series is going to have a new version, that's why I did those comments. If it had been the only comments, I would have not posted them.
Signature · 2 lines
With Best Regards, Andy Shevchenko
Re: [PATCH v2 4/7] i2c: i2c-core-acpi: Add i2c_acpi_dev_name()
Quoted 3 lines · Andy Shevchenko
Quoted 2 lines · Joe Perches
Quoted 1 line · Andy Shevchenko
On Mon, Jan 18, 2021 at 12:34:25AM +0000, Daniel Scally wrote:
...
Quoted 7 lines
Quoted 4 lines
Quoted 1 line
Prefix: "i2c: core: "
Please stop being a pedant on these trivial things. It's unimportant and has almost no value.
This series is going to have a new version, that's why I did those comments. If it had been the only comments, I would have not posted them.
And actually to the rationale: it makes slightly easier to grep for patches against same driver / group of drivers / subsystem.
I bet the ... --grep 'i2c: core:' will give different results to the ... -- drivers/i2c/i2c-* include/i2c*` besides being shorter.
Signature · 2 lines
With Best Regards, Andy Shevchenko
Re: [PATCH v2 4/7] i2c: i2c-core-acpi: Add i2c_acpi_dev_name()
In reply to Andy ShevchenkoQuoted 10 lines · Andy Shevchenko
Quoted 7 lines · Joe Perches
Quoted 4 lines · Andy Shevchenko
Quoted 1 line · Daniel Scally
We want to refer to an i2c device by name before it has been
I²C
Andy, are you next going to suggest renaming all the files with i2c?
Where did you get this from?
By extension from the request to use I²C. And it's a leading question not a statement of fact.
PATCH v2 5/7 gpio: gpiolib-acpi: Export acpi_get_gpiod()
In reply to Daniel ScallyI need to be able to translate GPIO resources in an acpi_device's _CRS into gpio_descs. Those are represented in _CRS as a pathname to a GPIO device plus the pin's index number: this function is perfect for that purpose.
---
Changes in v2:
-None
drivers/gpio/gpiolib-acpi.c | 3 ++- include/linux/acpi.h | 5 +++++ 2 files changed, 7 insertions(+), 1 deletion(-)
drivers/gpio/gpiolib-acpi.c +2 -1
@@ -111,7 +111,7 @@ static int acpi_gpiochip_find(struct gpio_chip *gc, void *data)* controller does not have GPIO chip registered at the moment. This is to * support probe deferral. */ -static struct gpio_desc *acpi_get_gpiod (char *path,int pin) +struct gpio_desc *acpi_get_gpiod (char *path,int pin) {struct gpio_chip *chip;acpi_handle handle;
@@ -127,6 +127,7 @@ static struct gpio_desc *acpi_get_gpiod(char *path, int pin)return gpiochip_get_desc (chip, pin); } +EXPORT_SYMBOL_GPL (acpi_get_gpiod);static irqreturn_t acpi_gpio_irq_handler (int irq,void *data) {
include/linux/acpi.h +5 -0
@@ -1066,6 +1066,7 @@ void __acpi_handle_debug(struct _ddebug *descriptor, acpi_handle handle, const cbool acpi_gpio_get_irq_resource (struct acpi_resource *ares,struct acpi_resource_gpio **agpio);int acpi_dev_gpio_irq_get (struct acpi_device *adev,int index); +struct gpio_desc *acpi_get_gpiod (char *path,int pin);#else static inline bool acpi_gpio_get_irq_resource (struct acpi_resource *ares,struct acpi_resource_gpio **agpio)
@@ -1076,6 +1077,10 @@ static inline int acpi_dev_gpio_irq_get(struct acpi_device *adev, int index) {return -ENXIO ; } +struct gpio_desc *acpi_get_gpiod (char *path,int pin) +{ +return NULL ; +}#endif /* Device properties */
Signature · 1 line
2.25.1
Re: [PATCH v2 5/7] gpio: gpiolib-acpi: Export acpi_get_gpiod()
Hi Daniel,
Thank you for the patch.
Quoted 6 lines · Daniel Scally
I need to be able to translate GPIO resources in an acpi_device's
_CRSintogpio_descs. Those are represented in_CRSas a pathname to a GPIO device plus the pin's index number: this function is perfect for that purpose.Signed-off-by Daniel Scally <[email protected]>
Quoted 53 lines
---
Changes in v2:-None
drivers/gpio/gpiolib-acpi.c | 3 ++- include/linux/acpi.h | 5 +++++ 2 files changed, 7 insertions(+), 1 deletion(-)drivers/gpio/gpiolib-acpi.c +2
-1@@ -111,7 +111,7 @@ static int acpi_gpiochip_find(struct gpio_chip *gc, void *data)* controller does not have GPIO chip registered at the moment. This is to * support probe deferral. */ -static struct gpio_desc *acpi_get_gpiod (char *path,int pin) +struct gpio_desc *acpi_get_gpiod (char *path,int pin) {struct gpio_chip *chip;acpi_handle handle;@@ -127,6 +127,7 @@ static struct gpio_desc *acpi_get_gpiod(char *path, int pin)return gpiochip_get_desc (chip, pin); } +EXPORT_SYMBOL_GPL (acpi_get_gpiod);static irqreturn_t acpi_gpio_irq_handler (int irq,void *data) {include/linux/acpi.h +5
-0@@ -1066,6 +1066,7 @@ void __acpi_handle_debug(struct _ddebug *descriptor, acpi_handle handle, const cbool acpi_gpio_get_irq_resource (struct acpi_resource *ares,struct acpi_resource_gpio **agpio);int acpi_dev_gpio_irq_get (struct acpi_device *adev,int index); +struct gpio_desc *acpi_get_gpiod (char *path,int pin);#else static inline bool acpi_gpio_get_irq_resource (struct acpi_resource *ares,struct acpi_resource_gpio **agpio)@@ -1076,6 +1077,10 @@ static inline int acpi_dev_gpio_irq_get(struct acpi_device *adev, int index) {return -ENXIO ; } +struct gpio_desc *acpi_get_gpiod (char *path,int pin) +{ +return NULL ; +}#endif /* Device properties */
Signature · 3 lines
Regards, Laurent Pinchart
Re: [PATCH v2 5/7] gpio: gpiolib-acpi: Export acpi_get_gpiod()
In reply to Daniel ScallyQuoted 1 line · Daniel Scally
I need to be able to translate GPIO resources in an acpi_device's
_CRS
ACPI device's
Quoted 1 line
into
gpio_descs. Those are represented in_CRSas a pathname to a GPIO
into GPIO descriptor array
Quoted 2 lines
device plus the pin's index number: this function is perfect for that purpose.
...
include/linux/acpi.h
Quoted 1 line
include/linux/acpi.h +0
-0
Wrong header. Please use gpio/consumer.h.
Signature · 2 lines
With Best Regards, Andy Shevchenko
Re: [PATCH v2 5/7] gpio: gpiolib-acpi: Export acpi_get_gpiod()
Quoted 1 line · Andy Shevchenko
On Mon, Jan 18, 2021 at 12:34:26AM +0000, Daniel Scally wrote:
And prefix: "gpiolib: acpi: ".
Signature · 2 lines
With Best Regards, Andy Shevchenko
Re: [PATCH v2 5/7] gpio: gpiolib-acpi: Export acpi_get_gpiod()
In reply to Andy ShevchenkoQuoted 9 lines · Andy Shevchenko
Quoted 1 line · Daniel Scally
I need to be able to translate GPIO resources in an acpi_device's
_CRSACPI device's
Quoted 1 line
into
gpio_descs. Those are represented in_CRSas a pathname to a GPIOinto GPIO descriptor array
Quoted 9 lines
Quoted 2 lines
device plus the pin's index number: this function is perfect for that purpose.
...
include/linux/acpi.h
Quoted 1 line
include/linux/acpi.h +0
-0Wrong header. Please use
gpio/consumer.h.
Ack to all - thanks.
PATCH v2 6/7 platform: x86: Add intel_skl_int3472 driver
In reply to Daniel ScallyACPI 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.
---
Changes in v2:
- Switched to a module registering a platform driver to run the dummy ACPI devices, plus an i2c driver to replace and extend the existing tps68470 driver
- Added clock handling functions to the int3472-discrete driver
- A whole bunch of other changes too numerous to enumerate
MAINTAINERS | 5 + 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 +++++ 7 files changed, 875 insertions(+) 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
MAINTAINERS +5 -0
@@ -9147,6 +9147,11 @@ S: Maintained F: arch/x86/include/asm/intel_scu_ipc.h F: drivers/platform/x86/intel_scu_* +INTEL SKL INT3472 ACPI DEVICE DRIVER +M: Daniel Scally <[email protected]> +S: Maintained +F: drivers/platform/x86/intel_skl_int3472_* + INTEL SPEED SELECT TECHNOLOGY M: Srinivas Pandruvada <[email protected]> L: [email protected]
drivers/platform/x86/Kconfig +25 -0
@@ -844,6 +844,31 @@ config INTEL_CHT_INT33FE device and CONFIG_TYPEC_FUSB302=m and CONFIG_BATTERY_MAX17042=m for Type-C device. +config INTEL_SKL_INT3472 + tristate "Intel SkyLake ACPI INT3472 Driver" + depends on X86 && ACPI + select REGMAP_I2C + help + This driver adds support for the INT3472 ACPI devices found on some + Intel SkyLake devices. + + There are 3 kinds of INT3472 ACPI device possible; two for devices + designed for Windows (either with or without a physical tps68470 + PMIC) and one designed for Chrome OS. This driver handles all three + situations by discovering information it needs to discern them at + runtime. + + If your device was designed for Chrome OS, this driver will provide + an ACPI operation region, which must be available before any of the + devices using this are probed. For this reason, you should select Y + if your device was designed for ChromeOS. This option also configures + the designware-i2c driver to be built-in, for the same reason. + + Say Y or M here if you have a SkyLake device designed for use + with Windows or ChromeOS. Say N here if you are not sure. + + The module will be named "intel-skl-int3472" + config INTEL_HID_EVENT tristate "INTEL HID Event" depends on ACPI
drivers/platform/x86/Makefile +4 -0
@@ -86,6 +86,10 @@ obj-$(CONFIG_INTEL_HID_EVENT) += intel-hid.o obj-$(CONFIG_INTEL_INT0002_VGPIO) += intel_int0002_vgpio.o obj-$(CONFIG_INTEL_MENLOW) += intel_menlow.o obj-$(CONFIG_INTEL_OAKTRAIL) += intel_oaktrail.o +obj-$(CONFIG_INTEL_SKL_INT3472) += intel_skl_int3472.o +intel_skl_int3472-objs := intel_skl_int3472_common.o \ + intel_skl_int3472_discrete.o \ + intel_skl_int3472_tps68470.o obj-$(CONFIG_INTEL_VBTN) += intel-vbtn.o # MSI
drivers/platform/x86/intel_skl_int3472_common.c new file +100 -0
100 lines not on this page · raw message
drivers/platform/x86/intel_skl_int3472_common.h new file +100 -0
100 lines not on this page · raw message
drivers/platform/x86/intel_skl_int3472_discrete.c new file +496 -0
496 lines not on this page · raw message
drivers/platform/x86/intel_skl_int3472_tps68470.c new file +145 -0
145 lines not on this page · raw message
Signature · 1 line
2.25.1
Re: [PATCH v2 6/7] platform: x86: Add intel_skl_int3472 driver
Hi Daniel,
Thank you for the patch.
Quoted 66 lines · Daniel Scally
ACPI devices with
_HIDINT3472 are currently matched to the tps68470 driver, however this does not cover all situations in which that_HIDoccurs. We've encountered three possibilities:1. On Chrome OS devices, an ACPI device with
_HIDINT3472 (representing a physical tps68470 device) that requires a GPIO and OpRegion driver
2. On devices designed for Windows, an ACPI device with_HIDINT3472 (again representing a physical tps68470 device) which requires GPIO, Clock and Regulator drivers.
3. On other devices designed for Windows, an ACPI device with_HIDINT3472 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]>---
Changes in v2:- Switched to a module registering a platform driver to run the dummy ACPI devices, plus an i2c driver to replace and extend the existing tps68470 driver
- Added clock handling functions to the int3472-discrete driver
- A whole bunch of other changes too numerous to enumerateMAINTAINERS | 5 + 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 +++++ 7 files changed, 875 insertions(+) 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.cMAINTAINERS +5
-0@@ -9147,6 +9147,11 @@ S: Maintained F: arch/x86/include/asm/intel_scu_ipc.h F: drivers/platform/x86/intel_scu_* +INTEL SKL INT3472 ACPI DEVICE DRIVER +M: Daniel Scally <[email protected]> +S: Maintained +F: drivers/platform/x86/intel_skl_int3472_* + INTEL SPEED SELECT TECHNOLOGY M: Srinivas Pandruvada <[email protected]> L: [email protected]drivers/platform/x86/Kconfig +0
-0@@ -844,6 +844,31 @@ config INTEL_CHT_INT33FE device and CONFIG_TYPEC_FUSB302=m and CONFIG_BATTERY_MAX17042=m for Type-C device.
drivers/platform/x86/Kconfig config INTEL_CHT_INT33FE · line 856
Quoted 10 lines
drivers/platform/x86/Kconfig +10
-0+config INTEL_SKL_INT3472 + tristate "Intel SkyLake ACPI INT3472 Driver" + depends on X86 && ACPI + select REGMAP_I2C + help + This driver adds support for the INT3472 ACPI devices found on some + Intel SkyLake devices. + + There are 3 kinds of INT3472 ACPI device possible; two for devices + designed for Windows (either with or without a physical tps68470
I'd capitalize TPS, chip names are usually written in upper case, and driver names in lower case.
drivers/platform/x86/Kconfig config INTEL_CHT_INT33FE · line 857
Quoted 1 line
drivers/platform/x86/Kconfig +1
-0+ PMIC) and one designed for Chrome OS.
How about expanding this a bit to explain what the INT3472 stands for ?
The INT3472 is an Intel camera power controller, a logical device found on some Skylake-based systems that can map to different hardware devices depending on the platform. On machines designed for Chrome OS, it maps to a TPS68470 camera PMIC. On machines designed for Windows, it maps to either a TP68470 camera PMIC, a uP6641Q sensor PMIC, or a set of discrete GPIOs and power gates.
drivers/platform/x86/Kconfig config INTEL_CHT_INT33FE · line 865
Quoted 9 lines
This driver handles all three
drivers/platform/x86/Kconfig +8
-0+ situations by discovering information it needs to discern them at + runtime. + + If your device was designed for Chrome OS, this driver will provide + an ACPI operation region, which must be available before any of the + devices using this are probed. For this reason, you should select Y + if your device was designed for ChromeOS. This option also configures + the designware-i2c driver to be built-in, for the same reason.
Is the last sentence a leftover ?
Quoted 30 lines
drivers/platform/x86/Kconfig +6
-0+ + Say Y or M here if you have a SkyLake device designed for use + with Windows or ChromeOS. Say N here if you are not sure. + + The module will be named "intel-skl-int3472" + config INTEL_HID_EVENT tristate "INTEL HID Event" depends on ACPIdrivers/platform/x86/Makefile +4
-0@@ -86,6 +86,10 @@ obj-$(CONFIG_INTEL_HID_EVENT) += intel-hid.o obj-$(CONFIG_INTEL_INT0002_VGPIO) += intel_int0002_vgpio.o obj-$(CONFIG_INTEL_MENLOW) += intel_menlow.o obj-$(CONFIG_INTEL_OAKTRAIL) += intel_oaktrail.o +obj-$(CONFIG_INTEL_SKL_INT3472) += intel_skl_int3472.o +intel_skl_int3472-objs := intel_skl_int3472_common.o \ + intel_skl_int3472_discrete.o \ + intel_skl_int3472_tps68470.o obj-$(CONFIG_INTEL_VBTN) += intel-vbtn.o # MSIdrivers/platform/x86/intel_skl_int3472_common.c new file +0
-0
drivers/platform/x86/intel_skl_int3472_common.c line 6
Quoted 6 lines
drivers/platform/x86/intel_skl_int3472_common.c new file +6
-0@@ -0,0 +1,100 @@ +// SPDX-License-Identifier: GPL-2.0 +/* Author: Dan Scally <[email protected]> */ + +#include <linux/acpi.h> +#include <linux/i2c.h> +#include <linux/platform_device.h>
#include <linux/slab.h>
for kfree().
Quoted 9 lines
drivers/platform/x86/intel_skl_int3472_common.c new file +9
-0+ +#include "intel_skl_int3472_common.h" + +int skl_int3472_get_cldb_buffer (struct acpi_device *adev, +struct int3472_cldb *cldb) +{ +struct acpi_buffer buffer = {ACPI_ALLOCATE_BUFFER ,NULL }; +acpi_handle handle = adev->handle; +union acpi_object *obj;
drivers/platform/x86/intel_skl_int3472_common.c line 25
Quoted 10 lines
drivers/platform/x86/intel_skl_int3472_common.c new file +10
-0+acpi_status status; +int ret =0 ; + + status =acpi_evaluate_object (handle,"CLDB" ,NULL , &buffer); +if (ACPI_FAILURE (status)) +return -ENODEV ; + + obj = buffer.pointer; +if (!obj) { +dev_err (&adev->dev,"ACPI device has no CLDB object\n" );
Is this the code path that is taken on Chrome OS ? If so an error message isn't appropriate. I'd drop this message, and instead add an error message in the discrete PMIC code.
Quoted 46 lines
drivers/platform/x86/intel_skl_int3472_common.c new file +46
-0+return -ENODEV ; + } + +if (obj->type !=ACPI_TYPE_BUFFER ) { +dev_err (&adev->dev,"CLDB object is not an ACPI buffer\n" ); + ret = -EINVAL ; + goto out_free_buff; + } + +if (obj->buffer.length >sizeof (*cldb)) { +dev_err (&adev->dev,"The CLDB buffer is too large\n" ); + ret = -EINVAL ; + goto out_free_buff; + } + +memcpy (cldb, obj->buffer.pointer, obj->buffer.length); + +out_free_buff: +kfree (buffer.pointer); +return ret; +} + +static const struct acpi_device_id int3472_device_id[] = { + {"INT3472" ,0 }, + { }, +}; +MODULE_DEVICE_TABLE (acpi, int3472_device_id); + +static struct platform_driver int3472_discrete = { + .driver = { + .name ="int3472-discrete" , + .acpi_match_table = int3472_device_id, + }, + .probe = skl_int3472_discrete_probe, + .remove = skl_int3472_discrete_remove, +}; + +static struct i2c_driver int3472_tps68470 = { + .driver = { + .name ="int3472-tps68470" , + .acpi_match_table = int3472_device_id, + }, + .probe_new = skl_int3472_tps68470_probe, +}; + +static int skl_int3472_init (void )
drivers/platform/x86/intel_skl_int3472_common.c line 81
Quoted 10 lines
drivers/platform/x86/intel_skl_int3472_common.c new file +10
-0+{ +int ret =0 ; + + ret =platform_driver_register (&int3472_discrete); +if (ret) +return ret; + + ret =i2c_register_driver (THIS_MODULE , &int3472_tps68470); +if (ret) + goto err_unregister_plat_drv;
You could call platform_driver_unregister() directly here and return ret. I don't expect this function will need to be extended with a more complex error handling code path.
Quoted 25 lines
drivers/platform/x86/intel_skl_int3472_common.c new file +19
-0+ +return 0 ; + +err_unregister_plat_drv: +platform_driver_unregister (&int3472_discrete); +return ret; +} +module_init (skl_int3472_init); + +static void skl_int3472_exit (void ) +{ +platform_driver_unregister (&int3472_discrete); +i2c_del_driver (&int3472_tps68470); +} +module_exit (skl_int3472_exit); + +MODULE_DESCRIPTION ("Intel SkyLake INT3472 ACPI Device Driver" ); +MODULE_AUTHOR ("Daniel Scally <[email protected]>" ); +MODULE_LICENSE ("GPL v2" );drivers/platform/x86/intel_skl_int3472_common.h new file +0
-0
drivers/platform/x86/intel_skl_int3472_common.h line 2
Quoted 2 lines
drivers/platform/x86/intel_skl_int3472_common.h new file +2
-0@@ -0,0 +1,100 @@ +/* SPDX-License-Identifier: GPL-2.0 */ +/* Author: Dan Scally <[email protected]> */
Missing blank line, and missing header guard.
drivers/platform/x86/intel_skl_int3472_common.h line 3
Quoted 1 line
drivers/platform/x86/intel_skl_int3472_common.h new file +1
-0+#include <linux/regulator/machine.h>
Alphabetically sorted please.
drivers/platform/x86/intel_skl_int3472_common.h line 5
Quoted 2 lines
drivers/platform/x86/intel_skl_int3472_common.h new file +2
-0+#include <linux/clk-provider.h> +#include <linux/gpio/machine.h>
You can drop this and forward-declare struct gpio_desc.
drivers/platform/x86/intel_skl_int3472_common.h line 13
Quoted 8 lines
drivers/platform/x86/intel_skl_int3472_common.h new file +8
-0+#include <linux/regulator/driver.h> +#include <linux/types.h> + +/* PMIC GPIO Types */ +#define INT3472_GPIO_TYPE_RESET 0x00 +#define INT3472_GPIO_TYPE_POWERDOWN 0x01 +#define INT3472_GPIO_TYPE_CLK_ENABLE 0x0c +#define INT3472_GPIO_TYPE_POWER_ENABLE 0x0b
Should the macros be sorted by value ?
drivers/platform/x86/intel_skl_int3472_common.h line 14
Quoted 1 line
drivers/platform/x86/intel_skl_int3472_common.h new file +1
-0+#define INT3472_GPIO_TYPE_PRIVACY_LED 0x0d
Blank line here ?
drivers/platform/x86/intel_skl_int3472_common.h line 16
Quoted 2 lines
drivers/platform/x86/intel_skl_int3472_common.h new file +2
-0+#define INT3472_PDEV_MAX_NAME_LEN 23 +#define INT3472_MAX_SENSOR_GPIOS 3
And blank line here too ?
drivers/platform/x86/intel_skl_int3472_common.h line 20
Quoted 4 lines
drivers/platform/x86/intel_skl_int3472_common.h new file +4
-0+#define GPIO_REGULATOR_NAME_LENGTH 27 +#define GPIO_REGULATOR_SUPPLY_NAME_LENGTH 9 + +#define INT3472_REGULATOR (_NAME, _SUPPLY, _OPS) \
Macro arguments don't need to be capitalized.
Quoted 39 lines
drivers/platform/x86/intel_skl_int3472_common.h new file +39
-0+ (const struct regulator_desc ) { \ + .name = _NAME, \ + .supply_name = _SUPPLY, \ + .id =0 , \ + .type =REGULATOR_VOLTAGE , \ + .ops = _OPS, \ + .owner =THIS_MODULE , \ + } + +#define INT3472_GPIO_FUNCTION_REMAP (_PIN, _FUNCTION) \ + (const struct int3472_gpio_function_remap) { \ + .documented = _PIN, \ + .actual = _FUNCTION \ + } + +#define to_int3472_clk (hw) \ + container_of(hw, struct int3472_gpio_clock, clk_hw) + +struct int3472_cldb { +u8 version; +/* +* control logic type +* 0: UNKNOWN +* 1: DISCRETE(CRD-D) +* 2: PMIC TPS68470 +* 3: PMIC uP6641 +*/ +u8 control_logic_type; +u8 control_logic_id; +u8 sensor_card_sku; +u8 reserved[28 ]; +}; + +struct int3472_gpio_regulator { +char regulator_name[GPIO_REGULATOR_NAME_LENGTH ]; +char supply_name[GPIO_REGULATOR_SUPPLY_NAME_LENGTH ]; +struct gpio_desc *gpio; +struct regulator_dev *rdev; +struct regulator_desc rdesc;
drivers/platform/x86/intel_skl_int3472_common.h line 69
Quoted 10 lines
drivers/platform/x86/intel_skl_int3472_common.h new file +10
-0+}; + +struct int3472_gpio_clock { +struct clk *clk; +struct clk_hw clk_hw; +struct clk_lookup *cl; +struct gpio_desc *gpio; +}; + +struct int3472_device {
Maybe int3472_discrete_device ?
drivers/platform/x86/intel_skl_int3472_common.h line 73
Quoted 4 lines
drivers/platform/x86/intel_skl_int3472_common.h new file +4
-0+struct acpi_device *adev; +struct platform_device *pdev; +struct acpi_device *sensor; +char *sensor_name;
const ?
drivers/platform/x86/intel_skl_int3472_common.h line 78
Quoted 5 lines
drivers/platform/x86/intel_skl_int3472_common.h new file +5
-0+ +unsigned int n_gpios;/* how many GPIOs have we seen */ + +struct int3472_gpio_regulator regulator; +struct int3472_gpio_clock clock;
You don't necessarily need to define separate structures for this, you could also write
struct {
char regulator_name[GPIO_REGULATOR_NAME_LENGTH];
char supply_name[GPIO_REGULATOR_SUPPLY_NAME_LENGTH];
struct gpio_desc *gpio;
struct regulator_dev *rdev;
struct regulator_desc rdesc;
} regulator;
struct {
struct clk *clk;
struct clk_hw clk_hw;
struct clk_lookup *cl;
struct gpio_desc *gpio;
} clock;It's entirely up to you.
drivers/platform/x86/intel_skl_int3472_common.h line 87
Quoted 9 lines
drivers/platform/x86/intel_skl_int3472_common.h new file +9
-0+ +unsigned int n_sensor_gpios;/* how many have we mapped to sensor */ +bool gpios_mapped; +struct gpiod_lookup_table gpios; +}; + +struct int3472_gpio_function_remap { +char *documented; +char *actual;
const for both ?
drivers/platform/x86/intel_skl_int3472_common.h line 100
Quoted 13 lines
drivers/platform/x86/intel_skl_int3472_common.h new file +13
-0+}; + +struct int3472_sensor_config { +char *sensor_module_name; +struct regulator_consumer_supply supply_map; +const struct int3472_gpio_function_remap *function_maps; +}; + +int skl_int3472_discrete_probe (struct platform_device *pdev); +int skl_int3472_discrete_remove (struct platform_device *pdev); +int skl_int3472_tps68470_probe (struct i2c_client *client); +int skl_int3472_get_cldb_buffer (struct acpi_device *adev, +struct int3472_cldb *cldb);
struct platform_device, struct i2c_client and strct acpi_device should be forward-declared at the top.
Quoted 19 lines
drivers/platform/x86/intel_skl_int3472_discrete.c new file +13
-0@@ -0,0 +1,496 @@ +// SPDX-License-Identifier: GPL-2.0 +/* Author: Dan Scally <[email protected]> */ + +#include <linux/acpi.h> +#include <linux/clkdev.h> +#include <linux/gpio/consumer.h> +#include <linux/i2c.h> +#include <linux/kernel.h> +#include <linux/module.h> +#include <linux/platform_device.h> +#include <linux/regulator/driver.h> + +#include "intel_skl_int3472_common.h"
drivers/platform/x86/intel_skl_int3472_discrete.c line 23
Quoted 10 lines
drivers/platform/x86/intel_skl_int3472_discrete.c new file +10
-0+ +/* 79234640-9e10-4fea-a5c1-b5aa8b19756f */ +static const guid_t int3472_gpio_guid = +GUID_INIT (0x79234640 ,0x9e10 ,0x4fea , +0xa5 ,0xc1 ,0xb5 ,0xaa ,0x8b ,0x19 ,0x75 ,0x6f ); + +/* 822ace8f-2814-4174-a56b-5f029fe079ee */ +static const guid_t cio2_sensor_module_guid = +GUID_INIT (0x822ace8f ,0x2814 ,0x4174 , +0xa5 ,0x6b ,0x5f ,0x02 ,0x9f ,0xe0 ,0x79 ,0xee );
A comment that explains what those DSM functions do would be useful for reference. It has taken lots of time to figure it out, let's spare the pain to the next person who tries to understand this :-)
Quoted 5 lines
drivers/platform/x86/intel_skl_int3472_discrete.c new file +5
-0+ +/* +* Here follows platform specific mapping information that we can pass to +* the functions mapping resources to the sensors. Where the sensors have +* a power enable pin defined in DSDT we need to provide a supply name so
drivers/platform/x86/intel_skl_int3472_discrete.c line 38
Quoted 10 lines
drivers/platform/x86/intel_skl_int3472_discrete.c new file +10
-0+* the sensor drivers can find the regulator. Optionally, we can provide a +* NULL terminated array of function name mappings to deal with any platform +* specific deviations from the documented behaviour of GPIOs. +* +* Map a GPIO function name to NULL to prevent the driver from mapping that +* GPIO at all. +*/ + +static const struct int3472_gpio_function_remap ov2680_gpio_function_remaps[] = { +INT3472_GPIO_FUNCTION_REMAP ("reset" ,NULL ),
Does the macro increase readability compared to writing
{ "reset", NULL },? I think I'd drop it.
drivers/platform/x86/intel_skl_int3472_discrete.c line 43
Quoted 5 lines
drivers/platform/x86/intel_skl_int3472_discrete.c new file +5
-0+ INT3472_GPIO_FUNCTION_REMAP("powerdown", "reset"), + { } +}; + +static struct int3472_sensor_config int3472_sensor_configs[] = {
static const struct
Quoted 10 lines
drivers/platform/x86/intel_skl_int3472_discrete.c new file +10
-0+/* Lenovo Miix 510-12ISK - OV2680, Front */ + { "GNDF140809R", { 0 }, ov2680_gpio_function_remaps}, +/* Lenovo Miix 510-12ISK - OV5648, Rear */ + { "GEFF150023R", REGULATOR_SUPPLY("avdd", "i2c-OVTI5648:00"), NULL}, +/* Surface Go 1&2 - OV5693, Front */ + { "YHCU", REGULATOR_SUPPLY("avdd", "i2c-INT33BE:00"), NULL}, +}; + +/* +* The regulators have to have .ops to be valid, but the only ops we actually
drivers/platform/x86/intel_skl_int3472_discrete.c line 63
Quoted 10 lines
drivers/platform/x86/intel_skl_int3472_discrete.c new file +10
-0+* support are .enable and .disable which are handled via .ena_gpiod. Pass an +* empty struct to clear the check without lying about capabilities. +*/ +static const struct regulator_ops int3472_gpio_regulator_ops = {0 }; + +static int skl_int3472_clk_enable (struct clk_hw *hw) +{ +struct int3472_gpio_clock *clk =to_int3472_clk (hw); + +gpiod_set_value (clk->gpio,1 );
The clock enable() and disable() methods are not supposed to sleep, while setting a GPIO value may sleep in the general case. Should this be moved to skl_int3472_clk_prepare() ? Same for skl_int3472_clk_disable() and skl_int3472_clk_unprepare().
Quoted 48 lines
drivers/platform/x86/intel_skl_int3472_discrete.c new file +48
-0+ +return 0 ; +} + +static void skl_int3472_clk_disable (struct clk_hw *hw) +{ +struct int3472_gpio_clock *clk =to_int3472_clk (hw); + +gpiod_set_value (clk->gpio,0 ); +} + +static int skl_int3472_clk_prepare (struct clk_hw *hw) +{ +/* +* We're just turning a GPIO on to enable, so nothing to do here, but +* we want to provide the op so prepare_enable() works. +*/ +return 0 ; +} + +static void skl_int3472_clk_unprepare (struct clk_hw *hw) +{ +/* Likewise, nothing to do here... */ +} + +static const struct clk_ops skl_int3472_clock_ops = { + .prepare = skl_int3472_clk_prepare, + .unprepare = skl_int3472_clk_unprepare, + .enable = skl_int3472_clk_enable, + .disable = skl_int3472_clk_disable, +}; + +static struct int3472_sensor_config * +skl_int3472_get_sensor_module_config (struct int3472_device *int3472) +{ +unsigned int i =ARRAY_SIZE (int3472_sensor_configs); +struct int3472_sensor_config *ret; +union acpi_object *obj; + + obj =acpi_evaluate_dsm_typed (int3472->sensor->handle, + &cio2_sensor_module_guid,0x00 , +0x01 ,NULL ,ACPI_TYPE_STRING ); + +if (!obj) { +dev_err (&int3472->pdev->dev, +"Failed to get sensor module string from _DSM\n" ); +return ERR_PTR (-ENODEV ); + }
drivers/platform/x86/intel_skl_int3472_discrete.c line 121
Quoted 10 lines
drivers/platform/x86/intel_skl_int3472_discrete.c new file +10
-0+ +if (obj->string.type !=ACPI_TYPE_STRING ) { +dev_err (&int3472->pdev->dev, +"Sensor _DSM returned a non-string value\n" ); + ret =ERR_PTR (-EINVAL ); + goto out_free_obj; + } + + ret =ERR_PTR (-ENODEV ); +while (i--) {
Unless there's a specific need to iterate backward over the array,
for (i = 0; i < ARRAY_SIZE(int3472_sensor_configs); ++i) {drivers/platform/x86/intel_skl_int3472_discrete.c line 124
Quoted 3 lines
drivers/platform/x86/intel_skl_int3472_discrete.c new file +3
-0+if (!strcmp (int3472_sensor_configs[i].sensor_module_name, + obj->string.pointer)) { + ret = &int3472_sensor_configs[i];
Just
break;
Quoted 4 lines
drivers/platform/x86/intel_skl_int3472_discrete.c new file +4
-0+ goto out_free_obj; + } + } +
drivers/platform/x86/intel_skl_int3472_discrete.c line 138
Quoted 10 lines
drivers/platform/x86/intel_skl_int3472_discrete.c new file +10
-0+out_free_obj: +ACPI_FREE (obj); +return ret; +} + +static int skl_int3472_map_gpio_to_sensor (struct int3472_device *int3472, +struct acpi_resource *ares, +char *func,u32 polarity) +{ +char *path = ares->data.gpio.resource_source.string_ptr;
const
drivers/platform/x86/intel_skl_int3472_discrete.c line 148
Quoted 10 lines
drivers/platform/x86/intel_skl_int3472_discrete.c new file +10
-0+struct int3472_sensor_config *sensor_config; +struct gpiod_lookup table_entry; +struct acpi_device *adev; +acpi_handle handle; +acpi_status status; +int ret; + + sensor_config =skl_int3472_get_sensor_module_config (int3472); +if (!IS_ERR (sensor_config) && sensor_config->function_maps) { +unsigned int i =0 ;
const struct int3472_gpio_function_remap *remap =
sensor_config->function_maps;
for (; remap->documented; ++remap) {
if (!strcmp(func, remap->documented)) {
func = remap->actual;drivers/platform/x86/intel_skl_int3472_discrete.c line 153
Quoted 5 lines
drivers/platform/x86/intel_skl_int3472_discrete.c new file +5
-0+ +while (sensor_config->function_maps[i].documented) { +if (!strcmp (func, sensor_config->function_maps[i].documented)) { + func = sensor_config->function_maps[i].actual; +
Extra blank line.
drivers/platform/x86/intel_skl_int3472_discrete.c line 162
Quoted 9 lines
drivers/platform/x86/intel_skl_int3472_discrete.c new file +9
-0+break ; + } + + i++; + } + } + +if (!func) +return 0 ;
I initially thought this wasn't right, as if no entry was found in the mapping table, func would still have its non-NULL value as passed to this function. I then realized that you're checking if the match that was found is NULL. A comment to explain this would be useful.
drivers/platform/x86/intel_skl_int3472_discrete.c line 167
Quoted 5 lines
drivers/platform/x86/intel_skl_int3472_discrete.c new file +5
-0+ +if (int3472->n_sensor_gpios >=INT3472_MAX_SENSOR_GPIOS ) { +dev_warn (&int3472->pdev->dev,"Too many GPIOs mapped\n" ); +return -EINVAL ; + }
You can move this to the top.
drivers/platform/x86/intel_skl_int3472_discrete.c line 179
Quoted 12 lines
drivers/platform/x86/intel_skl_int3472_discrete.c new file +12
-0+ + status =acpi_get_handle (NULL , path, &handle); +if (ACPI_FAILURE (status)) +return -EINVAL ; + + ret =acpi_bus_get_device (handle, &adev); +if (ret) +return -ENODEV ; + + table_entry = (struct gpiod_lookup )GPIO_LOOKUP_IDX (acpi_dev_name (adev), + ares->data.gpio.pin_table[0 ], + func,0 , polarity);
I wonder if
table_entry.key = acpi_dev_name(adev); table_entry.chip_hwnum = ares->data.gpio.pin_table[0]; table_entry.con_id = func; table_entry.idx = 0; table_entry.flags = polarity;
(with struct gpiod_lookup table_entry = { }; above) would be more readable. Up to you.
drivers/platform/x86/intel_skl_int3472_discrete.c line 182
Quoted 3 lines
drivers/platform/x86/intel_skl_int3472_discrete.c new file +3
-0+ +memcpy (&int3472->gpios.table[int3472->n_sensor_gpios], &table_entry, +sizeof (table_entry));
Ah, or maybe
struct gpio_lookup *table_entry; table_entry = &int3472->gpios.table[int3472->n_sensor_gpios]; table_entry->key = acpi_dev_name(adev); table_entry->chip_hwnum = ares->data.gpio.pin_table[0]; table_entry->con_id = func; table_entry->idx = 0; table_entry->flags = polarity;
(no need to memset() to 0 first as the whole structure has been allocated with kzalloc()).
drivers/platform/x86/intel_skl_int3472_discrete.c line 192
Quoted 10 lines
drivers/platform/x86/intel_skl_int3472_discrete.c new file +10
-0+ + int3472->n_sensor_gpios++; + +return 0 ; +} + +static int skl_int3472_register_clock (struct int3472_device *int3472, +struct acpi_resource *ares) +{ +char *path = ares->data.gpio.resource_source.string_ptr;
const
drivers/platform/x86/intel_skl_int3472_discrete.c line 193
Quoted 1 line
drivers/platform/x86/intel_skl_int3472_discrete.c new file +1
-0+struct clk_init_data init = { };
struct clk_init_data init = {
.ops = &skl_int3472_clock_ops,
};and drop it from below (up to you).
drivers/platform/x86/intel_skl_int3472_discrete.c line 197
Quoted 4 lines
drivers/platform/x86/intel_skl_int3472_discrete.c new file +4
-0+int ret =0 ; + + init.name =kasprintf (GFP_KERNEL ,"%s-clk" , +acpi_dev_name (int3472->adev));
You need to check for NULL and return -ENOMEM.
Quoted 10 lines
drivers/platform/x86/intel_skl_int3472_discrete.c new file +10
-0+ init.ops = &skl_int3472_clock_ops; + + int3472->clock.gpio =acpi_get_gpiod (path, + ares->data.gpio.pin_table[0 ]); +if (IS_ERR (int3472->clock.gpio)) { + ret =PTR_ERR (int3472->clock.gpio); + goto out_free_init_name; + } + + int3472->clock.clk_hw.init = &init;
drivers/platform/x86/intel_skl_int3472_discrete.c line 217
Quoted 10 lines
drivers/platform/x86/intel_skl_int3472_discrete.c new file +10
-0+ int3472->clock.clk =clk_register (&int3472->adev->dev, + &int3472->clock.clk_hw); +if (IS_ERR (int3472->clock.clk)) { + ret =PTR_ERR (int3472->clock.clk); + goto err_put_gpio; + } + + int3472->clock.cl =clkdev_create (int3472->clock.clk,"xvclk" , + int3472->sensor_name); +if (IS_ERR_OR_NULL (int3472->clock.cl))
if (!int3472->clock.cl)
as the function never return an error pointer.
drivers/platform/x86/intel_skl_int3472_discrete.c line 218
Quoted 1 line
drivers/platform/x86/intel_skl_int3472_discrete.c new file +1
-0+ goto err_unregister_clk;
If this fails, you will end up calling clk_unregister() and clkdev_drop() in skl_int3472_discrete_remove(). You should replace the check in the remove function with
if (!int3472->clock.cl) {Quoted 7 lines
drivers/platform/x86/intel_skl_int3472_discrete.c new file +7
-0+ + goto out_free_init_name; + +err_unregister_clk: +clk_unregister (int3472->clock.clk); +err_put_gpio: +gpiod_put (int3472->clock.gpio);
drivers/platform/x86/intel_skl_int3472_discrete.c line 235
Quoted 10 lines
drivers/platform/x86/intel_skl_int3472_discrete.c new file +10
-0+out_free_init_name: +kfree (init.name); + +return ret; +} + +static int skl_int3472_register_regulator (struct int3472_device *int3472, +struct acpi_resource *ares) +{ +char *path = ares->data.gpio.resource_source.string_ptr;
const
drivers/platform/x86/intel_skl_int3472_discrete.c line 242
Quoted 7 lines
drivers/platform/x86/intel_skl_int3472_discrete.c new file +7
-0+struct int3472_sensor_config *sensor_config; +struct regulator_init_data init_data = { }; +struct regulator_config cfg = { }; +int ret; + + sensor_config =skl_int3472_get_sensor_module_config (int3472); +if (IS_ERR_OR_NULL (sensor_config)) {
The function never returns NULL, you can use IS_ERR().
drivers/platform/x86/intel_skl_int3472_discrete.c line 245
Quoted 3 lines
drivers/platform/x86/intel_skl_int3472_discrete.c new file +3
-0+dev_err (&int3472->pdev->dev,"No sensor module config\n" ); +return PTR_ERR (sensor_config); + }
Would it make sense to call this in skl_int3472_discrete_probe() or skl_int3472_parse_crs() and cache the config pointer ?
drivers/platform/x86/intel_skl_int3472_discrete.c line 252
Quoted 7 lines
drivers/platform/x86/intel_skl_int3472_discrete.c new file +7
-0+ +if (!sensor_config->supply_map.supply) { +dev_err (&int3472->pdev->dev,"No supply name defined\n" ); +return -ENODEV ; + } + + init_data.supply_regulator =NULL ;
Not needed, you initialize init_data to 0 when declaring it.
drivers/platform/x86/intel_skl_int3472_discrete.c line 258
Quoted 6 lines
drivers/platform/x86/intel_skl_int3472_discrete.c new file +6
-0+ init_data.constraints.valid_ops_mask =REGULATOR_CHANGE_STATUS ; + init_data.num_consumer_supplies =1 ; + init_data.consumer_supplies = &sensor_config->supply_map; + +snprintf (int3472->regulator.regulator_name, +GPIO_REGULATOR_NAME_LENGTH ,"int3472-discrete-regulator" );
s/GPIO_REGULATOR_NAME_LENGTH/sizeof(int3472->regulator.regulator_name)/
Do regulator names need to be unique ? If so you may have a problem if a platform has two discrete INT3472.
drivers/platform/x86/intel_skl_int3472_discrete.c line 270
Quoted 12 lines
drivers/platform/x86/intel_skl_int3472_discrete.c new file +12
-0+snprintf (int3472->regulator.supply_name, +GPIO_REGULATOR_SUPPLY_NAME_LENGTH ,"supply-0" ); + + int3472->regulator.rdesc =INT3472_REGULATOR ( + int3472->regulator.regulator_name, + int3472->regulator.supply_name, + &int3472_gpio_regulator_ops); + + int3472->regulator.gpio =acpi_get_gpiod (path, + ares->data.gpio.pin_table[0 ]); +if (IS_ERR (int3472->regulator.gpio)) { +dev_err (&int3472->pdev->dev,"Failed to get GPIO line\n" );
s/GPIO line/regulator GPIO lines/ ?
Quoted 14 lines
drivers/platform/x86/intel_skl_int3472_discrete.c new file +14
-0+return PTR_ERR (int3472->regulator.gpio); + } + + cfg.dev = &int3472->adev->dev; + cfg.init_data = &init_data; + cfg.ena_gpiod = int3472->regulator.gpio; + + int3472->regulator.rdev =regulator_register (&int3472->regulator.rdesc, + &cfg); +if (IS_ERR (int3472->regulator.rdev)) { + ret =PTR_ERR (int3472->regulator.rdev); + goto err_free_gpio; + } +
drivers/platform/x86/intel_skl_int3472_discrete.c line 294
Quoted 10 lines
drivers/platform/x86/intel_skl_int3472_discrete.c new file +10
-0+return 0 ; + +err_free_gpio: +gpiod_put (int3472->regulator.gpio); + +return ret; +} + +/** +* skl_int3472_handle_gpio_resources: maps PMIC resources to consuming sensor
s/: maps/ - Map/
Quoted 29 lines
drivers/platform/x86/intel_skl_int3472_discrete.c new file +29
-0+* @ares: A pointer to a &struct acpi_resource +* @data: A pointer to a &struct int3472_device +* +* This function handles GPIO resources that are against an INT3472 +* ACPI device, by checking the value of the corresponding _DSM entry. +* This will return a 32bit int, where the lowest byte represents the +* function of the GPIO pin: +* +* 0x00 Reset +* 0x01 Power down +* 0x0b Power enable +* 0x0c Clock enable +* 0x0d Privacy LED +* +* There are some known platform specific quirks where that does not quite +* hold up; for example where a pin with type 0x01 (Power down) is mapped to +* a sensor pin that performs a reset function or entries in _CRS and _DSM that +* do not actually correspond to a physical connection. These will be handled by +* the mapping sub-functions. +* +* GPIOs will either be mapped directly to the sensor device or else used +* to create clocks and regulators via the usual frameworks. +* +* Return: +* * 0 - When all resources found are handled properly. +* * -EINVAL - If the resource is not a GPIO IO resource +* * -ENODEV - If the resource has no corresponding _DSM entry +* * -Other - Errors propagated from one of the sub-functions. +*/
drivers/platform/x86/intel_skl_int3472_discrete.c line 333
Quoted 10 lines
drivers/platform/x86/intel_skl_int3472_discrete.c new file +10
-0+static int skl_int3472_handle_gpio_resources (struct acpi_resource *ares, +void *data) +{ +struct int3472_device *int3472 = data; +union acpi_object *obj; +int ret =0 ; + +if (ares->type !=ACPI_RESOURCE_TYPE_GPIO || + ares->data.gpio.connection_type !=ACPI_RESOURCE_GPIO_TYPE_IO ) +return EINVAL ;/* Deliberately positive so parsing continues */
Maybe 1 instead of EINVAL ?
drivers/platform/x86/intel_skl_int3472_discrete.c line 346
Quoted 13 lines
drivers/platform/x86/intel_skl_int3472_discrete.c new file +13
-0+ +/* +* n_gpios + 2 because the index of this _DSM function is 1-based and +* the first function is just a count. +*/ + obj =acpi_evaluate_dsm_typed (int3472->adev->handle, + &int3472_gpio_guid,0x00 , + int3472->n_gpios +2 , +NULL ,ACPI_TYPE_INTEGER ); + +if (!obj) { +dev_warn (&int3472->pdev->dev, +"No _DSM entry for this GPIO pin\n" );
s/this GPIO pin/GPIO pin %u/
(and add the corresponding argument).
drivers/platform/x86/intel_skl_int3472_discrete.c line 347
Quoted 1 line
drivers/platform/x86/intel_skl_int3472_discrete.c new file +1
-0+return ENODEV ;
return 1;
Quoted 28 lines
drivers/platform/x86/intel_skl_int3472_discrete.c new file +28
-0+ } + +switch (obj->integer.value &0xff ) { +case INT3472_GPIO_TYPE_RESET : + ret =skl_int3472_map_gpio_to_sensor (int3472, ares,"reset" , +GPIO_ACTIVE_LOW ); +if (ret) +dev_err (&int3472->pdev->dev, +"Failed to map reset pin to sensor\n" ); + +break ; +case INT3472_GPIO_TYPE_POWERDOWN : + ret =skl_int3472_map_gpio_to_sensor (int3472, ares,"powerdown" , +GPIO_ACTIVE_LOW ); +if (ret) +dev_err (&int3472->pdev->dev, +"Failed to map powerdown pin to sensor\n" ); + +break ; +case INT3472_GPIO_TYPE_CLK_ENABLE : + ret =skl_int3472_register_clock (int3472, ares); +if (ret) +dev_err (&int3472->pdev->dev, +"Failed to map clock to sensor\n" ); + +break ; +case INT3472_GPIO_TYPE_POWER_ENABLE : + ret =skl_int3472_register_regulator (int3472, ares);
drivers/platform/x86/intel_skl_int3472_discrete.c line 385
Quoted 10 lines
drivers/platform/x86/intel_skl_int3472_discrete.c new file +10
-0+if (ret) { +dev_err (&int3472->pdev->dev, +"Failed to map regulator to sensor\n" ); + } + +break ; +case INT3472_GPIO_TYPE_PRIVACY_LED : + ret =skl_int3472_map_gpio_to_sensor (int3472, ares, +"indicator-led" , +GPIO_ACTIVE_HIGH );
Mapping the indicator LED to the sensor isn't great, as all sensor drivers would then need to handle it. Could it be handled in the regulator instead, so that it would be turned on automatically when the sensor is powered up ? Another option, more complicated, would be to handle it in the CIO2 driver (but I'm not sure how we would map it).
drivers/platform/x86/intel_skl_int3472_discrete.c line 394
Quoted 9 lines
drivers/platform/x86/intel_skl_int3472_discrete.c new file +9
-0+if (ret) +dev_err (&int3472->pdev->dev, +"Failed to map indicator led to sensor\n" ); + +break ; +default : +dev_warn (&int3472->pdev->dev, +"GPIO type 0x%llx unknown; the sensor may not work\n" , + (obj->integer.value &0xff ));
No need for parentheses.
drivers/platform/x86/intel_skl_int3472_discrete.c line 395
Quoted 1 line
drivers/platform/x86/intel_skl_int3472_discrete.c new file +1
-0+ ret =EINVAL ;
ret = 1; break;
drivers/platform/x86/intel_skl_int3472_discrete.c line 407
Quoted 12 lines
drivers/platform/x86/intel_skl_int3472_discrete.c new file +12
-0+ } + + int3472->n_gpios++; +ACPI_FREE (obj); + +return ret; +} + +static int skl_int3472_parse_crs (struct int3472_device *int3472) +{ +struct list_head resource_list; +int ret =0 ;
No need to initialize ret to 0.
drivers/platform/x86/intel_skl_int3472_discrete.c line 414
Quoted 7 lines
drivers/platform/x86/intel_skl_int3472_discrete.c new file +7
-0+ +INIT_LIST_HEAD (&resource_list); + + ret =acpi_dev_get_resources (int3472->adev, &resource_list, + skl_int3472_handle_gpio_resources, + int3472); +
You can drop this blank line.
Quoted 6 lines
drivers/platform/x86/intel_skl_int3472_discrete.c new file +6
-0+if (!ret) { +gpiod_add_lookup_table (&int3472->gpios); + int3472->gpios_mapped = true; + } + +acpi_dev_free_resource_list (&resource_list);
drivers/platform/x86/intel_skl_int3472_discrete.c line 430
Quoted 10 lines
drivers/platform/x86/intel_skl_int3472_discrete.c new file +10
-0+ +return ret; +} + +int skl_int3472_discrete_probe (struct platform_device *pdev) +{ +struct acpi_device *adev =ACPI_COMPANION (&pdev->dev); +struct int3472_device *int3472; +struct int3472_cldb cldb; +int ret =0 ;
No need to initialize ret to 0.
drivers/platform/x86/intel_skl_int3472_discrete.c line 433
Quoted 3 lines
drivers/platform/x86/intel_skl_int3472_discrete.c new file +3
-0+ + ret =skl_int3472_get_cldb_buffer (adev, &cldb); +if (ret || cldb.control_logic_type !=1 )
An error message is needed for unsupported control_logic_type values.
drivers/platform/x86/intel_skl_int3472_discrete.c line 437
Quoted 4 lines
drivers/platform/x86/intel_skl_int3472_discrete.c new file +4
-0+return -EINVAL ; + + int3472 = kzalloc(sizeof(*int3472) + + ((INT3472_MAX_SENSOR_GPIOS + 1) * sizeof(struct gpiod_lookup)),
One more space for the indentation, and the outer parentheses are not needed.
drivers/platform/x86/intel_skl_int3472_discrete.c line 449
Quoted 12 lines
drivers/platform/x86/intel_skl_int3472_discrete.c new file +12
-0+ GFP_KERNEL); +if (!int3472) +return -ENOMEM ; + + int3472->adev = adev; + int3472->pdev = pdev; +platform_set_drvdata (pdev, int3472); + + int3472->sensor =acpi_dev_get_next_dep_dev (adev,NULL ); +if (!int3472->sensor) { +dev_err (&pdev->dev, +"This INT3472 entry seems to have no dependents.\n" );
s/This INT3472 entry/INT3472/
drivers/platform/x86/intel_skl_int3472_discrete.c line 459
Quoted 10 lines
drivers/platform/x86/intel_skl_int3472_discrete.c new file +10
-0+ ret = -ENODEV ; + goto err_free_int3472; + } + int3472->sensor_name =i2c_acpi_dev_name (int3472->sensor); + int3472->gpios.dev_id = int3472->sensor_name; + + ret =skl_int3472_parse_crs (int3472); +if (ret) { +skl_int3472_discrete_remove (pdev); + goto err_return_ret;
Just
return ret;
will do.
Quoted 5 lines
drivers/platform/x86/intel_skl_int3472_discrete.c new file +5
-0+ } + +return 0 ; + +err_free_int3472:
drivers/platform/x86/intel_skl_int3472_discrete.c line 474
Quoted 10 lines
drivers/platform/x86/intel_skl_int3472_discrete.c new file +10
-0+kfree (int3472); +err_return_ret: +return ret; +} + +int skl_int3472_discrete_remove (struct platform_device *pdev) +{ +struct int3472_device *int3472; + + int3472 =platform_get_drvdata (pdev);
struct int3472_device *int3472 = platform_get_drvdata(pdev);
drivers/platform/x86/intel_skl_int3472_discrete.c line 477
Quoted 3 lines
drivers/platform/x86/intel_skl_int3472_discrete.c new file +3
-0+ +if (int3472->gpios_mapped) +gpiod_remove_lookup_table (&int3472->gpios);
You could avoid the need for the gpios_mapped field by checking for
if (int3472->gpios.list.next)
Up to you.
drivers/platform/x86/intel_skl_int3472_discrete.c line 481
Quoted 4 lines
drivers/platform/x86/intel_skl_int3472_discrete.c new file +4
-0+ +if (!IS_ERR_OR_NULL (int3472->regulator.rdev)) { +gpiod_put (int3472->regulator.gpio); +regulator_unregister (int3472->regulator.rdev);
You should call regulator_unregister(), in case unregistering the regulator tries to turn it off.
drivers/platform/x86/intel_skl_int3472_discrete.c line 487
Quoted 6 lines
drivers/platform/x86/intel_skl_int3472_discrete.c new file +6
-0+ } + +if (!IS_ERR_OR_NULL (int3472->clock.clk)) { +gpiod_put (int3472->clock.gpio); +clk_unregister (int3472->clock.clk); +clkdev_drop (int3472->clock.cl);
Same here, gpiod_put() should go last.
Quoted 38 lines
drivers/platform/x86/intel_skl_int3472_discrete.c new file +9
-0+ } + +acpi_dev_put (int3472->sensor); + +kfree (int3472->sensor_name); +kfree (int3472); + +return 0 ; +}drivers/platform/x86/intel_skl_int3472_tps68470.c new file +23
-0@@ -0,0 +1,145 @@ +// SPDX-License-Identifier: GPL-2.0 +/* Author: Dan Scally <[email protected]> */ + +#include <linux/i2c.h> +#include <linux/mfd/tps68470.h> +#include <linux/platform_device.h> +#include <linux/regmap.h> + +#include "intel_skl_int3472_common.h" + +static const struct regmap_config tps68470_regmap_config = { + .reg_bits =8 , + .val_bits =8 , + .max_register =TPS68470_REG_MAX , +}; + +static int tps68470_chip_init (struct device *dev,struct regmap *regmap) +{ +unsigned int version; +int ret; + +/* Force software reset */ + ret =regmap_write (regmap,TPS68470_REG_RESET ,TPS68470_REG_RESET_MASK );
drivers/platform/x86/intel_skl_int3472_tps68470.c line 33
Quoted 10 lines
drivers/platform/x86/intel_skl_int3472_tps68470.c new file +10
-0+if (ret) +return ret; + + ret =regmap_read (regmap,TPS68470_REG_REVID , &version); +if (ret) { +dev_err (dev,"Failed to read revision register: %d\n" , ret); +return ret; + } + +dev_info (dev,"TPS68470 REVID: 0x%x\n" , version);
0x%02x
Quoted 32 lines
drivers/platform/x86/intel_skl_int3472_tps68470.c new file +32
-0+ +return 0 ; +} + +static struct platform_device * +skl_int3472_register_pdev (const char *name,struct device *parent) +{ +struct platform_device *pdev; +int ret; + + pdev =platform_device_alloc (name,PLATFORM_DEVID_NONE ); +if (IS_ERR_OR_NULL (pdev)) +return ERR_PTR (-ENOMEM ); + + pdev->dev.parent = parent; + pdev->driver_override =kstrndup (pdev->name,INT3472_PDEV_MAX_NAME_LEN , +GFP_KERNEL ); + + ret =platform_device_add (pdev); +if (ret) { +platform_device_put (pdev); +return ERR_PTR (ret); + } + +return pdev; +} + +int skl_int3472_tps68470_probe (struct i2c_client *client) +{ +struct acpi_device *adev =ACPI_COMPANION (&client->dev); +struct platform_device *regulator_dev; +struct platform_device *opregion_dev;
drivers/platform/x86/intel_skl_int3472_tps68470.c line 75
Quoted 10 lines
drivers/platform/x86/intel_skl_int3472_tps68470.c new file +10
-0+struct platform_device *gpio_dev; +struct int3472_cldb cldb = {0 }; +struct platform_device *clk_dev; +bool cldb_present = true; +struct regmap *regmap; +int ret =0 ; + + regmap =devm_regmap_init_i2c (client, &tps68470_regmap_config); +if (IS_ERR (regmap)) { + dev_err(&client->dev, "devm_regmap_init_i2c Error %ld\n",
s/Error/error/
I'd actually write "Failed to create regmap" or something similar.
drivers/platform/x86/intel_skl_int3472_tps68470.c line 84
Quoted 9 lines
drivers/platform/x86/intel_skl_int3472_tps68470.c new file +9
-0+ PTR_ERR(regmap)); +return PTR_ERR (regmap); + } + +i2c_set_clientdata (client, regmap); + + ret =tps68470_chip_init (&client->dev, regmap); +if (ret <0 ) { +dev_err (&client->dev,"TPS68470 Init Error %d\n" , ret);
s/Init Error/init error/
Quoted 7 lines
drivers/platform/x86/intel_skl_int3472_tps68470.c new file +7
-0+return ret; + } + +/* +* Check CLDB buffer against the PMIC's adev. If present, then we check +* the value of control_logic_type field and follow one of the +* following scenarios:
drivers/platform/x86/intel_skl_int3472_tps68470.c line 101
Quoted 10 lines
drivers/platform/x86/intel_skl_int3472_tps68470.c new file +10
-0+* +* 1. No CLDB - likely ACPI tables designed for ChromeOS. We +* create platform devices for the GPIOs and OpRegion drivers. +* +* 2. CLDB, with control_logic_type = 2 - probably ACPI tables +* made for Windows 2-in-1 platforms. Register pdevs for GPIO, +* Clock and Regulator drivers to bind to. +* +* 3. Any other value in control_logic_type, we should never have +* gotten to this point; crash and burn.
Crash is a bit hard, and that's not what you do below.
drivers/platform/x86/intel_skl_int3472_tps68470.c line 104
Quoted 3 lines
drivers/platform/x86/intel_skl_int3472_tps68470.c new file +3
-0+*/ + ret =skl_int3472_get_cldb_buffer (adev, &cldb); +if (!ret && cldb.control_logic_type !=2 )
You should print an error message here (at least to catch an unsupported control_logic_type value, skl_int3472_get_cldb_buffer() errors are already logged in that function).
Quoted 21 lines
drivers/platform/x86/intel_skl_int3472_tps68470.c new file +21
-0+return -EINVAL ; + +if (ret) + cldb_present = false; + + gpio_dev =skl_int3472_register_pdev ("tps68470-gpio" , &client->dev); +if (IS_ERR (gpio_dev)) +return PTR_ERR (gpio_dev); + +if (cldb_present) { + clk_dev =skl_int3472_register_pdev ("tps68470-clk" , + &client->dev); +if (IS_ERR (clk_dev)) { + ret =PTR_ERR (clk_dev); + goto err_free_gpio; + } + + regulator_dev =skl_int3472_register_pdev ("tps68470-regulator" , + &client->dev); +if (IS_ERR (regulator_dev)) { + ret =PTR_ERR (regulator_dev);
drivers/platform/x86/intel_skl_int3472_tps68470.c line 135
Quoted 10 lines
drivers/platform/x86/intel_skl_int3472_tps68470.c new file +10
-0+ goto err_free_clk; + } + }else { + opregion_dev =skl_int3472_register_pdev ("tps68470_pmic_opregion" , + &client->dev); +if (IS_ERR (opregion_dev)) { + ret =PTR_ERR (opregion_dev); + goto err_free_gpio; + } + }
I wonder if this could be simplified by using devm_mfd_add_devices. You could have two arrays of mfd_cell, one for each case.
Quoted 10 lines
drivers/platform/x86/intel_skl_int3472_tps68470.c new file +10
-0+ +return 0 ; + +err_free_clk: +platform_device_put (clk_dev); +err_free_gpio: +platform_device_put (gpio_dev); + +return ret; +}
Signature · 3 lines
Regards, Laurent Pinchart
Re: [PATCH v2 6/7] platform: x86: Add intel_skl_int3472 driver
Quoted 1 line · Laurent Pinchart
On Mon, Jan 18, 2021 at 12:34:27AM +0000, Daniel Scally wrote:
My comments on top of Laurent's to avoid dups.
First of all, PDx86 has its own prefix pattern: "platform/x86: ..."
Quoted 11 lines
Quoted 11 lines
ACPI devices with
_HIDINT3472 are currently matched to the tps68470 driver, however this does not cover all situations in which that_HIDoccurs. We've encountered three possibilities:1. On Chrome OS devices, an ACPI device with
_HIDINT3472 (representing a physical tps68470 device) that requires a GPIO and OpRegion driver
2. On devices designed for Windows, an ACPI device with_HIDINT3472 (again representing a physical tps68470 device) which requires GPIO, Clock and Regulator drivers.
3. On other devices designed for Windows, an ACPI device with_HIDINT3472 which does NOT represent a physical tps68470, and is instead
In cover letter you are using form of "**not**", as well as in prerequisite patch series, can we be consistent with that?
tps -> TPS (same reason as Laurent put below).
Quoted 5 lines
Quoted 5 lines
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
I²C driver ?
Quoted 2 lines
Quoted 2 lines
querying the CLDB buffer found against INT3472 entries to determine which is most appropriate.
...
Quoted 1 line
Quoted 1 line
+INTEL SKL INT3472 ACPI DEVICE DRIVER
Here you may spell it in full, i.e. SKYLAKE
Quoted 3 lines
Quoted 3 lines
MAINTAINERS +3
-0+M: Daniel Scally <[email protected]> +S: Maintained +F: drivers/platform/x86/intel_skl_int3472_*
...
Quoted 3 lines
drivers/platform/x86/Kconfig config INTEL_CHT_INT33FE · line 849
Quoted 3 lines
drivers/platform/x86/Kconfig +3
-0+config INTEL_SKL_INT3472 + tristate "Intel SkyLake ACPI INT3472 Driver" + depends on X86 && ACPI
X86 is a dup. Entire lot of PDx86 is a priory dependent on it (find "if X86" line in Kconfig).
Quoted 12 lines
drivers/platform/x86/Kconfig config INTEL_CHT_INT33FE · line 856
Quoted 7 lines
drivers/platform/x86/Kconfig +7
-0+ select REGMAP_I2C + help + This driver adds support for the INT3472 ACPI devices found on some + Intel SkyLake devices. + + There are 3 kinds of INT3472 ACPI device possible; two for devices + designed for Windows (either with or without a physical tps68470I'd capitalize TPS, chip names are usually written in upper case, and driver names in lower case.
Quoted 1 line
(quoted diff) +1
-0+ PMIC) and one designed for Chrome OS.
...
Quoted 5 lines
drivers/platform/x86/Makefile obj-$(CONFIG_INTEL_HID_EVENT) += intel-hid.o · line 92
Quoted 5 lines
drivers/platform/x86/Makefile +4
-0+obj-$(CONFIG_INTEL_SKL_INT3472) += intel_skl_int3472.o +intel_skl_int3472-objs := intel_skl_int3472_common.o \ + intel_skl_int3472_discrete.o \ + intel_skl_int3472_tps68470.o
Mix of TABs and spaces detected in above two lines!
...
Quoted 3 lines
drivers/platform/x86/intel_skl_int3472_common.c line 50
Quoted 3 lines
drivers/platform/x86/intel_skl_int3472_common.c new file +3
-0+static const struct acpi_device_id int3472_device_id[] = { + {"INT3472" ,0 }, + { },
No comma for terminator entry.
Quoted 1 line
Quoted 1 line
+};
...
Quoted 7 lines
drivers/platform/x86/intel_skl_int3472_common.c line 69
Quoted 7 lines
drivers/platform/x86/intel_skl_int3472_common.c new file +7
-0+static struct i2c_driver int3472_tps68470 = { + .driver = { + .name ="int3472-tps68470" , + .acpi_match_table = int3472_device_id, + }, + .probe_new = skl_int3472_tps68470_probe, +};
I'm not sure we want to have like this. If I'm not mistaken the I²C driver can be separated without ACPI IDs (just having I²C IDs) and you may instantiate it via i2c_new_client_device() or i2c_acpi_new_device() whichever suits better...
Quoted 2 lines
drivers/platform/x86/intel_skl_int3472_common.c line 96
Quoted 2 lines
drivers/platform/x86/intel_skl_int3472_common.c new file +2
-0+module_init (skl_int3472_init); +module_exit (skl_int3472_exit);
...and this will become simple module_platfom_driver().
...
Quoted 9 lines
Quoted 1 line
+#define
INT3472_REGULATOR(_NAME, _SUPPLY, _OPS)\Macro arguments don't need to be capitalized.
drivers/platform/x86/intel_skl_int3472_common.h line 24
Quoted 5 lines
drivers/platform/x86/intel_skl_int3472_common.h new file +4
-0+ (const struct regulator_desc ) { \ + .name = _NAME, \ + .supply_name = _SUPPLY, \ + .id =0 , \
IIRC it will be 0 by standard rules.
Quoted 10 lines
drivers/platform/x86/intel_skl_int3472_common.h line 33
Quoted 10 lines
drivers/platform/x86/intel_skl_int3472_common.h new file +9
-0+ .type = REGULATOR_VOLTAGE, \ + .ops = _OPS, \ + .owner = THIS_MODULE, \ + } + +#define INT3472_GPIO_FUNCTION_REMAP (_PIN, _FUNCTION) \ + (const struct int3472_gpio_function_remap) { \ + .documented = _PIN, \ + .actual = _FUNCTION \
+ comma
Quoted 1 line
Quoted 1 line
(quoted diff) +1
-0+ }
...
Quoted 6 lines
drivers/platform/x86/intel_skl_int3472_common.h line 67
Quoted 6 lines
drivers/platform/x86/intel_skl_int3472_common.h new file +6
-0+struct int3472_gpio_clock { +struct clk *clk; +struct clk_hw clk_hw; +struct clk_lookup *cl; +struct gpio_desc *gpio; +};
Wondering if this has some similarities with and actually can utilize clk-gpio driver.
...
Quoted 4 lines
drivers/platform/x86/intel_skl_int3472_discrete.c line 49
Quoted 4 lines
drivers/platform/x86/intel_skl_int3472_discrete.c new file +4
-0+/* Lenovo Miix 510-12ISK - OV5648, Rear */ + { "GEFF150023R", REGULATOR_SUPPLY("avdd", "i2c-OVTI5648:00"), NULL}, +/* Surface Go 1&2 - OV5693, Front */ + { "YHCU", REGULATOR_SUPPLY("avdd", "i2c-INT33BE:00"), NULL},
I'm wondering if you should use same I2C format macro and create this dynamically? Or rather find a corresponding ACPI device instance and copy it's name?
...
Quoted 6 lines
drivers/platform/x86/intel_skl_int3472_discrete.c line 94
Quoted 6 lines
drivers/platform/x86/intel_skl_int3472_discrete.c new file +6
-0+static const struct clk_ops skl_int3472_clock_ops = { + .prepare = skl_int3472_clk_prepare, + .unprepare = skl_int3472_clk_unprepare, + .enable = skl_int3472_clk_enable, + .disable = skl_int3472_clk_disable, +};
Yeah, sounds like reinventing clk-gpio.c.
static const struct clk_ops clk_gpio_gate_ops = {
.enable = clk_gpio_gate_enable,
.disable = clk_gpio_gate_disable,
.is_enabled = clk_gpio_gate_is_enabled,
};
(Or is it mux? It has support there as well.
...
Quoted 21 lines
Quoted 20 lines
drivers/platform/x86/intel_skl_int3472_discrete.c new file +20
-0+static struct int3472_sensor_config * +skl_int3472_get_sensor_module_config (struct int3472_device *int3472) +{ +unsigned int i =ARRAY_SIZE (int3472_sensor_configs); +struct int3472_sensor_config *ret; +union acpi_object *obj; + + obj =acpi_evaluate_dsm_typed (int3472->sensor->handle, + &cio2_sensor_module_guid,0x00 , +0x01 ,NULL ,ACPI_TYPE_STRING ); + +if (!obj) { +dev_err (&int3472->pdev->dev, +"Failed to get sensor module string from _DSM\n" ); +return ERR_PTR (-ENODEV ); + } + +if (obj->string.type !=ACPI_TYPE_STRING ) { +dev_err (&int3472->pdev->dev, +"Sensor _DSM returned a non-string value\n" );
Quoted 2 lines
Review
Quoted 2 lines
(quoted diff) +2
-0+ ret = ERR_PTR(-EINVAL); + goto out_free_obj;
And after below change you can turn this to
ACPI_FREE(obj); return ERR_PTR(-EINVAL);
and remove label completely, but it's up to you.
Quoted 3 lines
drivers/platform/x86/intel_skl_int3472_discrete.c line 120
Quoted 3 lines
drivers/platform/x86/intel_skl_int3472_discrete.c new file +2
-0+ } + ret =ERR_PTR (-ENODEV );
This seems redundant. Or are you expecting ARRAY_SIZE() to be 0? If no, you may add static_assert() near to the array definition.
Quoted 22 lines
drivers/platform/x86/intel_skl_int3472_discrete.c line 121
Quoted 1 line
drivers/platform/x86/intel_skl_int3472_discrete.c new file +1
-0+while (i--) {Unless there's a specific need to iterate backward over the array,
for (i = 0; i < ARRAY_SIZE(int3472_sensor_configs); ++i) {drivers/platform/x86/intel_skl_int3472_discrete.c line 124
Quoted 3 lines
drivers/platform/x86/intel_skl_int3472_discrete.c new file +3
-0+if (!strcmp (int3472_sensor_configs[i].sensor_module_name, + obj->string.pointer)) { + ret = &int3472_sensor_configs[i];Just
break;Quoted 8 lines
drivers/platform/x86/intel_skl_int3472_discrete.c new file +8
-0+ goto out_free_obj; + } + } + +out_free_obj: +ACPI_FREE (obj); +return ret; +}
...
Quoted 8 lines
drivers/platform/x86/intel_skl_int3472_discrete.c line 148
Quoted 3 lines
drivers/platform/x86/intel_skl_int3472_discrete.c new file +3
-0+ sensor_config =skl_int3472_get_sensor_module_config (int3472); +if (!IS_ERR (sensor_config) && sensor_config->function_maps) { +unsigned int i =0 ;const struct int3472_gpio_function_remap *remap = sensor_config->function_maps; for (; remap->documented; ++remap) {
Post-increment in for-loops will work fine (to all Laurent's examples :-).
Quoted 17 lines
if (!strcmp(func, remap->documented)) { func = remap->actual;drivers/platform/x86/intel_skl_int3472_discrete.c line 153
Quoted 5 lines
drivers/platform/x86/intel_skl_int3472_discrete.c new file +5
-0+ +while (sensor_config->function_maps[i].documented) { +if (!strcmp (func, sensor_config->function_maps[i].documented)) { + func = sensor_config->function_maps[i].actual; +Extra blank line.
Quoted 6 lines
drivers/platform/x86/intel_skl_int3472_discrete.c new file +6
-0+break ; + } + + i++; + } + }
...
Quoted 3 lines
drivers/platform/x86/intel_skl_int3472_discrete.c line 179
Quoted 3 lines
drivers/platform/x86/intel_skl_int3472_discrete.c new file +3
-0+ table_entry = (struct gpiod_lookup )GPIO_LOOKUP_IDX (acpi_dev_name (adev), + ares->data.gpio.pin_table[0 ], + func,0 , polarity);
Agree with below. But you nay change those GPIO_LOOKUP*() macros to be compound literals in order to be used in the assignments like this.
Quoted 28 lines
I wonder if
table_entry.key = acpi_dev_name(adev); table_entry.chip_hwnum = ares->data.gpio.pin_table[0]; table_entry.con_id = func; table_entry.idx = 0; table_entry.flags = polarity;(with struct
gpiod_lookuptable_entry= { }; above) would be more readable. Up to you.drivers/platform/x86/intel_skl_int3472_discrete.c line 182
Quoted 3 lines
drivers/platform/x86/intel_skl_int3472_discrete.c new file +3
-0+ +memcpy (&int3472->gpios.table[int3472->n_sensor_gpios], &table_entry, +sizeof (table_entry));Ah, or maybe
struct gpio_lookup *table_entry; table_entry = &int3472->gpios.table[int3472->n_sensor_gpios]; table_entry->key = acpi_dev_name(adev); table_entry->chip_hwnum = ares->data.gpio.pin_table[0]; table_entry->con_id = func; table_entry->idx = 0; table_entry->flags = polarity;(no need to
memset()to 0 first as the whole structure has been allocated withkzalloc()).
...
Quoted 7 lines
drivers/platform/x86/intel_skl_int3472_discrete.c line 217
Quoted 3 lines
drivers/platform/x86/intel_skl_int3472_discrete.c new file +3
-0+ int3472->clock.cl =clkdev_create (int3472->clock.clk,"xvclk" , + int3472->sensor_name); +if (IS_ERR_OR_NULL (int3472->clock.cl))if (!int3472->clock.cl)as the function never return an error pointer.
One more time, please consider to utilize clk-gpio.c.
...
Quoted 7 lines
drivers/platform/x86/intel_skl_int3472_discrete.c line 270
Quoted 4 lines
drivers/platform/x86/intel_skl_int3472_discrete.c new file +4
-0+ int3472->regulator.gpio =acpi_get_gpiod (path, + ares->data.gpio.pin_table[0 ]); +if (IS_ERR (int3472->regulator.gpio)) { +dev_err (&int3472->pdev->dev,"Failed to get GPIO line\n" );s/GPIO line/regulator GPIO lines/ ?
Quoted 13 lines
drivers/platform/x86/intel_skl_int3472_discrete.c line 283
Quoted 13 lines
drivers/platform/x86/intel_skl_int3472_discrete.c new file +13
-0+return PTR_ERR (int3472->regulator.gpio); + } + + cfg.dev = &int3472->adev->dev; + cfg.init_data = &init_data; + cfg.ena_gpiod = int3472->regulator.gpio; + + int3472->regulator.rdev =regulator_register (&int3472->regulator.rdesc, + &cfg); +if (IS_ERR (int3472->regulator.rdev)) { + ret =PTR_ERR (int3472->regulator.rdev); + goto err_free_gpio; + }
Similar here, can we utilize gpio-regulator.c?
...
Quoted 3 lines
drivers/platform/x86/intel_skl_int3472_discrete.c line 333
Quoted 1 line
drivers/platform/x86/intel_skl_int3472_discrete.c new file +1
-0+return EINVAL ;/* Deliberately positive so parsing continues */ Maybe 1 instead of EINVAL ?
That's, i.e. 1, what we usually use in other ACPI related code like this.
...
Quoted 1 line
Review
Quoted 1 line
(quoted diff) +1
-0+ dev_warn(&int3472->pdev->dev,
Better to have struct device in the structure, you will put this on one line and derive struct platform_device from it whenever it's required by to_platform_device() call.
Quoted 5 lines
drivers/platform/x86/intel_skl_int3472_discrete.c line 346
Quoted 1 line
drivers/platform/x86/intel_skl_int3472_discrete.c new file +1
-0+ "No _DSM entry for this GPIO pin\n");s/this GPIO pin/GPIO pin %u/
(and add the corresponding argument).
...
Quoted 5 lines
drivers/platform/x86/intel_skl_int3472_discrete.c line 394
Quoted 3 lines
drivers/platform/x86/intel_skl_int3472_discrete.c new file +3
-0+dev_warn (&int3472->pdev->dev, +"GPIO type 0x%llx unknown; the sensor may not work\n" , + (obj->integer.value &0xff ));No need for parentheses.
And instead of "%llx" with " & 0xff" you may use "%x" with "(u8)" cast. However, I don't think we need to show only last byte, because it may give wrong impression on values like "0x100".
...
Quoted 4 lines
drivers/platform/x86/intel_skl_int3472_discrete.c line 433
Quoted 2 lines
drivers/platform/x86/intel_skl_int3472_discrete.c new file +2
-0+ ret =skl_int3472_get_cldb_buffer (adev, &cldb); +if (ret || cldb.control_logic_type !=1 )An error message is needed for unsupported
control_logic_typevalues.
Yeah, please split checks to two.
Quoted 1 line
Quoted 1 line
(quoted diff) +1
-0+ return -EINVAL;
...
Quoted 5 lines
drivers/platform/x86/intel_skl_int3472_discrete.c line 437
Quoted 2 lines
drivers/platform/x86/intel_skl_int3472_discrete.c new file +2
-0+ int3472 = kzalloc(sizeof(*int3472) + + ((INT3472_MAX_SENSOR_GPIOS + 1) * sizeof(struct gpiod_lookup)),One more space for the indentation, and the outer parentheses are not needed.
And use struct_size() from overflow.h.
Quoted 1 line
Quoted 1 line
(quoted diff) +1
-0+ GFP_KERNEL);
...
Quoted 6 lines
drivers/platform/x86/intel_skl_int3472_discrete.c line 477
Quoted 2 lines
drivers/platform/x86/intel_skl_int3472_discrete.c new file +2
-0+if (int3472->gpios_mapped) +gpiod_remove_lookup_table (&int3472->gpios);You could avoid the need for the
gpios_mappedfield by checking forif (int3472->gpios.list.next)
I think this is an intrusion to GPIO realm.
Instead would you consider to drop the check completely and use ->gpios to be NULL / not-NULL (and yes, you won't need gpios_mapped flag)?
d321ad1286d2 ("gpiolib: Follow usual pattern for gpiod_remove_lookup_table() call")
in I²C tree makes it possible.
...
Quoted 5 lines
Quoted 5 lines
drivers/platform/x86/intel_skl_int3472_tps68470.c new file +5
-0+static struct platform_device * +skl_int3472_register_pdev (const char *name,struct device *parent) +{ +struct platform_device *pdev; +int ret;
Quoted 8 lines
drivers/platform/x86/intel_skl_int3472_tps68470.c line 50
Quoted 8 lines
drivers/platform/x86/intel_skl_int3472_tps68470.c new file +8
-0+ + pdev =platform_device_alloc (name,PLATFORM_DEVID_NONE ); +if (IS_ERR_OR_NULL (pdev)) +return ERR_PTR (-ENOMEM ); + + pdev->dev.parent = parent; + pdev->driver_override =kstrndup (pdev->name,INT3472_PDEV_MAX_NAME_LEN , +GFP_KERNEL );
NULL check?
Quoted 8 lines
Quoted 8 lines
drivers/platform/x86/intel_skl_int3472_tps68470.c new file +8
-0+ ret =platform_device_add (pdev); +if (ret) { +platform_device_put (pdev); +return ERR_PTR (ret); + } + +return pdev; +}
...
Quoted 11 lines
Quoted 10 lines
drivers/platform/x86/intel_skl_int3472_tps68470.c new file +10
-0+int skl_int3472_tps68470_probe (struct i2c_client *client) +{ +struct acpi_device *adev =ACPI_COMPANION (&client->dev); +struct platform_device *regulator_dev; +struct platform_device *opregion_dev; +struct platform_device *gpio_dev; +struct int3472_cldb cldb = {0 }; +struct platform_device *clk_dev; +bool cldb_present = true; +struct regmap *regmap;
Quoted 1 line
Review
Quoted 1 line
(quoted diff) +1
-0+ int ret = 0;
Redundant assignment.
Quoted 74 lines
drivers/platform/x86/intel_skl_int3472_tps68470.c line 75
Quoted 3 lines
drivers/platform/x86/intel_skl_int3472_tps68470.c new file +3
-0+ regmap =devm_regmap_init_i2c (client, &tps68470_regmap_config); +if (IS_ERR (regmap)) { + dev_err(&client->dev, "devm_regmap_init_i2c Error %ld\n",s/Error/error/
I'd actually write "Failed to create regmap" or something similar.
drivers/platform/x86/intel_skl_int3472_tps68470.c line 84
Quoted 9 lines
drivers/platform/x86/intel_skl_int3472_tps68470.c new file +9
-0+ PTR_ERR(regmap)); +return PTR_ERR (regmap); + } + +i2c_set_clientdata (client, regmap); + + ret =tps68470_chip_init (&client->dev, regmap); +if (ret <0 ) { +dev_err (&client->dev,"TPS68470 Init Error %d\n" , ret);s/Init Error/init error/
Quoted 7 lines
drivers/platform/x86/intel_skl_int3472_tps68470.c new file +7
-0+return ret; + } + +/* +* Check CLDB buffer against the PMIC's adev. If present, then we check +* the value of control_logic_type field and follow one of the +* following scenarios: drivers/platform/x86/intel_skl_int3472_tps68470.c line 101
Quoted 10 lines
drivers/platform/x86/intel_skl_int3472_tps68470.c new file +10
-0+* +* 1. No CLDB - likely ACPI tables designed for ChromeOS. We +* create platform devices for the GPIOs and OpRegion drivers. +* +* 2. CLDB, with control_logic_type = 2 - probably ACPI tables +* made for Windows 2-in-1 platforms. Register pdevs for GPIO, +* Clock and Regulator drivers to bind to. +* +* 3. Any other value in control_logic_type, we should never have +* gotten to this point; crash and burn. Crash is a bit hard, and that's not what you do below.
drivers/platform/x86/intel_skl_int3472_tps68470.c line 104
Quoted 3 lines
drivers/platform/x86/intel_skl_int3472_tps68470.c new file +3
-0+*/ + ret =skl_int3472_get_cldb_buffer (adev, &cldb); +if (!ret && cldb.control_logic_type !=2 )You should print an error message here (at least to catch an unsupported
control_logic_typevalue,skl_int3472_get_cldb_buffer()errors are already logged in that function).Quoted 26 lines
drivers/platform/x86/intel_skl_int3472_tps68470.c new file +26
-0+return -EINVAL ; + +if (ret) + cldb_present = false; + + gpio_dev =skl_int3472_register_pdev ("tps68470-gpio" , &client->dev); +if (IS_ERR (gpio_dev)) +return PTR_ERR (gpio_dev); + +if (cldb_present) { + clk_dev =skl_int3472_register_pdev ("tps68470-clk" , + &client->dev); +if (IS_ERR (clk_dev)) { + ret =PTR_ERR (clk_dev); + goto err_free_gpio; + } + + regulator_dev =skl_int3472_register_pdev ("tps68470-regulator" , + &client->dev); +if (IS_ERR (regulator_dev)) { + ret =PTR_ERR (regulator_dev); + goto err_free_clk; + } + }else { + opregion_dev =skl_int3472_register_pdev ("tps68470_pmic_opregion" , + &client->dev);
Quoted 8 lines
drivers/platform/x86/intel_skl_int3472_tps68470.c line 135
Quoted 5 lines
drivers/platform/x86/intel_skl_int3472_tps68470.c new file +5
-0+if (IS_ERR (opregion_dev)) { + ret =PTR_ERR (opregion_dev); + goto err_free_gpio; + } + }I wonder if this could be simplified by using
devm_mfd_add_devices. You could have two arrays ofmfd_cell, one for each case.
Yeah, which effectively means that we should have some kind of mfd/tps68470 in place.
Quoted 9 lines
Quoted 9 lines
drivers/platform/x86/intel_skl_int3472_tps68470.c new file +9
-0+return 0 ; + +err_free_clk: +platform_device_put (clk_dev); +err_free_gpio: +platform_device_put (gpio_dev); + +return ret; +}
Signature · 2 lines
With Best Regards, Andy Shevchenko
Re: [PATCH v2 6/7] platform: x86: Add intel_skl_int3472 driver
Hi Andy - thanks as always for the comments
Some responses below, but if not mentioned I'll follow your suggestion of course
Quoted 5 lines · Andy Shevchenko
Quoted 1 line · Laurent Pinchart
On Mon, Jan 18, 2021 at 12:34:27AM +0000, Daniel Scally wrote:
My comments on top of Laurent's to avoid dups.
First of all, PDx86 has its own prefix pattern: "platform/x86: ..."
Sorry, I probably should have put more effort into figuring out the right pattern for those
Quoted 5 lines
Quoted 3 lines
drivers/platform/x86/Kconfig config INTEL_CHT_INT33FE · line 849
Quoted 3 lines
drivers/platform/x86/Kconfig +3
-0+config INTEL_SKL_INT3472 + tristate "Intel SkyLake ACPI INT3472 Driver" + depends on X86 && ACPIX86 is a dup. Entire lot of PDx86 is a priory dependent on it (find "if X86" line in
Kconfig).
Ah, oh yeah - thanks. I'll watch for that in future
Quoted 10 lines
Quoted 7 lines
drivers/platform/x86/intel_skl_int3472_common.c line 69
Quoted 7 lines
drivers/platform/x86/intel_skl_int3472_common.c new file +7
-0+static struct i2c_driver int3472_tps68470 = { + .driver = { + .name ="int3472-tps68470" , + .acpi_match_table = int3472_device_id, + }, + .probe_new = skl_int3472_tps68470_probe, +};I'm not sure we want to have like this. If I'm not mistaken the I²C driver can be separated without ACPI IDs (just having I²C IDs) and you may instantiate it via
i2c_new_client_device()ori2c_acpi_new_device()whichever suits better...
Sorry, I'm a bit confused by this. The i2c device is already present...we just want the driver to bind to them, so what role do those functions have there?
Quoted 19 lines
Quoted 6 lines
drivers/platform/x86/intel_skl_int3472_common.h line 67
Quoted 6 lines
drivers/platform/x86/intel_skl_int3472_common.h new file +6
-0+struct int3472_gpio_clock { +struct clk *clk; +struct clk_hw clk_hw; +struct clk_lookup *cl; +struct gpio_desc *gpio; +};Wondering if this has some similarities with and actually can utilize clk-gpio driver.
Quoted 6 lines
drivers/platform/x86/intel_skl_int3472_discrete.c line 94
Quoted 6 lines
drivers/platform/x86/intel_skl_int3472_discrete.c new file +6
-0+static const struct clk_ops skl_int3472_clock_ops = { + .prepare = skl_int3472_clk_prepare, + .unprepare = skl_int3472_clk_unprepare, + .enable = skl_int3472_clk_enable, + .disable = skl_int3472_clk_disable, +};Yeah, sounds like reinventing
clk-gpio.c.
Quoted 8 lines
static const struct
clk_opsclk_gpio_gate_ops= {
.enable =clk_gpio_gate_enable,
.disable =clk_gpio_gate_disable,
.is_enabled =clk_gpio_gate_is_enabled,
};(Or is it mux? It has support there as well.
Hmm, yeah, this looks like it would work actually. So I think I'd need to:
1. Make enabling INTEL_SKL_INT3472 also enable the clk-gpio driver
2. Register a platform device to bind to the clk-gpio driver
3. Register a gpio lookup table so that the clk-gpio driver can find the gpio in question using gpiod_get()
And that looks like it will work; I'll try it.
Quoted 7 lines
Quoted 4 lines
drivers/platform/x86/intel_skl_int3472_discrete.c line 49
Quoted 4 lines
drivers/platform/x86/intel_skl_int3472_discrete.c new file +4
-0+/* Lenovo Miix 510-12ISK - OV5648, Rear */ + { "GEFF150023R", REGULATOR_SUPPLY("avdd", "i2c-OVTI5648:00"), NULL}, +/* Surface Go 1&2 - OV5693, Front */ + { "YHCU", REGULATOR_SUPPLY("avdd", "i2c-INT33BE:00"), NULL},I'm wondering if you should use same I2C format macro and create this dynamically? Or rather find a corresponding ACPI device instance and copy it's name? ...
The supply name needs hard-coding really, but the device name I suppose can come from int3472->sensor_name.
Quoted 27 lines
Quoted 14 lines
Quoted 14 lines
drivers/platform/x86/intel_skl_int3472_discrete.c new file +14
-0+static struct int3472_sensor_config * +skl_int3472_get_sensor_module_config (struct int3472_device *int3472) +{ +unsigned int i =ARRAY_SIZE (int3472_sensor_configs); +struct int3472_sensor_config *ret; +union acpi_object *obj; + + obj =acpi_evaluate_dsm_typed (int3472->sensor->handle, + &cio2_sensor_module_guid,0x00 , +0x01 ,NULL ,ACPI_TYPE_STRING ); + +if (!obj) { +dev_err (&int3472->pdev->dev, +"Failed to get sensor module string from _DSM\n" );Quoted 8 lines
drivers/platform/x86/intel_skl_int3472_discrete.c line 117
Quoted 8 lines
drivers/platform/x86/intel_skl_int3472_discrete.c new file +8
-0+return ERR_PTR (-ENODEV ); + } + +if (obj->string.type !=ACPI_TYPE_STRING ) { +dev_err (&int3472->pdev->dev, +"Sensor _DSM returned a non-string value\n" ); + ret =ERR_PTR (-EINVAL ); + goto out_free_obj;And after below change you can turn this to
ACPI_FREE(obj); return ERR_PTR(-EINVAL);
Quoted 6 lines
and remove label completely, but it's up to you.
Quoted 2 lines
Review
Quoted 2 lines
(quoted diff) +2
-0+ } + ret = ERR_PTR(-ENODEV);This seems redundant. Or are you expecting
ARRAY_SIZE()to be 0? If no, you may addstatic_assert()near to the array definition.
It **could** become 0, if the entries I've added are removed in future because the sensors are no longer supported or something. There might be no sensor_module_config for a given device. We only need to supply one if
a) The platform has a 0x0b type GPIO, which means we need to define a supply name the driver is expecting
b) The GPIO functions deviate from documented purpose, which means we need to supply a remapping struct
Otherwise, there's no need for it.
Quoted 9 lines
Quoted 7 lines
drivers/platform/x86/intel_skl_int3472_discrete.c line 283
Quoted 7 lines
drivers/platform/x86/intel_skl_int3472_discrete.c new file +7
-0+ + int3472->regulator.rdev =regulator_register (&int3472->regulator.rdesc, + &cfg); +if (IS_ERR (int3472->regulator.rdev)) { + ret =PTR_ERR (int3472->regulator.rdev); + goto err_free_gpio; + }Similar here, can we utilize
gpio-regulator.c?
Also yes probably, with the same steps as for the clocks. Again, I'll try that out, thanks very much.
Quoted 7 lines
Quoted 4 lines
drivers/platform/x86/intel_skl_int3472_discrete.c line 394
Quoted 3 lines
drivers/platform/x86/intel_skl_int3472_discrete.c new file +3
-0+dev_warn (&int3472->pdev->dev, +"GPIO type 0x%llx unknown; the sensor may not work\n" , + (obj->integer.value &0xff ));No need for parentheses.
And instead of "%llx" with " &
0xff" you may use "%x" with "(u8)" cast. However, I don't think we need to show only last byte, because it may give wrong impression on values like "0x100".
But in this case only the last byte holds the type information, second lowest byte is the pin number. So as we understand it, 0x100 would be invalid anyway.
Quoted 5 lines
Quoted 4 lines
drivers/platform/x86/intel_skl_int3472_discrete.c line 437
Quoted 2 lines
drivers/platform/x86/intel_skl_int3472_discrete.c new file +2
-0+ int3472 = kzalloc(sizeof(*int3472) + + ((INT3472_MAX_SENSOR_GPIOS + 1) * sizeof(struct gpiod_lookup)),One more space for the indentation, and the outer parentheses are not needed.
And use
struct_size()fromoverflow.h.
TIL! Thank you
Quoted 4 lines
Quoted 4 lines
drivers/platform/x86/intel_skl_int3472_discrete.c line 477
Quoted 2 lines
drivers/platform/x86/intel_skl_int3472_discrete.c new file +2
-0+if (int3472->gpios_mapped) +gpiod_remove_lookup_table (&int3472->gpios);You could avoid the need for the
gpios_mappedfield by checking for
Quoted 8 lines
Quoted 1 line
if (int3472->gpios.list.next)I think this is an intrusion to GPIO realm.
Instead would you consider to drop the check completely and use ->gpios to be NULL / not-NULL (and yes, you won't needgpios_mappedflag)?
d321ad1286d2("gpiolib: Follow usual pattern forgpiod_remove_lookup_table()call")in I²C tree makes it possible.
That's also fine by me; or I guess also check int3472->gpiods.dev_id, and only set the pointer the first time a GPIO is mapped.
I'll rework it, thanks.
Quoted 33 lines
Quoted 25 lines
Quoted 25 lines
drivers/platform/x86/intel_skl_int3472_tps68470.c new file +25
-0+return -EINVAL ; + +if (ret) + cldb_present = false; + + gpio_dev =skl_int3472_register_pdev ("tps68470-gpio" , &client->dev); +if (IS_ERR (gpio_dev)) +return PTR_ERR (gpio_dev); + +if (cldb_present) { + clk_dev =skl_int3472_register_pdev ("tps68470-clk" , + &client->dev); +if (IS_ERR (clk_dev)) { + ret =PTR_ERR (clk_dev); + goto err_free_gpio; + } + + regulator_dev =skl_int3472_register_pdev ("tps68470-regulator" , + &client->dev); +if (IS_ERR (regulator_dev)) { + ret =PTR_ERR (regulator_dev); + goto err_free_clk; + } + }else { + opregion_dev = skl_int3472_register_pdev("tps68470_pmic_opregion",Quoted 8 lines
drivers/platform/x86/intel_skl_int3472_tps68470.c line 135
Quoted 6 lines
drivers/platform/x86/intel_skl_int3472_tps68470.c new file +6
-0+ &client->dev); +if (IS_ERR (opregion_dev)) { + ret =PTR_ERR (opregion_dev); + goto err_free_gpio; + } + }I wonder if this could be simplified by using
devm_mfd_add_devices. You could have two arrays ofmfd_cell, one for each case.
Quoted 2 lines
Yeah, which effectively means that we should have some kind of mfd/tps68470 in place.
Can you expand on what you mean by that a little, please?
Re: [PATCH v2 6/7] platform: x86: Add intel_skl_int3472 driver
Hi Andy, Laurent
Quoted 21 lines · Daniel Scally
Quoted 8 lines
Quoted 6 lines
drivers/platform/x86/intel_skl_int3472_discrete.c line 94
Quoted 6 lines
drivers/platform/x86/intel_skl_int3472_discrete.c new file +6
-0+static const struct clk_ops skl_int3472_clock_ops = { + .prepare = skl_int3472_clk_prepare, + .unprepare = skl_int3472_clk_unprepare, + .enable = skl_int3472_clk_enable, + .disable = skl_int3472_clk_disable, +};Yeah, sounds like reinventing
clk-gpio.c.Quoted 8 lines
static const struct
clk_opsclk_gpio_gate_ops= {
.enable =clk_gpio_gate_enable,
.disable =clk_gpio_gate_disable,
.is_enabled =clk_gpio_gate_is_enabled,
};(Or is it mux? It has support there as well.
Hmm, yeah, this looks like it would work actually. So I think I'd need to:
1. Make enabling
INTEL_SKL_INT3472also enable the clk-gpio driver
Quoted 7 lines
2. Register a platform device to bind to the clk-gpio driver
3. Register a gpio lookup table so that the clk-gpio driver can find the gpio in question using
gpiod_get()And that looks like it will work; I'll try it.
I'm more and more confident that this will work, but it has some knock-on effects:
The both clk and regulator gpio driver expects to be able to fetch the GPIO using devm_gpiod_get(&pdev->dev, "enable", ...). That won't work of course, so we need to add another GPIO lookup table so those drivers can see the GPIOs. For that, we need to know what dev_name(&pdev->dev) will be so we can set the .dev_id member of a gpiod_lookup_table to that value, but that isn't set until _after_ the pdev is registered (because it has to figure out the id, we can't manually set the IDs because there could be more than one instance of int3472-discrete bound to multiple PMIC devices, and we don't know which id the current one should have). Finally, we can't wait until the device is registered because it immediately probes, can't find the GPIO and then fails probe.
It's similar problem that causes us to need the i2c-acpi name format macros, but complicated by the dynamic ID part of dev_name(&pdev->dev)
Solving it is a bit of a sticky one; perhaps something like moving the dev_set_name() part of platform_device_add() [1] to its own function, that's called in both platform_device_alloc() and platform_device_register(). That way it would be available before the device itself was registered, meaning we could create the lookup table before it probes the driver.
(also, Laurent, if we did it this way we wouldn't be able to also handle the led-indicator GPIO here without some fairly major rework)
[1]
https://elixir.bootlin.com/linux/latest/source/drivers/base/platform.c#L563
Re: [PATCH v2 6/7] platform: x86: Add intel_skl_int3472 driver
Hi Daniel,
Quoted 54 lines · Daniel Scally
Quoted 19 lines · Daniel Scally
Quoted 9 lines
Quoted 6 lines
drivers/platform/x86/intel_skl_int3472_discrete.c line 94
Quoted 6 lines
drivers/platform/x86/intel_skl_int3472_discrete.c new file +6
-0+static const struct clk_ops skl_int3472_clock_ops = { + .prepare = skl_int3472_clk_prepare, + .unprepare = skl_int3472_clk_unprepare, + .enable = skl_int3472_clk_enable, + .disable = skl_int3472_clk_disable, +};Yeah, sounds like reinventing
clk-gpio.c.Quoted 8 lines
static const struct
clk_opsclk_gpio_gate_ops= {
.enable =clk_gpio_gate_enable,
.disable =clk_gpio_gate_disable,
.is_enabled =clk_gpio_gate_is_enabled,
};(Or is it mux? It has support there as well.
Hmm, yeah, this looks like it would work actually. So I think I'd need to:
Quoted 8 lines
1. Make enabling
INTEL_SKL_INT3472also enable the clk-gpio driver2. Register a platform device to bind to the clk-gpio driver
3. Register a gpio lookup table so that the clk-gpio driver can find the gpio in question using
gpiod_get()And that looks like it will work; I'll try it.
I'm more and more confident that this will work, but it has some knock-on effects:
The both clk and regulator gpio driver expects to be able to fetch the GPIO using
devm_gpiod_get(&pdev->dev, "enable", ...). That won't work of course, so we need to add another GPIO lookup table so those drivers can see the GPIOs. For that, we need to know whatdev_name(&pdev->dev)will be so we can set the .dev_id member of agpiod_lookup_tableto that value, but that isn't set until _after_ the pdev is registered (because it has to figure out the id, we can't manually set the IDs because there could be more than one instance of int3472-discrete bound to multiple PMIC devices, and we don't know which id the current one should have). Finally, we can't wait until the device is registered because it immediately probes, can't find the GPIO and then fails probe.It's similar problem that causes us to need the i2c-acpi name format macros, but complicated by the dynamic ID part of
dev_name(&pdev->dev)Solving it is a bit of a sticky one; perhaps something like moving the
dev_set_name()part ofplatform_device_add()[1] to its own function, that's called in bothplatform_device_alloc()andplatform_device_register(). That way it would be available before the device itself was registered, meaning we could create the lookup table before it probes the driver.
Quoted 2 lines
(also, Laurent, if we did it this way we wouldn't be able to also handle the led-indicator GPIO here without some fairly major rework)
Given the additional complexity I don't think it's worth it, your implementation is fine and code duplication with clk-gpio is minimal.
Signature · 3 lines
Regards, Laurent Pinchart
Re: [PATCH v2 6/7] platform: x86: Add intel_skl_int3472 driver
Quoted 2 lines · Laurent Pinchart
Quoted 1 line · Daniel Scally
On 18/01/2021 21:19, Daniel Scally wrote:
...
Quoted 5 lines
Quoted 2 lines
(also, Laurent, if we did it this way we wouldn't be able to also handle the led-indicator GPIO here without some fairly major rework)
Given the additional complexity I don't think it's worth it, your implementation is fine and code duplication with clk-gpio is minimal.
Making clk-gpio.c available as a library is a win in long term and reduces a possible duplication by others in the future. I bet we even might find already clk-gpio parts in some drivers.
Signature · 2 lines
With Best Regards, Andy Shevchenko
Re: [PATCH v2 6/7] platform: x86: Add intel_skl_int3472 driver
Quoted 9 lines · Andy Shevchenko
Quoted 2 lines · Laurent Pinchart
Quoted 1 line · Daniel Scally
On 18/01/2021 21:19, Daniel Scally wrote:
...
Quoted 3 lines
Quoted 2 lines
(also, Laurent, if we did it this way we wouldn't be able to also handle the led-indicator GPIO here without some fairly major rework)
Quoted 6 lines
Quoted 2 lines
Given the additional complexity I don't think it's worth it, your implementation is fine and code duplication with clk-gpio is minimal.
Making
clk-gpio.cavailable as a library is a win in long term and reduces a possible duplication by others in the future. I bet we even might find already clk-gpio parts in some drivers.
How about you submit a patch on top then ? :-) Let's avoid yak shaving.
Signature · 3 lines
Regards, Laurent Pinchart
Re: [PATCH v2 6/7] platform: x86: Add intel_skl_int3472 driver
In reply to Daniel ScallyQuoted 20 lines · Daniel Scally
On 18/01/2021 21:19, Daniel Scally wrote:
I'm more and more confident that this will work, but it has some knock-on effects:
The both clk and regulator gpio driver expects to be able to fetch the GPIO using
devm_gpiod_get(&pdev->dev, "enable", ...). That won't work of course, so we need to add another GPIO lookup table so those drivers can see the GPIOs. For that, we need to know whatdev_name(&pdev->dev)will be so we can set the .dev_id member of agpiod_lookup_tableto that value, but that isn't set until _after_ the pdev is registered (because it has to figure out the id, we can't manually set the IDs because there could be more than one instance of int3472-discrete bound to multiple PMIC devices, and we don't know which id the current one should have). Finally, we can't wait until the device is registered because it immediately probes, can't find the GPIO and then fails probe.It's similar problem that causes us to need the i2c-acpi name format macros, but complicated by the dynamic ID part of
dev_name(&pdev->dev)
Quoted 6 lines
Solving it is a bit of a sticky one; perhaps something like moving the
dev_set_name()part ofplatform_device_add()[1] to its own function, that's called in bothplatform_device_alloc()andplatform_device_register(). That way it would be available before the device itself was registered, meaning we could create the lookup table before it probes the driver.
See my previous reply. TL;DR: you have to modify clk-gpio.c to export couple of methods to be able to use it as a library.
Quoted 2 lines
(also, Laurent, if we did it this way we wouldn't be able to also handle the led-indicator GPIO here without some fairly major rework)
LED indicators are done as LED class devices (see plenty of examples in PDx86
drivers: drivers/platform/x86/)
Signature · 2 lines
With Best Regards, Andy Shevchenko
Re: [PATCH v2 6/7] platform: x86: Add intel_skl_int3472 driver
Morning Andy
Quoted 20 lines · Andy Shevchenko
Quoted 19 lines · Daniel Scally
On 18/01/2021 21:19, Daniel Scally wrote:
I'm more and more confident that this will work, but it has some knock-on effects:The both clk and regulator gpio driver expects to be able to fetch the GPIO using
devm_gpiod_get(&pdev->dev, "enable", ...). That won't work of course, so we need to add another GPIO lookup table so those drivers can see the GPIOs. For that, we need to know whatdev_name(&pdev->dev)will be so we can set the .dev_id member of agpiod_lookup_tableto that value, but that isn't set until _after_ the pdev is registered (because it has to figure out the id, we can't manually set the IDs because there could be more than one instance of int3472-discrete bound to multiple PMIC devices, and we don't know which id the current one should have). Finally, we can't wait until the device is registered because it immediately probes, can't find the GPIO and then fails probe.It's similar problem that causes us to need the i2c-acpi name format macros, but complicated by the dynamic ID part of
dev_name(&pdev->dev)
Quoted 8 lines
Quoted 6 lines
Solving it is a bit of a sticky one; perhaps something like moving the
dev_set_name()part ofplatform_device_add()[1] to its own function, that's called in bothplatform_device_alloc()andplatform_device_register(). That way it would be available before the device itself was registered, meaning we could create the lookup table before it probes the driver.See my previous reply. TL;DR: you have to modify
clk-gpio.cto export couple of methods to be able to use it as a library.
Ack! Ok, I thought about that the wrong way. I'll take another look tonight then.
Quoted 4 lines
Quoted 2 lines
(also, Laurent, if we did it this way we wouldn't be able to also handle the led-indicator GPIO here without some fairly major rework)
LED indicators are done as LED class devices (see plenty of examples in PDx86
drivers:drivers/platform/x86/)
And this too - thanks very much
Re: [PATCH v2 6/7] platform: x86: Add intel_skl_int3472 driver
In reply to Andy ShevchenkoHi Andy,
Quoted 28 lines · Andy Shevchenko
Quoted 20 lines · Daniel Scally
On 18/01/2021 21:19, Daniel Scally wrote:
I'm more and more confident that this will work, but it has some knock-on effects:
The both clk and regulator gpio driver expects to be able to fetch the GPIO using
devm_gpiod_get(&pdev->dev, "enable", ...). That won't work of course, so we need to add another GPIO lookup table so those drivers can see the GPIOs. For that, we need to know whatdev_name(&pdev->dev)will be so we can set the .dev_id member of agpiod_lookup_tableto that value, but that isn't set until _after_ the pdev is registered (because it has to figure out the id, we can't manually set the IDs because there could be more than one instance of int3472-discrete bound to multiple PMIC devices, and we don't know which id the current one should have). Finally, we can't wait until the device is registered because it immediately probes, can't find the GPIO and then fails probe.It's similar problem that causes us to need the i2c-acpi name format macros, but complicated by the dynamic ID part of
dev_name(&pdev->dev)Quoted 6 lines
Solving it is a bit of a sticky one; perhaps something like moving the
dev_set_name()part ofplatform_device_add()[1] to its own function, that's called in bothplatform_device_alloc()andplatform_device_register(). That way it would be available before the device itself was registered, meaning we could create the lookup table before it probes the driver.
Quoted 2 lines
See my previous reply. TL;DR: you have to modify
clk-gpio.cto export couple of methods to be able to use it as a library.
That seems really overkill given the very simple implementation of the clock provided here.
Quoted 5 lines
Quoted 2 lines
(also, Laurent, if we did it this way we wouldn't be able to also handle the led-indicator GPIO here without some fairly major rework)
LED indicators are done as LED class devices (see plenty of examples in PDx86
drivers:drivers/platform/x86/)
How do you expose the link between the sensor and its indicator LED to userspace ? Isn't it better to handle it in the kernel to avoid rogue userspace turning the camera on without notifying the user ?
Signature · 3 lines
Regards, Laurent Pinchart
Re: [PATCH v2 6/7] platform: x86: Add intel_skl_int3472 driver
Quoted 3 lines · Laurent Pinchart
Quoted 2 lines · Andy Shevchenko
Quoted 1 line · Daniel Scally
On 18/01/2021 21:19, Daniel Scally wrote:
...
Quoted 5 lines
Quoted 2 lines
See my previous reply. TL;DR: you have to modify
clk-gpio.cto export couple of methods to be able to use it as a library.That seems really overkill given the very simple implementation of the clock provided here.
Less code in the end is called an overkill? Hmm...
I think since we in Linux it's better to utilize what it provides. Do you want me to prepare a patch to show that there is no overkill at all?
...
Quoted 9 lines
Quoted 5 lines
Quoted 2 lines
(also, Laurent, if we did it this way we wouldn't be able to also handle the led-indicator GPIO here without some fairly major rework)
LED indicators are done as LED class devices (see plenty of examples in PDx86
drivers:drivers/platform/x86/)How do you expose the link between the sensor and its indicator LED to userspace ? Isn't it better to handle it in the kernel to avoid rogue userspace turning the camera on without notifying the user ?
I didn't get this. It's completely a LED handling driver business. We may expose it to user space or not, but it's orthogonal to the usage of LED class IIUC. Am I mistaken here?
Signature · 2 lines
With Best Regards, Andy Shevchenko
Re: [PATCH v2 6/7] platform: x86: Add intel_skl_int3472 driver
Hi Andy,
Quoted 10 lines · Andy Shevchenko
Quoted 3 lines · Laurent Pinchart
Quoted 2 lines · Andy Shevchenko
Quoted 1 line · Daniel Scally
On 18/01/2021 21:19, Daniel Scally wrote:
...
Quoted 3 lines
Quoted 2 lines
See my previous reply. TL;DR: you have to modify
clk-gpio.cto export couple of methods to be able to use it as a library.
Quoted 6 lines
Quoted 2 lines
That seems really overkill given the very simple implementation of the clock provided here.
Less code in the end is called an overkill? Hmm...
I think since we in Linux it's better to utilize what it provides. Do you want me to prepare a patch to show that there is no overkill at all?
The amount of code we would save it very small. It's not necessarily a bad idea, but I think such an improvement could be made on top, it shouldn't block this series.
Quoted 8 lines
...
Quoted 6 lines
Quoted 5 lines
Quoted 2 lines
(also, Laurent, if we did it this way we wouldn't be able to also handle the led-indicator GPIO here without some fairly major rework)
LED indicators are done as LED class devices (see plenty of examples in PDx86
drivers:drivers/platform/x86/)
Quoted 7 lines
Quoted 3 lines
How do you expose the link between the sensor and its indicator LED to userspace ? Isn't it better to handle it in the kernel to avoid rogue userspace turning the camera on without notifying the user ?
I didn't get this. It's completely a LED handling driver business. We may expose it to user space or not, but it's orthogonal to the usage of LED class IIUC. Am I mistaken here?
If it stays internal to the kernel and is solely controlled from the int3472 driver, there's no need to involve the LED class. If we want to expose the privacy LED to userspace then the LED framework is the way to go, but we will also need to find a way to expose the link between the camera sensor and the LED to userspace. If there are two privacy LEDs, one for the front sensor and one for the back sensor, userspace will need to know which is which.
Signature · 3 lines
Regards, Laurent Pinchart
Re: [PATCH v2 6/7] platform: x86: Add intel_skl_int3472 driver
Quoted 5 lines · Laurent Pinchart
Quoted 4 lines · Andy Shevchenko
Quoted 3 lines · Laurent Pinchart
Quoted 2 lines · Andy Shevchenko
Quoted 1 line · Daniel Scally
On 18/01/2021 21:19, Daniel Scally wrote:
...
Quoted 6 lines
Quoted 6 lines
Quoted 5 lines
Quoted 2 lines
See my previous reply. TL;DR: you have to modify
clk-gpio.cto export couple of methods to be able to use it as a library.That seems really overkill given the very simple implementation of the clock provided here.
Quoted 7 lines
Quoted 3 lines
Less code in the end is called an overkill? Hmm...
I think since we in Linux it's better to utilize what it provides. Do you want me to prepare a patch to show that there is no overkill at all?The amount of code we would save it very small. It's not necessarily a bad idea, but I think such an improvement could be made on top, it shouldn't block this series.
Okay, let's wait what Dan will say on this.
I can probably help to achieve this improvement sooner than later.
...
Quoted 14 lines
Quoted 6 lines
Quoted 6 lines
Quoted 5 lines
Quoted 2 lines
(also, Laurent, if we did it this way we wouldn't be able to also handle the led-indicator GPIO here without some fairly major rework)
LED indicators are done as LED class devices (see plenty of examples in PDx86
drivers:drivers/platform/x86/)Quoted 7 lines
Quoted 3 lines
How do you expose the link between the sensor and its indicator LED to userspace ? Isn't it better to handle it in the kernel to avoid rogue userspace turning the camera on without notifying the user ?
I didn't get this. It's completely a LED handling driver business. We may expose it to user space or not, but it's orthogonal to the usage of LED class IIUC. Am I mistaken here?
Quoted 7 lines
If it stays internal to the kernel and is solely controlled from the int3472 driver, there's no need to involve the LED class. If we want to expose the privacy LED to userspace then the LED framework is the way to go, but we will also need to find a way to expose the link between the camera sensor and the LED to userspace. If there are two privacy LEDs, one for the front sensor and one for the back sensor, userspace will need to know which is which.
I see. For now we probably can keep GPIO LED implementation internally.
Signature · 2 lines
With Best Regards, Andy Shevchenko
Re: [PATCH v2 6/7] platform: x86: Add intel_skl_int3472 driver
Hi both
Quoted 12 lines · Andy Shevchenko
Quoted 5 lines · Laurent Pinchart
Quoted 4 lines · Andy Shevchenko
Quoted 3 lines · Laurent Pinchart
Quoted 2 lines · Andy Shevchenko
Quoted 1 line · Daniel Scally
On 18/01/2021 21:19, Daniel Scally wrote:
...
Quoted 4 lines
Quoted 4 lines
Quoted 4 lines
Quoted 2 lines
See my previous reply. TL;DR: you have to modify
clk-gpio.cto export couple of methods to be able to use it as a library.That seems really overkill given the very simple implementation of the clock provided here.
Quoted 8 lines
Quoted 6 lines
Quoted 3 lines
Less code in the end is called an overkill? Hmm...
I think since we in Linux it's better to utilize what it provides. Do you want me to prepare a patch to show that there is no overkill at all?The amount of code we would save it very small. It's not necessarily a bad idea, but I think such an improvement could be made on top, it shouldn't block this series.
Okay, let's wait what Dan will say on this.
I can probably help to achieve this improvement sooner than later.
Well; turns out that we missed an operation we really need to add (clk_recalc_rate) which in our case needs to read a fixed value stored in a buffer in ACPI; most of the code is shared with an existing function in the driver so it's not much extra to add, but I think it kinda precludes using clk-gpio for this anyway
Quoted 19 lines
Quoted 10 lines
Quoted 10 lines
Quoted 7 lines
Quoted 4 lines
Quoted 2 lines
(also, Laurent, if we did it this way we wouldn't be able to also handle the led-indicator GPIO here without some fairly major rework)
LED indicators are done as LED class devices (see plenty of examples in PDx86
drivers:drivers/platform/x86/)How do you expose the link between the sensor and its indicator LED to userspace ? Isn't it better to handle it in the kernel to avoid rogue userspace turning the camera on without notifying the user ?
I didn't get this. It's completely a LED handling driver business. We may expose it to user space or not, but it's orthogonal to the usage of LED class IIUC. Am I mistaken here?
Quoted 7 lines
If it stays internal to the kernel and is solely controlled from the int3472 driver, there's no need to involve the LED class. If we want to expose the privacy LED to userspace then the LED framework is the way to go, but we will also need to find a way to expose the link between the camera sensor and the LED to userspace. If there are two privacy LEDs, one for the front sensor and one for the back sensor, userspace will need to know which is which.
I see. For now we probably can keep GPIO LED implementation internally.
Re: [PATCH v2 6/7] platform: x86: Add intel_skl_int3472 driver
In reply to Daniel ScallyQuoted 3 lines · Daniel Scally
Quoted 2 lines · Andy Shevchenko
Quoted 1 line · Laurent Pinchart
On Mon, Jan 18, 2021 at 12:34:27AM +0000, Daniel Scally wrote:
...
Quoted 11 lines
Quoted 10 lines
Quoted 7 lines
drivers/platform/x86/intel_skl_int3472_common.c line 69
Quoted 7 lines
drivers/platform/x86/intel_skl_int3472_common.c new file +7
-0+static struct i2c_driver int3472_tps68470 = { + .driver = { + .name ="int3472-tps68470" , + .acpi_match_table = int3472_device_id, + }, + .probe_new = skl_int3472_tps68470_probe, +};I'm not sure we want to have like this. If I'm not mistaken the I²C driver can be separated without ACPI IDs (just having I²C IDs) and you may instantiate it via
i2c_new_client_device()ori2c_acpi_new_device()whichever suits better...
Quoted 3 lines
Sorry, I'm a bit confused by this. The i2c device is already present...we just want the driver to bind to them, so what role do those functions have there?
What I meant is something like
*_i2c.c
real I²C driver for the TPS chip, but solely with I²C ID table, no ACPI involved (and it sounds like it should be mfd/tps one, in which you just cut out ACPI IDs and convert to pure I²C one, that what I had suggested in the first place)
*_proxy.c
GPIO proxy as library
*.c
platform driver with ACPI ID, in which ->probe() we actually instantiate above via calling i2c_acpi_new_device(), *if needed*, along with GPIO proxy
...
Quoted 29 lines
Quoted 18 lines
Quoted 7 lines
Quoted 6 lines
drivers/platform/x86/intel_skl_int3472_common.h new file +6
-0+struct int3472_gpio_clock { +struct clk *clk; +struct clk_hw clk_hw; +struct clk_lookup *cl; +struct gpio_desc *gpio; +};Quoted 6 lines
drivers/platform/x86/intel_skl_int3472_discrete.c line 94
Quoted 6 lines
drivers/platform/x86/intel_skl_int3472_discrete.c new file +6
-0+static const struct clk_ops skl_int3472_clock_ops = { + .prepare = skl_int3472_clk_prepare, + .unprepare = skl_int3472_clk_unprepare, + .enable = skl_int3472_clk_enable, + .disable = skl_int3472_clk_disable, +};Wondering if this has some similarities with and actually can utilize clk-gpio driver.
Yeah, sounds like reinventingclk-gpio.c.Quoted 8 lines
static const struct
clk_opsclk_gpio_gate_ops= {
.enable =clk_gpio_gate_enable,
.disable =clk_gpio_gate_disable,
.is_enabled =clk_gpio_gate_is_enabled,
};Or is it mux? It has support there as well.
Hmm, yeah, this looks like it would work actually. So I think I'd need to:
Quoted 8 lines
1. Make enabling
INTEL_SKL_INT3472also enable the clk-gpio driver2. Register a platform device to bind to the clk-gpio driver
3. Register a gpio lookup table so that the clk-gpio driver can find the gpio in question using
gpiod_get()And that looks like it will work; I'll try it.
You need to modify clk-gpio.c to export
clk_hw_register_gpio_gate()clk_hw_register_gpio_mux()
(perhaps it will require to add *_unregister() counterparts) and call it from your code.
See, for example, how clk_hw_unregister_fixed_rate() is being used. Another case is to add a helper directly into clk-gpio and call it instead of clk_hw_*() one, see how clk_register_fractional_divider() is implemented and used.
...
Quoted 10 lines
Quoted 7 lines
Quoted 4 lines
drivers/platform/x86/intel_skl_int3472_discrete.c line 49
Quoted 4 lines
drivers/platform/x86/intel_skl_int3472_discrete.c new file +4
-0+/* Lenovo Miix 510-12ISK - OV5648, Rear */ + { "GEFF150023R", REGULATOR_SUPPLY("avdd", "i2c-OVTI5648:00"), NULL}, +/* Surface Go 1&2 - OV5693, Front */ + { "YHCU", REGULATOR_SUPPLY("avdd", "i2c-INT33BE:00"), NULL},I'm wondering if you should use same I2C format macro and create this dynamically? Or rather find a corresponding ACPI device instance and copy it's name? ...
The supply name needs hard-coding really, but the device name I suppose can come from
int3472->sensor_name.
To be strict in terms you are using "device instance name" in the REGULATOR_SUPPLY() second parameter. Because "device name" is generic and doesn't point to the actual *instance* of the device in the system.
So, and "device name instance" we may get only by traversing through the (ACPI) bus and find corresponding struct device and derive name from it. Same way like you have done in previous patch series.
Because there is no guarantee that, e.g., i2c-INT33BE:00 will be present on the system and moreover there is no guarantee that if two INT33BE or more devices are present you will get :00 always for the one you need!
...
Quoted 8 lines
Quoted 3 lines
Quoted 1 line
drivers/platform/x86/intel_skl_int3472_discrete.c line 120
Quoted 1 line
drivers/platform/x86/intel_skl_int3472_discrete.c new file +1
-0+ ret =ERR_PTR (-ENODEV );This seems redundant. Or are you expecting
ARRAY_SIZE()to be 0? If no, you may addstatic_assert()near to the array definition.It **could** become 0, if the entries I've added are removed in future because the sensors are no longer supported or something. There might be no
sensor_module_configfor a given device. We only need to supply one if
Quoted 7 lines
a) The platform has a
0x0btype GPIO, which means we need to define a supply name the driver is expectingb) The GPIO functions deviate from documented purpose, which means we need to supply a remapping struct
Otherwise, there's no need for it.
I see. So, up to you then.
Quoted 12 lines
Quoted 11 lines
Quoted 9 lines
drivers/platform/x86/intel_skl_int3472_discrete.c line 283
Quoted 9 lines
drivers/platform/x86/intel_skl_int3472_discrete.c new file +7
-0+ + int3472->regulator.rdev =regulator_register (&int3472->regulator.rdesc, + &cfg); +if (IS_ERR (int3472->regulator.rdev)) { + ret =PTR_ERR (int3472->regulator.rdev); + goto err_free_gpio; + }Similar here, can we utilize
gpio-regulator.c?
Quoted 2 lines
Also yes probably, with the same steps as for the clocks. Again, I'll try that out, thanks very much.
You may look at arch/x86/platform/intel-mid/device_libs/platform_bcm43xx.c (but in your case you probably don't need a GPIO lookup table, just check).
...
Quoted 11 lines
Quoted 7 lines
Quoted 4 lines
drivers/platform/x86/intel_skl_int3472_discrete.c line 394
Quoted 3 lines
drivers/platform/x86/intel_skl_int3472_discrete.c new file +3
-0+dev_warn (&int3472->pdev->dev, +"GPIO type 0x%llx unknown; the sensor may not work\n" , + (obj->integer.value &0xff ));No need for parentheses.
And instead of "%llx" with " &
0xff" you may use "%x" with "(u8)" cast. However, I don't think we need to show only last byte, because it may give wrong impression on values like "0x100".But in this case only the last byte holds the type information, second lowest byte is the pin number. So as we understand it,
0x100would be invalid anyway.
Ah, indeed. So, I think the best is to have %hhx and see if you can supply just obj->integer.value and compiler won't warn about type mismatch.
...
Quoted 10 lines
Quoted 10 lines
Quoted 10 lines
drivers/platform/x86/intel_skl_int3472_tps68470.c line 135
Quoted 8 lines
drivers/platform/x86/intel_skl_int3472_tps68470.c new file +8
-0+ }else { + opregion_dev =skl_int3472_register_pdev ("tps68470_pmic_opregion" , + &client->dev); +if (IS_ERR (opregion_dev)) { + ret =PTR_ERR (opregion_dev); + goto err_free_gpio; + } + }I wonder if this could be simplified by using
devm_mfd_add_devices. You could have two arrays ofmfd_cell, one for each case.
Quoted 4 lines
Quoted 2 lines
Yeah, which effectively means that we should have some kind of mfd/tps68470 in place.
Can you expand on what you mean by that a little, please?
The very first comment in this reply should hopefully shed a light on my idea.
Signature · 2 lines
With Best Regards, Andy Shevchenko
Re: [PATCH v2 6/7] platform: x86: Add intel_skl_int3472 driver
Quoted 13 lines · Andy Shevchenko
Quoted 10 lines
Quoted 10 lines
Quoted 7 lines
drivers/platform/x86/intel_skl_int3472_common.c line 69
Quoted 7 lines
drivers/platform/x86/intel_skl_int3472_common.c new file +7
-0+static struct i2c_driver int3472_tps68470 = { + .driver = { + .name ="int3472-tps68470" , + .acpi_match_table = int3472_device_id, + }, + .probe_new = skl_int3472_tps68470_probe, +};I'm not sure we want to have like this. If I'm not mistaken the I²C driver can be separated without ACPI IDs (just having I²C IDs) and you may instantiate it via
i2c_new_client_device()ori2c_acpi_new_device()whichever suits better...Quoted 3 lines
Sorry, I'm a bit confused by this. The i2c device is already present...we just want the driver to bind to them, so what role do those functions have there?
Quoted 7 lines
What I meant is something like
*_i2c.c
real I²C driver for the TPS chip, but solely with I²C ID table, no ACPI involved (and it sounds like it should be mfd/tps one, in which you just cut out ACPI IDs and convert to pure I²C one, that what I had suggested in the first place)
Ahh; sorry - i misunderstood what you meant there. I understand now I think, but there is one complication; the ACPI subsystem already creates a client for that i2c adapter and address; i2c_new_client_device() includes a check to see whether that adapter / address combination has an i2c device already. So we would have to have the platform driver with ACPI ID first find the existing i2c_client and unregister it before registering the new one...the existing clients have a name matching the ACPI device instance name (e.g i2c-INT3472:00) which we can't use as an i2c_device_id of course.
Quoted 51 lines
*_proxy.c
GPIO proxy as library*.c
platform driver with ACPI ID, in which ->probe() we actually instantiate above via calling i2c_acpi_new_device(), *if needed*, along with GPIO proxy...
Quoted 27 lines
Quoted 16 lines
Quoted 4 lines
Quoted 4 lines
drivers/platform/x86/intel_skl_int3472_common.h new file +4
-0+struct int3472_gpio_clock { +struct clk *clk; +struct clk_hw clk_hw; +struct clk_lookup *cl;Quoted 8 lines
drivers/platform/x86/intel_skl_int3472_discrete.c line 94
Quoted 8 lines
drivers/platform/x86/intel_skl_int3472_discrete.c new file +8
-0+struct gpio_desc *gpio; +}; +static const struct clk_ops skl_int3472_clock_ops = { + .prepare = skl_int3472_clk_prepare, + .unprepare = skl_int3472_clk_unprepare, + .enable = skl_int3472_clk_enable, + .disable = skl_int3472_clk_disable, +};Wondering if this has some similarities with and actually can utilize clk-gpio driver.
Yeah, sounds like reinventingclk-gpio.c.Quoted 8 lines
static const struct
clk_opsclk_gpio_gate_ops= {
.enable =clk_gpio_gate_enable,
.disable =clk_gpio_gate_disable,
.is_enabled =clk_gpio_gate_is_enabled,
};Or is it mux? It has support there as well.
Hmm, yeah, this looks like it would work actually. So I think I'd need to:
Quoted 8 lines
1. Make enabling
INTEL_SKL_INT3472also enable the clk-gpio driver2. Register a platform device to bind to the clk-gpio driver
3. Register a gpio lookup table so that the clk-gpio driver can find the gpio in question using
gpiod_get()And that looks like it will work; I'll try it.
You need to modify
clk-gpio.cto export
clk_hw_register_gpio_gate()clk_hw_register_gpio_mux()
Quoted 7 lines
(perhaps it will require to add
*_unregister()counterparts) and call it from your code.See, for example, how
clk_hw_unregister_fixed_rate()is being used. Another case is to add a helper directly into clk-gpio and call it instead of clk_hw_*() one, see howclk_register_fractional_divider()is implemented and used.
I'll take a look, thanks
Quoted 15 lines
...
Quoted 9 lines
Quoted 7 lines
Quoted 4 lines
drivers/platform/x86/intel_skl_int3472_discrete.c line 49
Quoted 4 lines
drivers/platform/x86/intel_skl_int3472_discrete.c new file +4
-0+/* Lenovo Miix 510-12ISK - OV5648, Rear */ + { "GEFF150023R", REGULATOR_SUPPLY("avdd", "i2c-OVTI5648:00"), NULL}, +/* Surface Go 1&2 - OV5693, Front */ + { "YHCU", REGULATOR_SUPPLY("avdd", "i2c-INT33BE:00"), NULL},I'm wondering if you should use same I2C format macro and create this dynamically? Or rather find a corresponding ACPI device instance and copy it's name? ...
The supply name needs hard-coding really, but the device name I suppose can come from
int3472->sensor_name.To be strict in terms you are using "device instance name" in the
REGULATOR_SUPPLY()second parameter. Because "device name" is generic and doesn't point to the actual *instance* of the device in the system.
Quoted 7 lines
So, and "device name instance" we may get only by traversing through the (ACPI) bus and find corresponding struct device and derive name from it. Same way like you have done in previous patch series.
Because there is no guarantee that, e.g., i2c-INT33BE:00 will be present on the system and moreover there is no guarantee that if two INT33BE or more devices are present you will get :00 always for the one you need!
Mm, good point, hadn't considered two identical sensors on the same platform. Alright; I'll think about this in more detail, thank you.
Quoted 9 lines
Quoted 9 lines
Quoted 9 lines
Quoted 9 lines
drivers/platform/x86/intel_skl_int3472_tps68470.c line 135
Quoted 7 lines
drivers/platform/x86/intel_skl_int3472_tps68470.c new file +7
-0+ opregion_dev =skl_int3472_register_pdev ("tps68470_pmic_opregion" , + &client->dev); +if (IS_ERR (opregion_dev)) { + ret =PTR_ERR (opregion_dev); + goto err_free_gpio; + } + }I wonder if this could be simplified by using
devm_mfd_add_devices. You could have two arrays ofmfd_cell, one for each case.
Quoted 5 lines
Quoted 3 lines
Quoted 2 lines
Yeah, which effectively means that we should have some kind of mfd/tps68470 in place.
Can you expand on what you mean by that a little, please?
The very first comment in this reply should hopefully shed a light on my idea.
It did, thanks
Re: [PATCH v2 6/7] platform: x86: Add intel_skl_int3472 driver
Quoted 22 lines · Daniel Scally
Quoted 13 lines · Andy Shevchenko
Quoted 10 lines
Quoted 10 lines
Quoted 7 lines
drivers/platform/x86/intel_skl_int3472_common.c line 69
Quoted 7 lines
drivers/platform/x86/intel_skl_int3472_common.c new file +7
-0+static struct i2c_driver int3472_tps68470 = { + .driver = { + .name ="int3472-tps68470" , + .acpi_match_table = int3472_device_id, + }, + .probe_new = skl_int3472_tps68470_probe, +};I'm not sure we want to have like this. If I'm not mistaken the I²C driver can be separated without ACPI IDs (just having I²C IDs) and you may instantiate it via
i2c_new_client_device()ori2c_acpi_new_device()whichever suits better...Quoted 3 lines
Sorry, I'm a bit confused by this. The i2c device is already present...we just want the driver to bind to them, so what role do those functions have there?
Quoted 7 lines
What I meant is something like
*_i2c.c
real I²C driver for the TPS chip, but solely with I²C ID table, no ACPI involved (and it sounds like it should be mfd/tps one, in which you just cut out ACPI IDs and convert to pure I²C one, that what I had suggested in the first place)
Quoted 9 lines
Ahh; sorry - i misunderstood what you meant there. I understand now I think, but there is one complication; the ACPI subsystem already creates a client for that i2c adapter and address;
i2c_new_client_device()includes a check to see whether that adapter / address combination has an i2c device already. So we would have to have the platform driver with ACPI ID first find the existingi2c_clientand unregister it before registering the new one...the existing clients have a name matching the ACPI device instance name (e.g i2c-INT3472:00) which we can't use as ani2c_device_idof course.
See how INT33FE is being handled. Hint: drivers/acpi/scan.c:~1600
static const struct acpi_device_id i2c_multi_instantiate_ids[] = {
{"BSG1160", },
{"BSG2150", },
{"INT33FE", },
{"INT3515", },
{}
};So, we quirklist it here and instantiate manually from platform driver (new coming one).
...
Quoted 9 lines
Quoted 9 lines
You need to modify
clk-gpio.cto export
clk_hw_register_gpio_gate()clk_hw_register_gpio_mux()(perhaps it will require to add
*_unregister()counterparts) and call it from your code.See, for example, how
clk_hw_unregister_fixed_rate()is being used. Another
Here I meant of course clk_hw_register_fixed_rate().
Quoted 5 lines
Quoted 3 lines
case is to add a helper directly into clk-gpio and call it instead of clk_hw_*() one, see how
clk_register_fractional_divider()is implemented and used.I'll take a look, thanks
Signature · 2 lines
With Best Regards, Andy Shevchenko
Re: [PATCH v2 6/7] platform: x86: Add intel_skl_int3472 driver
Quoted 43 lines · Andy Shevchenko
Quoted 22 lines · Daniel Scally
Quoted 13 lines · Andy Shevchenko
Quoted 10 lines
Quoted 10 lines
Quoted 7 lines
Review
Quoted 7 lines
(quoted diff) +7
-0+static struct i2c_driver int3472_tps68470 = { + .driver = { + .name = "int3472-tps68470", + .acpi_match_table = int3472_device_id, + }, + .probe_new = skl_int3472_tps68470_probe, +};I'm not sure we want to have like this. If I'm not mistaken the I²C driver can be separated without ACPI IDs (just having I²C IDs) and you may instantiate it via
i2c_new_client_device()ori2c_acpi_new_device()whichever suits better...Quoted 3 lines
Sorry, I'm a bit confused by this. The i2c device is already present...we just want the driver to bind to them, so what role do those functions have there?
Quoted 7 lines
What I meant is something like
*_i2c.c
real I²C driver for the TPS chip, but solely with I²C ID table, no ACPI involved (and it sounds like it should be mfd/tps one, in which you just cut out ACPI IDs and convert to pure I²C one, that what I had suggested in the first place)Quoted 9 lines
Ahh; sorry - i misunderstood what you meant there. I understand now I think, but there is one complication; the ACPI subsystem already creates a client for that i2c adapter and address;
i2c_new_client_device()includes a check to see whether that adapter / address combination has an i2c device already. So we would have to have the platform driver with ACPI ID first find the existingi2c_clientand unregister it before registering the new one...the existing clients have a name matching the ACPI device instance name (e.g i2c-INT3472:00) which we can't use as ani2c_device_idof course.See how INT33FE is being handled. Hint: drivers/acpi/scan.c:~1600
static const struct acpi_device_id i2c_multi_instantiate_ids[] = { {"BSG1160", }, {"BSG2150", }, {"INT33FE", }, {"INT3515", }, {} };
Quoted 2 lines
So, we quirklist it here and instantiate manually from platform driver (new coming one).
This is documented as used for devices that have multiple I2cSerialBus resources. That's not the case for the INT3472 as far as I can tell. I don't think we should abuse this mechanism.
Don't forget that the TPS68470 I2C driver needs to be ACPI-aware, as it has to register an OpRegion for ACPI-based Chrome OS devices. On other platforms (including DT platforms), it should only register regulators, clocks and GPIOs. Given the differences between those platforms, I don't think a TPS68470 driver that would fake being unaware of being probed through ACPI would be a good idea. We can always refactor the code later when we'll have a non-ACPI based platform using the TPS68470, without such a platform there's no way we can test the I2C driver without ACPI anyway.
Quoted 19 lines
...
Quoted 9 lines
Quoted 9 lines
You need to modify
clk-gpio.cto export
clk_hw_register_gpio_gate()clk_hw_register_gpio_mux()(perhaps it will require to add
*_unregister()counterparts) and call it from your code.See, for example, how
clk_hw_unregister_fixed_rate()is being used. AnotherHere I meant of course
clk_hw_register_fixed_rate().Quoted 5 lines
Quoted 3 lines
case is to add a helper directly into clk-gpio and call it instead of clk_hw_*() one, see how
clk_register_fractional_divider()is implemented and used.I'll take a look, thanks
Signature · 3 lines
Regards, Laurent Pinchart
Re: [PATCH v2 6/7] platform: x86: Add intel_skl_int3472 driver
Quoted 44 lines · Laurent Pinchart
Quoted 43 lines · Andy Shevchenko
Quoted 22 lines · Daniel Scally
Quoted 13 lines · Andy Shevchenko
Quoted 10 lines
Quoted 10 lines
Quoted 7 lines
Review
Quoted 7 lines
(quoted diff) +7
-0+static struct i2c_driver int3472_tps68470 = { + .driver = { + .name = "int3472-tps68470", + .acpi_match_table = int3472_device_id, + }, + .probe_new = skl_int3472_tps68470_probe, +};I'm not sure we want to have like this. If I'm not mistaken the I²C driver can be separated without ACPI IDs (just having I²C IDs) and you may instantiate it via
i2c_new_client_device()ori2c_acpi_new_device()whichever suits better...Quoted 3 lines
Sorry, I'm a bit confused by this. The i2c device is already present...we just want the driver to bind to them, so what role do those functions have there?
Quoted 7 lines
What I meant is something like
*_i2c.c
real I²C driver for the TPS chip, but solely with I²C ID table, no ACPI involved (and it sounds like it should be mfd/tps one, in which you just cut out ACPI IDs and convert to pure I²C one, that what I had suggested in the first place)Quoted 9 lines
Ahh; sorry - i misunderstood what you meant there. I understand now I think, but there is one complication; the ACPI subsystem already creates a client for that i2c adapter and address;
i2c_new_client_device()includes a check to see whether that adapter / address combination has an i2c device already. So we would have to have the platform driver with ACPI ID first find the existingi2c_clientand unregister it before registering the new one...the existing clients have a name matching the ACPI device instance name (e.g i2c-INT3472:00) which we can't use as ani2c_device_idof course.See how INT33FE is being handled. Hint: drivers/acpi/scan.c:~1600
static const struct acpi_device_id i2c_multi_instantiate_ids[] = { {"BSG1160", }, {"BSG2150", }, {"INT33FE", }, {"INT3515", }, {} };
Quoted 6 lines
Quoted 2 lines
So, we quirklist it here and instantiate manually from platform driver (new coming one).
This is documented as used for devices that have multiple I2cSerialBus resources. That's not the case for the INT3472 as far as I can tell. I don't think we should abuse this mechanism.
This is quite a similar case to that one. Let's avoid yak shaving, right?
Quoted 9 lines
Don't forget that the TPS68470 I2C driver needs to be ACPI-aware, as it has to register an OpRegion for ACPI-based Chrome OS devices. On other platforms (including DT platforms), it should only register regulators, clocks and GPIOs. Given the differences between those platforms, I don't think a TPS68470 driver that would fake being unaware of being probed through ACPI would be a good idea. We can always refactor the code later when we'll have a non-ACPI based platform using the TPS68470, without such a platform there's no way we can test the I2C driver without ACPI anyway.
Are you agree that MFD approach should stay? How then we can manage to have an MFD driver cohabit with our new driver? I proposed a clean solution which will handle all possible cases via quirk driver. Having two drivers enumerated by different scenarios is a call for troubles (we have already with one of that sensors).
And there is no "faking" anything, it's rather gating it depending on the platform.
Signature · 2 lines
With Best Regards, Andy Shevchenko
Re: [PATCH v2 6/7] platform: x86: Add intel_skl_int3472 driver
Hi Andy,
Quoted 45 lines · Andy Shevchenko
Quoted 44 lines · Laurent Pinchart
Quoted 43 lines · Andy Shevchenko
Quoted 22 lines · Daniel Scally
Quoted 13 lines · Andy Shevchenko
Quoted 10 lines
Quoted 10 lines
Quoted 7 lines
Review
Quoted 7 lines
(quoted diff) +7
-0+static struct i2c_driver int3472_tps68470 = { + .driver = { + .name = "int3472-tps68470", + .acpi_match_table = int3472_device_id, + }, + .probe_new = skl_int3472_tps68470_probe, +};I'm not sure we want to have like this. If I'm not mistaken the I²C driver can be separated without ACPI IDs (just having I²C IDs) and you may instantiate it via
i2c_new_client_device()ori2c_acpi_new_device()whichever suits better...Quoted 3 lines
Sorry, I'm a bit confused by this. The i2c device is already present...we just want the driver to bind to them, so what role do those functions have there?
Quoted 7 lines
What I meant is something like
*_i2c.c
real I²C driver for the TPS chip, but solely with I²C ID table, no ACPI involved (and it sounds like it should be mfd/tps one, in which you just cut out ACPI IDs and convert to pure I²C one, that what I had suggested in the first place)Quoted 9 lines
Ahh; sorry - i misunderstood what you meant there. I understand now I think, but there is one complication; the ACPI subsystem already creates a client for that i2c adapter and address;
i2c_new_client_device()includes a check to see whether that adapter / address combination has an i2c device already. So we would have to have the platform driver with ACPI ID first find the existingi2c_clientand unregister it before registering the new one...the existing clients have a name matching the ACPI device instance name (e.g i2c-INT3472:00) which we can't use as ani2c_device_idof course.See how INT33FE is being handled. Hint: drivers/acpi/scan.c:~1600
static const struct acpi_device_id i2c_multi_instantiate_ids[] = { {"BSG1160", }, {"BSG2150", }, {"INT33FE", }, {"INT3515", }, {} };
Quoted 8 lines
Quoted 6 lines
Quoted 2 lines
So, we quirklist it here and instantiate manually from platform driver (new coming one).
This is documented as used for devices that have multiple I2cSerialBus resources. That's not the case for the INT3472 as far as I can tell. I don't think we should abuse this mechanism.
This is quite a similar case to that one. Let's avoid yak shaving, right?
Exactly my point, that's why I think this patch is good overall, I don't think it requires a complete rewrite.
Quoted 10 lines
Quoted 9 lines
Don't forget that the TPS68470 I2C driver needs to be ACPI-aware, as it has to register an OpRegion for ACPI-based Chrome OS devices. On other platforms (including DT platforms), it should only register regulators, clocks and GPIOs. Given the differences between those platforms, I don't think a TPS68470 driver that would fake being unaware of being probed through ACPI would be a good idea. We can always refactor the code later when we'll have a non-ACPI based platform using the TPS68470, without such a platform there's no way we can test the I2C driver without ACPI anyway.
Quoted 5 lines
Are you agree that MFD approach should stay? How then we can manage to have an MFD driver cohabit with our new driver? I proposed a clean solution which will handle all possible cases via quirk driver. Having two drivers enumerated by different scenarios is a call for troubles (we have already with one of that sensors).
I think we should solve this problem when it will arise. Solving problems with complex architectures without a platform to test the code on is a pretty sure way to get the architecture design wrong. Let's get this merged, it's an improvement compared to the current situation, and then let's improve it further on top when we'll need to support more use cases.
Quoted 2 lines
And there is no "faking" anything, it's rather gating it depending on the platform.
Signature · 3 lines
Regards, Laurent Pinchart
Re: [PATCH v2 6/7] platform: x86: Add intel_skl_int3472 driver
Quoted 49 lines · Laurent Pinchart
Quoted 48 lines · Andy Shevchenko
Quoted 47 lines · Laurent Pinchart
Quoted 45 lines · Andy Shevchenko
Quoted 22 lines · Daniel Scally
Quoted 13 lines · Andy Shevchenko
Quoted 10 lines
Quoted 10 lines
Quoted 7 lines
Review
Quoted 7 lines
(quoted diff) +7
-0+static struct i2c_driver int3472_tps68470 = { + .driver = { + .name = "int3472-tps68470", + .acpi_match_table = int3472_device_id, + }, + .probe_new = skl_int3472_tps68470_probe, +};I'm not sure we want to have like this. If I'm not mistaken the I²C driver can be separated without ACPI IDs (just having I²C IDs) and you may instantiate it via
i2c_new_client_device()ori2c_acpi_new_device()whichever suits better...Quoted 3 lines
Sorry, I'm a bit confused by this. The i2c device is already present...we just want the driver to bind to them, so what role do those functions have there?
Quoted 7 lines
What I meant is something like
*_i2c.c
real I²C driver for the TPS chip, but solely with I²C ID table, no ACPI involved (and it sounds like it should be mfd/tps one, in which you just cut out ACPI IDs and convert to pure I²C one, that what I had suggested in the first place)Quoted 9 lines
Ahh; sorry - i misunderstood what you meant there. I understand now I think, but there is one complication; the ACPI subsystem already creates a client for that i2c adapter and address;
i2c_new_client_device()includes a check to see whether that adapter / address combination has an i2c device already. So we would have to have the platform driver with ACPI ID first find the existingi2c_clientand unregister it before registering the new one...the existing clients have a name matching the ACPI device instance name (e.g i2c-INT3472:00) which we can't use as ani2c_device_idof course.See how INT33FE is being handled. Hint: drivers/acpi/scan.c:~1600
static const struct acpi_device_id i2c_multi_instantiate_ids[] = { {"BSG1160", }, {"BSG2150", }, {"INT33FE", }, {"INT3515", }, {} };So, we quirklist it here and instantiate manually from platform driver (new coming one).
Quoted 8 lines
Quoted 5 lines
Quoted 3 lines
This is documented as used for devices that have multiple I2cSerialBus resources. That's not the case for the INT3472 as far as I can tell. I don't think we should abuse this mechanism.
This is quite a similar case to that one. Let's avoid yak shaving, right?
Exactly my point, that's why I think this patch is good overall, I don't think it requires a complete rewrite.
The approach in the series is to reinvent the MFD driver which I against of. I don;t think we need to kill it there and reborn in a new form and dragging code from there to here to there.
On top of that the approach with a quirk driver in the middle seems to me cleaner than using different paths how the two drivers are being initialized. In the proposed approach there will be one making decision point and easy to understand what's going on.
The bad example of two making decision points is acpi_lpss.c vs. individual drivers (however in that case it have different ID's, i.e. ACPI vs. PCI),
Quoted 16 lines
Quoted 10 lines
Quoted 9 lines
Don't forget that the TPS68470 I2C driver needs to be ACPI-aware, as it has to register an OpRegion for ACPI-based Chrome OS devices. On other platforms (including DT platforms), it should only register regulators, clocks and GPIOs. Given the differences between those platforms, I don't think a TPS68470 driver that would fake being unaware of being probed through ACPI would be a good idea. We can always refactor the code later when we'll have a non-ACPI based platform using the TPS68470, without such a platform there's no way we can test the I2C driver without ACPI anyway.
Quoted 5 lines
Are you agree that MFD approach should stay? How then we can manage to have an MFD driver cohabit with our new driver? I proposed a clean solution which will handle all possible cases via quirk driver. Having two drivers enumerated by different scenarios is a call for troubles (we have already with one of that sensors).
Quoted 6 lines
I think we should solve this problem when it will arise. Solving problems with complex architectures without a platform to test the code on is a pretty sure way to get the architecture design wrong. Let's get this merged, it's an improvement compared to the current situation, and then let's improve it further on top when we'll need to support more use cases.
But this is problem already here right now. The submitted code is to support a new platform that needs a quirk and treats INT3472 differently. The usual way is to refactor the existing solution to make them both to have a best compromise.
Quoted 2 lines
Quoted 2 lines
And there is no "faking" anything, it's rather gating it depending on the platform.
Signature · 2 lines
With Best Regards, Andy Shevchenko
Re: [PATCH v2 6/7] platform: x86: Add intel_skl_int3472 driver
Quoted 63 lines · Andy Shevchenko
Quoted 49 lines · Laurent Pinchart
Quoted 48 lines · Andy Shevchenko
Quoted 47 lines · Laurent Pinchart
Quoted 45 lines · Andy Shevchenko
Quoted 22 lines · Daniel Scally
Quoted 13 lines · Andy Shevchenko
Quoted 10 lines
Quoted 10 lines
Quoted 7 lines
Review
Quoted 7 lines
(quoted diff) +7
-0+static struct i2c_driver int3472_tps68470 = { + .driver = { + .name = "int3472-tps68470", + .acpi_match_table = int3472_device_id, + }, + .probe_new = skl_int3472_tps68470_probe, +};I'm not sure we want to have like this. If I'm not mistaken the I²C driver can be separated without ACPI IDs (just having I²C IDs) and you may instantiate it via
i2c_new_client_device()ori2c_acpi_new_device()whichever suits better...Quoted 3 lines
Sorry, I'm a bit confused by this. The i2c device is already present...we just want the driver to bind to them, so what role do those functions have there?
Quoted 7 lines
What I meant is something like
*_i2c.c
real I²C driver for the TPS chip, but solely with I²C ID table, no ACPI involved (and it sounds like it should be mfd/tps one, in which you just cut out ACPI IDs and convert to pure I²C one, that what I had suggested in the first place)Quoted 9 lines
Ahh; sorry - i misunderstood what you meant there. I understand now I think, but there is one complication; the ACPI subsystem already creates a client for that i2c adapter and address;
i2c_new_client_device()includes a check to see whether that adapter / address combination has an i2c device already. So we would have to have the platform driver with ACPI ID first find the existingi2c_clientand unregister it before registering the new one...the existing clients have a name matching the ACPI device instance name (e.g i2c-INT3472:00) which we can't use as ani2c_device_idof course.See how INT33FE is being handled. Hint: drivers/acpi/scan.c:~1600
static const struct acpi_device_id i2c_multi_instantiate_ids[] = { {"BSG1160", }, {"BSG2150", }, {"INT33FE", }, {"INT3515", }, {} };So, we quirklist it here and instantiate manually from platform driver (new coming one).
Quoted 8 lines
Quoted 5 lines
Quoted 3 lines
This is documented as used for devices that have multiple I2cSerialBus resources. That's not the case for the INT3472 as far as I can tell. I don't think we should abuse this mechanism.
This is quite a similar case to that one. Let's avoid yak shaving, right?
Exactly my point, that's why I think this patch is good overall, I don't think it requires a complete rewrite.
The approach in the series is to reinvent the MFD driver which I against of. I don;t think we need to kill it there and reborn in a new form and dragging code from there to here to there.
Quoted 7 lines
On top of that the approach with a quirk driver in the middle seems to me cleaner than using different paths how the two drivers are being initialized. In the proposed approach there will be one making decision point and easy to understand what's going on.
The bad example of two making decision points is
acpi_lpss.cvs. individual drivers (however in that case it have different ID's, i.e. ACPI vs. PCI),
Right; so if I understand correctly, the proposal is:
1. Add INT3472 to the i2c_multi_instantiate_ids, which blocks it getting created as an i2c device
2. instead of intel-skl-int3472 registering an i2c and a platform driver, just register a platform driver that binds to the INT3472 acpi_device_id. We can check hardware type like in intel_cht_int33fe_common.c and call either discrete probe that does what the discrete driver is doing now, or else call tps68470 which is just a stub driver registering an i2c device like intel_cht_int33fe_microb.c
3. Change the existing tps68470 mfd driver to match to that created i2c device instead of ACPI match, and move the code from intel_skl_int3472_tps68470.c to that driver instead
I think I finally got what you meant there, Andy, but correct me if I'm wrong please.
I'm not sure that one's better than the other, to be honest. Either the multi-function device functionality lives in the conventional place, or else _all_ of the int3472 handling code lives together in one module.
Quoted 10 lines
Quoted 10 lines
Quoted 10 lines
Quoted 9 lines
Don't forget that the TPS68470 I2C driver needs to be ACPI-aware, as it has to register an OpRegion for ACPI-based Chrome OS devices. On other platforms (including DT platforms), it should only register regulators, clocks and GPIOs. Given the differences between those platforms, I don't think a TPS68470 driver that would fake being unaware of being probed through ACPI would be a good idea. We can always refactor the code later when we'll have a non-ACPI based platform using the TPS68470, without such a platform there's no way we can test the I2C driver without ACPI anyway.
Quoted 5 lines
Quoted 5 lines
Quoted 5 lines
Are you agree that MFD approach should stay? How then we can manage to have an MFD driver cohabit with our new driver? I proposed a clean solution which will handle all possible cases via quirk driver. Having two drivers enumerated by different scenarios is a call for troubles (we have already with one of that sensors).
What kind of troubles do you anticipate here?
Quoted 15 lines
Quoted 6 lines
I think we should solve this problem when it will arise. Solving problems with complex architectures without a platform to test the code on is a pretty sure way to get the architecture design wrong. Let's get this merged, it's an improvement compared to the current situation, and then let's improve it further on top when we'll need to support more use cases.
But this is problem already here right now. The submitted code is to support a new platform that needs a quirk and treats INT3472 differently. The usual way is to refactor the existing solution to make them both to have a best compromise.
Quoted 2 lines
Quoted 2 lines
And there is no "faking" anything, it's rather gating it depending on the platform.
Re: [PATCH v2 6/7] platform: x86: Add intel_skl_int3472 driver
Hello Andy, Laurent
Quoted 80 lines · Daniel Scally
Quoted 57 lines · Andy Shevchenko
Quoted 44 lines · Laurent Pinchart
Quoted 43 lines · Andy Shevchenko
Quoted 42 lines · Laurent Pinchart
Quoted 41 lines · Andy Shevchenko
Quoted 21 lines · Daniel Scally
Quoted 13 lines · Andy Shevchenko
Quoted 10 lines
Quoted 10 lines
Quoted 7 lines
Review
Quoted 7 lines
(quoted diff) +7
-0+static struct i2c_driver int3472_tps68470 = { + .driver = { + .name = "int3472-tps68470", + .acpi_match_table = int3472_device_id, + }, + .probe_new = skl_int3472_tps68470_probe, +};I'm not sure we want to have like this. If I'm not mistaken the I²C driver can be separated without ACPI IDs (just having I²C IDs) and you may instantiate it via
i2c_new_client_device()ori2c_acpi_new_device()whichever suits better...Quoted 3 lines
Sorry, I'm a bit confused by this. The i2c device is already present...we just want the driver to bind to them, so what role do those functions have there?
Quoted 7 lines
What I meant is something like
*_i2c.c
real I²C driver for the TPS chip, but solely with I²C ID table, no ACPI involved (and it sounds like it should be mfd/tps one, in which you just cut out ACPI IDs and convert to pure I²C one, that what I had suggested in the first place)Quoted 9 lines
Ahh; sorry - i misunderstood what you meant there. I understand now I think, but there is one complication; the ACPI subsystem already creates a client for that i2c adapter and address;
i2c_new_client_device()includes a check to see whether that adapter / address combination has an i2c device already. So we would have to have the platform driver with ACPI ID first find the existingi2c_clientand unregister it before registering the new one...the existing clients have a name matching the ACPI device instance name (e.g i2c-INT3472:00) which we can't use as ani2c_device_idof course.See how INT33FE is being handled. Hint: drivers/acpi/scan.c:~1600
static const struct acpi_device_id i2c_multi_instantiate_ids[] = { {"BSG1160", }, {"BSG2150", }, {"INT33FE", }, {"INT3515", }, {} };Quoted 8 lines
Quoted 6 lines
Quoted 5 lines
Quoted 2 lines
So, we quirklist it here and instantiate manually from platform driver (new coming one).
This is documented as used for devices that have multiple I2cSerialBus resources. That's not the case for the INT3472 as far as I can tell. I don't think we should abuse this mechanism.
This is quite a similar case to that one. Let's avoid yak shaving, right?
Exactly my point, that's why I think this patch is good overall, I don't think it requires a complete rewrite.
The approach in the series is to reinvent the MFD driver which I against of. I don;t think we need to kill it there and reborn in a new form and dragging code from there to here to there.
Quoted 7 lines
On top of that the approach with a quirk driver in the middle seems to me cleaner than using different paths how the two drivers are being initialized. In the proposed approach there will be one making decision point and easy to understand what's going on.
The bad example of two making decision points is
acpi_lpss.cvs. individual drivers (however in that case it have different ID's, i.e. ACPI vs. PCI),Right; so if I understand correctly, the proposal is:
1. Add INT3472 to the
i2c_multi_instantiate_ids, which blocks it getting created as an i2c device
2. instead of intel-skl-int3472 registering an i2c and a platform driver, just register a platform driver that binds to the INT3472acpi_device_id. We can check hardware type like inintel_cht_int33fe_common.cand call either discrete probe that does what the discrete driver is doing now, or else call tps68470 which is just a stub driver registering an i2c device likeintel_cht_int33fe_microb.c
3. Change the existing tps68470 mfd driver to match to that created i2c device instead of ACPI match, and move the code fromintel_skl_int3472_tps68470.cto that driver instead
Quoted 6 lines
I think I finally got what you meant there, Andy, but correct me if I'm wrong please.
I'm not sure that one's better than the other, to be honest. Either the multi-function device functionality lives in the conventional place, or else _all_ of the int3472 handling code lives together in one module.
Can we come to a consensus on this? I would rather be in agreement than leave it hanging...I do see the argument that it's better not to rebirth the MFD driver away from that subsystem, but at the moment I lean towards the view that having all the code handling this particular _HID in one place is probably preferable, if only to make it easier for anyone coming in the future to understand what's happening. That said; I'm not particularly precious about it, I'd just like to agree an approach so I can move forward with the next version
Quoted 29 lines
Quoted 9 lines
Quoted 9 lines
Quoted 9 lines
Quoted 9 lines
Don't forget that the TPS68470 I2C driver needs to be ACPI-aware, as it has to register an OpRegion for ACPI-based Chrome OS devices. On other platforms (including DT platforms), it should only register regulators, clocks and GPIOs. Given the differences between those platforms, I don't think a TPS68470 driver that would fake being unaware of being probed through ACPI would be a good idea. We can always refactor the code later when we'll have a non-ACPI based platform using the TPS68470, without such a platform there's no way we can test the I2C driver without ACPI anyway.
Quoted 5 lines
Quoted 5 lines
Quoted 5 lines
Are you agree that MFD approach should stay? How then we can manage to have an MFD driver cohabit with our new driver? I proposed a clean solution which will handle all possible cases via quirk driver. Having two drivers enumerated by different scenarios is a call for troubles (we have already with one of that sensors).
What kind of troubles do you anticipate here?
Quoted 13 lines
Quoted 6 lines
I think we should solve this problem when it will arise. Solving problems with complex architectures without a platform to test the code on is a pretty sure way to get the architecture design wrong. Let's get this merged, it's an improvement compared to the current situation, and then let's improve it further on top when we'll need to support more use cases.
But this is problem already here right now. The submitted code is to support a new platform that needs a quirk and treats INT3472 differently. The usual way is to refactor the existing solution to make them both to have a best compromise.
Quoted 2 lines
Quoted 2 lines
And there is no "faking" anything, it's rather gating it depending on the platform.
Re: [PATCH v2 6/7] platform: x86: Add intel_skl_int3472 driver
Quoted 2 lines · Daniel Scally
Quoted 1 line · Daniel Scally
On 20/01/2021 12:57, Andy Shevchenko wrote:
...
Quoted 11 lines
Quoted 3 lines
I'm not sure that one's better than the other, to be honest. Either the multi-function device functionality lives in the conventional place, or else _all_ of the int3472 handling code lives together in one module.
Can we come to a consensus on this? I would rather be in agreement than leave it hanging...I do see the argument that it's better not to rebirth the MFD driver away from that subsystem, but at the moment I lean towards the view that having all the code handling this particular
_HIDin one place is probably preferable, if only to make it easier for anyone coming in the future to understand what's happening. That said; I'm not particularly precious about it, I'd just like to agree an approach so I can move forward with the next version
So, my priorities of rejection (first is higher)
- open-coding MFD subsystem (that said, if you shuffle the code, at least leave it as an MFD driver)
- moving out from MFD (although I understand intentions)
Summarize, go ahead with your view (leaving it as an MFD driver) and look forward to what maintainer(s) will say.
Signature · 2 lines
With Best Regards, Andy Shevchenko
Re: [PATCH v2 6/7] platform: x86: Add intel_skl_int3472 driver
In reply to Laurent PinchartHi Laurent, thanks for the comments - really appreciate the detail.
Some specific responses below but assume a general "will do" to everything you mentioned otherwise...
Quoted 10 lines · Laurent Pinchart
Review
Quoted 1 line
(quoted diff) +1
-0+ PMIC) and one designed for Chrome OS.How about expanding this a bit to explain what the INT3472 stands for ?
The INT3472 is an Intel camera power controller, a logical device found on some Skylake-based systems that can map to different hardware devices depending on the platform. On machines designed for Chrome OS, it maps to a TPS68470 camera PMIC. On machines designed for Windows, it maps to either a TP68470 camera PMIC, a uP6641Q sensor PMIC, or a set of discrete GPIOs and power gates.
Yeah sure ok
Quoted 10 lines
drivers/platform/x86/Kconfig config INTEL_CHT_INT33FE · line 865
Quoted 9 lines
This driver handles all three
drivers/platform/x86/Kconfig +8
-0+ situations by discovering information it needs to discern them at + runtime. + + If your device was designed for Chrome OS, this driver will provide + an ACPI operation region, which must be available before any of the + devices using this are probed. For this reason, you should select Y + if your device was designed for ChromeOS. This option also configures + the designware-i2c driver to be built-in, for the same reason.Is the last sentence a leftover ?
Oops - it is, but it was supposed to remind me to double check that that was still necessary. I'll take a look, thanks.
Quoted 14 lines
Quoted 14 lines
drivers/platform/x86/intel_skl_int3472_common.c new file +14
-0+ +#include "intel_skl_int3472_common.h" + +int skl_int3472_get_cldb_buffer (struct acpi_device *adev, +struct int3472_cldb *cldb) +{ +struct acpi_buffer buffer = {ACPI_ALLOCATE_BUFFER ,NULL }; +acpi_handle handle = adev->handle; +union acpi_object *obj; +acpi_status status; +int ret =0 ; + + status =acpi_evaluate_object (handle,"CLDB" ,NULL , &buffer); +if (ACPI_FAILURE (status))
Quoted 8 lines
drivers/platform/x86/intel_skl_int3472_common.c line 25
Quoted 5 lines
drivers/platform/x86/intel_skl_int3472_common.c new file +5
-0+return -ENODEV ; + + obj = buffer.pointer; +if (!obj) { +dev_err (&adev->dev,"ACPI device has no CLDB object\n" );Is this the code path that is taken on Chrome OS ? If so an error message isn't appropriate. I'd drop this message, and instead add an error message in the discrete PMIC code.
Ah yes of course, thanks, I'll move the error message.
Quoted 23 lines
drivers/platform/x86/intel_skl_int3472_common.h line 78
Quoted 5 lines
drivers/platform/x86/intel_skl_int3472_common.h new file +5
-0+ +unsigned int n_gpios;/* how many GPIOs have we seen */ + +struct int3472_gpio_regulator regulator; +struct int3472_gpio_clock clock;You don't necessarily need to define separate structures for this, you could also write
struct { char regulator_name[GPIO_REGULATOR_NAME_LENGTH]; char supply_name[GPIO_REGULATOR_SUPPLY_NAME_LENGTH]; struct gpio_desc *gpio; struct regulator_dev *rdev; struct regulator_desc rdesc; } regulator; struct { struct clk *clk; struct clk_hw clk_hw; struct clk_lookup *cl; struct gpio_desc *gpio; } clock;
Quoted 1 line
It's entirely up to you.
Ooh yeah I like that more, thanks very much.
Quoted 4 lines
Quoted 4 lines
drivers/platform/x86/intel_skl_int3472_discrete.c new file +4
-0+/* 79234640-9e10-4fea-a5c1-b5aa8b19756f */ +static const guid_t int3472_gpio_guid = +GUID_INIT (0x79234640 ,0x9e10 ,0x4fea , +0xa5 ,0xc1 ,0xb5 ,0xaa ,0x8b ,0x19 ,0x75 ,0x6f );
Quoted 8 lines
drivers/platform/x86/intel_skl_int3472_discrete.c line 23
Quoted 5 lines
drivers/platform/x86/intel_skl_int3472_discrete.c new file +5
-0+ +/* 822ace8f-2814-4174-a56b-5f029fe079ee */ +static const guid_t cio2_sensor_module_guid = +GUID_INIT (0x822ace8f ,0x2814 ,0x4174 , +0xa5 ,0x6b ,0x5f ,0x02 ,0x9f ,0xe0 ,0x79 ,0xee );A comment that explains what those DSM functions do would be useful for reference. It has taken lots of time to figure it out, let's spare the pain to the next person who tries to understand this :-)
Hah - good point, well made. I'll explain what they're for then.
Quoted 9 lines
drivers/platform/x86/intel_skl_int3472_discrete.c line 63
Quoted 5 lines
drivers/platform/x86/intel_skl_int3472_discrete.c new file +5
-0+static int skl_int3472_clk_enable (struct clk_hw *hw) +{ +struct int3472_gpio_clock *clk =to_int3472_clk (hw); + +gpiod_set_value (clk->gpio,1 );The clock
enable()anddisable()methods are not supposed to sleep, while setting a GPIO value may sleep in the general case. Should this be moved toskl_int3472_clk_prepare()? Same forskl_int3472_clk_disable()andskl_int3472_clk_unprepare().
I was under the assumption the difference between gpiod_set_value() and gpiod_set_value_cansleep() was that gpiod_set_value() _can't_ sleep, but actually reading the function's comments it seems it will just complain if it turns out it can sleep:
* This function can be called from contexts where we cannot sleep, and will
* complain if the GPIO chip functions potentially sleep. It doesn't complain, on either of my devices, but I guess that can't be guaranteed for _every_ device, so these calls probably are safer in (un)prepare() yes.
Quoted 4 lines
Quoted 4 lines
drivers/platform/x86/intel_skl_int3472_discrete.c new file +4
-0+ } + + i++; + }
Quoted 8 lines
drivers/platform/x86/intel_skl_int3472_discrete.c line 162
Quoted 4 lines
drivers/platform/x86/intel_skl_int3472_discrete.c new file +4
-0+ } + +if (!func) +return 0 ;I initially thought this wasn't right, as if no entry was found in the mapping table, func would still have its non-NULL value as passed to this function. I then realized that you're checking if the match that was found is NULL. A comment to explain this would be useful.
Yep ok - I actually had one and decided it was superfluous and removed it - my bad.
Quoted 37 lines
drivers/platform/x86/intel_skl_int3472_discrete.c line 179
Quoted 12 lines
drivers/platform/x86/intel_skl_int3472_discrete.c new file +12
-0+ + status =acpi_get_handle (NULL , path, &handle); +if (ACPI_FAILURE (status)) +return -EINVAL ; + + ret =acpi_bus_get_device (handle, &adev); +if (ret) +return -ENODEV ; + + table_entry = (struct gpiod_lookup )GPIO_LOOKUP_IDX (acpi_dev_name (adev), + ares->data.gpio.pin_table[0 ], + func,0 , polarity);I wonder if
table_entry.key = acpi_dev_name(adev); table_entry.chip_hwnum = ares->data.gpio.pin_table[0]; table_entry.con_id = func; table_entry.idx = 0; table_entry.flags = polarity;(with struct
gpiod_lookuptable_entry= { }; above) would be more readable. Up to you.drivers/platform/x86/intel_skl_int3472_discrete.c line 182
Quoted 3 lines
drivers/platform/x86/intel_skl_int3472_discrete.c new file +3
-0+ +memcpy (&int3472->gpios.table[int3472->n_sensor_gpios], &table_entry, +sizeof (table_entry));Ah, or maybe
struct gpio_lookup *table_entry; table_entry = &int3472->gpios.table[int3472->n_sensor_gpios]; table_entry->key = acpi_dev_name(adev); table_entry->chip_hwnum = ares->data.gpio.pin_table[0]; table_entry->con_id = func; table_entry->idx = 0; table_entry->flags = polarity;
Quoted 2 lines
(no need to
memset()to 0 first as the whole structure has been allocated withkzalloc()).
Yeah you're right, this looks much nicer - thanks.
Quoted 5 lines
drivers/platform/x86/intel_skl_int3472_discrete.c line 197
Quoted 4 lines
drivers/platform/x86/intel_skl_int3472_discrete.c new file +4
-0+int ret =0 ; + + init.name =kasprintf (GFP_KERNEL ,"%s-clk" , +acpi_dev_name (int3472->adev));You need to check for NULL and return
-ENOMEM.
Oops, of course, thanks
Quoted 6 lines
drivers/platform/x86/intel_skl_int3472_discrete.c line 218
Quoted 1 line
drivers/platform/x86/intel_skl_int3472_discrete.c new file +1
-0+ goto err_unregister_clk;If this fails, you will end up calling
clk_unregister()andclkdev_drop()inskl_int3472_discrete_remove(). You should replace the check in the remove function withif (!int3472->clock.cl) {
You're right, good spot, thank you.
Quoted 5 lines
drivers/platform/x86/intel_skl_int3472_discrete.c line 245
Quoted 3 lines
drivers/platform/x86/intel_skl_int3472_discrete.c new file +3
-0+dev_err (&int3472->pdev->dev,"No sensor module config\n" ); +return PTR_ERR (sensor_config); + }Would it make sense to call this in
skl_int3472_discrete_probe()orskl_int3472_parse_crs()and cache the config pointer ?
Yes, probably actually, and then the GPIO mapping function can just check for its presence.
Quoted 10 lines
drivers/platform/x86/intel_skl_int3472_discrete.c line 258
Quoted 6 lines
drivers/platform/x86/intel_skl_int3472_discrete.c new file +6
-0+ init_data.constraints.valid_ops_mask =REGULATOR_CHANGE_STATUS ; + init_data.num_consumer_supplies =1 ; + init_data.consumer_supplies = &sensor_config->supply_map; + +snprintf (int3472->regulator.regulator_name, +GPIO_REGULATOR_NAME_LENGTH ,"int3472-discrete-regulator" );s/GPIO_REGULATOR_NAME_LENGTH/sizeof(int3472->regulator.regulator_name)/
Do regulator names need to be unique ? If so you may have a problem if a platform has two discrete INT3472.
Unlike clocks, the regulator framework doesn't shout at you when you do this, but I agree it's suboptimal at the very least, I'll set it to ..."%s-regulator", acpi_dev_name(int3472->adev)... as with the clock.
Quoted 9 lines
drivers/platform/x86/intel_skl_int3472_discrete.c line 385
Quoted 4 lines
drivers/platform/x86/intel_skl_int3472_discrete.c new file +4
-0+case INT3472_GPIO_TYPE_PRIVACY_LED : + ret =skl_int3472_map_gpio_to_sensor (int3472, ares, +"indicator-led" , +GPIO_ACTIVE_HIGH );Mapping the indicator LED to the sensor isn't great, as all sensor drivers would then need to handle it. Could it be handled in the regulator instead, so that it would be turned on automatically when the sensor is powered up ? Another option, more complicated, would be to handle it in the CIO2 driver (but I'm not sure how we would map it).
Not with the regulator, because it turns out only the 0x0b pin is one of those and those appear on very few devices in scope, so it wouldn't be called on a Surface Book 2 for example. Perhaps as part of clock prepare/enable? I don't much like the idea of it running in the CIO2 driver to be honest, feels a bit out of place.
Quoted 8 lines
drivers/platform/x86/intel_skl_int3472_discrete.c line 477
Quoted 3 lines
drivers/platform/x86/intel_skl_int3472_discrete.c new file +3
-0+ +if (int3472->gpios_mapped) +gpiod_remove_lookup_table (&int3472->gpios);You could avoid the need for the
gpios_mappedfield by checking forif (int3472->gpios.list.next)Up to you.
Thank you! I was scratching my head trying to figure out a better way of doing that.
Re: [PATCH v2 6/7] platform: x86: Add intel_skl_int3472 driver
Hi Daniel,
Quoted 121 lines · Daniel Scally
Hi Laurent, thanks for the comments - really appreciate the detail.
Some specific responses below but assume a general "will do" to everything you mentioned otherwise...
Quoted 11 lines · Laurent Pinchart
Review
Quoted 1 line
(quoted diff) +1
-0+ PMIC) and one designed for Chrome OS.How about expanding this a bit to explain what the INT3472 stands for ?
The INT3472 is an Intel camera power controller, a logical device found on some Skylake-based systems that can map to different hardware devices depending on the platform. On machines designed for Chrome OS, it maps to a TPS68470 camera PMIC. On machines designed for Windows, it maps to either a TP68470 camera PMIC, a uP6641Q sensor PMIC, or a set of discrete GPIOs and power gates.
Yeah sure ok
Quoted 11 lines
drivers/platform/x86/Kconfig config INTEL_CHT_INT33FE · line 865
Quoted 9 lines
This driver handles all three
drivers/platform/x86/Kconfig +8
-0+ situations by discovering information it needs to discern them at + runtime. + + If your device was designed for Chrome OS, this driver will provide + an ACPI operation region, which must be available before any of the + devices using this are probed. For this reason, you should select Y + if your device was designed for ChromeOS. This option also configures + the designware-i2c driver to be built-in, for the same reason.Is the last sentence a leftover ?
Oops - it is, but it was supposed to remind me to double check that that was still necessary. I'll take a look, thanks.
Quoted 15 lines
Quoted 15 lines
drivers/platform/x86/intel_skl_int3472_common.c new file +15
-0+ +#include "intel_skl_int3472_common.h" + +int skl_int3472_get_cldb_buffer (struct acpi_device *adev, +struct int3472_cldb *cldb) +{ +struct acpi_buffer buffer = {ACPI_ALLOCATE_BUFFER ,NULL }; +acpi_handle handle = adev->handle; +union acpi_object *obj; +acpi_status status; +int ret =0 ; + + status =acpi_evaluate_object (handle,"CLDB" ,NULL , &buffer); +if (ACPI_FAILURE (status)) +return -ENODEV ;Quoted 8 lines
drivers/platform/x86/intel_skl_int3472_common.c line 25
Quoted 4 lines
drivers/platform/x86/intel_skl_int3472_common.c new file +4
-0+ + obj = buffer.pointer; +if (!obj) { +dev_err (&adev->dev,"ACPI device has no CLDB object\n" );Is this the code path that is taken on Chrome OS ? If so an error message isn't appropriate. I'd drop this message, and instead add an error message in the discrete PMIC code.
Ah yes of course, thanks, I'll move the error message.
Quoted 24 lines
drivers/platform/x86/intel_skl_int3472_common.h line 78
Quoted 5 lines
drivers/platform/x86/intel_skl_int3472_common.h new file +5
-0+ +unsigned int n_gpios;/* how many GPIOs have we seen */ + +struct int3472_gpio_regulator regulator; +struct int3472_gpio_clock clock;You don't necessarily need to define separate structures for this, you could also write
struct { char regulator_name[GPIO_REGULATOR_NAME_LENGTH]; char supply_name[GPIO_REGULATOR_SUPPLY_NAME_LENGTH]; struct gpio_desc *gpio; struct regulator_dev *rdev; struct regulator_desc rdesc; } regulator; struct { struct clk *clk; struct clk_hw clk_hw; struct clk_lookup *cl; struct gpio_desc *gpio; } clock;Quoted 1 line
It's entirely up to you.
Ooh yeah I like that more, thanks very much.
Quoted 5 lines
Quoted 5 lines
drivers/platform/x86/intel_skl_int3472_discrete.c new file +5
-0+/* 79234640-9e10-4fea-a5c1-b5aa8b19756f */ +static const guid_t int3472_gpio_guid = +GUID_INIT (0x79234640 ,0x9e10 ,0x4fea , +0xa5 ,0xc1 ,0xb5 ,0xaa ,0x8b ,0x19 ,0x75 ,0x6f ); +Quoted 8 lines
drivers/platform/x86/intel_skl_int3472_discrete.c line 23
Quoted 4 lines
drivers/platform/x86/intel_skl_int3472_discrete.c new file +4
-0+/* 822ace8f-2814-4174-a56b-5f029fe079ee */ +static const guid_t cio2_sensor_module_guid = +GUID_INIT (0x822ace8f ,0x2814 ,0x4174 , +0xa5 ,0x6b ,0x5f ,0x02 ,0x9f ,0xe0 ,0x79 ,0xee );A comment that explains what those DSM functions do would be useful for reference. It has taken lots of time to figure it out, let's spare the pain to the next person who tries to understand this :-)
Hah - good point, well made. I'll explain what they're for then.
Quoted 10 lines
drivers/platform/x86/intel_skl_int3472_discrete.c line 63
Quoted 5 lines
drivers/platform/x86/intel_skl_int3472_discrete.c new file +5
-0+static int skl_int3472_clk_enable (struct clk_hw *hw) +{ +struct int3472_gpio_clock *clk =to_int3472_clk (hw); + +gpiod_set_value (clk->gpio,1 );The clock
enable()anddisable()methods are not supposed to sleep, while setting a GPIO value may sleep in the general case. Should this be moved toskl_int3472_clk_prepare()? Same forskl_int3472_clk_disable()andskl_int3472_clk_unprepare().I was under the assumption the difference between
gpiod_set_value()andgpiod_set_value_cansleep()was thatgpiod_set_value()_can't_ sleep, but actually reading the function's comments it seems it will just complain if it turns out it can sleep:
Quoted 4 lines
* This function can be called from contexts where we cannot sleep, and will
* complain if the GPIO chip functions potentially sleep. It doesn't complain, on either of my devices, but I guess that can't be guaranteed for _every_ device, so these calls probably are safer in (un)prepare() yes.
If we could guarantee that the GPIOs are connected to the SoC, we could keep using the code above, as there should be no need to sleep. The question is whether this can be guaranteed or not. It's true that I would be surprised if the GPIOs were connected, for instance, to an I2C GPIO expander..
Quoted 117 lines
Quoted 5 lines
Quoted 5 lines
drivers/platform/x86/intel_skl_int3472_discrete.c new file +5
-0+ } + + i++; + } + }Quoted 8 lines
drivers/platform/x86/intel_skl_int3472_discrete.c line 162
Quoted 3 lines
drivers/platform/x86/intel_skl_int3472_discrete.c new file +3
-0+ +if (!func) +return 0 ;I initially thought this wasn't right, as if no entry was found in the mapping table, func would still have its non-NULL value as passed to this function. I then realized that you're checking if the match that was found is NULL. A comment to explain this would be useful.
Yep ok - I actually had one and decided it was superfluous and removed it - my bad.
Quoted 39 lines
drivers/platform/x86/intel_skl_int3472_discrete.c line 179
Quoted 12 lines
drivers/platform/x86/intel_skl_int3472_discrete.c new file +12
-0+ + status =acpi_get_handle (NULL , path, &handle); +if (ACPI_FAILURE (status)) +return -EINVAL ; + + ret =acpi_bus_get_device (handle, &adev); +if (ret) +return -ENODEV ; + + table_entry = (struct gpiod_lookup )GPIO_LOOKUP_IDX (acpi_dev_name (adev), + ares->data.gpio.pin_table[0 ], + func,0 , polarity);I wonder if
table_entry.key = acpi_dev_name(adev); table_entry.chip_hwnum = ares->data.gpio.pin_table[0]; table_entry.con_id = func; table_entry.idx = 0; table_entry.flags = polarity;(with struct
gpiod_lookuptable_entry= { }; above) would be more readable. Up to you.drivers/platform/x86/intel_skl_int3472_discrete.c line 182
Quoted 3 lines
drivers/platform/x86/intel_skl_int3472_discrete.c new file +3
-0+ +memcpy (&int3472->gpios.table[int3472->n_sensor_gpios], &table_entry, +sizeof (table_entry));Ah, or maybe
struct gpio_lookup *table_entry; table_entry = &int3472->gpios.table[int3472->n_sensor_gpios]; table_entry->key = acpi_dev_name(adev); table_entry->chip_hwnum = ares->data.gpio.pin_table[0]; table_entry->con_id = func; table_entry->idx = 0; table_entry->flags = polarity;Quoted 2 lines
(no need to
memset()to 0 first as the whole structure has been allocated withkzalloc()).Yeah you're right, this looks much nicer - thanks.
Quoted 6 lines
drivers/platform/x86/intel_skl_int3472_discrete.c line 197
Quoted 4 lines
drivers/platform/x86/intel_skl_int3472_discrete.c new file +4
-0+int ret =0 ; + + init.name =kasprintf (GFP_KERNEL ,"%s-clk" , +acpi_dev_name (int3472->adev));You need to check for NULL and return
-ENOMEM.Oops, of course, thanks
Quoted 7 lines
drivers/platform/x86/intel_skl_int3472_discrete.c line 218
Quoted 1 line
drivers/platform/x86/intel_skl_int3472_discrete.c new file +1
-0+ goto err_unregister_clk;If this fails, you will end up calling
clk_unregister()andclkdev_drop()inskl_int3472_discrete_remove(). You should replace the check in the remove function withif (!int3472->clock.cl) {You're right, good spot, thank you.
Quoted 6 lines
drivers/platform/x86/intel_skl_int3472_discrete.c line 245
Quoted 3 lines
drivers/platform/x86/intel_skl_int3472_discrete.c new file +3
-0+dev_err (&int3472->pdev->dev,"No sensor module config\n" ); +return PTR_ERR (sensor_config); + }Would it make sense to call this in
skl_int3472_discrete_probe()orskl_int3472_parse_crs()and cache the config pointer ?Yes, probably actually, and then the GPIO mapping function can just check for its presence.
Quoted 11 lines
drivers/platform/x86/intel_skl_int3472_discrete.c line 258
Quoted 6 lines
drivers/platform/x86/intel_skl_int3472_discrete.c new file +6
-0+ init_data.constraints.valid_ops_mask =REGULATOR_CHANGE_STATUS ; + init_data.num_consumer_supplies =1 ; + init_data.consumer_supplies = &sensor_config->supply_map; + +snprintf (int3472->regulator.regulator_name, +GPIO_REGULATOR_NAME_LENGTH ,"int3472-discrete-regulator" );s/GPIO_REGULATOR_NAME_LENGTH/sizeof(int3472->regulator.regulator_name)/
Do regulator names need to be unique ? If so you may have a problem if a platform has two discrete INT3472.
Unlike clocks, the regulator framework doesn't shout at you when you do this, but I agree it's suboptimal at the very least, I'll set it to ..."%s-regulator",
acpi_dev_name(int3472->adev)... as with the clock.Quoted 10 lines
drivers/platform/x86/intel_skl_int3472_discrete.c line 385
Quoted 4 lines
drivers/platform/x86/intel_skl_int3472_discrete.c new file +4
-0+case INT3472_GPIO_TYPE_PRIVACY_LED : + ret =skl_int3472_map_gpio_to_sensor (int3472, ares, +"indicator-led" , +GPIO_ACTIVE_HIGH );Mapping the indicator LED to the sensor isn't great, as all sensor drivers would then need to handle it. Could it be handled in the regulator instead, so that it would be turned on automatically when the sensor is powered up ? Another option, more complicated, would be to handle it in the CIO2 driver (but I'm not sure how we would map it).
Quoted 5 lines
Not with the regulator, because it turns out only the
0x0bpin is one of those and those appear on very few devices in scope, so it wouldn't be called on a Surface Book 2 for example. Perhaps as part of clock prepare/enable? I don't much like the idea of it running in the CIO2 driver to be honest, feels a bit out of place.
The clock is another option, but could there be platforms where the clock GPIO isn't present ?
Another option would be to let userspace handle that GPIO, but we then need to convey it to userspace.
Quoted 12 lines
Quoted 9 lines
drivers/platform/x86/intel_skl_int3472_discrete.c line 477
Quoted 3 lines
drivers/platform/x86/intel_skl_int3472_discrete.c new file +3
-0+ +if (int3472->gpios_mapped) +gpiod_remove_lookup_table (&int3472->gpios);You could avoid the need for the
gpios_mappedfield by checking forif (int3472->gpios.list.next)Up to you.
Thank you! I was scratching my head trying to figure out a better way of doing that.
Signature · 3 lines
Regards, Laurent Pinchart
Re: [PATCH v2 6/7] platform: x86: Add intel_skl_int3472 driver
Hi Laurent
Quoted 116 lines · Laurent Pinchart
Hi Daniel,
Quoted 109 lines · Daniel Scally
Hi Laurent, thanks for the comments - really appreciate the detail.
Some specific responses below but assume a general "will do" to everything you mentioned otherwise...
Quoted 10 lines · Laurent Pinchart
Review
Quoted 1 line
(quoted diff) +1
-0+ PMIC) and one designed for Chrome OS.How about expanding this a bit to explain what the INT3472 stands for ?
The INT3472 is an Intel camera power controller, a logical device found on some Skylake-based systems that can map to different hardware devices depending on the platform. On machines designed for Chrome OS, it maps to a TPS68470 camera PMIC. On machines designed for Windows, it maps to either a TP68470 camera PMIC, a uP6641Q sensor PMIC, or a set of discrete GPIOs and power gates.
Yeah sure ok
Quoted 10 lines
drivers/platform/x86/Kconfig config INTEL_CHT_INT33FE · line 865
Quoted 9 lines
This driver handles all three
drivers/platform/x86/Kconfig +8
-0+ situations by discovering information it needs to discern them at + runtime. + + If your device was designed for Chrome OS, this driver will provide + an ACPI operation region, which must be available before any of the + devices using this are probed. For this reason, you should select Y + if your device was designed for ChromeOS. This option also configures + the designware-i2c driver to be built-in, for the same reason.Is the last sentence a leftover ?
Oops - it is, but it was supposed to remind me to double check that that was still necessary. I'll take a look, thanks.
Quoted 14 lines
Quoted 14 lines
drivers/platform/x86/intel_skl_int3472_common.c new file +14
-0+ +#include "intel_skl_int3472_common.h" + +int skl_int3472_get_cldb_buffer (struct acpi_device *adev, +struct int3472_cldb *cldb) +{ +struct acpi_buffer buffer = {ACPI_ALLOCATE_BUFFER ,NULL }; +acpi_handle handle = adev->handle; +union acpi_object *obj; +acpi_status status; +int ret =0 ; + + status =acpi_evaluate_object (handle,"CLDB" ,NULL , &buffer); +if (ACPI_FAILURE (status))Quoted 8 lines
drivers/platform/x86/intel_skl_int3472_common.c line 25
Quoted 5 lines
drivers/platform/x86/intel_skl_int3472_common.c new file +5
-0+return -ENODEV ; + + obj = buffer.pointer; +if (!obj) { +dev_err (&adev->dev,"ACPI device has no CLDB object\n" );Is this the code path that is taken on Chrome OS ? If so an error message isn't appropriate. I'd drop this message, and instead add an error message in the discrete PMIC code.
Ah yes of course, thanks, I'll move the error message.
Quoted 23 lines
drivers/platform/x86/intel_skl_int3472_common.h line 78
Quoted 5 lines
drivers/platform/x86/intel_skl_int3472_common.h new file +5
-0+ +unsigned int n_gpios;/* how many GPIOs have we seen */ + +struct int3472_gpio_regulator regulator; +struct int3472_gpio_clock clock;You don't necessarily need to define separate structures for this, you could also write
struct { char regulator_name[GPIO_REGULATOR_NAME_LENGTH]; char supply_name[GPIO_REGULATOR_SUPPLY_NAME_LENGTH]; struct gpio_desc *gpio; struct regulator_dev *rdev; struct regulator_desc rdesc; } regulator; struct { struct clk *clk; struct clk_hw clk_hw; struct clk_lookup *cl; struct gpio_desc *gpio; } clock;Quoted 1 line
It's entirely up to you.
Ooh yeah I like that more, thanks very much.
Quoted 4 lines
Quoted 4 lines
drivers/platform/x86/intel_skl_int3472_discrete.c new file +4
-0+/* 79234640-9e10-4fea-a5c1-b5aa8b19756f */ +static const guid_t int3472_gpio_guid = +GUID_INIT (0x79234640 ,0x9e10 ,0x4fea , +0xa5 ,0xc1 ,0xb5 ,0xaa ,0x8b ,0x19 ,0x75 ,0x6f );Quoted 8 lines
drivers/platform/x86/intel_skl_int3472_discrete.c line 23
Quoted 5 lines
drivers/platform/x86/intel_skl_int3472_discrete.c new file +5
-0+ +/* 822ace8f-2814-4174-a56b-5f029fe079ee */ +static const guid_t cio2_sensor_module_guid = +GUID_INIT (0x822ace8f ,0x2814 ,0x4174 , +0xa5 ,0x6b ,0x5f ,0x02 ,0x9f ,0xe0 ,0x79 ,0xee );A comment that explains what those DSM functions do would be useful for reference. It has taken lots of time to figure it out, let's spare the pain to the next person who tries to understand this :-)
Hah - good point, well made. I'll explain what they're for then.
Quoted 9 lines
drivers/platform/x86/intel_skl_int3472_discrete.c line 63
Quoted 5 lines
drivers/platform/x86/intel_skl_int3472_discrete.c new file +5
-0+static int skl_int3472_clk_enable (struct clk_hw *hw) +{ +struct int3472_gpio_clock *clk =to_int3472_clk (hw); + +gpiod_set_value (clk->gpio,1 );The clock
enable()anddisable()methods are not supposed to sleep, while setting a GPIO value may sleep in the general case. Should this be moved toskl_int3472_clk_prepare()? Same forskl_int3472_clk_disable()andskl_int3472_clk_unprepare().I was under the assumption the difference between
gpiod_set_value()andgpiod_set_value_cansleep()was thatgpiod_set_value()_can't_ sleep, but actually reading the function's comments it seems it will just complain if it turns out it can sleep:Quoted 4 lines
* This function can be called from contexts where we cannot sleep, and will
* complain if the GPIO chip functions potentially sleep. It doesn't complain, on either of my devices, but I guess that can't be guaranteed for _every_ device, so these calls probably are safer in (un)prepare() yes.
Quoted 5 lines
If we could guarantee that the GPIOs are connected to the SoC, we could keep using the code above, as there should be no need to sleep. The question is whether this can be guaranteed or not. It's true that I would be surprised if the GPIOs were connected, for instance, to an I2C GPIO expander..
Is that the deciding factor? I'd say that's unlikely, but what do I know? Then again, is there actually any downside to calling gpiod_set_value() in the prepare() function instead? If not, may as well be safe.
Quoted 102 lines
Quoted 102 lines
Quoted 4 lines
Quoted 4 lines
drivers/platform/x86/intel_skl_int3472_discrete.c new file +4
-0+ } + + i++; + }Quoted 8 lines
drivers/platform/x86/intel_skl_int3472_discrete.c line 162
Quoted 4 lines
drivers/platform/x86/intel_skl_int3472_discrete.c new file +4
-0+ } + +if (!func) +return 0 ;I initially thought this wasn't right, as if no entry was found in the mapping table, func would still have its non-NULL value as passed to this function. I then realized that you're checking if the match that was found is NULL. A comment to explain this would be useful.
Yep ok - I actually had one and decided it was superfluous and removed it - my bad.
Quoted 37 lines
drivers/platform/x86/intel_skl_int3472_discrete.c line 179
Quoted 12 lines
drivers/platform/x86/intel_skl_int3472_discrete.c new file +12
-0+ + status =acpi_get_handle (NULL , path, &handle); +if (ACPI_FAILURE (status)) +return -EINVAL ; + + ret =acpi_bus_get_device (handle, &adev); +if (ret) +return -ENODEV ; + + table_entry = (struct gpiod_lookup )GPIO_LOOKUP_IDX (acpi_dev_name (adev), + ares->data.gpio.pin_table[0 ], + func,0 , polarity);I wonder if
table_entry.key = acpi_dev_name(adev); table_entry.chip_hwnum = ares->data.gpio.pin_table[0]; table_entry.con_id = func; table_entry.idx = 0; table_entry.flags = polarity;(with struct
gpiod_lookuptable_entry= { }; above) would be more readable. Up to you.drivers/platform/x86/intel_skl_int3472_discrete.c line 182
Quoted 3 lines
drivers/platform/x86/intel_skl_int3472_discrete.c new file +3
-0+ +memcpy (&int3472->gpios.table[int3472->n_sensor_gpios], &table_entry, +sizeof (table_entry));Ah, or maybe
struct gpio_lookup *table_entry; table_entry = &int3472->gpios.table[int3472->n_sensor_gpios]; table_entry->key = acpi_dev_name(adev); table_entry->chip_hwnum = ares->data.gpio.pin_table[0]; table_entry->con_id = func; table_entry->idx = 0; table_entry->flags = polarity;Quoted 2 lines
(no need to
memset()to 0 first as the whole structure has been allocated withkzalloc()).Yeah you're right, this looks much nicer - thanks.
Quoted 5 lines
drivers/platform/x86/intel_skl_int3472_discrete.c line 197
Quoted 4 lines
drivers/platform/x86/intel_skl_int3472_discrete.c new file +4
-0+int ret =0 ; + + init.name =kasprintf (GFP_KERNEL ,"%s-clk" , +acpi_dev_name (int3472->adev));You need to check for NULL and return
-ENOMEM.Oops, of course, thanks
Quoted 6 lines
drivers/platform/x86/intel_skl_int3472_discrete.c line 218
Quoted 1 line
drivers/platform/x86/intel_skl_int3472_discrete.c new file +1
-0+ goto err_unregister_clk;If this fails, you will end up calling
clk_unregister()andclkdev_drop()inskl_int3472_discrete_remove(). You should replace the check in the remove function withif (!int3472->clock.cl) {You're right, good spot, thank you.
Quoted 5 lines
drivers/platform/x86/intel_skl_int3472_discrete.c line 245
Quoted 3 lines
drivers/platform/x86/intel_skl_int3472_discrete.c new file +3
-0+dev_err (&int3472->pdev->dev,"No sensor module config\n" ); +return PTR_ERR (sensor_config); + }Would it make sense to call this in
skl_int3472_discrete_probe()orskl_int3472_parse_crs()and cache the config pointer ?Yes, probably actually, and then the GPIO mapping function can just check for its presence.
Quoted 10 lines
drivers/platform/x86/intel_skl_int3472_discrete.c line 258
Quoted 6 lines
drivers/platform/x86/intel_skl_int3472_discrete.c new file +6
-0+ init_data.constraints.valid_ops_mask =REGULATOR_CHANGE_STATUS ; + init_data.num_consumer_supplies =1 ; + init_data.consumer_supplies = &sensor_config->supply_map; + +snprintf (int3472->regulator.regulator_name, +GPIO_REGULATOR_NAME_LENGTH ,"int3472-discrete-regulator" );s/GPIO_REGULATOR_NAME_LENGTH/sizeof(int3472->regulator.regulator_name)/
Do regulator names need to be unique ? If so you may have a problem if a platform has two discrete INT3472.
Unlike clocks, the regulator framework doesn't shout at you when you do this, but I agree it's suboptimal at the very least, I'll set it to ..."%s-regulator",
acpi_dev_name(int3472->adev)... as with the clock.Quoted 9 lines
drivers/platform/x86/intel_skl_int3472_discrete.c line 385
Quoted 4 lines
drivers/platform/x86/intel_skl_int3472_discrete.c new file +4
-0+case INT3472_GPIO_TYPE_PRIVACY_LED : + ret =skl_int3472_map_gpio_to_sensor (int3472, ares, +"indicator-led" , +GPIO_ACTIVE_HIGH );Mapping the indicator LED to the sensor isn't great, as all sensor drivers would then need to handle it. Could it be handled in the regulator instead, so that it would be turned on automatically when the sensor is powered up ? Another option, more complicated, would be to handle it in the CIO2 driver (but I'm not sure how we would map it).
Quoted 7 lines
Quoted 5 lines
Not with the regulator, because it turns out only the
0x0bpin is one of those and those appear on very few devices in scope, so it wouldn't be called on a Surface Book 2 for example. Perhaps as part of clock prepare/enable? I don't much like the idea of it running in the CIO2 driver to be honest, feels a bit out of place.The clock is another option, but could there be platforms where the clock GPIO isn't present ?
I haven't ever seen a DSDT that didn't include a 0x0c pin to enable the clock, though that doesn't necessarily mean they're always there. Plenty of driver datasheets say they're happy for the external clock to be free running, so it could just be always active I suppose.
Quoted 2 lines
Another option would be to let userspace handle that GPIO, but we then need to convey it to userspace.
Can you point me to an example of that to look at perhaps?
Quoted 10 lines
Quoted 10 lines
Quoted 8 lines
drivers/platform/x86/intel_skl_int3472_discrete.c line 477
Quoted 3 lines
drivers/platform/x86/intel_skl_int3472_discrete.c new file +3
-0+ +if (int3472->gpios_mapped) +gpiod_remove_lookup_table (&int3472->gpios);You could avoid the need for the
gpios_mappedfield by checking forif (int3472->gpios.list.next)Up to you.
Thank you! I was scratching my head trying to figure out a better way of doing that.
Re: [PATCH v2 6/7] platform: x86: Add intel_skl_int3472 driver
Hi Daniel,
Quoted 121 lines · Daniel Scally
Quoted 114 lines · Laurent Pinchart
Quoted 109 lines · Daniel Scally
Hi Laurent, thanks for the comments - really appreciate the detail.
Some specific responses below but assume a general "will do" to everything you mentioned otherwise...
Quoted 10 lines · Laurent Pinchart
Review
Quoted 1 line
(quoted diff) +1
-0+ PMIC) and one designed for Chrome OS.How about expanding this a bit to explain what the INT3472 stands for ?
The INT3472 is an Intel camera power controller, a logical device found on some Skylake-based systems that can map to different hardware devices depending on the platform. On machines designed for Chrome OS, it maps to a TPS68470 camera PMIC. On machines designed for Windows, it maps to either a TP68470 camera PMIC, a uP6641Q sensor PMIC, or a set of discrete GPIOs and power gates.
Yeah sure ok
Quoted 10 lines
drivers/platform/x86/Kconfig config INTEL_CHT_INT33FE · line 865
Quoted 9 lines
This driver handles all three
drivers/platform/x86/Kconfig +8
-0+ situations by discovering information it needs to discern them at + runtime. + + If your device was designed for Chrome OS, this driver will provide + an ACPI operation region, which must be available before any of the + devices using this are probed. For this reason, you should select Y + if your device was designed for ChromeOS. This option also configures + the designware-i2c driver to be built-in, for the same reason.Is the last sentence a leftover ?
Oops - it is, but it was supposed to remind me to double check that that was still necessary. I'll take a look, thanks.
Quoted 14 lines
Quoted 14 lines
drivers/platform/x86/intel_skl_int3472_common.c new file +14
-0+ +#include "intel_skl_int3472_common.h" + +int skl_int3472_get_cldb_buffer (struct acpi_device *adev, +struct int3472_cldb *cldb) +{ +struct acpi_buffer buffer = {ACPI_ALLOCATE_BUFFER ,NULL }; +acpi_handle handle = adev->handle; +union acpi_object *obj; +acpi_status status; +int ret =0 ; + + status =acpi_evaluate_object (handle,"CLDB" ,NULL , &buffer); +if (ACPI_FAILURE (status))Quoted 8 lines
drivers/platform/x86/intel_skl_int3472_common.c line 25
Quoted 5 lines
drivers/platform/x86/intel_skl_int3472_common.c new file +5
-0+return -ENODEV ; + + obj = buffer.pointer; +if (!obj) { +dev_err (&adev->dev,"ACPI device has no CLDB object\n" );Is this the code path that is taken on Chrome OS ? If so an error message isn't appropriate. I'd drop this message, and instead add an error message in the discrete PMIC code.
Ah yes of course, thanks, I'll move the error message.
Quoted 23 lines
drivers/platform/x86/intel_skl_int3472_common.h line 78
Quoted 5 lines
drivers/platform/x86/intel_skl_int3472_common.h new file +5
-0+ +unsigned int n_gpios;/* how many GPIOs have we seen */ + +struct int3472_gpio_regulator regulator; +struct int3472_gpio_clock clock;You don't necessarily need to define separate structures for this, you could also write
struct { char regulator_name[GPIO_REGULATOR_NAME_LENGTH]; char supply_name[GPIO_REGULATOR_SUPPLY_NAME_LENGTH]; struct gpio_desc *gpio; struct regulator_dev *rdev; struct regulator_desc rdesc; } regulator; struct { struct clk *clk; struct clk_hw clk_hw; struct clk_lookup *cl; struct gpio_desc *gpio; } clock;Quoted 1 line
It's entirely up to you.
Ooh yeah I like that more, thanks very much.
Quoted 4 lines
Quoted 4 lines
drivers/platform/x86/intel_skl_int3472_discrete.c new file +4
-0+/* 79234640-9e10-4fea-a5c1-b5aa8b19756f */ +static const guid_t int3472_gpio_guid = +GUID_INIT (0x79234640 ,0x9e10 ,0x4fea , +0xa5 ,0xc1 ,0xb5 ,0xaa ,0x8b ,0x19 ,0x75 ,0x6f );Quoted 8 lines
drivers/platform/x86/intel_skl_int3472_discrete.c line 23
Quoted 5 lines
drivers/platform/x86/intel_skl_int3472_discrete.c new file +5
-0+ +/* 822ace8f-2814-4174-a56b-5f029fe079ee */ +static const guid_t cio2_sensor_module_guid = +GUID_INIT (0x822ace8f ,0x2814 ,0x4174 , +0xa5 ,0x6b ,0x5f ,0x02 ,0x9f ,0xe0 ,0x79 ,0xee );A comment that explains what those DSM functions do would be useful for reference. It has taken lots of time to figure it out, let's spare the pain to the next person who tries to understand this :-)
Hah - good point, well made. I'll explain what they're for then.
Quoted 9 lines
drivers/platform/x86/intel_skl_int3472_discrete.c line 63
Quoted 5 lines
drivers/platform/x86/intel_skl_int3472_discrete.c new file +5
-0+static int skl_int3472_clk_enable (struct clk_hw *hw) +{ +struct int3472_gpio_clock *clk =to_int3472_clk (hw); + +gpiod_set_value (clk->gpio,1 );The clock
enable()anddisable()methods are not supposed to sleep, while setting a GPIO value may sleep in the general case. Should this be moved toskl_int3472_clk_prepare()? Same forskl_int3472_clk_disable()andskl_int3472_clk_unprepare().I was under the assumption the difference between
gpiod_set_value()andgpiod_set_value_cansleep()was thatgpiod_set_value()_can't_ sleep, but actually reading the function's comments it seems it will just complain if it turns out it can sleep:Quoted 4 lines
* This function can be called from contexts where we cannot sleep, and will
* complain if the GPIO chip functions potentially sleep. It doesn't complain, on either of my devices, but I guess that can't be guaranteed for _every_ device, so these calls probably are safer in (un)prepare() yes.Quoted 5 lines
If we could guarantee that the GPIOs are connected to the SoC, we could keep using the code above, as there should be no need to sleep. The question is whether this can be guaranteed or not. It's true that I would be surprised if the GPIOs were connected, for instance, to an I2C GPIO expander..
Quoted 4 lines
Is that the deciding factor? I'd say that's unlikely, but what do I know? Then again, is there actually any downside to calling
gpiod_set_value()in theprepare()function instead? If not, may as well be safe.
The downside is that prepare() is meant to be called earlier than enable() when the consumer needs to call enable() in a context that can't sleep. This can sometimes cause the clock to be enabled for longer than necessary. In this case I don't think it's an issue, sensor drivers will use clk_prepare_enable() anyway.
Quoted 107 lines
Quoted 107 lines
Quoted 107 lines
Quoted 4 lines
Quoted 4 lines
drivers/platform/x86/intel_skl_int3472_discrete.c new file +4
-0+ } + + i++; + }Quoted 8 lines
drivers/platform/x86/intel_skl_int3472_discrete.c line 162
Quoted 4 lines
drivers/platform/x86/intel_skl_int3472_discrete.c new file +4
-0+ } + +if (!func) +return 0 ;I initially thought this wasn't right, as if no entry was found in the mapping table, func would still have its non-NULL value as passed to this function. I then realized that you're checking if the match that was found is NULL. A comment to explain this would be useful.
Yep ok - I actually had one and decided it was superfluous and removed it - my bad.
Quoted 37 lines
drivers/platform/x86/intel_skl_int3472_discrete.c line 179
Quoted 12 lines
drivers/platform/x86/intel_skl_int3472_discrete.c new file +12
-0+ + status =acpi_get_handle (NULL , path, &handle); +if (ACPI_FAILURE (status)) +return -EINVAL ; + + ret =acpi_bus_get_device (handle, &adev); +if (ret) +return -ENODEV ; + + table_entry = (struct gpiod_lookup )GPIO_LOOKUP_IDX (acpi_dev_name (adev), + ares->data.gpio.pin_table[0 ], + func,0 , polarity);I wonder if
table_entry.key = acpi_dev_name(adev); table_entry.chip_hwnum = ares->data.gpio.pin_table[0]; table_entry.con_id = func; table_entry.idx = 0; table_entry.flags = polarity;(with struct
gpiod_lookuptable_entry= { }; above) would be more readable. Up to you.drivers/platform/x86/intel_skl_int3472_discrete.c line 182
Quoted 3 lines
drivers/platform/x86/intel_skl_int3472_discrete.c new file +3
-0+ +memcpy (&int3472->gpios.table[int3472->n_sensor_gpios], &table_entry, +sizeof (table_entry));Ah, or maybe
struct gpio_lookup *table_entry; table_entry = &int3472->gpios.table[int3472->n_sensor_gpios]; table_entry->key = acpi_dev_name(adev); table_entry->chip_hwnum = ares->data.gpio.pin_table[0]; table_entry->con_id = func; table_entry->idx = 0; table_entry->flags = polarity;Quoted 2 lines
(no need to
memset()to 0 first as the whole structure has been allocated withkzalloc()).Yeah you're right, this looks much nicer - thanks.
Quoted 5 lines
drivers/platform/x86/intel_skl_int3472_discrete.c line 197
Quoted 4 lines
drivers/platform/x86/intel_skl_int3472_discrete.c new file +4
-0+int ret =0 ; + + init.name =kasprintf (GFP_KERNEL ,"%s-clk" , +acpi_dev_name (int3472->adev));You need to check for NULL and return
-ENOMEM.Oops, of course, thanks
Quoted 6 lines
drivers/platform/x86/intel_skl_int3472_discrete.c line 218
Quoted 1 line
drivers/platform/x86/intel_skl_int3472_discrete.c new file +1
-0+ goto err_unregister_clk;If this fails, you will end up calling
clk_unregister()andclkdev_drop()inskl_int3472_discrete_remove(). You should replace the check in the remove function withif (!int3472->clock.cl) {You're right, good spot, thank you.
Quoted 5 lines
drivers/platform/x86/intel_skl_int3472_discrete.c line 245
Quoted 3 lines
drivers/platform/x86/intel_skl_int3472_discrete.c new file +3
-0+dev_err (&int3472->pdev->dev,"No sensor module config\n" ); +return PTR_ERR (sensor_config); + }Would it make sense to call this in
skl_int3472_discrete_probe()orskl_int3472_parse_crs()and cache the config pointer ?Yes, probably actually, and then the GPIO mapping function can just check for its presence.
Quoted 10 lines
drivers/platform/x86/intel_skl_int3472_discrete.c line 258
Quoted 6 lines
drivers/platform/x86/intel_skl_int3472_discrete.c new file +6
-0+ init_data.constraints.valid_ops_mask =REGULATOR_CHANGE_STATUS ; + init_data.num_consumer_supplies =1 ; + init_data.consumer_supplies = &sensor_config->supply_map; + +snprintf (int3472->regulator.regulator_name, +GPIO_REGULATOR_NAME_LENGTH ,"int3472-discrete-regulator" );s/GPIO_REGULATOR_NAME_LENGTH/sizeof(int3472->regulator.regulator_name)/
Do regulator names need to be unique ? If so you may have a problem if a platform has two discrete INT3472.
Unlike clocks, the regulator framework doesn't shout at you when you do this, but I agree it's suboptimal at the very least, I'll set it to ..."%s-regulator",
acpi_dev_name(int3472->adev)... as with the clock.Quoted 9 lines
drivers/platform/x86/intel_skl_int3472_discrete.c line 385
Quoted 4 lines
drivers/platform/x86/intel_skl_int3472_discrete.c new file +4
-0+case INT3472_GPIO_TYPE_PRIVACY_LED : + ret =skl_int3472_map_gpio_to_sensor (int3472, ares, +"indicator-led" , +GPIO_ACTIVE_HIGH );Mapping the indicator LED to the sensor isn't great, as all sensor drivers would then need to handle it. Could it be handled in the regulator instead, so that it would be turned on automatically when the sensor is powered up ? Another option, more complicated, would be to handle it in the CIO2 driver (but I'm not sure how we would map it).
Not with the regulator, because it turns out only the
0x0bpin is one of those and those appear on very few devices in scope, so it wouldn't be called on a Surface Book 2 for example. Perhaps as part of clock prepare/enable? I don't much like the idea of it running in the CIO2 driver to be honest, feels a bit out of place.
Quoted 7 lines
Quoted 2 lines
The clock is another option, but could there be platforms where the clock GPIO isn't present ?
I haven't ever seen a DSDT that didn't include a
0x0cpin to enable the clock, though that doesn't necessarily mean they're always there. Plenty of driver datasheets say they're happy for the external clock to be free running, so it could just be always active I suppose.
Maybe we can handle this later if such a platform is found. You should then print a warning message if no clock is present.
Quoted 4 lines
Quoted 2 lines
Another option would be to let userspace handle that GPIO, but we then need to convey it to userspace.
Can you point me to an example of that to look at perhaps?
I don't think there's any :-) We'd have to design the mechanism.
Quoted 10 lines
Quoted 10 lines
Quoted 10 lines
Quoted 8 lines
drivers/platform/x86/intel_skl_int3472_discrete.c line 477
Quoted 3 lines
drivers/platform/x86/intel_skl_int3472_discrete.c new file +3
-0+ +if (int3472->gpios_mapped) +gpiod_remove_lookup_table (&int3472->gpios);You could avoid the need for the
gpios_mappedfield by checking forif (int3472->gpios.list.next)Up to you.
Thank you! I was scratching my head trying to figure out a better way of doing that.
Signature · 3 lines
Regards, Laurent Pinchart
Re: [PATCH v2 6/7] platform: x86: Add intel_skl_int3472 driver
In reply to Daniel ScallyHi
2021. január 18., hétfő 1:34 keltezéssel, Daniel Scally írta:
Quoted 29 lines
ACPI devices with
_HIDINT3472 are currently matched to the tps68470 driver, however this does not cover all situations in which that_HIDoccurs. We've encountered three possibilities:1. On Chrome OS devices, an ACPI device with
_HIDINT3472 (representing a physical tps68470 device) that requires a GPIO and OpRegion driver
2. On devices designed for Windows, an ACPI device with_HIDINT3472 (again representing a physical tps68470 device) which requires GPIO, Clock and Regulator drivers.
3. On other devices designed for Windows, an ACPI device with_HIDINT3472 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]>---
Changes in v2:- Switched to a module registering a platform driver to run the dummy ACPI devices, plus an i2c driver to replace and extend the existing tps68470 driver
- Added clock handling functions to the int3472-discrete driver
- A whole bunch of other changes too numerous to enumerate
Quoted 12 lines
MAINTAINERS | 5 + 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 +++++ 7 files changed, 875 insertions(+) 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
Have you considered putting the source (and header) files into a dedicated folder? I think it'd help manageability in the long run, and it'd be immediately obvious that these source files form a single "unit".
Regards,
Barnabás Pőcze
Re: [PATCH v2 6/7] platform: x86: Add intel_skl_int3472 driver
Quoted 5 lines · Barnabás Pőcze
2021. január 18., hétfő 1:34 keltezéssel, Daniel Scally írta:
Have you considered putting the source (and header) files into a dedicated folder? I think it'd help manageability in the long run, and it'd be immediately obvious that these source files form a single "unit".
What would be the folder name? Because, for example, intel_cht_int33fe* have no folder (yet?) and here it's kinda similar case when HID describes something else than just one IP.
Signature · 2 lines
With Best Regards, Andy Shevchenko
Re: [PATCH v2 6/7] platform: x86: Add intel_skl_int3472 driver
2021. január 18., hétfő 14:51 keltezéssel, Andy Shevchenko írta:
Quoted 10 lines · Barnabás Pőcze
Quoted 5 lines
2021. január 18., hétfő 1:34 keltezéssel, Daniel Scally írta:
Have you considered putting the source (and header) files into a dedicated folder? I think it'd help manageability in the long run, and it'd be immediately obvious that these source files form a single "unit".
What would be the folder name? Because, for example, intel_cht_int33fe* have no folder (yet?) and here it's kinda similar case when HID describes something else than just one IP.
I think "intel_skl_int3472" would not be a bad name for the folder. And I believe "intel_cht_int33fe" could be given its own folder as well.
Regards,
Barnabás Pőcze
Re: [PATCH v2 6/7] platform: x86: Add intel_skl_int3472 driver
Quoted 9 lines · Barnabás Pőcze
2021. január 18., hétfő 14:51 keltezéssel, Andy Shevchenko írta:
Quoted 7 lines · Barnabás Pőcze
Quoted 5 lines
2021. január 18., hétfő 1:34 keltezéssel, Daniel Scally írta:
Have you considered putting the source (and header) files into a dedicated folder? I think it'd help manageability in the long run, and it'd be immediately obvious that these source files form a single "unit".
Quoted 6 lines
Quoted 3 lines
What would be the folder name? Because, for example, intel_cht_int33fe* have no folder (yet?) and here it's kinda similar case when HID describes something else than just one IP.
I think "
intel_skl_int3472" would not be a bad name for the folder. And I believe "intel_cht_int33fe" could be given its own folder as well.
I;m not objecting (at some point in the past I had proposed moving Intel stuff to a separate folder, but at that time PDx86 has no folders at all and Darren was kinda not in favour of creating ones, but things changed), just let's hear Hans on this.
Signature · 2 lines
With Best Regards, Andy Shevchenko
Re: [PATCH v2 6/7] platform: x86: Add intel_skl_int3472 driver
Hi,
Quoted 14 lines · On 1/18/21 4:23 PM, [email protected] wrote:
Quoted 13 lines · Barnabás Pőcze
2021. január 18., hétfő 14:51 keltezéssel, Andy Shevchenko írta:
Quoted 10 lines · Barnabás Pőcze
Quoted 5 lines
2021. január 18., hétfő 1:34 keltezéssel, Daniel Scally írta:
Have you considered putting the source (and header) files into a dedicated folder? I think it'd help manageability in the long run, and it'd be immediately obvious that these source files form a single "unit".
What would be the folder name? Because, for example, intel_cht_int33fe* have no folder (yet?) and here it's kinda similar case when HID describes something else than just one IP.
Quoted 7 lines
Quoted 2 lines
I think "
intel_skl_int3472" would not be a bad name for the folder. And I believe "intel_cht_int33fe" could be given its own folder as well.I;m not objecting (at some point in the past I had proposed moving Intel stuff to a separate folder, but at that time PDx86 has no folders at all and Darren was kinda not in favour of creating ones, but things changed), just let's hear Hans on this.
I'm in favor of using a folder for this and "intel_skl_int3472" is fine with me.
With that said I'm not entirely sure if I'm in favor of the _skl_ part of the folder and driver name or not.
The INT3472 ACPI device is used with other CPUs, e.g. Apollo Lake too and I think the driver should work fine with those.
The intel_cht_int33fe case is special because the driver only applies to some models with an INT33FE ACPI device (the whole INT33FE ACPI device is a horrible thing which seems to stem from Intel rushing Bay Trail to market to try and compete on the tablet market).
With that all said SKL probably is the first SoC to feature this and I guess future IPUs may still use INT3472 given Intel's BAD habit of re-using ACPI HIDs for multiple incompatible generations. So I guess that keeping it is fine; and if we then need an incompatible INT3472 driver for newer IPUs we can use a different prefix for those.
TL;DR:
1. Using a folder is fine, desirable even
2. I've some concerns about the name, but I'm not really objecting, just giving my 2 cents.
Regards,
Hans
Re: [PATCH v2 6/7] platform: x86: Add intel_skl_int3472 driver
Quoted 1 line · Hans de Goede
On 1/18/21 4:23 PM, [email protected] wrote:
...
Quoted 3 lines
1. Using a folder is fine, desirable even
2. I've some concerns about the name, but I'm not really objecting, just giving my 2 cents.
Let's get into compromised summary:
- create a folder for these driver files
- name it without _skl_ while leaving this in the file / driver names
Does everybody agree on this approach?
Signature · 2 lines
With Best Regards, Andy Shevchenko
Re: [PATCH v2 6/7] platform: x86: Add intel_skl_int3472 driver
Quoted 4 lines · On 18/01/2021 15:48, [email protected] wrote:
Quoted 1 line · Hans de Goede
On 1/18/21 4:23 PM, [email protected] wrote:
...
Quoted 9 lines
Quoted 3 lines
1. Using a folder is fine, desirable even
2. I've some concerns about the name, but I'm not really objecting, just giving my 2 cents.Let's get into compromised summary:
- create a folder for these driver files
- name it without _skl_ while leaving this in the file / driver namesDoes everybody agree on this approach?
Works for me!
Re: [PATCH v2 6/7] platform: x86: Add intel_skl_int3472 driver
Hi,
Quoted 9 lines · Daniel Scally
Quoted 7 lines · On 18/01/2021 15:48, [email protected] wrote:
Quoted 1 line · Hans de Goede
On 1/18/21 4:23 PM, [email protected] wrote:
...
Quoted 3 lines
1. Using a folder is fine, desirable even
2. I've some concerns about the name, but I'm not really objecting, just giving my 2 cents.
Quoted 8 lines
Quoted 6 lines
Let's get into compromised summary:
- create a folder for these driver files
- name it without _skl_ while leaving this in the file / driver namesDoes everybody agree on this approach?
Works for me!
Also works for me.
Regards,
Hans
Re: [PATCH v2 6/7] platform: x86: Add intel_skl_int3472 driver
In reply to Hans de GoedeHi Hans,
Quoted 23 lines · Hans de Goede
Quoted 14 lines · On 1/18/21 4:23 PM, [email protected] wrote:
Quoted 13 lines · Barnabás Pőcze
2021. január 18., hétfő 14:51 keltezéssel, Andy Shevchenko írta:
Quoted 10 lines · Barnabás Pőcze
Quoted 5 lines
2021. január 18., hétfő 1:34 keltezéssel, Daniel Scally írta:
Have you considered putting the source (and header) files into a dedicated folder? I think it'd help manageability in the long run, and it'd be immediately obvious that these source files form a single "unit".
What would be the folder name? Because, for example, intel_cht_int33fe* have no folder (yet?) and here it's kinda similar case when HID describes something else than just one IP.
Quoted 7 lines
Quoted 2 lines
I think "
intel_skl_int3472" would not be a bad name for the folder. And I believe "intel_cht_int33fe" could be given its own folder as well.I;m not objecting (at some point in the past I had proposed moving Intel stuff to a separate folder, but at that time PDx86 has no folders at all and Darren was kinda not in favour of creating ones, but things changed), just let's hear Hans on this.
Quoted 7 lines
I'm in favor of using a folder for this and "
intel_skl_int3472" is fine with me.With that said I'm not entirely sure if I'm in favor of the _skl_ part of the folder and driver name or not.
The INT3472 ACPI device is used with other CPUs, e.g. Apollo Lake too and I think the driver should work fine with those.
It should work on Kabylake as well, although there are some differences in the way the INT3472 device is modelled in the DSDT between those two platforms. Hopefully nothing that couldn't be supported in a single driver without adding too many hacks.
Quoted 4 lines
The
intel_cht_int33fecase is special because the driver only applies to some models with an INT33FE ACPI device (the whole INT33FE ACPI device is a horrible thing which seems to stem from Intel rushing Bay Trail to market to try and compete on the tablet market).
The INT3472 ACPI device is also horrible. It reminds me of Intercal, the programming language that was created by gathering features of several well known languages and then making sure that none of them would be
used: the ACPI model of the device was probably created by someone who has studied ACPI extensively and decided to break every single best practice rule. I lack English words strong enough to express my dismay on this topic (but I still have hope to find solace in Finnish).
Quoted 11 lines
With that all said SKL probably is the first SoC to feature this and I guess future IPUs may still use INT3472 given Intel's BAD habit of re-using ACPI HIDs for multiple incompatible generations. So I guess that keeping it is fine; and if we then need an incompatible INT3472 driver for newer IPUs we can use a different prefix for those.
TL;DR:
1. Using a folder is fine, desirable even
2. I've some concerns about the name, but I'm not really objecting, just giving my 2 cents.
Signature · 3 lines
Regards, Laurent Pinchart
Re: [PATCH v2 6/7] platform: x86: Add intel_skl_int3472 driver
In reply to Daniel ScallyHi Daniel,
Quoted 63 lines · Daniel Scally
ACPI devices with
_HIDINT3472 are currently matched to the tps68470 driver, however this does not cover all situations in which that_HIDoccurs. We've encountered three possibilities:1. On Chrome OS devices, an ACPI device with
_HIDINT3472 (representing a physical tps68470 device) that requires a GPIO and OpRegion driver
2. On devices designed for Windows, an ACPI device with_HIDINT3472 (again representing a physical tps68470 device) which requires GPIO, Clock and Regulator drivers.
3. On other devices designed for Windows, an ACPI device with_HIDINT3472 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]>---
Changes in v2:- Switched to a module registering a platform driver to run the dummy ACPI devices, plus an i2c driver to replace and extend the existing tps68470 driver
- Added clock handling functions to the int3472-discrete driver
- A whole bunch of other changes too numerous to enumerateMAINTAINERS | 5 + 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 +++++ 7 files changed, 875 insertions(+) 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.cMAINTAINERS +5
-0@@ -9147,6 +9147,11 @@ S: Maintained F: arch/x86/include/asm/intel_scu_ipc.h F: drivers/platform/x86/intel_scu_* +INTEL SKL INT3472 ACPI DEVICE DRIVER +M: Daniel Scally <[email protected]> +S: Maintained +F: drivers/platform/x86/intel_skl_int3472_* + INTEL SPEED SELECT TECHNOLOGY M: Srinivas Pandruvada <[email protected]> L: [email protected]drivers/platform/x86/Kconfig +0
-0
drivers/platform/x86/Kconfig config INTEL_CHT_INT33FE · line 850
Quoted 7 lines
drivers/platform/x86/Kconfig +4
-0@@ -844,6 +844,31 @@ config INTEL_CHT_INT33FE device and CONFIG_TYPEC_FUSB302=m and CONFIG_BATTERY_MAX17042=m for Type-C device. +config INTEL_SKL_INT3472 + tristate "Intel SkyLake ACPI INT3472 Driver" + depends on X86 && ACPI + select REGMAP_I2C
I've tried compiling this as a built in and a module and on my minimal config I had failures on both for regulator_register and regulator_unregister.
I suspect this needs to have either a selects or a depends upon CONFIG_REGULATOR
--
Regards
Kieran
Quoted 905 lines
drivers/platform/x86/Kconfig +21
-0+ help + This driver adds support for the INT3472 ACPI devices found on some + Intel SkyLake devices. + + There are 3 kinds of INT3472 ACPI device possible; two for devices + designed for Windows (either with or without a physical tps68470 + PMIC) and one designed for Chrome OS. This driver handles all three + situations by discovering information it needs to discern them at + runtime. + + If your device was designed for Chrome OS, this driver will provide + an ACPI operation region, which must be available before any of the + devices using this are probed. For this reason, you should select Y + if your device was designed for ChromeOS. This option also configures + the designware-i2c driver to be built-in, for the same reason. + + Say Y or M here if you have a SkyLake device designed for use + with Windows or ChromeOS. Say N here if you are not sure. + + The module will be named "intel-skl-int3472" + config INTEL_HID_EVENT tristate "INTEL HID Event" depends on ACPIdrivers/platform/x86/Makefile +4
-0@@ -86,6 +86,10 @@ obj-$(CONFIG_INTEL_HID_EVENT) += intel-hid.o obj-$(CONFIG_INTEL_INT0002_VGPIO) += intel_int0002_vgpio.o obj-$(CONFIG_INTEL_MENLOW) += intel_menlow.o obj-$(CONFIG_INTEL_OAKTRAIL) += intel_oaktrail.o +obj-$(CONFIG_INTEL_SKL_INT3472) += intel_skl_int3472.o +intel_skl_int3472-objs := intel_skl_int3472_common.o \ + intel_skl_int3472_discrete.o \ + intel_skl_int3472_tps68470.o obj-$(CONFIG_INTEL_VBTN) += intel-vbtn.o # MSIdrivers/platform/x86/intel_skl_int3472_common.c new file +100
-0@@ -0,0 +1,100 @@ +// SPDX-License-Identifier: GPL-2.0 +/* Author: Dan Scally <[email protected]> */ + +#include <linux/acpi.h> +#include <linux/i2c.h> +#include <linux/platform_device.h> + +#include "intel_skl_int3472_common.h" + +int skl_int3472_get_cldb_buffer (struct acpi_device *adev, +struct int3472_cldb *cldb) +{ +struct acpi_buffer buffer = {ACPI_ALLOCATE_BUFFER ,NULL }; +acpi_handle handle = adev->handle; +union acpi_object *obj; +acpi_status status; +int ret =0 ; + + status =acpi_evaluate_object (handle,"CLDB" ,NULL , &buffer); +if (ACPI_FAILURE (status)) +return -ENODEV ; + + obj = buffer.pointer; +if (!obj) { +dev_err (&adev->dev,"ACPI device has no CLDB object\n" ); +return -ENODEV ; + } + +if (obj->type !=ACPI_TYPE_BUFFER ) { +dev_err (&adev->dev,"CLDB object is not an ACPI buffer\n" ); + ret = -EINVAL ; + goto out_free_buff; + } + +if (obj->buffer.length >sizeof (*cldb)) { +dev_err (&adev->dev,"The CLDB buffer is too large\n" ); + ret = -EINVAL ; + goto out_free_buff; + } + +memcpy (cldb, obj->buffer.pointer, obj->buffer.length); + +out_free_buff: +kfree (buffer.pointer); +return ret; +} + +static const struct acpi_device_id int3472_device_id[] = { + {"INT3472" ,0 }, + { }, +}; +MODULE_DEVICE_TABLE (acpi, int3472_device_id); + +static struct platform_driver int3472_discrete = { + .driver = { + .name ="int3472-discrete" , + .acpi_match_table = int3472_device_id, + }, + .probe = skl_int3472_discrete_probe, + .remove = skl_int3472_discrete_remove, +}; + +static struct i2c_driver int3472_tps68470 = { + .driver = { + .name ="int3472-tps68470" , + .acpi_match_table = int3472_device_id, + }, + .probe_new = skl_int3472_tps68470_probe, +}; + +static int skl_int3472_init (void ) +{ +int ret =0 ; + + ret =platform_driver_register (&int3472_discrete); +if (ret) +return ret; + + ret =i2c_register_driver (THIS_MODULE , &int3472_tps68470); +if (ret) + goto err_unregister_plat_drv; + +return 0 ; + +err_unregister_plat_drv: +platform_driver_unregister (&int3472_discrete); +return ret; +} +module_init (skl_int3472_init); + +static void skl_int3472_exit (void ) +{ +platform_driver_unregister (&int3472_discrete); +i2c_del_driver (&int3472_tps68470); +} +module_exit (skl_int3472_exit); + +MODULE_DESCRIPTION ("Intel SkyLake INT3472 ACPI Device Driver" ); +MODULE_AUTHOR ("Daniel Scally <[email protected]>" ); +MODULE_LICENSE ("GPL v2" );drivers/platform/x86/intel_skl_int3472_common.h new file +100
-0@@ -0,0 +1,100 @@ +/* SPDX-License-Identifier: GPL-2.0 */ +/* Author: Dan Scally <[email protected]> */ +#include <linux/regulator/machine.h> +#include <linux/clk-provider.h> +#include <linux/gpio/machine.h> +#include <linux/regulator/driver.h> +#include <linux/types.h> + +/* PMIC GPIO Types */ +#define INT3472_GPIO_TYPE_RESET 0x00 +#define INT3472_GPIO_TYPE_POWERDOWN 0x01 +#define INT3472_GPIO_TYPE_CLK_ENABLE 0x0c +#define INT3472_GPIO_TYPE_POWER_ENABLE 0x0b +#define INT3472_GPIO_TYPE_PRIVACY_LED 0x0d +#define INT3472_PDEV_MAX_NAME_LEN 23 +#define INT3472_MAX_SENSOR_GPIOS 3 +#define GPIO_REGULATOR_NAME_LENGTH 27 +#define GPIO_REGULATOR_SUPPLY_NAME_LENGTH 9 + +#define INT3472_REGULATOR (_NAME, _SUPPLY, _OPS) \ + (const struct regulator_desc) { \ + .name = _NAME, \ + .supply_name = _SUPPLY, \ + .id = 0, \ + .type = REGULATOR_VOLTAGE, \ + .ops = _OPS, \ + .owner = THIS_MODULE, \ + } + +#define INT3472_GPIO_FUNCTION_REMAP (_PIN, _FUNCTION) \ + (const struct int3472_gpio_function_remap) { \ + .documented = _PIN, \ + .actual = _FUNCTION \ + } + +#define to_int3472_clk (hw) \ + container_of(hw, struct int3472_gpio_clock, clk_hw) + +struct int3472_cldb { +u8 version; +/* +* control logic type +* 0: UNKNOWN +* 1: DISCRETE(CRD-D) +* 2: PMIC TPS68470 +* 3: PMIC uP6641 +*/ +u8 control_logic_type; +u8 control_logic_id; +u8 sensor_card_sku; +u8 reserved[28 ]; +}; + +struct int3472_gpio_regulator { +char regulator_name[GPIO_REGULATOR_NAME_LENGTH ]; +char supply_name[GPIO_REGULATOR_SUPPLY_NAME_LENGTH ]; +struct gpio_desc *gpio; +struct regulator_dev *rdev; +struct regulator_desc rdesc; +}; + +struct int3472_gpio_clock { +struct clk *clk; +struct clk_hw clk_hw; +struct clk_lookup *cl; +struct gpio_desc *gpio; +}; + +struct int3472_device { +struct acpi_device *adev; +struct platform_device *pdev; +struct acpi_device *sensor; +char *sensor_name; + +unsigned int n_gpios;/* how many GPIOs have we seen */ + +struct int3472_gpio_regulator regulator; +struct int3472_gpio_clock clock; + +unsigned int n_sensor_gpios;/* how many have we mapped to sensor */ +bool gpios_mapped; +struct gpiod_lookup_table gpios; +}; + +struct int3472_gpio_function_remap { +char *documented; +char *actual; +}; + +struct int3472_sensor_config { +char *sensor_module_name; +struct regulator_consumer_supply supply_map; +const struct int3472_gpio_function_remap *function_maps; +}; + +int skl_int3472_discrete_probe (struct platform_device *pdev); +int skl_int3472_discrete_remove (struct platform_device *pdev); +int skl_int3472_tps68470_probe (struct i2c_client *client); +int skl_int3472_get_cldb_buffer (struct acpi_device *adev, +struct int3472_cldb *cldb);drivers/platform/x86/intel_skl_int3472_discrete.c new file +496
-0@@ -0,0 +1,496 @@ +// SPDX-License-Identifier: GPL-2.0 +/* Author: Dan Scally <[email protected]> */ + +#include <linux/acpi.h> +#include <linux/clkdev.h> +#include <linux/gpio/consumer.h> +#include <linux/i2c.h> +#include <linux/kernel.h> +#include <linux/module.h> +#include <linux/platform_device.h> +#include <linux/regulator/driver.h> + +#include "intel_skl_int3472_common.h" + +/* 79234640-9e10-4fea-a5c1-b5aa8b19756f */ +static const guid_t int3472_gpio_guid = +GUID_INIT (0x79234640 ,0x9e10 ,0x4fea , +0xa5 ,0xc1 ,0xb5 ,0xaa ,0x8b ,0x19 ,0x75 ,0x6f ); + +/* 822ace8f-2814-4174-a56b-5f029fe079ee */ +static const guid_t cio2_sensor_module_guid = +GUID_INIT (0x822ace8f ,0x2814 ,0x4174 , +0xa5 ,0x6b ,0x5f ,0x02 ,0x9f ,0xe0 ,0x79 ,0xee ); + +/* +* Here follows platform specific mapping information that we can pass to +* the functions mapping resources to the sensors. Where the sensors have +* a power enable pin defined in DSDT we need to provide a supply name so +* the sensor drivers can find the regulator. Optionally, we can provide a +* NULL terminated array of function name mappings to deal with any platform +* specific deviations from the documented behaviour of GPIOs. +* +* Map a GPIO function name to NULL to prevent the driver from mapping that +* GPIO at all. +*/ + +static const struct int3472_gpio_function_remap ov2680_gpio_function_remaps[] = { +INT3472_GPIO_FUNCTION_REMAP ("reset" ,NULL ), +INT3472_GPIO_FUNCTION_REMAP ("powerdown" ,"reset" ), + { } +}; + +static struct int3472_sensor_config int3472_sensor_configs[] = { +/* Lenovo Miix 510-12ISK - OV2680, Front */ + {"GNDF140809R" , {0 }, ov2680_gpio_function_remaps}, +/* Lenovo Miix 510-12ISK - OV5648, Rear */ + {"GEFF150023R" ,REGULATOR_SUPPLY ("avdd" ,"i2c-OVTI5648:00" ),NULL }, +/* Surface Go 1&2 - OV5693, Front */ + {"YHCU" ,REGULATOR_SUPPLY ("avdd" ,"i2c-INT33BE:00" ),NULL }, +}; + +/* +* The regulators have to have .ops to be valid, but the only ops we actually +* support are .enable and .disable which are handled via .ena_gpiod. Pass an +* empty struct to clear the check without lying about capabilities. +*/ +static const struct regulator_ops int3472_gpio_regulator_ops = {0 }; + +static int skl_int3472_clk_enable (struct clk_hw *hw) +{ +struct int3472_gpio_clock *clk =to_int3472_clk (hw); + +gpiod_set_value (clk->gpio,1 ); + +return 0 ; +} + +static void skl_int3472_clk_disable (struct clk_hw *hw) +{ +struct int3472_gpio_clock *clk =to_int3472_clk (hw); + +gpiod_set_value (clk->gpio,0 ); +} + +static int skl_int3472_clk_prepare (struct clk_hw *hw) +{ +/* +* We're just turning a GPIO on to enable, so nothing to do here, but +* we want to provide the op so prepare_enable() works. +*/ +return 0 ; +} + +static void skl_int3472_clk_unprepare (struct clk_hw *hw) +{ +/* Likewise, nothing to do here... */ +} + +static const struct clk_ops skl_int3472_clock_ops = { + .prepare = skl_int3472_clk_prepare, + .unprepare = skl_int3472_clk_unprepare, + .enable = skl_int3472_clk_enable, + .disable = skl_int3472_clk_disable, +}; + +static struct int3472_sensor_config * +skl_int3472_get_sensor_module_config (struct int3472_device *int3472) +{ +unsigned int i =ARRAY_SIZE (int3472_sensor_configs); +struct int3472_sensor_config *ret; +union acpi_object *obj; + + obj =acpi_evaluate_dsm_typed (int3472->sensor->handle, + &cio2_sensor_module_guid,0x00 , +0x01 ,NULL ,ACPI_TYPE_STRING ); + +if (!obj) { +dev_err (&int3472->pdev->dev, +"Failed to get sensor module string from _DSM\n" ); +return ERR_PTR (-ENODEV ); + } + +if (obj->string.type !=ACPI_TYPE_STRING ) { +dev_err (&int3472->pdev->dev, +"Sensor _DSM returned a non-string value\n" ); + ret =ERR_PTR (-EINVAL ); + goto out_free_obj; + } + + ret =ERR_PTR (-ENODEV ); +while (i--) { +if (!strcmp (int3472_sensor_configs[i].sensor_module_name, + obj->string.pointer)) { + ret = &int3472_sensor_configs[i]; + goto out_free_obj; + } + } + +out_free_obj: +ACPI_FREE (obj); +return ret; +} + +static int skl_int3472_map_gpio_to_sensor (struct int3472_device *int3472, +struct acpi_resource *ares, +char *func,u32 polarity) +{ +char *path = ares->data.gpio.resource_source.string_ptr; +struct int3472_sensor_config *sensor_config; +struct gpiod_lookup table_entry; +struct acpi_device *adev; +acpi_handle handle; +acpi_status status; +int ret; + + sensor_config =skl_int3472_get_sensor_module_config (int3472); +if (!IS_ERR (sensor_config) && sensor_config->function_maps) { +unsigned int i =0 ; + +while (sensor_config->function_maps[i].documented) { +if (!strcmp (func, sensor_config->function_maps[i].documented)) { + func = sensor_config->function_maps[i].actual; + +break ; + } + + i++; + } + } + +if (!func) +return 0 ; + +if (int3472->n_sensor_gpios >=INT3472_MAX_SENSOR_GPIOS ) { +dev_warn (&int3472->pdev->dev,"Too many GPIOs mapped\n" ); +return -EINVAL ; + } + + status =acpi_get_handle (NULL , path, &handle); +if (ACPI_FAILURE (status)) +return -EINVAL ; + + ret =acpi_bus_get_device (handle, &adev); +if (ret) +return -ENODEV ; + + table_entry = (struct gpiod_lookup )GPIO_LOOKUP_IDX (acpi_dev_name (adev), + ares->data.gpio.pin_table[0 ], + func,0 , polarity); + +memcpy (&int3472->gpios.table[int3472->n_sensor_gpios], &table_entry, +sizeof (table_entry)); + + int3472->n_sensor_gpios++; + +return 0 ; +} + +static int skl_int3472_register_clock (struct int3472_device *int3472, +struct acpi_resource *ares) +{ +char *path = ares->data.gpio.resource_source.string_ptr; +struct clk_init_data init = { }; +int ret =0 ; + + init.name =kasprintf (GFP_KERNEL ,"%s-clk" , +acpi_dev_name (int3472->adev)); + init.ops = &skl_int3472_clock_ops; + + int3472->clock.gpio =acpi_get_gpiod (path, + ares->data.gpio.pin_table[0 ]); +if (IS_ERR (int3472->clock.gpio)) { + ret =PTR_ERR (int3472->clock.gpio); + goto out_free_init_name; + } + + int3472->clock.clk_hw.init = &init; + int3472->clock.clk =clk_register (&int3472->adev->dev, + &int3472->clock.clk_hw); +if (IS_ERR (int3472->clock.clk)) { + ret =PTR_ERR (int3472->clock.clk); + goto err_put_gpio; + } + + int3472->clock.cl =clkdev_create (int3472->clock.clk,"xvclk" , + int3472->sensor_name); +if (IS_ERR_OR_NULL (int3472->clock.cl)) + goto err_unregister_clk; + + goto out_free_init_name; + +err_unregister_clk: +clk_unregister (int3472->clock.clk); +err_put_gpio: +gpiod_put (int3472->clock.gpio); +out_free_init_name: +kfree (init.name); + +return ret; +} + +static int skl_int3472_register_regulator (struct int3472_device *int3472, +struct acpi_resource *ares) +{ +char *path = ares->data.gpio.resource_source.string_ptr; +struct int3472_sensor_config *sensor_config; +struct regulator_init_data init_data = { }; +struct regulator_config cfg = { }; +int ret; + + sensor_config =skl_int3472_get_sensor_module_config (int3472); +if (IS_ERR_OR_NULL (sensor_config)) { +dev_err (&int3472->pdev->dev,"No sensor module config\n" ); +return PTR_ERR (sensor_config); + } + +if (!sensor_config->supply_map.supply) { +dev_err (&int3472->pdev->dev,"No supply name defined\n" ); +return -ENODEV ; + } + + init_data.supply_regulator =NULL ; + init_data.constraints.valid_ops_mask =REGULATOR_CHANGE_STATUS ; + init_data.num_consumer_supplies =1 ; + init_data.consumer_supplies = &sensor_config->supply_map; + +snprintf (int3472->regulator.regulator_name, +GPIO_REGULATOR_NAME_LENGTH ,"int3472-discrete-regulator" ); +snprintf (int3472->regulator.supply_name, +GPIO_REGULATOR_SUPPLY_NAME_LENGTH ,"supply-0" ); + + int3472->regulator.rdesc =INT3472_REGULATOR ( + int3472->regulator.regulator_name, + int3472->regulator.supply_name, + &int3472_gpio_regulator_ops); + + int3472->regulator.gpio =acpi_get_gpiod (path, + ares->data.gpio.pin_table[0 ]); +if (IS_ERR (int3472->regulator.gpio)) { +dev_err (&int3472->pdev->dev,"Failed to get GPIO line\n" ); +return PTR_ERR (int3472->regulator.gpio); + } + + cfg.dev = &int3472->adev->dev; + cfg.init_data = &init_data; + cfg.ena_gpiod = int3472->regulator.gpio; + + int3472->regulator.rdev =regulator_register (&int3472->regulator.rdesc, + &cfg); +if (IS_ERR (int3472->regulator.rdev)) { + ret =PTR_ERR (int3472->regulator.rdev); + goto err_free_gpio; + } + +return 0 ; + +err_free_gpio: +gpiod_put (int3472->regulator.gpio); + +return ret; +} + +/** +* skl_int3472_handle_gpio_resources: maps PMIC resources to consuming sensor +* @ares: A pointer to a &struct acpi_resource +* @data: A pointer to a &struct int3472_device +* +* This function handles GPIO resources that are against an INT3472 +* ACPI device, by checking the value of the corresponding _DSM entry. +* This will return a 32bit int, where the lowest byte represents the +* function of the GPIO pin: +* +* 0x00 Reset +* 0x01 Power down +* 0x0b Power enable +* 0x0c Clock enable +* 0x0d Privacy LED +* +* There are some known platform specific quirks where that does not quite +* hold up; for example where a pin with type 0x01 (Power down) is mapped to +* a sensor pin that performs a reset function or entries in _CRS and _DSM that +* do not actually correspond to a physical connection. These will be handled by +* the mapping sub-functions. +* +* GPIOs will either be mapped directly to the sensor device or else used +* to create clocks and regulators via the usual frameworks. +* +* Return: +* * 0 - When all resources found are handled properly. +* * -EINVAL - If the resource is not a GPIO IO resource +* * -ENODEV - If the resource has no corresponding _DSM entry +* * -Other - Errors propagated from one of the sub-functions. +*/ +static int skl_int3472_handle_gpio_resources (struct acpi_resource *ares, +void *data) +{ +struct int3472_device *int3472 = data; +union acpi_object *obj; +int ret =0 ; + +if (ares->type !=ACPI_RESOURCE_TYPE_GPIO || + ares->data.gpio.connection_type !=ACPI_RESOURCE_GPIO_TYPE_IO ) +return EINVAL ;/* Deliberately positive so parsing continues */ + +/* +* n_gpios + 2 because the index of this _DSM function is 1-based and +* the first function is just a count. +*/ + obj =acpi_evaluate_dsm_typed (int3472->adev->handle, + &int3472_gpio_guid,0x00 , + int3472->n_gpios +2 , +NULL ,ACPI_TYPE_INTEGER ); + +if (!obj) { +dev_warn (&int3472->pdev->dev, +"No _DSM entry for this GPIO pin\n" ); +return ENODEV ; + } + +switch (obj->integer.value &0xff ) { +case INT3472_GPIO_TYPE_RESET : + ret =skl_int3472_map_gpio_to_sensor (int3472, ares,"reset" , +GPIO_ACTIVE_LOW ); +if (ret) +dev_err (&int3472->pdev->dev, +"Failed to map reset pin to sensor\n" ); + +break ; +case INT3472_GPIO_TYPE_POWERDOWN : + ret =skl_int3472_map_gpio_to_sensor (int3472, ares,"powerdown" , +GPIO_ACTIVE_LOW ); +if (ret) +dev_err (&int3472->pdev->dev, +"Failed to map powerdown pin to sensor\n" ); + +break ; +case INT3472_GPIO_TYPE_CLK_ENABLE : + ret =skl_int3472_register_clock (int3472, ares); +if (ret) +dev_err (&int3472->pdev->dev, +"Failed to map clock to sensor\n" ); + +break ; +case INT3472_GPIO_TYPE_POWER_ENABLE : + ret =skl_int3472_register_regulator (int3472, ares); +if (ret) { +dev_err (&int3472->pdev->dev, +"Failed to map regulator to sensor\n" ); + } + +break ; +case INT3472_GPIO_TYPE_PRIVACY_LED : + ret =skl_int3472_map_gpio_to_sensor (int3472, ares, +"indicator-led" , +GPIO_ACTIVE_HIGH ); +if (ret) +dev_err (&int3472->pdev->dev, +"Failed to map indicator led to sensor\n" ); + +break ; +default : +dev_warn (&int3472->pdev->dev, +"GPIO type 0x%llx unknown; the sensor may not work\n" , + (obj->integer.value &0xff )); + ret =EINVAL ; + } + + int3472->n_gpios++; +ACPI_FREE (obj); + +return ret; +} + +static int skl_int3472_parse_crs (struct int3472_device *int3472) +{ +struct list_head resource_list; +int ret =0 ; + +INIT_LIST_HEAD (&resource_list); + + ret =acpi_dev_get_resources (int3472->adev, &resource_list, + skl_int3472_handle_gpio_resources, + int3472); + +if (!ret) { +gpiod_add_lookup_table (&int3472->gpios); + int3472->gpios_mapped = true; + } + +acpi_dev_free_resource_list (&resource_list); + +return ret; +} + +int skl_int3472_discrete_probe (struct platform_device *pdev) +{ +struct acpi_device *adev =ACPI_COMPANION (&pdev->dev); +struct int3472_device *int3472; +struct int3472_cldb cldb; +int ret =0 ; + + ret =skl_int3472_get_cldb_buffer (adev, &cldb); +if (ret || cldb.control_logic_type !=1 ) +return -EINVAL ; + + int3472 =kzalloc (sizeof (*int3472) + + ((INT3472_MAX_SENSOR_GPIOS +1 ) *sizeof (struct gpiod_lookup )), +GFP_KERNEL ); +if (!int3472) +return -ENOMEM ; + + int3472->adev = adev; + int3472->pdev = pdev; +platform_set_drvdata (pdev, int3472); + + int3472->sensor =acpi_dev_get_next_dep_dev (adev,NULL ); +if (!int3472->sensor) { +dev_err (&pdev->dev, +"This INT3472 entry seems to have no dependents.\n" ); + ret = -ENODEV ; + goto err_free_int3472; + } + int3472->sensor_name =i2c_acpi_dev_name (int3472->sensor); + int3472->gpios.dev_id = int3472->sensor_name; + + ret =skl_int3472_parse_crs (int3472); +if (ret) { +skl_int3472_discrete_remove (pdev); + goto err_return_ret; + } + +return 0 ; + +err_free_int3472: +kfree (int3472); +err_return_ret: +return ret; +} + +int skl_int3472_discrete_remove (struct platform_device *pdev) +{ +struct int3472_device *int3472; + + int3472 =platform_get_drvdata (pdev); + +if (int3472->gpios_mapped) +gpiod_remove_lookup_table (&int3472->gpios); + +if (!IS_ERR_OR_NULL (int3472->regulator.rdev)) { +gpiod_put (int3472->regulator.gpio); +regulator_unregister (int3472->regulator.rdev); + } + +if (!IS_ERR_OR_NULL (int3472->clock.clk)) { +gpiod_put (int3472->clock.gpio); +clk_unregister (int3472->clock.clk); +clkdev_drop (int3472->clock.cl); + } + +acpi_dev_put (int3472->sensor); + +kfree (int3472->sensor_name); +kfree (int3472); + +return 0 ; +}drivers/platform/x86/intel_skl_int3472_tps68470.c new file +145
-0@@ -0,0 +1,145 @@ +// SPDX-License-Identifier: GPL-2.0 +/* Author: Dan Scally <[email protected]> */ + +#include <linux/i2c.h> +#include <linux/mfd/tps68470.h> +#include <linux/platform_device.h> +#include <linux/regmap.h> + +#include "intel_skl_int3472_common.h" + +static const struct regmap_config tps68470_regmap_config = { + .reg_bits =8 , + .val_bits =8 , + .max_register =TPS68470_REG_MAX , +}; + +static int tps68470_chip_init (struct device *dev,struct regmap *regmap) +{ +unsigned int version; +int ret; + +/* Force software reset */ + ret =regmap_write (regmap,TPS68470_REG_RESET ,TPS68470_REG_RESET_MASK ); +if (ret) +return ret; + + ret =regmap_read (regmap,TPS68470_REG_REVID , &version); +if (ret) { +dev_err (dev,"Failed to read revision register: %d\n" , ret); +return ret; + } + +dev_info (dev,"TPS68470 REVID: 0x%x\n" , version); + +return 0 ; +} + +static struct platform_device * +skl_int3472_register_pdev (const char *name,struct device *parent) +{ +struct platform_device *pdev; +int ret; + + pdev =platform_device_alloc (name,PLATFORM_DEVID_NONE ); +if (IS_ERR_OR_NULL (pdev)) +return ERR_PTR (-ENOMEM ); + + pdev->dev.parent = parent; + pdev->driver_override =kstrndup (pdev->name,INT3472_PDEV_MAX_NAME_LEN , +GFP_KERNEL ); + + ret =platform_device_add (pdev); +if (ret) { +platform_device_put (pdev); +return ERR_PTR (ret); + } + +return pdev; +} + +int skl_int3472_tps68470_probe (struct i2c_client *client) +{ +struct acpi_device *adev =ACPI_COMPANION (&client->dev); +struct platform_device *regulator_dev; +struct platform_device *opregion_dev; +struct platform_device *gpio_dev; +struct int3472_cldb cldb = {0 }; +struct platform_device *clk_dev; +bool cldb_present = true; +struct regmap *regmap; +int ret =0 ; + + regmap =devm_regmap_init_i2c (client, &tps68470_regmap_config); +if (IS_ERR (regmap)) { +dev_err (&client->dev,"devm_regmap_init_i2c Error %ld\n" , +PTR_ERR (regmap)); +return PTR_ERR (regmap); + } + +i2c_set_clientdata (client, regmap); + + ret =tps68470_chip_init (&client->dev, regmap); +if (ret <0 ) { +dev_err (&client->dev,"TPS68470 Init Error %d\n" , ret); +return ret; + } + +/* +* Check CLDB buffer against the PMIC's adev. If present, then we check +* the value of control_logic_type field and follow one of the +* following scenarios: +* +* 1. No CLDB - likely ACPI tables designed for ChromeOS. We +* create platform devices for the GPIOs and OpRegion drivers. +* +* 2. CLDB, with control_logic_type = 2 - probably ACPI tables +* made for Windows 2-in-1 platforms. Register pdevs for GPIO, +* Clock and Regulator drivers to bind to. +* +* 3. Any other value in control_logic_type, we should never have +* gotten to this point; crash and burn. +*/ + ret =skl_int3472_get_cldb_buffer (adev, &cldb); +if (!ret && cldb.control_logic_type !=2 ) +return -EINVAL ; + +if (ret) + cldb_present = false; + + gpio_dev =skl_int3472_register_pdev ("tps68470-gpio" , &client->dev); +if (IS_ERR (gpio_dev)) +return PTR_ERR (gpio_dev); + +if (cldb_present) { + clk_dev =skl_int3472_register_pdev ("tps68470-clk" , + &client->dev); +if (IS_ERR (clk_dev)) { + ret =PTR_ERR (clk_dev); + goto err_free_gpio; + } + + regulator_dev =skl_int3472_register_pdev ("tps68470-regulator" , + &client->dev); +if (IS_ERR (regulator_dev)) { + ret =PTR_ERR (regulator_dev); + goto err_free_clk; + } + }else { + opregion_dev =skl_int3472_register_pdev ("tps68470_pmic_opregion" , + &client->dev); +if (IS_ERR (opregion_dev)) { + ret =PTR_ERR (opregion_dev); + goto err_free_gpio; + } + } + +return 0 ; + +err_free_clk: +platform_device_put (clk_dev); +err_free_gpio: +platform_device_put (gpio_dev); + +return ret; +}
Signature · 3 lines
Regards -- Kieran
Re: [PATCH v2 6/7] platform: x86: Add intel_skl_int3472 driver
Quoted 1 line · Kieran Bingham
On 18/01/2021 00:34, Daniel Scally wrote:
...
Quoted 11 lines
drivers/platform/x86/Kconfig config INTEL_CHT_INT33FE · line 850
Quoted 4 lines
drivers/platform/x86/Kconfig +4
-0+config INTEL_SKL_INT3472 + tristate "Intel SkyLake ACPI INT3472 Driver" + depends on X86 && ACPI + select REGMAP_I2CI've tried compiling this as a built in and a module and on my minimal config I had failures on both for
regulator_registerandregulator_unregister.I suspect this needs to have either a selects or a depends upon
CONFIG_REGULATOR
Valid point, although it seems no consensus on which is better to use. It seems to me that in this case we need to select it.
Signature · 2 lines
With Best Regards, Andy Shevchenko
Re: [PATCH v2 6/7] platform: x86: Add intel_skl_int3472 driver
Quoted 12 lines · Andy Shevchenko
Quoted 1 line · Kieran Bingham
On 18/01/2021 00:34, Daniel Scally wrote:
...
Quoted 8 lines
drivers/platform/x86/Kconfig config INTEL_CHT_INT33FE · line 850
Quoted 4 lines
drivers/platform/x86/Kconfig +4
-0+config INTEL_SKL_INT3472 + tristate "Intel SkyLake ACPI INT3472 Driver" + depends on X86 && ACPI + select REGMAP_I2CI've tried compiling this as a built in and a module and on my minimal config I had failures on both for
regulator_registerandregulator_unregister.
Quoted 5 lines
Quoted 2 lines
I suspect this needs to have either a selects or a depends upon
CONFIG_REGULATORValid point, although it seems no consensus on which is better to use. It seems to me that in this case we need to select it.
Yeah; it will be necessary for the gpio-regulator too anyway I expect.
Thanks Kieran; I missed that entirely.
PATCH v2 7/7 mfd: Remove tps68470 MFD driver
In reply to Daniel ScallyThis driver only covered one scenario in which ACPI devices with _HID INT3472 are found, and its functionality has been taken over by the intel-skl-int3472 module, so remove it.
---
Changes in v2:
- Introduced
drivers/acpi/pmic/Kconfig | 1 - drivers/gpio/Kconfig | 1 - drivers/mfd/Kconfig | 18 -------- drivers/mfd/Makefile | 1 - drivers/mfd/tps68470.c | 97 --------------------------------------- 5 files changed, 118 deletions(-) delete mode 100644 drivers/mfd/tps68470.c
drivers/acpi/pmic/Kconfig +0 -1
@@ -52,7 +52,6 @@ endif # PMIC_OPREGION config TPS68470_PMIC_OPREGION bool "ACPI operation region support for TPS68470 PMIC" - depends on MFD_TPS68470 help This config adds ACPI operation region support for TI TPS68470 PMIC. TPS68470 device is an advanced power management unit that powers
drivers/gpio/Kconfig +0 -1
@@ -1343,7 +1343,6 @@ config GPIO_TPS65912 config GPIO_TPS68470 bool "TPS68470 GPIO" - depends on MFD_TPS68470 help Select this option to enable GPIO driver for the TPS68470 chip family.
drivers/mfd/Kconfig +0 -18
@@ -1520,24 +1520,6 @@ config MFD_TPS65217 This driver can also be built as a module. If so, the module will be called tps65217. -config MFD_TPS68470 - bool "TI TPS68470 Power Management / LED chips" - depends on ACPI && PCI && I2C=y - depends on I2C_DESIGNWARE_PLATFORM=y - select MFD_CORE - select REGMAP_I2C - help - If you say yes here you get support for the TPS68470 series of - Power Management / LED chips. - - These include voltage regulators, LEDs and other features - that are often used in portable devices. - - This option is a bool as it provides an ACPI operation - region, which must be available before any of the devices - using this are probed. This option also configures the - designware-i2c driver to be built-in, for the same reason. - config MFD_TI_LP873X tristate "TI LP873X Power Management IC" depends on I2C
drivers/mfd/Makefile +0 -1
@@ -105,7 +105,6 @@ obj-$(CONFIG_MFD_TPS65910) += tps65910.o obj-$(CONFIG_MFD_TPS65912) += tps65912-core.o obj-$(CONFIG_MFD_TPS65912_I2C) += tps65912-i2c.o obj-$(CONFIG_MFD_TPS65912_SPI) += tps65912-spi.o -obj-$(CONFIG_MFD_TPS68470) += tps68470.o obj-$(CONFIG_MFD_TPS80031) += tps80031.o obj-$(CONFIG_MENELAUS) += menelaus.o
drivers/mfd/tps68470.c deleted +0 -97
97 lines not on this page · raw message
Signature · 1 line
2.25.1
Re: [PATCH v2 7/7] mfd: Remove tps68470 MFD driver
Hi Daniel,
Thank you for the patch.
Quoted 23 lines · Daniel Scally
This driver only covered one scenario in which ACPI devices with
_HIDINT3472 are found, and its functionality has been taken over by the intel-skl-int3472 module, so remove it.Signed-off-by Daniel Scally <[email protected]>---
Changes in v2:- Introduced
drivers/acpi/pmic/Kconfig | 1 - drivers/gpio/Kconfig | 1 - drivers/mfd/Kconfig | 18 -------- drivers/mfd/Makefile | 1 - drivers/mfd/tps68470.c | 97 --------------------------------------- 5 files changed, 118 deletions(-) delete mode 100644 drivers/mfd/tps68470.cdrivers/acpi/pmic/Kconfig +0
-0
drivers/acpi/pmic/Kconfig endif # PMIC_OPREGION · line 55
Quoted 4 lines
drivers/acpi/pmic/Kconfig +0
-1@@ -52,7 +52,6 @@ endif # PMIC_OPREGION config TPS68470_PMIC_OPREGION bool "ACPI operation region support for TPS68470 PMIC" - depends on MFD_TPS68470
Should this now depend on INTEL_SKL_INT3472 ?
drivers/gpio/Kconfig config GPIO_TPS65912 · line 1346
Quoted 12 lines
drivers/acpi/pmic/Kconfig +0
-0help This config adds ACPI operation region support for TI TPS68470 PMIC. TPS68470 device is an advanced power management unit that powersdrivers/gpio/Kconfig +0
-1@@ -1343,7 +1343,6 @@ config GPIO_TPS65912 config GPIO_TPS68470 bool "TPS68470 GPIO" - depends on MFD_TPS68470
Same here.
This won't deal with the case where th TPS68470 is instantiated through DT, but that's not supported yet, so it can be dealt with it later when the need arises.
Quoted 147 lines
drivers/gpio/Kconfig +0
-0help Select this option to enable GPIO driver for the TPS68470 chip family.drivers/mfd/Kconfig +0
-18@@ -1520,24 +1520,6 @@ config MFD_TPS65217 This driver can also be built as a module. If so, the module will be called tps65217. -config MFD_TPS68470 - bool "TI TPS68470 Power Management / LED chips" - depends on ACPI && PCI && I2C=y - depends on I2C_DESIGNWARE_PLATFORM=y - select MFD_CORE - select REGMAP_I2C - help - If you say yes here you get support for the TPS68470 series of - Power Management / LED chips. - - These include voltage regulators, LEDs and other features - that are often used in portable devices. - - This option is a bool as it provides an ACPI operation - region, which must be available before any of the devices - using this are probed. This option also configures the - designware-i2c driver to be built-in, for the same reason. - config MFD_TI_LP873X tristate "TI LP873X Power Management IC" depends on I2Cdrivers/mfd/Makefile +0
-1@@ -105,7 +105,6 @@ obj-$(CONFIG_MFD_TPS65910) += tps65910.o obj-$(CONFIG_MFD_TPS65912) += tps65912-core.o obj-$(CONFIG_MFD_TPS65912_I2C) += tps65912-i2c.o obj-$(CONFIG_MFD_TPS65912_SPI) += tps65912-spi.o -obj-$(CONFIG_MFD_TPS68470) += tps68470.o obj-$(CONFIG_MFD_TPS80031) += tps80031.o obj-$(CONFIG_MENELAUS) += menelaus.odrivers/mfd/tps68470.c deleted +0
-97@@ -1,97 +0,0 @@ -// SPDX-License-Identifier: GPL-2.0 -/* -* TPS68470 chip Parent driver -* -* Copyright (C) 2017 Intel Corporation -* -* Authors: -* Rajmohan Mani <[email protected]> -* Tianshu Qiu <[email protected]> -* Jian Xu Zheng <[email protected]> -* Yuning Pu <[email protected]> -*/ - -#include <linux/acpi.h> -#include <linux/delay.h> -#include <linux/i2c.h> -#include <linux/init.h> -#include <linux/mfd/core.h> -#include <linux/mfd/tps68470.h> -#include <linux/regmap.h> - -static const struct mfd_cell tps68470s[] = { - { .name ="tps68470-gpio" }, - { .name ="tps68470_pmic_opregion" }, -}; - -static const struct regmap_config tps68470_regmap_config = { - .reg_bits =8 , - .val_bits =8 , - .max_register =TPS68470_REG_MAX , -}; - -static int tps68470_chip_init (struct device *dev,struct regmap *regmap) -{ -unsigned int version; -int ret; - -/* Force software reset */ - ret =regmap_write (regmap,TPS68470_REG_RESET ,TPS68470_REG_RESET_MASK ); -if (ret) -return ret; - - ret =regmap_read (regmap,TPS68470_REG_REVID , &version); -if (ret) { -dev_err (dev,"Failed to read revision register: %d\n" , ret); -return ret; - } - -dev_info (dev,"TPS68470 REVID: 0x%x\n" , version); - -return 0 ; -} - -static int tps68470_probe (struct i2c_client *client) -{ -struct device *dev = &client->dev; -struct regmap *regmap; -int ret; - - regmap =devm_regmap_init_i2c (client, &tps68470_regmap_config); -if (IS_ERR (regmap)) { -dev_err (dev,"devm_regmap_init_i2c Error %ld\n" , -PTR_ERR (regmap)); -return PTR_ERR (regmap); - } - -i2c_set_clientdata (client, regmap); - - ret =tps68470_chip_init (dev, regmap); -if (ret <0 ) { -dev_err (dev,"TPS68470 Init Error %d\n" , ret); -return ret; - } - - ret =devm_mfd_add_devices (dev,PLATFORM_DEVID_NONE , tps68470s, -ARRAY_SIZE (tps68470s),NULL ,0 ,NULL ); -if (ret <0 ) { -dev_err (dev,"devm_mfd_add_devices failed: %d\n" , ret); -return ret; - } - -return 0 ; -} - -static const struct acpi_device_id tps68470_acpi_ids[] = { - {"INT3472" }, - {}, -}; - -static struct i2c_driver tps68470_driver = { - .driver = { - .name ="tps68470" , - .acpi_match_table = tps68470_acpi_ids, - }, - .probe_new = tps68470_probe, -}; -builtin_i2c_driver (tps68470_driver);
Signature · 3 lines
Regards, Laurent Pinchart
Re: [PATCH v2 7/7] mfd: Remove tps68470 MFD driver
In reply to Daniel ScallyQuoted 3 lines · Daniel Scally
This driver only covered one scenario in which ACPI devices with
_HIDINT3472 are found, and its functionality has been taken over by the intel-skl-int3472 module, so remove it.
Prefix: "mfd: tps68470: ". Rationale: easier to look for specific commits, by, for example, running git log --grep tps68470.
Signature · 2 lines
With Best Regards, Andy Shevchenko
Re: [PATCH v2 7/7] mfd: Remove tps68470 MFD driver
Quoted 7 lines · Andy Shevchenko
Quoted 3 lines · Daniel Scally
This driver only covered one scenario in which ACPI devices with
_HIDINT3472 are found, and its functionality has been taken over by the intel-skl-int3472 module, so remove it.Prefix: "mfd: tps68470: ". Rationale: easier to look for specific commits, by, for example, running
git log --grep tps68470.
It's also reasonable to grep by path instead
$ git log --pretty=oneline --grep 'tps68470' cf2e8c544cd3b33e9e403b7b72404c221bf888d1 Merge tag 'mfd-next-5.1' of git://git.kernel.org/pub/scm/linux/kernel/git/lee/mfd 66265e719b4603ef9a1b8a6c876bcb542c021496 mfd: tps68470: Drop unused MODULE_DEVICE_TABLE 883cad5ba8cc2d9b740b4ad0a8a91063c99c75a3 Merge tag 'mfd-next-4.18' of git://git.kernel.org/pub/scm/linux/kernel/git/lee/mfd ca34b4f0bed802e1c8612ef08456b20992aeb02a gpio: tps68470: Update to SPDX license identifier
vs
$ git log --pretty=oneline -- '*tps68470*' e42615ec233b30dfaf117b108d4cb49455b4df1d gpio: Use new GPIO_LINE_DIRECTION 66265e719b4603ef9a1b8a6c876bcb542c021496 mfd: tps68470: Drop unused MODULE_DEVICE_TABLE 36b835176fe014197639f335d9d35424b7805027 ACPI / PMIC: Sort headers alphabetically 37c089d1facaf03969f66a5469c169a2c73429f6 mfd: Update to SPDX license identifier 1b2951dd99af3970c1c1a8385a12b90236b837de Merge tag 'gpio-v4.17-1' of git://git.kernel.org/pub/scm/linux/kernel/git/linusw/linux-gpio ca34b4f0bed802e1c8612ef08456b20992aeb02a gpio: tps68470: Update to SPDX license identifier 66444f460e68d641a63f0787627bac6c1ee340b5 ACPI / PMIC: Replace license boilerplate with SPDX license identifier e13452ac379070f038c264618e35559434252175 ACPI / PMIC: Add TI PMIC TPS68470 operation region driver 968c61f7da3cf6d58a49587cfe00d899ca72c1ad Merge tag 'mfd-next-4.14' of git://git.kernel.org/pub/scm/linux/kernel/git/lee/mfd 9bbf6a15ce19dd947b7fa6ad4095931ab3682da8 mfd: Add support for TPS68470 device 275b13a65547e2dc39c75d660d2e0f0fddde90f6 gpio: Add support for TPS68470 GPIOs