From: Jonathan Cameron <jic23@kernel.org>
To: Miao Li <limiao870622@163.com>
Cc: andy@kernel.org, dixitparmar19@gmail.com, dlechner@baylibre.com,
nuno.sa@analog.com, waqar.hameed@axis.com,
linux-iio@vger.kernel.org, linux-kernel@vger.kernel.org,
Miao Li <limiao@kylinos.cn>
Subject: Re: [PATCH v3] iio: light: stk3310: Deal with the ps interrupt issue in PM
Date: Wed, 29 Apr 2026 10:19:25 +0100 [thread overview]
Message-ID: <20260429101925.158b2bd9@jic23-huawei> (raw)
In-Reply-To: <20260429071402.209438-1-limiao870622@163.com>
On Wed, 29 Apr 2026 15:14:02 +0800
Miao Li <limiao870622@163.com> wrote:
> From: Miao Li <limiao@kylinos.cn>
>
> On the Inspur HS326 laptop(which integrated with HiSilicon M900
> processor), if the STK3311-X chip's PS interrupt is configured
> in "Recommended interrupt mode", the interrupt cannot be triggered
> normally after waking from suspend or hibernation.
>
> In this case, neither disabling and re-enabling the interrupt nor
> resetting the PS threshold register can restore the interrupt to
> normal operation.
>
> If the interrupt is disabled in suspend() then reset the PS threshold
> register and enable the interrupt in resume(). This resolves the issue.
>
> Signed-off-by: Miao Li <limiao@kylinos.cn>
Hi.
Please do not send a new version in reply to an old one. A few reasons
that most kernel maintainers ask for new threads for each version.
1. Threads can get very complex if there are lots of versions.
2. Many reviewers who find themselves with a few minutes look at most recent
emails. In a threaded email client, a reply like this one ends up pages
back so attracts fewer reviews.
I don't have anything else to add to Andy's review. However please
slow down a bit on new versions to allow people to respond to earlier
ones. If there is a known problem you have noticed after sending it
out feel free to review your own patch on the list and point that problem out.
Jonathan
prev parent reply other threads:[~2026-04-29 9:19 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-04-27 9:43 [PATCH] iio: light: stk3310: Deal with the ps interrupt issue in PM Miao Li
2026-04-27 9:56 ` Andy Shevchenko
2026-04-27 10:13 ` Joshua Crofts
2026-04-28 18:22 ` Jonathan Cameron
2026-04-29 6:18 ` Miao Li
2026-04-29 6:45 ` Miao Li
2026-04-29 6:51 ` [PATCH v2] " Miao Li
2026-04-29 6:59 ` Andy Shevchenko
2026-04-29 7:50 ` Miao Li
2026-04-29 7:14 ` [PATCH v3] " Miao Li
2026-04-29 9:03 ` Andy Shevchenko
2026-04-29 9:19 ` 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=20260429101925.158b2bd9@jic23-huawei \
--to=jic23@kernel.org \
--cc=andy@kernel.org \
--cc=dixitparmar19@gmail.com \
--cc=dlechner@baylibre.com \
--cc=limiao870622@163.com \
--cc=limiao@kylinos.cn \
--cc=linux-iio@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=nuno.sa@analog.com \
--cc=waqar.hameed@axis.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