From: Will Deacon <will@kernel.org>
To: Prarit Bhargava <prarit@redhat.com>,
sudeep.holla@arm.com, lpieralisi@kernel.org,
guohanjun@huawei.com
Cc: Liu Wei <liuwei09@cestc.cn>,
catalin.marinas@arm.com, linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org, liuwei09.cestc.cn@cecloud.com,
rafael@kernel.org
Subject: Re: [PATCH] ACPI: Do not enable ACPI SPCR console by default on arm64
Date: Tue, 18 Jun 2024 16:29:24 +0100 [thread overview]
Message-ID: <20240618152923.GB2354@willie-the-truck> (raw)
In-Reply-To: <cb4c5fd0-9629-4362-918a-cb044eb9e558@redhat.com>
On Thu, May 30, 2024 at 09:06:17AM -0400, Prarit Bhargava wrote:
> On 5/29/24 21:53, Liu Wei wrote:
> > Consistency with x86 and loongarch, don't enable ACPI SPCR console
> > by default on arm64
> >
> > Signed-off-by: Liu Wei <liuwei09@cestc.cn>
> > ---
> > arch/arm64/kernel/acpi.c | 3 ++-
> > 1 file changed, 2 insertions(+), 1 deletion(-)
> >
> > diff --git a/arch/arm64/kernel/acpi.c b/arch/arm64/kernel/acpi.c
> > index dba8fcec7f33..1deda3e5a0d2 100644
> > --- a/arch/arm64/kernel/acpi.c
> > +++ b/arch/arm64/kernel/acpi.c
> > @@ -227,7 +227,8 @@ void __init acpi_boot_table_init(void)
> > if (earlycon_acpi_spcr_enable)
> > early_init_dt_scan_chosen_stdout();
> > } else {
> > - acpi_parse_spcr(earlycon_acpi_spcr_enable, true);
> > + /* Do not enable ACPI SPCR console by default */
> > + acpi_parse_spcr(earlycon_acpi_spcr_enable, false);
> > if (IS_ENABLED(CONFIG_ACPI_BGRT))
> > acpi_table_parse(ACPI_SIG_BGRT, acpi_parse_bgrt);
> > }
>
> It's been a while, and the status of arm hardware may have changed. IIRC the
> choice to force enable this is that most arm hardware is headless and this
> was a _required_ option for booting.
>
> I'm not sure if that's still the case as it's been a long time.
>
> Can anyone from the ARM community provide an approval here?
I don't have a strong opinion either way, but adding the Arm ACPI folks
in case they care.
Having said that, if the only rationale for this patch is consistency
with other architectures, then I think I'd lean towards leaving the
behaviour as-is so we don't give users a nasty surprise on their next
kernel upgrade.
Will
next prev parent reply other threads:[~2024-06-18 15:29 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-05-30 1:53 [PATCH] ACPI: Do not enable ACPI SPCR console by default on arm64 Liu Wei
2024-05-30 13:06 ` Prarit Bhargava
2024-06-18 15:29 ` Will Deacon [this message]
2024-06-18 16:40 ` Sudeep Holla
2024-06-20 12:04 ` Prarit Bhargava
2024-06-21 4:37 ` Liu Wei
2024-05-31 1:52 ` Liu Wei
2024-06-21 4:47 ` [PATCH v2] ACPI: Add config to disable " Liu Wei
2024-06-21 11:26 ` Prarit Bhargava
2024-06-21 16:39 ` Liu Wei
2024-06-22 9:35 ` [PATCH V3] ACPI: Add acpi=nospcr to disable ACPI SPCR as default console " Liu Wei
2024-06-22 17:05 ` Andrew Lunn
2024-06-24 5:04 ` Liu Wei
2024-06-24 14:42 ` Will Deacon
2024-06-24 15:10 ` Andrew Lunn
2024-06-25 2:48 ` Liu Wei
2024-06-25 3:05 ` [PATCH v4] ACPI: Add acpi=nospcr to disable ACPI SPCR as default console on ARM64 Liu Wei
2024-06-25 12:58 ` Prarit Bhargava
2024-06-26 3:07 ` Liu Wei
2024-06-26 7:54 ` Hanjun Guo
2024-07-04 16:22 ` Catalin Marinas
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=20240618152923.GB2354@willie-the-truck \
--to=will@kernel.org \
--cc=catalin.marinas@arm.com \
--cc=guohanjun@huawei.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=liuwei09.cestc.cn@cecloud.com \
--cc=liuwei09@cestc.cn \
--cc=lpieralisi@kernel.org \
--cc=prarit@redhat.com \
--cc=rafael@kernel.org \
--cc=sudeep.holla@arm.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