[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <5fab980d-d937-8806-9745-9850947a9096@redhat.com>
Date: Tue, 23 Jan 2018 07:41:56 -0500
From: Prarit Bhargava <prarit@...hat.com>
To: Timur Tabi <timur@...eaurora.org>, linux-kernel@...r.kernel.org
Cc: linux-acpi@...r.kernel.org, linux-doc@...r.kernel.org,
linux-arm-kernel@...ts.infradead.org, linux-pm@...r.kernel.org,
linux-serial@...r.kernel.org, Bhupesh Sharma <bhsharma@...hat.com>,
Lv Zheng <lv.zheng@...el.com>,
Thomas Gleixner <tglx@...utronix.de>,
Ingo Molnar <mingo@...hat.com>,
"H. Peter Anvin" <hpa@...or.com>, x86@...nel.org,
Jonathan Corbet <corbet@....net>,
Catalin Marinas <catalin.marinas@....com>,
Will Deacon <will.deacon@....com>, graeme.gregory@...aro.org,
mark.salter@...hat.com
Subject: Re: [PATCH] acpi, spcr: Make SPCR available to x86
On 01/22/2018 04:49 PM, Timur Tabi wrote:
> On 01/18/2018 09:09 AM, Prarit Bhargava wrote:
>> if (acpi_disabled) {
>> - if (earlycon_init_is_deferred)
>> + if (earlycon_acpi_spcr_enable)
>
> This patch works for me, so I can ACK it, but first you might want to rename
> earlycon_acpi_spcr_enable, because these two lines don't make much sense.
>
> "If ACPI is disabled, and ACPI SCPR is enabled, then ...."
>
> If ACPI is disabled, then how can a variable called "earlycon_acpi_spcr_enable"
> be true?
>
> Would it make more sense to rename it to earlycon_spcr_enable?
>
acpi_disabled is a global runtime flag that can be set via "acpi=off" on the
command line. It does not disable the tables, only the reading and interpreting
of the data in the tables.
P.
Powered by blists - more mailing lists