[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20240624050404.84512-1-liuwei09@cestc.cn>
Date: Mon, 24 Jun 2024 13:04:04 +0800
From: Liu Wei <liuwei09@...tc.cn>
To: andrew@...n.ch,
Liu Wei <liuwei09@...tc.cn>
Cc: catalin.marinas@....com,
linux-arm-kernel@...ts.infradead.org,
linux-kernel@...r.kernel.org,
prarit@...hat.com,
will@...nel.org
Subject: Re: [PATCH V3] ACPI: Add acpi=nospcr to disable ACPI SPCR as default console on arm64
From: Andrew Lunn <andrew@...n.ch>
> On Sat, Jun 22, 2024 at 05:35:21PM +0800, Liu Wei wrote:
> > For varying privacy and security reasons, sometimes we would like to
> > completely silence the serial console, and only enable it when needed.
> >
> > But there are many existing systems that depend on this console,
> > so add acpi=nospcr for this situation.
>
> Maybe it is just me, but i see nospcr and my brain expands it to "no
> speaker". Adding to that, your commit message says "completely
> silence"...
>
> > + nospcr -- disable ACPI SPCR as default console on ARM64
> > + For ARM64, ONLY "acpi=off", "acpi=on", "acpi=force" or
> > + "acpi=nospcr" are available
> > + For RISCV64, ONLY "acpi=off", "acpi=on" or "acpi=force"
> > + are available
>
> How about putting the word 'serial' in here somewhere, just to give
> users an additional clue you are not talking about a speaker, CTRL-G
> etc.
Thank you for your suggestion.
You mean acpi=nospcr_serial or acpi=no_spcrserial? However, it appears
somewhat unconventional compared to the original acpi=* parameter.
How about introducing a new one, such as acpi_no_spcr_serial or
acpi_no_spcr_console?
Best wishes,
Liu Wei
> Andrew
Powered by blists - more mailing lists