From: Andy Shevchenko <andriy.shevchenko@intel.com>
To: Miao Li <limiao870622@163.com>
Cc: jic23@kernel.org, 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 12:03:02 +0300 [thread overview]
Message-ID: <afHJRjol87hCHOvw@ashevche-desk.local> (raw)
In-Reply-To: <20260429071402.209438-1-limiao870622@163.com>
On Wed, Apr 29, 2026 at 03:14:02PM +0800, Miao Li wrote:
> On the Inspur HS326 laptop(which integrated with HiSilicon M900
'...laptop (which...'
> 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.
...
> + if (state == false)
> + data->ps_int_enabled = false;
> + else
> + data->ps_int_enabled = true;
data->ps_int_enabled = state;
--
With Best Regards,
Andy Shevchenko
next prev parent reply other threads:[~2026-04-29 9:03 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 [this message]
2026-04-29 9:19 ` 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=afHJRjol87hCHOvw@ashevche-desk.local \
--to=andriy.shevchenko@intel.com \
--cc=andy@kernel.org \
--cc=dixitparmar19@gmail.com \
--cc=dlechner@baylibre.com \
--cc=jic23@kernel.org \
--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