kernel.git/drivers/acpi/dptf, branch linux-6.16.y

ACPI: DPTF: Support Panther Lake

2024-12-10T19:01:38Z

Add Panther Lake ACPI IDs for DPTF. Signed-off-by: Zhang Rui Link: https://patch.msgid.link/20241203075802.584741-4-rui.zhang@intel.com [ rjw: Changelog edit ] Signed-off-by: Rafael J. Wysocki

ACPI: Switch back to struct platform_driver::remove()

2024-11-12T20:30:30Z

After commit 0edb555a65d1 ("platform: Make platform_driver::remove() return void") .remove() is (again) the right callback to implement for platform drivers. Convert all platform drivers below drivers/acpi to use .remove(), with the eventual goal to drop struct platform_driver::remove_new(). As .remove() and .remove_new() have the same prototypes, conversion is done by just changing the structure member name in the driver initializer. Signed-off-by: Uwe Kleine-König Link: https://patch.msgid.link/9ee1a9813f53698be62aab9d810b2d97a2a9f186.1731397722.git.u.kleine-koenig@baylibre.com [ rjw: Subject edit ] Signed-off-by: Rafael J. Wysocki

ACPI: DPTF: Add Lunar Lake support

2024-04-08T14:10:27Z

Add Lunar Lake ACPI IDs for DPTF devices. Signed-off-by: Sumeet Pawnikar Signed-off-by: Rafael J. Wysocki

ACPI: DPTF: Convert to platform remove callback returning void

2024-02-27T14:57:33Z

The .remove() callback for a platform driver returns an int which makes many driver authors wrongly assume it's possible to do error handling by returning an error code. However the value returned is ignored (apart from emitting a warning) and this typically results in resource leaks. To improve here there is a quest to make the remove callback return void. In the first step of this quest all drivers are converted to .remove_new(), which already returns void. Eventually after all drivers are converted, .remove_new() will be renamed to .remove(). Trivially convert these two drivers from always returning zero in the remove callback to the void returning variant. Signed-off-by: Uwe Kleine-König Signed-off-by: Rafael J. Wysocki

ACPI: DPTF: Drop stale link from Kconfig help

2022-09-28T15:26:25Z

The web site pointed to from the DPTF Kconfig help is not accessible any more, so drop the link to it from there. Signed-off-by: Rafael J. Wysocki

ACPI: DPTF: Support Meteor Lake

2022-05-25T13:37:07Z

Add Meteor Lake ACPI IDs for DPTF devices. Signed-off-by: Sumeet Pawnikar Reviewed-by: Srinivas Pandruvada Signed-off-by: Rafael J. Wysocki

ACPI: DPTF: Add support for high frequency impedance notification

2022-05-06T18:51:42Z

Add high frequency impedance notification support under DPTF. This returns high frequency impedance value that can be obtained from battery fuel gauge whenever there is change over a threshold. Also, corrected the typo from IMPEDANCED_CHNGED to IMPEDANCE_CHANGED. Signed-off-by: Sumeet Pawnikar Signed-off-by: Rafael J. Wysocki

ACPI: DPTF: Correct description of INT3407 / INT3532 attributes

2022-04-22T14:57:42Z

Remove duplicate comments of PBSS for Battery steady state power and correct the typo for PMAX Maximum platform power. Signed-off-by: Sumeet Pawnikar Signed-off-by: Rafael J. Wysocki

ACPI: DPTF: Support Raptor Lake

2022-01-17T18:45:38Z

Add Raptor Lake ACPI IDs for DPTF devices. Signed-off-by: Srinivas Pandruvada Signed-off-by: Rafael J. Wysocki

ACPI: DPTF: Update device ID in a comment

2021-11-24T16:40:22Z

There is a comment in dptf_pch_fivr.c which seemingly was added under the assumption that the PCH FIVR driver would be used on Tiger Lake platforms, but support for Alder Lake has been udded to it by commit 38748bcb940e ("ACPI: DPTF: Support Alder Lake"), so update the comment to cover a broader range of platforms by changing the device ID mentioned by it to INTC10xx. Signed-off-by: Sumeet Pawnikar [ rjw: Subject and changelog rewrite ] Signed-off-by: Rafael J. Wysocki