From: "jiale yao" <19888972804@163.com>
To: "Jonathan Cameron" <jic23@kernel.org>
Cc: "Andy Shevchenko" <andriy.shevchenko@intel.com>,
"David Lechner" <dlechner@baylibre.com>,
"Nuno Sá" <nuno.sa@analog.com>,
"Andy Shevchenko" <andy@kernel.org>,
"Uwe Kleine-König (The Capable Hub)"
<u.kleine-koenig@baylibre.com>,
"Takashi Sakamoto" <o-takashi@sakamocchi.jp>,
"Siratul Islam" <email@sirat.me>,
"Maxwell Doose" <maxwell@maxwelld.cc>,
linux-iio@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re:Re: [PATCH] iio: imu: kmx61: reject duplicate event disable
Date: Mon, 28 Sep 2026 16:30:02 +0800 (CST) [thread overview]
Message-ID: <1024d805.7930.1a0e722a587.Coremail.19888972804@163.com> (raw)
In-Reply-To: <20260927182031.6d490331@jic23-hlaptop>
At 2026-09-28 01:20:31, "Jonathan Cameron" <jic23@kernel.org> wrote:
>On Fri, 25 Sep 2026 17:18:44 +0300
>Andy Shevchenko <andriy.shevchenko@intel.com> wrote:
>
>> On Fri, Sep 25, 2026 at 10:10:05PM +0800, Jiale Yao wrote:
>> > The IIO core does not filter duplicate writes to the event enable
>> > attribute. kmx61_write_event_config() already ignores repeated enable
>> > requests, but a repeated disable request still calls
>> > kmx61_set_power_state(data, false, KMX61_ACC), 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.
>>
>> Same comments as per previous patches of the same topic.
>>
>Fixes tag needed.
Fixes: fd3ae7a9f21c ("iio: imu: kmx61: Add support for any motion trigger")
next prev parent reply other threads:[~2026-09-28 8:30 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-25 14:10 Jiale Yao
2026-09-25 14:18 ` Andy Shevchenko
2026-09-27 17:20 ` Jonathan Cameron
2026-09-28 8:30 ` jiale yao [this message]
2026-10-11 11:31 ` 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=1024d805.7930.1a0e722a587.Coremail.19888972804@163.com \
--to=19888972804@163.com \
--cc=andriy.shevchenko@intel.com \
--cc=andy@kernel.org \
--cc=dlechner@baylibre.com \
--cc=email@sirat.me \
--cc=jic23@kernel.org \
--cc=linux-iio@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=maxwell@maxwelld.cc \
--cc=nuno.sa@analog.com \
--cc=o-takashi@sakamocchi.jp \
--cc=u.kleine-koenig@baylibre.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®