Linux IIO development
 help / color / mirror / Atom feed
From: Jonathan Cameron <jic23@kernel.org>
To: Denis Benato <benato.denis96@gmail.com>
Cc: Lars-Peter Clausen <lars@metafoo.de>,
	Jagath Jog J <jagathjog1996@gmail.com>,
	linux-iio@vger.kernel.org, linux-kernel@vger.kernel.org,
	"Luke D . Jones" <luke@ljones.dev>,
	Jonathan LoBue <jlobue10@gmail.com>
Subject: Re: [PATCH v3 0/2] iio: fix bug with triggers not resuming after sleep
Date: Sat, 10 Aug 2024 11:20:03 +0100	[thread overview]
Message-ID: <20240810112003.3e0b77a5@jic23-huawei> (raw)
In-Reply-To: <20240807185619.7261-1-benato.denis96@gmail.com>

On Wed,  7 Aug 2024 20:56:17 +0200
Denis Benato <benato.denis96@gmail.com> wrote:

> When a device enters an idle state (for example ASUS RC71L with s2idle)
> and an iio driver has a trigger attached such as iio-trig-hrtimer,
> after resuming the device the trigger is not triggering data acquisition.
> 
> This patch series solves the problem reliably and is well tested after
> many cycles and many reboots.
> 
> Closes: https://lore.kernel.org/all/31d7f7aa-e834-4fd0-a66a-e0ff528425dc@gmail.com/
> 
> Changelog:
> - V2: patch 2:
>         + Simplify code
>         + Remove unneeded code protections around SET_RUNTIME_PM_OPS()
>         + pm_ptr() to let the compiler drop bmi323_core_pm_ops if !CONFIG_PM
> 
> - V3: patch 1:
> 	+ Add pf->irq=0 that was accidentally left out
Dropped v2 and picked up v3.

Thanks,

Jonathan

> 
> Previous patches obsoleted:
> https://lore.kernel.org/all/20240727123034.5541-1-benato.denis96@gmail.com/
> https://lore.kernel.org/all/20240725002641.191509-3-benato.denis96@gmail.com/
> 
> Denis Benato (2):
>   iio: trigger: allow devices to suspend/resume theirs associated
>     trigger
>   iio: bmi323: suspend and resume triggering on relevant pm operations
> 
>  drivers/iio/imu/bmi323/bmi323.h      |  1 +
>  drivers/iio/imu/bmi323/bmi323_core.c | 23 +++++++++++++++++++++++
>  drivers/iio/imu/bmi323/bmi323_i2c.c  |  1 +
>  drivers/iio/imu/bmi323/bmi323_spi.c  |  1 +
>  drivers/iio/industrialio-trigger.c   | 27 +++++++++++++++++++++++++++
>  include/linux/iio/iio.h              | 17 +++++++++++++++++
>  6 files changed, 70 insertions(+)
> 


      parent reply	other threads:[~2024-08-10 10:20 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-08-07 18:56 [PATCH v3 0/2] iio: fix bug with triggers not resuming after sleep Denis Benato
2024-08-07 18:56 ` [PATCH v3 1/2] iio: trigger: allow devices to suspend/resume theirs associated trigger Denis Benato
2024-08-07 18:56 ` [PATCH v3 2/2] iio: bmi323: suspend and resume triggering on relevant pm operations Denis Benato
2024-08-10 10:20 ` 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=20240810112003.3e0b77a5@jic23-huawei \
    --to=jic23@kernel.org \
    --cc=benato.denis96@gmail.com \
    --cc=jagathjog1996@gmail.com \
    --cc=jlobue10@gmail.com \
    --cc=lars@metafoo.de \
    --cc=linux-iio@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=luke@ljones.dev \
    /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