Linux IIO development
 help / color / mirror / Atom feed
From: Jonathan Cameron <jic23@kernel.org>
To: Jacopo Mondi <jacopo@jmondi.org>
Cc: Lars-Peter Clausen <lars@metafoo.de>,
	Andy Shevchenko <andriy.shevchenko@linux.intel.com>,
	Matt Ranostay <matt.ranostay@konsulko.com>,
	Magnus Damm <magnus.damm@gmail.com>,
	linux-iio@vger.kernel.org, Peter Rosin <peda@axentia.se>,
	Wolfram Sang <wsa@kernel.org>
Subject: Re: [PATCH v5 3/4] iio: chemical: Add Senseair Sunrise 006-0-007 driver
Date: Sat, 11 Sep 2021 16:29:59 +0100	[thread overview]
Message-ID: <20210911162959.1018316c@jic23-huawei> (raw)
In-Reply-To: <20210909094537.218064-4-jacopo@jmondi.org>

On Thu,  9 Sep 2021 11:45:36 +0200
Jacopo Mondi <jacopo@jmondi.org> wrote:

> Add support for the Senseair Sunrise 006-0-0007 driver through the
> IIO subsystem.
> 
> Datasheet: https://rmtplusstoragesenseair.blob.core.windows.net/docs/Dev/publicerat/TDE5531.pdf
> Signed-off-by: Jacopo Mondi <jacopo@jmondi.org>
Given you will be doing a v6 anyway, I noticed one small place inline where you can reduce
the scope of the lock and hence simplify error paths a bit (it occurs a few times in similar functions).

Regmap stuff looks acceptable to me, though if a better way comes from Peter's comments even
better!

Thanks,

Jonathan

> +
> +/* Custom regmap read/write operations: perform unlocked access to the i2c bus. */
> +
> +static int sunrise_regmap_read(void *context, const void *reg_buf,
> +			       size_t reg_size, void *val_buf, size_t val_size)
> +{
> +	struct i2c_client *client = context;
> +	union i2c_smbus_data data;
> +	int ret;
> +
> +	memset(&data, 0, sizeof(data));
> +	data.block[0] = val_size;
> +
> +	/*
> +	 * Wake up sensor by sending sensor address: START, sensor address,
> +	 * STOP. Sensor will not ACK this byte.
> +	 *
> +	 * The chip enters a low power state after 15msec without
> +	 * communications or after a complete read/write sequence.
> +	 */
> +	__i2c_smbus_xfer(client->adapter, client->addr, I2C_M_IGNORE_NAK,
> +			 I2C_SMBUS_WRITE, 0, I2C_SMBUS_QUICK, NULL);
> +
> +	ret = __i2c_smbus_xfer(client->adapter, client->addr, client->flags,
> +			       I2C_SMBUS_READ, ((u8 *)reg_buf)[0],
> +			       I2C_SMBUS_I2C_BLOCK_DATA, &data);
> +	if (ret < 0)
> +		return ret;
> +
> +	memcpy(val_buf, &data.block[1], data.block[0]);
> +
> +	return 0;
> +}
> +
> +static int sunrise_regmap_write(void *context, const void *val_buf, size_t count)
> +{
> +	struct i2c_client *client = context;
> +	union i2c_smbus_data data;
> +
> +	/* Discard reg address from values count. */
> +	if (count < 1)
> +		return -EINVAL;
> +	count--;
> +
> +	memset(&data, 0, sizeof(data));
> +	data.block[0] = count;
> +	memcpy(&data.block[1], (u8 *)val_buf + 1, count);
> +
> +	__i2c_smbus_xfer(client->adapter, client->addr, I2C_M_IGNORE_NAK,
> +			 I2C_SMBUS_WRITE, 0, I2C_SMBUS_QUICK, NULL);
> +
> +	return __i2c_smbus_xfer(client->adapter, client->addr, client->flags,
> +				I2C_SMBUS_WRITE, ((u8 *)val_buf)[0],
> +				I2C_SMBUS_I2C_BLOCK_DATA, &data);
> +}

This didn't end up looking too bad :)


...

> +
> +static ssize_t sunrise_cal_background_write(struct iio_dev *iiodev,
> +					    uintptr_t private,
> +					    const struct iio_chan_spec *chan,
> +					    const char *buf, size_t len)
> +{
> +	struct sunrise_dev *sunrise = iio_priv(iiodev);
> +	bool enable;
> +	int ret;
> +
> +	mutex_lock(&sunrise->lock);
> +	ret = kstrtobool(buf, &enable);
> +	if (ret)
> +		goto out_unlock;
> +
> +	if (!enable)
> +		goto out_unlock;

Trivial: Move these outside the lock (as only use local variables) and
then return directly from them.  That gets rid of the need for the label as well.

Same for other cases that look like this...

> +
> +	ret = sunrise_calibrate(sunrise, &calib_data[SUNRISE_CALIBRATION_BACKGROUND]);
> +
> +out_unlock:
> +	mutex_unlock(&sunrise->lock);
> +	if (ret)
> +		return ret;
> +
> +	return len;
> +}
> +

Thanks,

Jonathan

  parent reply	other threads:[~2021-09-11 15:26 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-09-09  9:45 [PATCH v5 0/4] iio: chemical: Add Senseair Sunrise CO2 sensor Jacopo Mondi
2021-09-09  9:45 ` [PATCH v5 1/4] dt-bindings: iio: chemical: Document senseair,sunrise " Jacopo Mondi
2021-09-09  9:45 ` [PATCH v5 2/4] iio: ABI: docs: Document Senseair Sunrise ABI Jacopo Mondi
2021-09-09  9:45 ` [PATCH v5 3/4] iio: chemical: Add Senseair Sunrise 006-0-007 driver Jacopo Mondi
2021-09-09 12:04   ` Peter Rosin
2021-09-20 13:02     ` Jacopo Mondi
2021-09-09 13:01   ` Andy Shevchenko
2021-09-09 13:03     ` Andy Shevchenko
2021-09-11 15:12     ` Jonathan Cameron
2021-09-11 15:29   ` Jonathan Cameron [this message]
2021-09-09  9:45 ` [PATCH v5 4/4] iio: ABI: Document in_concentration_co2_scale Jacopo Mondi
2021-09-09 13:05   ` Andy Shevchenko
2021-09-10 10:47     ` Jonathan Cameron
2021-09-11 15:04       ` 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=20210911162959.1018316c@jic23-huawei \
    --to=jic23@kernel.org \
    --cc=andriy.shevchenko@linux.intel.com \
    --cc=jacopo@jmondi.org \
    --cc=lars@metafoo.de \
    --cc=linux-iio@vger.kernel.org \
    --cc=magnus.damm@gmail.com \
    --cc=matt.ranostay@konsulko.com \
    --cc=peda@axentia.se \
    --cc=wsa@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