linux-toradex.git/include/linux/thermal.h, branch v5.10-rc2

thermal: cooling: Remove unused variable *tz

2020-10-12T10:08:36+00:00

1. devfreq_cooling.c: The variable *tz is not used in
devfreq_cooling_get_requested_power(), devfreq_cooling_state2power()
and devfreq_cooling_power2state().

2. cpufreq_cooling.c: After 84fe2cab48590, the variable *tz is not used
anymore in cpufreq_get_requested_power(), cpufreq_state2power() and
cpufreq_power2state().

Remove the variable *tz.

Signed-off-by: zhuguangqing 
Signed-off-by: Daniel Lezcano 
Link: https://lore.kernel.org/r/20200914071101.13575-1-zhuguangqing83@gmail.com

thermal: core: Add new event for sending keep alive notifications

2020-10-12T10:08:35+00:00

This event is sent by the platform firmware to confirm that
user space thermal solution is alive. The response to this event
from the user space thermal solution is platform specific.

Signed-off-by: Srinivas Pandruvada 
Signed-off-by: Daniel Lezcano 
Link: https://lore.kernel.org/r/20200915223650.406046-3-srinivas.pandruvada@linux.intel.com

thermal: core: genetlink support for events/cmd/sampling

2020-07-07T13:55:21+00:00

Initially the thermal framework had a very simple notification
mechanism to send generic netlink messages to the userspace.

The notification function was never called from anywhere and the
corresponding dead code was removed. It was probably a first attempt
to introduce the netlink notification.

At LPC2018, the presentation "Linux thermal: User kernel interface",
proposed to create the notifications to the userspace via a kfifo.

The advantage of the kfifo is the performance. It is usually used from
a 1:1 communication channel where a driver captures data and sends it
as fast as possible to a userspace process.

The drawback is that only one process uses the notification channel
exclusively, thus no other process is allowed to use the channel to
get temperature or notifications.

This patch defines a generic netlink API to discover the current
thermal setup and adds event notifications as well as temperature
sampling. As any genetlink protocol, it can evolve and the versioning
allows to keep the backward compatibility.

In order to prevent the user from getting flooded with data on a
single channel, there are two multicast channels, one for the
temperature sampling when the thermal zone is updated and another one
for the events, so the user can get the events only without the
thermal zone temperature sampling.

Also, a list of commands to discover the thermal setup is added and
can be extended when needed.

Reviewed-by: Amit Kucheria 
Signed-off-by: Daniel Lezcano 
Acked-by: Zhang Rui 
Link: https://lore.kernel.org/r/20200706105538.2159-3-daniel.lezcano@linaro.org

thermal: Make thermal_zone_device_is_enabled() available to core only

2020-07-06T23:26:07+00:00

This function is not needed by drivers.

Signed-off-by: Andrzej Pietrasiewicz 
Signed-off-by: Daniel Lezcano 
Link: https://lore.kernel.org/r/20200703104354.19657-4-andrzej.p@collabora.com

thermal: Rename set_mode() to change_mode()

2020-06-29T18:26:39+00:00

set_mode() is only called when tzd's mode is about to change. Actual
setting is performed in thermal_core, in thermal_zone_device_set_mode().
The meaning of set_mode() callback is actually to notify the driver about
the mode being changed and giving the driver a chance to oppose such
change.

To better reflect the purpose of the method rename it to change_mode()

Signed-off-by: Andrzej Pietrasiewicz 
[for acerhdf]
Acked-by: Peter Kaestle 
Reviewed-by: Bartlomiej Zolnierkiewicz 
Reviewed-by: Amit Kucheria 
Signed-off-by: Daniel Lezcano 
Link: https://lore.kernel.org/r/20200629122925.21729-12-andrzej.p@collabora.com

thermal: Add mode helpers

2020-06-29T18:26:36+00:00

Prepare for making the drivers not access tzd's private members.

Signed-off-by: Andrzej Pietrasiewicz 
Reviewed-by: Bartlomiej Zolnierkiewicz 
[staticize thermal_zone_device_set_mode()]
Signed-off-by: kernel test robot 
Signed-off-by: Daniel Lezcano 
Link: https://lore.kernel.org/r/20200629122925.21729-7-andrzej.p@collabora.com

thermal: remove get_mode() operation of drivers

2020-06-29T18:26:35+00:00

get_mode() is now redundant, as the state is stored in struct
thermal_zone_device.

Consequently the "mode" attribute in sysfs can always be visible, because
it is always possible to get the mode from struct tzd.

Signed-off-by: Andrzej Pietrasiewicz 
[for acerhdf]
Acked-by: Peter Kaestle 
Reviewed-by: Bartlomiej Zolnierkiewicz 
Reviewed-by: Amit Kucheria 
Signed-off-by: Daniel Lezcano 
Link: https://lore.kernel.org/r/20200629122925.21729-6-andrzej.p@collabora.com

thermal: Add current mode to thermal zone device

2020-06-29T18:26:34+00:00

Prepare for changing the place where the mode is stored: now it is in
drivers, which might or might not implement get_mode()/set_mode() methods.
A lot of cleanup can be done thanks to storing it in struct tzd. The
get_mode() methods will become redundant.

Signed-off-by: Andrzej Pietrasiewicz 
Reviewed-by: Guenter Roeck 
Reviewed-by: Bartlomiej Zolnierkiewicz 
Reviewed-by: Amit Kucheria 
Signed-off-by: Daniel Lezcano 
Link: https://lore.kernel.org/r/20200629122925.21729-4-andrzej.p@collabora.com

thermal: Remove thermal_zone_device_update() stub

2020-04-14T09:41:12+00:00

All users of the function depends on THERMAL, no stub is
needed. Remove it.

Signed-off-by: Daniel Lezcano 
Reviewed-by: Amit Kucheria 
Acked-by: Zhang Rui 
Link: https://lore.kernel.org/r/20200402142747.8307-9-daniel.lezcano@linaro.org

thermal: Remove stubs for thermal_zone_[un]bind_cooling_device

2020-04-14T09:41:12+00:00

All callers of the functions depends on THERMAL, it is pointless to
define stubs. Remove them.

Signed-off-by: Daniel Lezcano 
Reviewed-by: Amit Kucheria 
Acked-by: Zhang Rui 
Link: https://lore.kernel.org/r/20200402142747.8307-8-daniel.lezcano@linaro.org