From: Jonathan Cameron <jic23@kernel.org>
To: Gustavo Silva <gustavograzs@gmail.com>
Cc: robh@kernel.org, krzk+dt@kernel.org, conor+dt@kernel.org,
lars@metafoo.de, christophe.jaillet@wanadoo.fr,
devicetree@vger.kernel.org, linux-iio@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH v3 3/6] iio: chemical: add driver for ENS160 sensor
Date: Sun, 9 Jun 2024 10:30:33 +0100 [thread overview]
Message-ID: <20240609103033.2f746f1e@jic23-huawei> (raw)
In-Reply-To: <20240604225747.7212-4-gustavograzs@gmail.com>
On Tue, 4 Jun 2024 19:57:27 -0300
Gustavo Silva <gustavograzs@gmail.com> wrote:
> ScioSense ENS160 is a digital metal oxide multi-gas sensor, designed
> for indoor air quality monitoring. The driver supports readings of
> CO2 and VOC, and can be accessed via both SPI and I2C.
>
> Datasheet: https://www.sciosense.com/wp-content/uploads/2023/12/ENS160-Datasheet.pdf
>
No blank lines in tags block. Datahsheet is a semi official tag.
I'll tidy up in this and previous patch if everything else fine.
> Signed-off-by: Gustavo Silva <gustavograzs@gmail.com>
> ---
> drivers/iio/chemical/Kconfig | 22 +++
> drivers/iio/chemical/Makefile | 3 +
> drivers/iio/chemical/ens160.h | 7 +
> drivers/iio/chemical/ens160_core.c | 221 +++++++++++++++++++++++++++++
> drivers/iio/chemical/ens160_i2c.c | 60 ++++++++
> drivers/iio/chemical/ens160_spi.c | 60 ++++++++
> 6 files changed, 373 insertions(+)
> create mode 100644 drivers/iio/chemical/ens160.h
> create mode 100644 drivers/iio/chemical/ens160_core.c
> create mode 100644 drivers/iio/chemical/ens160_i2c.c
> create mode 100644 drivers/iio/chemical/ens160_spi.c
>
> diff --git a/drivers/iio/chemical/Kconfig b/drivers/iio/chemical/Kconfig
> index 02649ab81..e407afab8 100644
> --- a/drivers/iio/chemical/Kconfig
> +++ b/drivers/iio/chemical/Kconfig
> @@ -76,6 +76,28 @@ config CCS811
> Say Y here to build I2C interface support for the AMS
> CCS811 VOC (Volatile Organic Compounds) sensor
>
> +config ENS160
> + tristate "ScioSense ENS160 sensor driver"
> + depends on (I2C || SPI)
> + select REGMAP
> + select ENS160_I2C if I2C
> + select ENS160_SPI if SPI
> + help
> + Say yes here to build support for ScioSense ENS160 multi-gas sensor.
> +
> + This driver can also be built as a module. If so, the module for I2C
> + would be called ens160_i2c and ens160_spi for SPI support.
> +
> +config ENS160_I2C
> + tristate
> + depends on I2C && ENS160
> + select REGMAP_I2C
> +
> +config ENS160_SPI
> + tristate
> + depends on SPI && ENS160
> + select REGMAP_SPI
As these two config symbols aren't exposed I think you don't need the
depends lines.
See the BMA400 entry in drivers/iio/accel/Kconfig for example.
If everything else looks good I'll drop those two lines whilst
applying.
Jonathan
next prev parent reply other threads:[~2024-06-09 9:31 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-06-04 22:57 [PATCH v3 0/6] Add driver for ENS160 sensor Gustavo Silva
2024-06-04 22:57 ` [PATCH v3 1/6] dt-bindings: vendor-prefixes: add ScioSense Gustavo Silva
2024-06-04 22:57 ` [PATCH v3 2/6] dt-bindings: iio: chemical: add ENS160 sensor Gustavo Silva
2024-06-04 22:57 ` [PATCH v3 3/6] iio: chemical: add driver for " Gustavo Silva
2024-06-09 9:30 ` Jonathan Cameron [this message]
2024-06-04 22:57 ` [PATCH v3 4/6] iio: chemical: ens160: add triggered buffer support Gustavo Silva
2024-06-04 22:57 ` [PATCH v3 5/6] iio: chemical: ens160: add power management support Gustavo Silva
2024-06-04 22:57 ` [PATCH v3 6/6] MAINTAINERS: Add ScioSense ENS160 Gustavo Silva
2024-06-09 9:36 ` [PATCH v3 0/6] Add driver for ENS160 sensor Jonathan Cameron
2024-06-09 18:05 ` Gustavo Silva
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=20240609103033.2f746f1e@jic23-huawei \
--to=jic23@kernel.org \
--cc=christophe.jaillet@wanadoo.fr \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=gustavograzs@gmail.com \
--cc=krzk+dt@kernel.org \
--cc=lars@metafoo.de \
--cc=linux-iio@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--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