]> git.ipfire.org Git - thirdparty/linux.git/commit
thermal: Get rid of CONFIG_THERMAL_WRITABLE_TRIPS
authorRafael J. Wysocki <rafael.j.wysocki@intel.com>
Mon, 12 Feb 2024 18:26:25 +0000 (19:26 +0100)
committerRafael J. Wysocki <rafael.j.wysocki@intel.com>
Fri, 23 Feb 2024 17:24:48 +0000 (18:24 +0100)
commita85739c8c6894c3b9ff860e79e91db44cb59bd63
treed87ef7b6e20cf15e60d0f89ac9eb5b07bdf01df6
parent62dd17846d33e75e623965e281e246dff0e01309
thermal: Get rid of CONFIG_THERMAL_WRITABLE_TRIPS

The only difference made by CONFIG_THERMAL_WRITABLE_TRIPS is whether or
not the writable trips mask passed during thermal zone registration
will take any effect, but whoever passes a non-zero writable trips mask
to thermal_zone_device_register_with_trips() can be forgiven thinking
that it will always work.

Moreover, some thermal drivers expect user space to set trip temperature
values, so they select CONFIG_THERMAL_WRITABLE_TRIPS, possibly overriding
a manual choice to unset it and going against the design purportedly
allowing system integrators to decide on the writability of trip points
for the given kernel build.  It is also set in one platform's defconfig.

Forthermore, CONFIG_THERMAL_WRITABLE_TRIPS only affects trip temperature,
because trip hysteresis is writable as long as the thermal zone provides
a callback to update it, regardless of the CONFIG_THERMAL_WRITABLE_TRIPS
value.

The above means that the symbol in question is used inconsistently and
its purpose is at least moot, so remove it and always take the writable
trip mask passed to thermal_zone_device_register_with_trips() into
account.

Signed-off-by: Rafael J. Wysocki <rafael.j.wysocki@intel.com>
Reviewed-by: Daniel Lezcano <daniel.lezcano@linaro.org>
arch/arm/configs/imx_v6_v7_defconfig
drivers/thermal/Kconfig
drivers/thermal/intel/Kconfig
drivers/thermal/thermal_sysfs.c