From: Jonathan Cameron <jic23@kernel.org>
To: Wadim Mueller <wafgo01@gmail.com>
Cc: krzk+dt@kernel.org, robh@kernel.org, conor+dt@kernel.org,
dlechner@baylibre.com, nuno.sa@analog.com, andy@kernel.org,
maxwell@maxwelld.cc, linux-iio@vger.kernel.org,
devicetree@vger.kernel.org, linux-kernel@vger.kernel.org,
marcelo.schmitt1@gmail.com, 455.rodrigo.alencar@gmail.com
Subject: Re: [PATCH v6 2/4] dt-bindings: iio: flow: add Sensirion SLF3S liquid flow sensor
Date: Sun, 2 Aug 2026 00:46:15 +0100 [thread overview]
Message-ID: <20260802004615.2193f11b@jic23-huawei> (raw)
In-Reply-To: <20260728214943.29820-3-wafgo01@gmail.com>
On Tue, 28 Jul 2026 23:49:41 +0200
Wadim Mueller <wafgo01@gmail.com> wrote:
> Document the bindings for the Sensirion SLF3S family of digital
> liquid-flow sensors on I2C. The family currently covers the
> SLF3S-0600F, SLF3S-1300F and SLF3S-4000B variants.
FWIW there is a false positive from Sashiko on this where it says
there is no interrupt pin. I'll guess that it found a datasheet
talking about one packaging option perhaps?
The first one I checked has the interrupt pin.
Jonathan
>
> All variants share the same register map and differ only in the flow
> scale factor and the calibrated measurement range, which the driver
> reads back from the product-information register. Since that lookup
> is needed in any case, a fallback compatible would buy nothing, so
> each variant gets its own compatible without a fallback. A future
> drop-in compatible part can then claim one of these compatibles and
> work on kernels that do not know its product ID yet.
>
> The active calibration medium (water / IPA) is runtime-switchable
> via the in_volumeflow_medium sysfs attribute and therefore not a
> DT property.
>
> Signed-off-by: Wadim Mueller <wafgo01@gmail.com>
> ---
> .../bindings/iio/flow/sensirion,slf3s.yaml | 55 +++++++++++++++++++
> MAINTAINERS | 7 +++
> 2 files changed, 62 insertions(+)
> create mode 100644 Documentation/devicetree/bindings/iio/flow/sensirion,slf3s.yaml
>
> diff --git a/Documentation/devicetree/bindings/iio/flow/sensirion,slf3s.yaml b/Documentation/devicetree/bindings/iio/flow/sensirion,slf3s.yaml
> new file mode 100644
> index 000000000000..79718f4f98bd
> --- /dev/null
> +++ b/Documentation/devicetree/bindings/iio/flow/sensirion,slf3s.yaml
> @@ -0,0 +1,55 @@
> +# SPDX-License-Identifier: (GPL-2.0-only OR BSD-2-Clause)
> +%YAML 1.2
> +---
> +$id: http://devicetree.org/schemas/iio/flow/sensirion,slf3s.yaml#
> +$schema: http://devicetree.org/meta-schemas/core.yaml#
> +
> +title: Sensirion SLF3S liquid flow sensor
> +
> +maintainers:
> + - Wadim Mueller <wafgo01@gmail.com>
> +
> +description:
> + Family of digital liquid-flow sensors from Sensirion with I2C interface. All
> + family members share the same register map; sub-types differ only in the flow
> + scale factor and the calibrated measurement range. The sub-type can be
> + identified from the product-information register.
> +
> +properties:
> + compatible:
> + enum:
> + - sensirion,slf3s-0600f
> + - sensirion,slf3s-1300f
> + - sensirion,slf3s-4000b
> +
> + reg:
> + maxItems: 1
> +
> + vdd-supply: true
> +
> + interrupts:
> + maxItems: 1
> +
> +required:
> + - compatible
> + - reg
> + - vdd-supply
> +
> +additionalProperties: false
> +
> +examples:
> + - |
> + #include <dt-bindings/interrupt-controller/irq.h>
> +
> + i2c {
> + #address-cells = <1>;
> + #size-cells = <0>;
> +
> + flow-sensor@8 {
> + compatible = "sensirion,slf3s-0600f";
> + reg = <0x08>;
> + vdd-supply = <®_3v3>;
> + interrupt-parent = <&gpio0>;
> + interrupts = <0 IRQ_TYPE_EDGE_RISING>;
> + };
> + };
> diff --git a/MAINTAINERS b/MAINTAINERS
> index ce020ded5fd3..497492825f70 100644
> --- a/MAINTAINERS
> +++ b/MAINTAINERS
> @@ -24583,6 +24583,13 @@ S: Maintained
> F: Documentation/ABI/testing/sysfs-bus-iio-chemical-sgp40
> F: drivers/iio/chemical/sgp40.c
>
> +SENSIRION SLF3S LIQUID FLOW SENSOR DRIVER
> +M: Wadim Mueller <wafgo01@gmail.com>
> +R: Maxwell Doose <maxwell@maxwelld.cc>
> +L: linux-iio@vger.kernel.org
> +S: Maintained
> +F: Documentation/devicetree/bindings/iio/flow/sensirion,slf3s.yaml
> +
> SENSIRION SPS30 AIR POLLUTION SENSOR DRIVER
> M: Tomasz Duszynski <tduszyns@gmail.com>
> S: Maintained
next prev parent reply other threads:[~2026-08-01 23:46 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-07-28 21:49 [PATCH v6 0/4] iio: flow: Sensirion SLF3S liquid flow sensor Wadim Mueller
2026-07-28 21:49 ` [PATCH v6 1/4] iio: types: add IIO_VOLUMEFLOW channel type Wadim Mueller
2026-07-28 21:49 ` [PATCH v6 2/4] dt-bindings: iio: flow: add Sensirion SLF3S liquid flow sensor Wadim Mueller
2026-07-28 21:55 ` sashiko-bot
2026-08-01 23:46 ` Jonathan Cameron [this message]
2026-07-28 21:49 ` [PATCH v6 3/4] iio: core: add IIO_VAL_DECIMAL64_FEMTO format type Wadim Mueller
2026-07-28 21:49 ` [PATCH v6 4/4] iio: flow: add Sensirion SLF3S liquid flow sensor driver Wadim Mueller
2026-07-29 12:21 ` Uwe Kleine-König
2026-08-02 0:04 ` Jonathan Cameron
2026-08-01 23:50 ` [PATCH v6 0/4] iio: flow: Sensirion SLF3S liquid flow sensor Jonathan Cameron
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=20260802004615.2193f11b@jic23-huawei \
--to=jic23@kernel.org \
--cc=455.rodrigo.alencar@gmail.com \
--cc=andy@kernel.org \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=dlechner@baylibre.com \
--cc=krzk+dt@kernel.org \
--cc=linux-iio@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=marcelo.schmitt1@gmail.com \
--cc=maxwell@maxwelld.cc \
--cc=nuno.sa@analog.com \
--cc=robh@kernel.org \
--cc=wafgo01@gmail.com \
/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