devicetree.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Jonathan Cameron <jic23@kernel.org>
To: Roan van Dijk <roan@protonic.nl>
Cc: Rob Herring <robh+dt@kernel.org>,
	Tomasz Duszynski <tomasz.duszynski@octakon.com>,
	linux-iio@vger.kernel.org, devicetree@vger.kernel.org,
	linux-kernel@vger.kernel.org, david@protonic.nl,
	Lars-Peter Clausen <lars@metafoo.de>
Subject: Re: [PATCH v5 0/4] iio: chemical: Add support for Sensirion SCD4x CO2 sensor
Date: Sun, 10 Oct 2021 16:59:19 +0100	[thread overview]
Message-ID: <20211010165919.51f06938@jic23-huawei> (raw)
In-Reply-To: <20211008101706.755942-1-roan@protonic.nl>

On Fri,  8 Oct 2021 12:17:02 +0200
Roan van Dijk <roan@protonic.nl> wrote:

> This series adds support for the Sensirion SCD4x sensor.
> 
> The driver supports continuous reads of temperature, relative humdity and CO2
> concentration. There is an interval of 5 seconds between readings. During
> this interval the drivers checks if the sensor has new data available.
> 
> The driver is based on the scd30 driver. However, The scd4x has become too
> different to just expand the scd30 driver. I made a new driver instead of
> expanding the scd30 driver. I hope I made the right choice by doing so?

Applied to the togreg branch of iio.git with the issues Randy mentioned tidied
up. Pushed out as testing for 0-day to see if it can find anything we missed

Thanks,

Jonathan

> 
> Changes since v5:
> scd4x.c:
>   - Fix bug in trigger_handler
> 
> Changes since v4:
> scd4x.c:
>   - Minor fixes in documentation
>   - Reorder trigger_handler so memcpy is not needed anymore
> Documentation:
>   - Change information about the KernelVersion for the 
>     calibration_forced_value_available
> 
> Changes since v3:
> scd4x.c
>   - Change read and write_and_fetch function parameter. CRC byte is now
>     hidden inside the function.
>   - Fix minor style issues
>   - Add calibration_forced_value_available attribute to the driver
>   - Remove including BUFFER_TRIGGERED
>   - Change calibbias to raw ADC readings rather than converting it to
>     milli degrees C.
> Documentation:
>   - Change description of driver attributes
>   - Add calibration_forced_value_available documentation
> 
> Changes since v2:
> scd4x.c:
>   - Change boolean operations
>   - Document scope of lock
>   - Remove device *dev from struct
>   - Add goto block for errror handling
>   - Add function to read value per channel in read_raw
>   - Fix bug with lock in error paths
>   - Remove conversion of humidity and temperature values
>   - Add scale and offset to temperature channel
>   - Add scale to humidity channel
>   - Move memset out of locked section
>   - Remove unused irq functions
>   - Move device register at end of probe function
> Documentation:
>   - Copy content of sysfs-bus-iio-scd30 to sysfs-bus-iio
>   - Remove Documentation/ABI/testing/sysfs-bus-iio-scd30
> 
> Changes since v1:
> dt-bindings:
>   - Separated compatible string for each sensor type
> scd4x.c:
>   - Changed probe, resume and suspend functions to static
>   - Added SIMPLE_DEV_PM_OPS function call for power management
>     operations.
> 
> Roan van Dijk (4):
>   dt-bindings: iio: chemical: sensirion,scd4x: Add yaml description
>   MAINTAINERS: Add myself as maintainer of the scd4x driver
>   drivers: iio: chemical: Add support for Sensirion SCD4x CO2 sensor
>   iio: documentation: Document scd4x calibration use
> 
>  Documentation/ABI/testing/sysfs-bus-iio       |  41 ++
>  Documentation/ABI/testing/sysfs-bus-iio-scd30 |  34 -
>  .../iio/chemical/sensirion,scd4x.yaml         |  46 ++
>  MAINTAINERS                                   |   6 +
>  drivers/iio/chemical/Kconfig                  |  13 +
>  drivers/iio/chemical/Makefile                 |   1 +
>  drivers/iio/chemical/scd4x.c                  | 689 ++++++++++++++++++
>  7 files changed, 796 insertions(+), 34 deletions(-)
>  delete mode 100644 Documentation/ABI/testing/sysfs-bus-iio-scd30
>  create mode 100644 Documentation/devicetree/bindings/iio/chemical/sensirion,scd4x.yaml
>  create mode 100644 drivers/iio/chemical/scd4x.c
> 


  parent reply	other threads:[~2021-10-10 15:55 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-10-08 10:17 [PATCH v5 0/4] iio: chemical: Add support for Sensirion SCD4x CO2 sensor Roan van Dijk
2021-10-08 10:17 ` [PATCH v5 1/4] dt-bindings: iio: chemical: sensirion,scd4x: Add yaml description Roan van Dijk
2021-10-08 10:17 ` [PATCH v5 2/4] MAINTAINERS: Add myself as maintainer of the scd4x driver Roan van Dijk
2021-10-08 10:17 ` [PATCH v5 3/4] drivers: iio: chemical: Add support for Sensirion SCD4x CO2 sensor Roan van Dijk
2021-10-08 16:15   ` Randy Dunlap
2021-10-08 10:17 ` [PATCH v5 4/4] iio: documentation: Document scd4x calibration use Roan van Dijk
2021-10-10 15:59 ` Jonathan Cameron [this message]
2021-10-13 17:38   ` [PATCH v5 0/4] iio: chemical: Add support for Sensirion SCD4x CO2 sensor Jonathan Cameron
2021-10-14  8:24     ` Roan van Dijk
2021-10-14 17:19       ` Jonathan Cameron
2021-10-18  8:19         ` Roan van Dijk
2021-10-18 17:52           ` Jonathan Cameron
2021-10-19  7:30             ` Roan van Dijk
2021-10-20 16:52               ` 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=20211010165919.51f06938@jic23-huawei \
    --to=jic23@kernel.org \
    --cc=david@protonic.nl \
    --cc=devicetree@vger.kernel.org \
    --cc=lars@metafoo.de \
    --cc=linux-iio@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=roan@protonic.nl \
    --cc=robh+dt@kernel.org \
    --cc=tomasz.duszynski@octakon.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;
as well as URLs for NNTP newsgroup(s).