From: Paul Walmsley <pjw@kernel.org>
To: Peixin Xie <peixin.xie@linux.spacemit.com>
Cc: Paul Walmsley <pjw@kernel.org>,
Palmer Dabbelt <palmer@dabbelt.com>,
Albert Ou <aou@eecs.berkeley.edu>,
Alexandre Ghiti <alex@ghiti.fr>, Yixun Lan <dlan@kernel.org>,
Sudeep Holla <sudeep.holla@kernel.org>,
Oza Pawandeep <quic_poza@quicinc.com>,
Will Deacon <will@kernel.org>,
"Rafael J. Wysocki" <rafael.j.wysocki@intel.com>,
linux-acpi@vger.kernel.org, linux-riscv@lists.infradead.org,
linux-kernel@vger.kernel.org, spacemit@lists.linux.dev,
stable@vger.kernel.org, Sunil V L <sunilvl@oss.qualcomm.com>,
Huisong Li <lihuisong@huawei.com>
Subject: Re: [PATCH v3] riscv: acpi: Handle LPI architectural context loss flags
Date: Wed, 5 Aug 2026 20:44:46 -0600 (MDT) [thread overview]
Message-ID: <e9ccdf60-481a-39a3-f0fa-428f47d838b9@kernel.org> (raw)
In-Reply-To: <20260803-riscv-acpi-lpi-timer-v3-1-520fa13732f5@linux.spacemit.com>
On Mon, 3 Aug 2026, Peixin Xie wrote:
> Commit 4785aa802853 ("cpuidle, ACPI: Evaluate LPI arch_flags for
> broadcast timer") replaced the generic nonzero check for LPI
> architectural context loss flags with arch_get_idle_state_flags().
> RISC-V does not implement the helper, so it falls back to the stub
> that returns 0. Consequently, CPUIDLE_FLAG_TIMER_STOP is not set when
> an LPI state loses the hart timer context, preventing cpuidle from
> using a broadcast timer for that state.
>
> Implement the RISC-V helper and map the hart timer context loss flag
> to CPUIDLE_FLAG_TIMER_STOP.
>
> Fixes: 4785aa802853 ("cpuidle, ACPI: Evaluate LPI arch_flags for broadcast timer")
> Cc: stable@vger.kernel.org
> Acked-by: Sudeep Holla <sudeep.holla@kernel.org>
> Reviewed-by: Yixun Lan <dlan@kernel.org>
> Reviewed-by: Sunil V L <sunilvl@oss.qualcomm.com>
> Reviewed-by: Huisong Li <lihuisong@huawei.com>
> Signed-off-by: Peixin Xie <peixin.xie@linux.spacemit.com>
Thanks, queued for v7.3.
- Paul
prev parent reply other threads:[~2026-08-06 2:44 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-08-03 1:20 Peixin Xie
2026-08-06 2:44 ` Paul Walmsley [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=e9ccdf60-481a-39a3-f0fa-428f47d838b9@kernel.org \
--to=pjw@kernel.org \
--cc=alex@ghiti.fr \
--cc=aou@eecs.berkeley.edu \
--cc=dlan@kernel.org \
--cc=lihuisong@huawei.com \
--cc=linux-acpi@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-riscv@lists.infradead.org \
--cc=palmer@dabbelt.com \
--cc=peixin.xie@linux.spacemit.com \
--cc=quic_poza@quicinc.com \
--cc=rafael.j.wysocki@intel.com \
--cc=spacemit@lists.linux.dev \
--cc=stable@vger.kernel.org \
--cc=sudeep.holla@kernel.org \
--cc=sunilvl@oss.qualcomm.com \
--cc=will@kernel.org \
/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®