diff options
| author | Karl Mehltretter <kmehltretter@gmail.com> | 2026-09-12 08:22:52 +0200 |
|---|---|---|
| committer | Daniel Lezcano <daniel.lezcano@kernel.org> | 2026-10-14 09:45:41 +0200 |
| commit | 82bb005cd9cf5a9df4cfe4a52db90346ac5fd17a (patch) | |
| tree | a46c1d2f4411c44f7fd4ce8b6a8c756d03f08454 /include/uapi | |
| parent | 379ae6766d1a7a1f78f1d97b6c72a262f14960e8 (diff) | |
| download | linux-next-82bb005cd9cf5a9df4cfe4a52db90346ac5fd17a.tar.gz linux-next-82bb005cd9cf5a9df4cfe4a52db90346ac5fd17a.zip | |
thermal: ti-soc-thermal: Fix the return value in ti_bandgap_get_sensor_data() kernel-doc
ti_bandgap_get_sensor_data() returns an ERR_PTR() if the bandgap
instance or sensor ID is invalid. Otherwise it returns the stored sensor
data, which can be NULL if no data has been set or the stored value has
been cleared.
This mismatch was already present in omap_bandgap_get_sensor_data() when
the driver was introduced in staging.
Document the validation errors while retaining NULL as a possible stored
value.
Fixes: 8feaf0ce1a04 ("staging: OMAP4+: thermal: introduce bandgap temperature sensor")
Assisted-by: LLM
Signed-off-by: Karl Mehltretter <kmehltretter@gmail.com>
Signed-off-by: Daniel Lezcano <daniel.lezcano@kernel.org>
Link: https://patch.msgid.link/20260912062252.42762-1-kmehltretter@gmail.com
Diffstat (limited to 'include/uapi')
0 files changed, 0 insertions, 0 deletions