Linux IIO development
 help / color / mirror / Atom feed
From: Jonathan Cameron <jic23@kernel.org>
To: Tetsuo Handa <penguin-kernel@I-love.SAKURA.ne.jp>
Cc: Lars-Peter Clausen <lars@metafoo.de>, linux-iio@vger.kernel.org
Subject: Re: [PATCH] iio:light:tsl2563: Replace cancel_delayed_work() with cancel_delayed_work_sync().
Date: Sat, 18 Jun 2022 14:57:50 +0100	[thread overview]
Message-ID: <20220618145750.3016e018@jic23-huawei> (raw)
In-Reply-To: <041b6745-f784-ff3f-9836-3f4397d35d94@I-love.SAKURA.ne.jp>

On Mon, 13 Jun 2022 00:04:00 +0900
Tetsuo Handa <penguin-kernel@I-love.SAKURA.ne.jp> wrote:

> Since cancel_delayed_work(&chip->poweroff_work) does not guarantee that
> tsl2563_poweroff_work() is not running, tsl2563_set_power(chip, 0) can be
> called from tsl2563_poweroff_work() after tsl2563_get_power(chip) and
> tsl2563_set_power(chip, 1) are called. Use _sync version in order to make
> sure that tsl2563_poweroff_work() is no longer running.
> 
> Signed-off-by: Tetsuo Handa <penguin-kernel@I-love.SAKURA.ne.jp>
Makes sense to me.

Applied to the togreg branch of iio.git.

Technically this may be a fix (at very least it removes some undesirable
behaviour) but I'm not proposing that we should backport it to stable.

Thanks,

Jonathan

> ---
>  drivers/iio/light/tsl2563.c | 4 ++--
>  1 file changed, 2 insertions(+), 2 deletions(-)
> 
> diff --git a/drivers/iio/light/tsl2563.c b/drivers/iio/light/tsl2563.c
> index 4d89ac3a5bbc..bbb577459fb9 100644
> --- a/drivers/iio/light/tsl2563.c
> +++ b/drivers/iio/light/tsl2563.c
> @@ -310,7 +310,7 @@ static int tsl2563_get_adc(struct tsl2563_chip *chip)
>  		goto out;
>  
>  	if (!chip->int_enabled) {
> -		cancel_delayed_work(&chip->poweroff_work);
> +		cancel_delayed_work_sync(&chip->poweroff_work);
>  
>  		if (!tsl2563_get_power(chip)) {
>  			ret = tsl2563_set_power(chip, 1);
> @@ -638,7 +638,7 @@ static int tsl2563_write_interrupt_config(struct iio_dev *indio_dev,
>  		chip->intr &= ~0x30;
>  		chip->intr |= 0x10;
>  		/* ensure the chip is actually on */
> -		cancel_delayed_work(&chip->poweroff_work);
> +		cancel_delayed_work_sync(&chip->poweroff_work);
>  		if (!tsl2563_get_power(chip)) {
>  			ret = tsl2563_set_power(chip, 1);
>  			if (ret)


      reply	other threads:[~2022-06-18 13:49 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-06-12 15:04 [PATCH] iio:light:tsl2563: Replace cancel_delayed_work() with cancel_delayed_work_sync() Tetsuo Handa
2022-06-18 13:57 ` Jonathan Cameron [this message]

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=20220618145750.3016e018@jic23-huawei \
    --to=jic23@kernel.org \
    --cc=lars@metafoo.de \
    --cc=linux-iio@vger.kernel.org \
    --cc=penguin-kernel@I-love.SAKURA.ne.jp \
    /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