mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: "jiale yao" <19888972804@163.com>
To: "Andy Shevchenko" <andriy.shevchenko@intel.com>
Cc: "Jonathan Cameron" <jic23@kernel.org>,
	"David Lechner" <dlechner@baylibre.com>,
	"Nuno Sá" <nuno.sa@analog.com>,
	"Andy Shevchenko" <andy@kernel.org>,
	"Stepan Ionichev" <sozdayvek@gmail.com>,
	linux-iio@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re:Re: [PATCH] iio: gyro: bmg160: reject duplicate event disable
Date: Fri, 25 Sep 2026 22:33:48 +0800 (CST)	[thread overview]
Message-ID: <6b2f4eef.1cf6.1a0d8fc9ac6.Coremail.19888972804@163.com> (raw)
In-Reply-To: <araCndRmAqnX1K9k@ashevche-desk.local>

At 2026-09-25 22:18:05, "Andy Shevchenko" <andriy.shevchenko@intel.com> wrote:
>On Fri, Sep 25, 2026 at 10:09:54PM +0800, Jiale Yao wrote:
>> The IIO core does not filter duplicate writes to the event enable
>> attribute.
>
>Can it be done there once for all?

I don't think the core can safely do this generically, since it doesn't own
the per-event state and read_event_config() may reflect shared hardware state.

The runtime PM accounting is driver-specific, so handling duplicate writes in
the driver seems safer. gp2ap002 does the same in commit 579c049b4cb6,
refer https://lore.kernel.org/all/20260720193911.74919-2-nikhilgtr@gmail.com/

>
>> bmg160_write_event_config() already ignores repeated enable
>> requests, but a repeated disable request still calls
>> bmg160_set_power_state(data, false), dropping a runtime PM reference
>> that was not acquired for this request. This can underflow the runtime
>> PM usage count and trigger a "Runtime PM usage count underflow" warning.
>> 
>> Return early when the requested state already matches ev_enable_state.
>
>-- 
>With Best Regards,
>Andy Shevchenko
>

      reply	other threads:[~2026-09-25 14:34 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-09-25 14:09 Jiale Yao
2026-09-25 14:18 ` Andy Shevchenko
2026-09-25 14:33   ` jiale yao [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=6b2f4eef.1cf6.1a0d8fc9ac6.Coremail.19888972804@163.com \
    --to=19888972804@163.com \
    --cc=andriy.shevchenko@intel.com \
    --cc=andy@kernel.org \
    --cc=dlechner@baylibre.com \
    --cc=jic23@kernel.org \
    --cc=linux-iio@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=nuno.sa@analog.com \
    --cc=sozdayvek@gmail.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®