From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: Randy Dunlap <rdunlap@infradead.org>
Cc: Daniel Kurtz <djkurtz@chromium.org>,
adurbin@chromium.org, briannorris@chromium.org,
Jiri Slaby <jslaby@suse.com>,
"open list:SERIAL DRIVERS" <linux-serial@vger.kernel.org>,
open list <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] earlycon: Allow specifying a uartclk in options
Date: Thu, 1 Mar 2018 19:42:52 +0100 [thread overview]
Message-ID: <20180301184252.GA29304@kroah.com> (raw)
In-Reply-To: <57fb4f35-fd75-b2cc-75f7-8157ab1081d5@infradead.org>
On Thu, Mar 01, 2018 at 10:30:45AM -0800, Randy Dunlap wrote:
> On 03/01/2018 10:20 AM, Daniel Kurtz wrote:
> > Currently when an earlycon is registered, the uartclk is assumed to be
> > BASE_BAUD * 16 = 1843200. If a baud rate is specified in the earlycon
> > options, then 8250_early's init_port will program the UART clock divider
> > registers based on this assumed uartclk.
> >
> > However, not all uarts have a UART clock of 1843200. For example, the
> > 8250_dw uart in AMD's CZ/ST uses a fixed 48 MHz clock (as specified in
> > cz_uart_desc in acpi_apd.c). Thus, specifying a baud when using earlycon
> > on such a device will result in incorrect divider values and a wrong UART
> > clock.
> >
> > Fix this by extending the earlycon options parameter to allow specification
> > of a uartclk, like so:
> >
> > earlycon=uart,mmio32,0xfedc6000,115200,48000000
> >
> > If none is specified, fall-back to prior behavior - 1843200.
> >
> > Signed-off-by: Daniel Kurtz <djkurtz@chromium.org>
>
> Hi,
>
> Hopefully there will also be an update to one of
> Documentation/admin-guide/kernel-parameters.txt or
> Documentation/admin-guide/serial-console.rst.
Well, considering I'm not taking this patch unless it comes with such an
update, I'm hoping as well :)
greg k-h
next prev parent reply other threads:[~2018-03-01 18:42 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-03-01 18:20 [PATCH] earlycon: Allow specifying a uartclk in options Daniel Kurtz
2018-03-01 18:20 ` Daniel Kurtz
2018-03-01 18:30 ` Randy Dunlap
2018-03-01 18:42 ` Greg Kroah-Hartman [this message]
2018-03-01 18:46 ` Andy Shevchenko
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=20180301184252.GA29304@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=adurbin@chromium.org \
--cc=briannorris@chromium.org \
--cc=djkurtz@chromium.org \
--cc=jslaby@suse.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-serial@vger.kernel.org \
--cc=rdunlap@infradead.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.