Hi Jonathan,
I've been extending iio-sensor-proxy to handle iio based proximity
sensors:
https://gitlab.freedesktop.org/hadess/iio-sensor-proxy/merge_requests/298
The API to applications shall not export the raw value but rather tell
if an object is near by:
https://gitlab.freedesktop.org/hadess/iio-sensor-proxy/merge_requests/298/diffs#67dff3849420abc19453e1998b8904bbaee6f13c_67_79
So in the simplest case we'd have to set a level above which an object
is considered close:
My intitial intent was to expose that via DT but looking around in iio
drivers i couldn't see any driver doing that (i missed
iio_read_mount_matrix) and noticed that the mount matrix is given via
systemd/udev's hwdb:
https://github.com/systemd/systemd/pull/14845
Since matching on hwdb is done via modalias we wouldn't be able to have
different values on different boards without DMI/smbios:
https://github.com/systemd/systemd/pull/14845/files#diff-37fdc5406b715a9996bdcd3d8e439e16R539
The matching rule is explained here:
https://github.com/systemd/systemd/blob/master/hwdb.d/60-sensor.hwdb#L12
So would specifying this via DT and then exporting via sysfs be an
acceptable solution? That is inventing something like
iio_read_close_level. The value would not be used by the driver itself
but only exposed to userspace.
Cheers,
-- Guido
