From: Siratul Islam <email@sirat.me>
To: linux-iio@vger.kernel.org, devicetree@vger.kernel.org
Cc: jic23@kernel.org, dlechner@baylibre.com, nuno.sa@analog.com,
andy@kernel.org, robh@kernel.org, krzk+dt@kernel.org,
conor+dt@kernel.org, linux-kernel@vger.kernel.org,
Siratul Islam <email@sirat.me>
Subject: [PATCH v2 0/2] iio: proximity: add driver for ST VL53L1X ToF sensor
Date: Sun, 8 Mar 2026 17:37:26 +0600 [thread overview]
Message-ID: <20260308113728.40860-1-email@sirat.me> (raw)
This series adds support for the STMicroelectronics VL53L1X
Time-of-Flight ranging sensor.
The VL53L1X is a ToF laser-ranging sensor with I2C interface,
capable of measuring distances up to 4 meters. The driver
supports both interrupt-driven and polled operation.
Tested on Raspberry Pi 5 with a VL53L1X breakout board.
---
Changes in v2:
- Skip software reset in chip_init when xshut GPIO is available, since the device was already hardware-reset during power-on.
- Rename "reset" GPIO to "xshut" to match the datasheet pin name and updated DT binding accordingly.
- Make vdd-supply required in DT binding.
- Use reg_sequence arrays and regmap_multi_reg_write() for distance mode configuration.
- Switch to a hardirq handler with iio_trigger_poll() and IRQF_NO_THREAD instead of a threaded handler.
- Drop IRQF_TRIGGER_FALLING fallback. Leave trigger type to firmware/DT.
- Use iio_validate_own_trigger() instead of a custom validate_trigger, drop trig pointer from driver data.
- Switch usleep_range() to fsleep() throughout and add comments for sleep values.
- Don't fail probe on unknown model ID, just log with dev_info().
- Split stop_ranging cleanup into its own devm action, separate from power_off.
- Add missing includes: device.h, bitfield.h, completion.h, mod_devicetable.h.
- Use FIELD_GET() for range status checks.
- Move configure_irq() closer to probe(), use dev_err_probe() for its error paths.
- Fix buffer ops symmetry: postdisable -> predisable.
- Drop reg_format_endian from regmap config.
- Various alignment and formatting fixes.
Link to v1: https://lore.kernel.org/linux-iio/20260303090253.42076-1-email@sirat.me
Siratul Islam (2):
dt-bindings: iio: proximity: add ST VL53L1X ToF sensor
iio: proximity: add driver for ST VL53L1X ToF sensor
.../bindings/iio/proximity/st,vl53l1x.yaml | 50 +
MAINTAINERS | 7 +
drivers/iio/proximity/Kconfig | 14 +
drivers/iio/proximity/Makefile | 1 +
drivers/iio/proximity/vl53l1x-i2c.c | 871 ++++++++++++++++++
5 files changed, 943 insertions(+)
create mode 100644 Documentation/devicetree/bindings/iio/proximity/st,vl53l1x.yaml
create mode 100644 drivers/iio/proximity/vl53l1x-i2c.c
--
2.53.0
next reply other threads:[~2026-03-08 11:39 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-03-08 11:37 Siratul Islam [this message]
2026-03-08 11:37 ` [PATCH v2 1/2] dt-bindings: iio: proximity: add ST VL53L1X ToF sensor Siratul Islam
2026-03-09 7:31 ` Krzysztof Kozlowski
2026-03-08 11:37 ` [PATCH v2 2/2] iio: proximity: add driver for " Siratul Islam
2026-03-08 21:08 ` Andy Shevchenko
2026-03-09 10:27 ` Sirat
2026-03-09 11:29 ` Andy Shevchenko
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20260308113728.40860-1-email@sirat.me \
--to=email@sirat.me \
--cc=andy@kernel.org \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=dlechner@baylibre.com \
--cc=jic23@kernel.org \
--cc=krzk+dt@kernel.org \
--cc=linux-iio@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=nuno.sa@analog.com \
--cc=robh@kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox