If an object can be considered close to the device that has the proximity sensor built in is hardware dependent. Allowing to configure the property via device tree allows to export this device specific value to userspace via ext_info. This is useful for e.g. iio-sensor-proxy. This came up when adding proximity support to iio-sensor-proxy [1], [2], it is not meant as a vcnl4000 thing but rather as something useful for other proximity sensors too in the future. Changes from v1: - as per review comments by Jonathan Cameron https://lore.kernel.org/linux-iio/20200221120519.43b72007@archlinux/ Document new sysfs file in Documentation/ABI/testing/sysfs-bus-iio-proximity - convert bindings to yaml - bindings: fix typo in near-level property [1]: https://gitlab.freedesktop.org/hadess/iio-sensor-proxy/merge_requests/298 [2]: https://lore.kernel.org/linux-iio/20200210154153.GA26903@xxxxxxxxxxxxxxxxxxx/ Guido Günther (4): dt-bindings: iio: vcnl4000: convert bindings to YAML format dt-bindings: iio: light: vcnl4000: Add near-level iio: vcnl4000: Export near level property for proximity sensor Documentation: ABI: document IIO in_proximity_near_level file .../ABI/testing/sysfs-bus-iio-proximity | 10 ++++ .../bindings/iio/light/vcnl4000.txt | 24 --------- .../bindings/iio/light/vcnl4000.yaml | 53 +++++++++++++++++++ drivers/iio/light/vcnl4000.c | 26 +++++++++ 4 files changed, 89 insertions(+), 24 deletions(-) create mode 100644 Documentation/ABI/testing/sysfs-bus-iio-proximity delete mode 100644 Documentation/devicetree/bindings/iio/light/vcnl4000.txt create mode 100644 Documentation/devicetree/bindings/iio/light/vcnl4000.yaml -- 2.23.0
