This is a different approach to [1] where I tried to add this proximity sensor logic to the input subsystem. Instead, we'll take the approach of making a small IIO proximity driver that parses the EC switch bitmap to find out if the front proximity sensor is detecting something or not. This allows us to treat proximity sensors as IIO devices all the time in userspace instead of handling this switch on the EC via the input subsystem and then other proximity sensors via IIO. [1] https://lore.kernel.org/r/20201205004709.3126266-1-swboyd@xxxxxxxxxxxx Cc: Dmitry Torokhov <dmitry.torokhov@xxxxxxxxx> Cc: Benson Leung <bleung@xxxxxxxxxxxx> Cc: Guenter Roeck <groeck@xxxxxxxxxxxx> Cc: Douglas Anderson <dianders@xxxxxxxxxxxx> Cc: Gwendal Grignou <gwendal@xxxxxxxxxxxx> Cc: <devicetree@xxxxxxxxxxxxxxx> Cc: Rob Herring <robh+dt@xxxxxxxxxx> Stephen Boyd (3): platform/chrome: cros_ec: Add SW_FRONT_PROXIMITY MKBP define dt-bindings: iio: Add cros ec proximity yaml doc iio: proximity: Add a ChromeOS EC MKBP proximity driver .../proximity/google,cros-ec-proximity.yaml | 37 +++ drivers/iio/proximity/Kconfig | 11 + drivers/iio/proximity/Makefile | 1 + drivers/iio/proximity/cros_ec_proximity.c | 252 ++++++++++++++++++ .../linux/platform_data/cros_ec_commands.h | 1 + 5 files changed, 302 insertions(+) create mode 100644 Documentation/devicetree/bindings/iio/proximity/google,cros-ec-proximity.yaml create mode 100644 drivers/iio/proximity/cros_ec_proximity.c base-commit: 19c329f6808995b142b3966301f217c831e7cf31 -- https://chromeos.dev
