diff options
| author | Christian Lamparter <chunkeey@gmail.com> | 2020-03-21 21:40:15 +0100 |
|---|---|---|
| committer | Christian Lamparter <chunkeey@gmail.com> | 2020-03-22 23:02:09 +0100 |
| commit | 3509d4ec56b488d82c8fc95df8d12691b2b6cd1d (patch) | |
| tree | 2f1cb7c27bfdfe03a73f70ce25f1a3bf4d7f5fc8 /target/toolchain | |
| parent | 01fe7a2b64091786b6518025641f17c725a7769b (diff) | |
| download | upstream-3509d4ec56b488d82c8fc95df8d12691b2b6cd1d.tar.gz upstream-3509d4ec56b488d82c8fc95df8d12691b2b6cd1d.tar.bz2 upstream-3509d4ec56b488d82c8fc95df8d12691b2b6cd1d.zip | |
apm821xx: wndr4700: add preliminary drivetemp sensor
This patch prepares the WNDR4700 to use the HDD sensor for
the thermal zone. While the kernel's thermal.txt device-tree
binding documentation files talks about supporting multiple
sensors for a zone. This sadly is NOT the case. Even the most
current upstream kernels (5.6-rc) supports just >one< sensor
per zone: (driver/base/of-thermal.c:886)
| * REVIST: for now, the thermal framework supports only
| * one sensor per thermal zone. Thus, we are considering
| * only the first two values as slope and offset.
I do hope that this warning will prevent others wasteing time
on trying to figure out why their multi-sensor thermal-zones
definitions are not working as specified.
Signed-off-by: Christian Lamparter <chunkeey@gmail.com>
Diffstat (limited to 'target/toolchain')
0 files changed, 0 insertions, 0 deletions