summaryrefslogtreecommitdiff
path: root/hwdb.d
diff options
context:
space:
mode:
authorPhilipp Jungkamp <p.jungkamp@gmx.net>2022-12-21 12:43:49 +0100
committerYu Watanabe <watanabe.yu+github@gmail.com>2022-12-22 05:31:04 +0900
commit71a639db68b0890b1f25f4b18ddf5c4b33e1f23f (patch)
treec30ec3e061647298437ed39abedcb75b440e777f /hwdb.d
parent09ed55c26d15401a893b52d4845414edab16f740 (diff)
downloadsystemd-71a639db68b0890b1f25f4b18ddf5c4b33e1f23f.tar.gz
hwdb: change definition of PROXIMITY_NEAR_LEVEL for sensors
The [kernel documentation][0] for the in_proximity_nearlevel sysfs attribute on iio proximity devices states: If the value read from the sensor is above or equal to the value in this file an object should typically be considered near. Meaning a 'greater than or equal to' comparison. Make the documentation comment in 60-sensors.hwdb suggest a greater-or-equal rather than a strict greater-than comparison. [0]: https://www.kernel.org/doc/Documentation/ABI/testing/sysfs-bus-iio-proximity Fixes #25793
Diffstat (limited to 'hwdb.d')
-rw-r--r--hwdb.d/60-sensor.hwdb4
1 files changed, 2 insertions, 2 deletions
diff --git a/hwdb.d/60-sensor.hwdb b/hwdb.d/60-sensor.hwdb
index 39abf4db19..6c26b73060 100644
--- a/hwdb.d/60-sensor.hwdb
+++ b/hwdb.d/60-sensor.hwdb
@@ -45,8 +45,8 @@
# subsystem[1]. The default, when unset, is equivalent to:
# ACCEL_MOUNT_MATRIX=1, 0, 0; 0, 1, 0; 0, 0, 1
# eg. the identity matrix,
-# and <value> is an integer value above which an object is considered
-# close by a proximity sensor:
+# and <value> is an integer value above or equal to which an object is
+# considered close by a proximity sensor:
# PROXIMITY_NEAR_LEVEL=100
#
# [1]: https://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/commit/?id=dfc57732ad38f93ae6232a3b4e64fd077383a0f1