From: Jonathan Cameron <jic23@kernel.org>
To: Nikhil Gautam <nikhilgtr@gmail.com>
Cc: linux-iio@vger.kernel.org, linux-kernel@vger.kernel.org,
dlechner@baylibre.com, nuno.sa@analog.com, andy@kernel.org,
Joshua Crofts <joshua.crofts1@gmail.com>
Subject: Re: [PATCH v2] iio: ccs811: Deassert WAKE GPIO on error paths
Date: Sat, 17 Oct 2026 21:46:59 +0100 [thread overview]
Message-ID: <20261017214659.5bbebc38@jic23-hlaptop> (raw)
In-Reply-To: <20261015123023.3417-1-nikhilgtr@gmail.com>
On Thu, 15 Oct 2026 18:00:23 +0530
Nikhil Gautam <nikhilgtr@gmail.com> wrote:
> Ensure the WAKE GPIO is deasserted when status polling fails or
> the data-ready timeout expires. Early returns could leave WAKE asserted,
> preventing the sensor from returning to its low-power state and
> potentially disrupting subsequent I2C transactions.
I need more on this point to know whether we care if an error
means we don't deassert the wake pin.
Why would failing to go to sleep break future transactions?
I'd kind of assume we'd awaken an already awake device (which sounds
idempotent but maybe not?) and carry on from there?
Jonathan
>
> Route error paths through a common cleanup label to ensure WAKE is
> deasserted before returning.
>
> Fixes: c6644f7201f3 ("iio: chemical: Add support for external Reset and Wakeup in CCS811")
> Signed-off-by: Nikhil Gautam <nikhilgtr@gmail.com>
> Reviewed-by: Joshua Crofts <joshua.crofts1@gmail.com>
> ---
> drivers/iio/chemical/ccs811.c | 9 ++++++---
> 1 file changed, 6 insertions(+), 3 deletions(-)
>
> diff --git a/drivers/iio/chemical/ccs811.c b/drivers/iio/chemical/ccs811.c
> index 998c9239c4c7..dad54f66ebb3 100644
> --- a/drivers/iio/chemical/ccs811.c
> +++ b/drivers/iio/chemical/ccs811.c
> @@ -198,18 +198,21 @@ static int ccs811_get_measurement(struct ccs811_data *data)
> while (tries-- > 0) {
> ret = i2c_smbus_read_byte_data(data->client, CCS811_STATUS);
> if (ret < 0)
> - return ret;
> + goto out;
>
> if ((ret & CCS811_STATUS_DATA_READY) || tries == 0)
> break;
> msleep(100);
> }
> - if (!(ret & CCS811_STATUS_DATA_READY))
> - return -EIO;
> + if (!(ret & CCS811_STATUS_DATA_READY)) {
> + ret = -EIO;
> + goto out;
> + }
>
> ret = i2c_smbus_read_i2c_block_data(data->client,
> CCS811_ALG_RESULT_DATA, 8,
> (char *)&data->buffer);
> +out:
> ccs811_set_wakeup(data, false);
>
> return ret;
next prev parent reply other threads:[~2026-10-17 20:47 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-10-15 12:30 Nikhil Gautam
2026-10-15 12:50 ` Joshua Crofts
2026-10-17 20:46 ` Jonathan Cameron [this message]
2026-10-17 21:12 ` Nikhil Gautam
2026-10-17 23:37 ` 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=20261017214659.5bbebc38@jic23-hlaptop \
--to=jic23@kernel.org \
--cc=andy@kernel.org \
--cc=dlechner@baylibre.com \
--cc=joshua.crofts1@gmail.com \
--cc=linux-iio@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=nikhilgtr@gmail.com \
--cc=nuno.sa@analog.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
all inboxes | Powered by JetHome®