From: "lihuisong (C)" <lihuisong@huawei.com>
To: Peixin Xie <peixin.xie@linux.spacemit.com>,
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>
Cc: <linux-acpi@vger.kernel.org>, <linux-riscv@lists.infradead.org>,
<linux-kernel@vger.kernel.org>, <spacemit@lists.linux.dev>,
<stable@vger.kernel.org>, <lihuisong@huawei.com>
Subject: Re: [PATCH v2] riscv: acpi: Handle LPI architectural context loss flags
Date: Wed, 29 Jul 2026 09:34:38 +0800 [thread overview]
Message-ID: <f4bf4615-d54f-4c08-b736-42b36d4645e8@huawei.com> (raw)
In-Reply-To: <20260728-riscv-acpi-lpi-timer-v2-1-5a30e0021ec9@linux.spacemit.com>
On 7/28/2026 7:47 PM, 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>
> Signed-off-by: Peixin Xie <peixin.xie@linux.spacemit.com>
> ---
LGTM,
Reviewed-by: Huisong Li <lihuisong@huawei.com>
>
prev parent reply other threads:[~2026-07-29 1:34 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-07-28 11:47 Peixin Xie
2026-07-28 12:54 ` Sunil V L
2026-07-28 13:19 ` Sunil V L
2026-07-29 1:34 ` lihuisong (C) [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=f4bf4615-d54f-4c08-b736-42b36d4645e8@huawei.com \
--to=lihuisong@huawei.com \
--cc=alex@ghiti.fr \
--cc=aou@eecs.berkeley.edu \
--cc=dlan@kernel.org \
--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=pjw@kernel.org \
--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=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®