From: Gustavo Arantes <dev.gustavoa@gmail.com>
To: gregkh@linuxfoundation.org, marvin24@gmx.de
Cc: linux-staging@lists.linux.dev, ac100@lists.launchpad.net,
linux-tegra@vger.kernel.org, linux-kernel@vger.kernel.org,
dev.gustavoa@gmail.com
Subject: [PATCH 0/2] staging: nvec_power: quiesce EC queries for system suspend
Date: Thu, 12 Mar 2026 18:11:49 -0300 [thread overview]
Message-ID: <20260312211151.85379-1-dev.gustavoa@gmail.com> (raw)
nvec_power still issues EC queries asynchronously and keeps work queued
across system sleep. This series first serializes the driver's EC
requests, then adds PM hooks so the remaining work items are quiesced
while the parent NVEC controller is suspended.
Patch 1 exports a small core parser helper, moves the battery metadata
queries into a worker, and switches nvec_power over to synchronous EC
requests.
Patch 2 tracks the suspend state per instance, prevents new work from
being queued during suspend, and restarts the polling and metadata work
on resume.
Gustavo Arantes (2):
staging: nvec_power: make EC queries synchronous
staging: nvec_power: stop EC queries during system suspend
drivers/staging/nvec/nvec.c | 7 +-
drivers/staging/nvec/nvec.h | 2 +
drivers/staging/nvec/nvec_power.c | 122 +++++++++++++++++++++++++-----
3 files changed, 111 insertions(+), 20 deletions(-)
base-commit: ad6bb64332bb4297110950769ad5af52791e33a2
--
2.53.0
next reply other threads:[~2026-03-12 21:11 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-03-12 21:11 Gustavo Arantes [this message]
2026-03-12 21:11 ` [PATCH 1/2] staging: nvec_power: make EC queries synchronous Gustavo Arantes
2026-03-12 21:11 ` [PATCH 2/2] staging: nvec_power: stop EC queries during system suspend Gustavo Arantes
2026-03-15 20:48 ` [PATCH 0/2] staging: nvec_power: quiesce EC queries for " Marc Dietrich
2026-03-15 21:48 ` Gustavo Arantes
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=20260312211151.85379-1-dev.gustavoa@gmail.com \
--to=dev.gustavoa@gmail.com \
--cc=ac100@lists.launchpad.net \
--cc=gregkh@linuxfoundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-staging@lists.linux.dev \
--cc=linux-tegra@vger.kernel.org \
--cc=marvin24@gmx.de \
/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