From: Doug Anderson <dianders@chromium.org>
To: Daniel Thompson <daniel.thompson@linaro.org>
Cc: Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
Jiri Slaby <jslaby@suse.com>, Sumit Garg <sumit.garg@linaro.org>,
linux-serial@vger.kernel.org, LKML <linux-kernel@vger.kernel.org>,
Patch Tracking <patches@linaro.org>
Subject: Re: [PATCH] serial: earlycon: Allow earlier DT scan is acpi=off
Date: Wed, 29 Apr 2020 17:40:10 -0700 [thread overview]
Message-ID: <CAD=FV=VTkO5AULJe1ksyhKLLxpywqX-RLC_T4ENyDf3ONJNMKg@mail.gmail.com> (raw)
In-Reply-To: <20200428162227.687978-1-daniel.thompson@linaro.org>
Hi,
On Tue, Apr 28, 2020 at 9:22 AM Daniel Thompson
<daniel.thompson@linaro.org> wrote:
>
> Currently if the kernel has support for ACPI SPCR parsing then earlycon
> without arguments is processed later than the full earlycon=...
> alternative.
>
> If ACPI has been explicitly disabled on the kernel command line then
> there is not need to defer since the ACPI code (both x86 and arm64)
> will never actually run.
>
> Or, put another way it allows lazy people to throw "acpi=off earlycon"
> onto the command line of a DT systems and be confident the console will
> start as early as possible without them having to lookup the driver
> and address needed for a specific platform.
>
> Signed-off-by: Daniel Thompson <daniel.thompson@linaro.org>
> ---
> drivers/tty/serial/earlycon.c | 28 +++++++++++++++++++++++++++-
> 1 file changed, 27 insertions(+), 1 deletion(-)
I wonder if a cleaner option is to just add a special "earlycon" value
like "earlycon=not_acpi". This wouldn't require any special peeking
and would just be a sentinel that just says "you should autodetect the
earlycon, but don't worry about waiting for ACPI". ...that in itself
is a bit of a hack, but at least it's more self contained in the
earlycon driver and maybe more discoverable when someone is figuring
out how to setup earlycon?
-Doug
>
> diff --git a/drivers/tty/serial/earlycon.c b/drivers/tty/serial/earlycon.c
> index 2ae9190b64bb..ebb648aacb47 100644
> --- a/drivers/tty/serial/earlycon.c
> +++ b/drivers/tty/serial/earlycon.c
> @@ -215,6 +215,31 @@ int __init setup_earlycon(char *buf)
> */
> bool earlycon_acpi_spcr_enable __initdata;
>
> +/*
> + * This takes a sneaky peek at other boot arguments (which may not have
> + * been parsed at this point in the boot) to check whether ACPI has
> + * been explicitly disabled. If it is explicitly disabled then there is
> + * no reason to defer initialization of the early console.
> + */
> +static bool earlycon_check_for_acpi_off(void)
> +{
> + static const char token[] = "acpi=off";
> + const char *arg;
> + char before, after;
> +
> + arg = strstr(boot_command_line, token);
> + while (arg) {
> + before = arg == boot_command_line ? ' ' : arg[-1];
> + after = arg[sizeof(token)-1];
> + if (isspace(before) && (isspace(after) || after == '\0'))
> + return true;
> +
> + arg = strstr(arg+1, token);
> + }
> +
> + return false;
> +}
> +
> /* early_param wrapper for setup_earlycon() */
> static int __init param_setup_earlycon(char *buf)
> {
> @@ -222,7 +247,8 @@ static int __init param_setup_earlycon(char *buf)
>
> /* Just 'earlycon' is a valid param for devicetree and ACPI SPCR. */
> if (!buf || !buf[0]) {
> - if (IS_ENABLED(CONFIG_ACPI_SPCR_TABLE)) {
> + if (IS_ENABLED(CONFIG_ACPI_SPCR_TABLE) &&
> + !earlycon_check_for_acpi_off()) {
> earlycon_acpi_spcr_enable = true;
> return 0;
> } else if (!buf) {
> --
> 2.25.1
>
next prev parent reply other threads:[~2020-04-30 0:40 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-04-28 16:22 [PATCH] serial: earlycon: Allow earlier DT scan is acpi=off Daniel Thompson
2020-04-30 0:40 ` Doug Anderson [this message]
2020-04-30 12:09 ` Daniel Thompson
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='CAD=FV=VTkO5AULJe1ksyhKLLxpywqX-RLC_T4ENyDf3ONJNMKg@mail.gmail.com' \
--to=dianders@chromium.org \
--cc=daniel.thompson@linaro.org \
--cc=gregkh@linuxfoundation.org \
--cc=jslaby@suse.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-serial@vger.kernel.org \
--cc=patches@linaro.org \
--cc=sumit.garg@linaro.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;
as well as URLs for NNTP newsgroup(s).