From: Breno Leitao <leitao@debian.org>
To: Sudeep Holla <sudeep.holla@kernel.org>
Cc: "lihuisong (C)" <lihuisong@huawei.com>,
"Rafael J. Wysocki" <rafael@kernel.org>,
Len Brown <lenb@kernel.org>,
lpieralisi@kernel.org, catalin.marinas@arm.com, will@kernel.org,
"Rafael J. Wysocki" <rafael.j.wysocki@intel.com>,
linux-acpi@vger.kernel.org, linux-kernel@vger.kernel.org,
pjaroszynski@nvidia.com, guohanjun@huawei.com,
linux-arm-kernel@lists.infradead.org, rmikey@meta.com,
kernel-team@meta.com
Subject: Re: [PATCH RFC] ACPI: processor: idle: Do not propagate acpi_processor_ffh_lpi_probe() -ENODEV
Date: Tue, 14 Apr 2026 06:14:19 -0700 [thread overview]
Message-ID: <ad48gItCwrC-ar34@gmail.com> (raw)
In-Reply-To: <20260414-cute-shapeless-dolphin-c5b2fc@sudeepholla>
Hello Sudeep,
On Tue, Apr 14, 2026 at 01:25:53PM +0100, Sudeep Holla wrote:
> So while I understand that the kernel did not report an error previously, that
> does not mean the _LPI table is merely moot on this platform when it contains
> only a WFI state.
Can you clarify whether datacenter ARM systems are expected to expose
deeper idle states beyond WFI in their _LPI tables?
Backing up, I'm observing 72 pr_err() messages during boot on these
hosts and trying to determine whether this indicates a firmware issue or
if the kernel needs adjustment.
next prev parent reply other threads:[~2026-04-14 13:14 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-04-13 16:54 [PATCH RFC] ACPI: processor: idle: Do not propagate acpi_processor_ffh_lpi_probe() -ENODEV Breno Leitao
2026-04-14 9:43 ` lihuisong (C)
2026-04-14 10:21 ` Breno Leitao
2026-04-14 11:31 ` lihuisong (C)
2026-04-14 12:05 ` Breno Leitao
2026-04-14 12:25 ` Sudeep Holla
2026-04-14 13:14 ` Breno Leitao [this message]
2026-04-14 14:10 ` Sudeep Holla
2026-04-14 16:31 ` Breno Leitao
2026-04-15 10:45 ` Sudeep Holla
2026-04-15 1:32 ` lihuisong (C)
2026-04-15 14:03 ` Rafael J. Wysocki
2026-04-20 6:38 ` lihuisong (C)
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=ad48gItCwrC-ar34@gmail.com \
--to=leitao@debian.org \
--cc=catalin.marinas@arm.com \
--cc=guohanjun@huawei.com \
--cc=kernel-team@meta.com \
--cc=lenb@kernel.org \
--cc=lihuisong@huawei.com \
--cc=linux-acpi@vger.kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=lpieralisi@kernel.org \
--cc=pjaroszynski@nvidia.com \
--cc=rafael.j.wysocki@intel.com \
--cc=rafael@kernel.org \
--cc=rmikey@meta.com \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.