From: Alan Cox <gnomes@lxorguk.ukuu.org.uk>
To: Aaron Durbin <adurbin@chromium.org>
Cc: Andy Shevchenko <andy.shevchenko@gmail.com>,
Daniel Kurtz <djkurtz@chromium.org>,
Ricardo Ribalda Delgado <ricardo.ribalda@gmail.com>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
Jiri Slaby <jslaby@suse.com>,
Marc Gonzalez <marc_gonzalez@sigmadesigns.com>,
Doug Anderson <dianders@chromium.org>,
Matt Redfearn <matt.redfearn@mips.com>,
Jeffy <jeffy.chen@rock-chips.com>,
"open list:SERIAL DRIVERS" <linux-serial@vger.kernel.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH 1/3] serial: 8250_early: Add earlycon support for AMD Carrizo / Stoneyridge
Date: Fri, 6 Apr 2018 14:47:13 +0100 [thread overview]
Message-ID: <20180406144713.30d1ca00@alans-desktop> (raw)
In-Reply-To: <CAE2855tmMwbOWDOs-iJS7i35=Y7gt0xun4ApfhZyY9Kr5N3NJA@mail.gmail.com>
> But we don't have the full ACPI interpreter up in the early part of
> the kernel. All these 'early' devices have their own setup/config
> which is the source of the issue. Or maybe I am wrong about the full
> interpreter and the early drivers are just not taking advantage of the
> ACPI device binding?
In very early boot with serial console you just have to pray. No change
there. Once ACPI comes up you however have the information to populate
everything and configure correctly.
So it should work fine except for kernel hackers trying to do early boot
debug, which is a small (but important) cornercase ?
Alan
next prev parent reply other threads:[~2018-04-06 13:47 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20180314003655.12141-1-djkurtz@chromium.org>
2018-03-14 0:36 ` [PATCH 1/3] serial: 8250_early: Add earlycon support for AMD Carrizo / Stoneyridge Daniel Kurtz
2018-03-14 10:35 ` Andy Shevchenko
2018-03-14 10:53 ` Ricardo Ribalda Delgado
2018-03-14 16:29 ` Daniel Kurtz
2018-03-14 16:38 ` Andy Shevchenko
2018-03-14 17:09 ` Aaron Durbin
2018-03-14 17:12 ` Aaron Durbin
2018-03-14 17:31 ` Andy Shevchenko
2018-03-26 18:24 ` Alan Cox
2018-03-27 2:56 ` Aaron Durbin
2018-03-29 13:34 ` Alan Cox
2018-04-01 18:54 ` Aaron Durbin
2018-04-06 13:47 ` Alan Cox [this message]
2018-04-09 16:00 ` Aaron Durbin
2018-03-14 0:36 ` [PATCH 2/3] ACPI: SPCR: Add support for AMD CT/SZ Daniel Kurtz
2018-03-14 10:36 ` Andy Shevchenko
2018-04-17 0:43 ` Jon Masters
2018-03-14 0:36 ` [PATCH 3/3] serial: core: Allow skipping old serial port initialization Daniel Kurtz
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=20180406144713.30d1ca00@alans-desktop \
--to=gnomes@lxorguk.ukuu.org.uk \
--cc=adurbin@chromium.org \
--cc=andy.shevchenko@gmail.com \
--cc=dianders@chromium.org \
--cc=djkurtz@chromium.org \
--cc=gregkh@linuxfoundation.org \
--cc=jeffy.chen@rock-chips.com \
--cc=jslaby@suse.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-serial@vger.kernel.org \
--cc=marc_gonzalez@sigmadesigns.com \
--cc=matt.redfearn@mips.com \
--cc=ricardo.ribalda@gmail.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;
as well as URLs for NNTP newsgroup(s).