From: Andy Shevchenko <andy.shevchenko@gmail.com>
To: Daniel Kurtz <djkurtz@chromium.org>
Cc: Ricardo Ribalda Delgado <ricardo.ribalda@gmail.com>,
Aaron Durbin <adurbin@chromium.org>,
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: Wed, 14 Mar 2018 18:38:38 +0200 [thread overview]
Message-ID: <CAHp75VehhNv6pPrRiM9jBAK9FsqZ2Defo8HKhutwn+GPnCFp3w@mail.gmail.com> (raw)
In-Reply-To: <CAGS+omCuEYSHFPmknvvvjUpCWFP_rCmwa9utQiO=aEmdm-anwg@mail.gmail.com>
On Wed, Mar 14, 2018 at 6:29 PM, Daniel Kurtz <djkurtz@chromium.org> wrote:
> On Wed, Mar 14, 2018 at 4:54 AM Ricardo Ribalda Delgado <
> ricardo.ribalda@gmail.com> wrote:
>> On Wed, Mar 14, 2018 at 1:36 AM, Daniel Kurtz <djkurtz@chromium.org>
> wrote:
> In fact, the recommended way is to have firmware specify an ACPI SPCR table
> with OEMID="AMDCZ " (see https://patchwork.kernel.org/patch/10281307/) to
> configure proper access and address.
Hmm... I was thinking it's already there. And thus, this is just a
quirk for *existing* firmware that doesn't correctly configured
hardware.
(Yes, I'm aware about one nuance in SPCR specification I'm trying to
address via official ways)
> With an SPCR table in place, the
> kernel command line just becomes "earlycon", with no parameters.
SPCR *provides* an address of UART (required by specification).
--
With Best Regards,
Andy Shevchenko
next prev parent reply other threads:[~2018-03-14 16:38 UTC|newest]
Thread overview: 14+ 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 [this message]
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
2018-04-09 16:00 ` Aaron Durbin
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=CAHp75VehhNv6pPrRiM9jBAK9FsqZ2Defo8HKhutwn+GPnCFp3w@mail.gmail.com \
--to=andy.shevchenko@gmail.com \
--cc=adurbin@chromium.org \
--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).