Skip to content

thermal: Eliminate thermal_zone_device_register()

Rafael J. Wysocki linux-pm lkml 1 version In review

Get series with b4
b4 am 1870450.tdWV9SEqCh@kreacher

Versions newest first

  1. v1 Latest4 patches 4 repliesIn review

Patches in v1 No applies recorded yet

#Subject and filesSizeRepliesApplied
1/4thermal: core: Clean up headers of thermal zone registration functionsinclude/linux/thermal.h+37 -160 replies
2/4thermal: core: Add function for registering tripless thermal zonesdrivers/thermal/thermal_core.c include/linux/thermal.h+24 -00 replies
3/4thermal: Use thermal_tripless_zone_device_register()drivers/power/supply/power_supply_core.c drivers/thermal/armada_thermal.c drivers/thermal/dove_thermal.c +3 more+14 -134 replies
4/4thermal: core: Drop thermal_zone_device_register()drivers/thermal/thermal_core.c include/linux/thermal.h+0 -280 replies

Reviews trailers per patch

1 of 4 patches has a Reviewed-by or Acked-by.

PatchMiquel RaynalSebastian Reichel
1/4
2/4
3/4A-b A-b
4/4

Trailers given in replies are filled; those carried in the patches from earlier versions are outlined with dashes.

Read the v1 thread

Cover letter [PATCH v1 0/4] thermal: Eliminate thermal_zone_device_register()

Hi Everyone,

After recently merged changes in the ACPI thermal and Intel DTS IOSF thermal drivers, the only callers of thermal_zone_device_register() are the ones using it for registering thermal zones without any trip points. They all pass zeros as 4 (out of 8) function arguments, so retaining the full thermal_zone_device_register() just for this purpose seems a bit excessive.

For this reason, the series adds a thermal_zone_device_register() replacement tailored to this specific use case and called thermal_tripless_zone_device_register() [2/4] and makes all of the existing callers of the former use the replacement [3/4]. This allows thermal_zone_device_register() to be dropped [4/4].

The first patch is just a clean up making function headers in thermal.h a bit more consistent.

This series it not intended to make any functional impact, but if the changes are fine with everyone, I would like to introduce them during the ongoing merge window to prevent the obsolete interface from lingering.

The series applies to the linux-next branch in linux-pm.git.

Thanks!