From: Peter Hurley <peter@hurleysoftware.com>
To: Sebastian Frias <sf84@laposte.net>
Cc: Mason <slash.tmp@free.fr>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
linux-serial@vger.kernel.org, LKML <linux-kernel@vger.kernel.org>,
Mans Rullgard <mans@mansr.com>
Subject: Re: [RFC PATCH] always probe UART HW when options are not specified
Date: Tue, 12 Jan 2016 11:47:26 -0800 [thread overview]
Message-ID: <5695584E.3040902@hurleysoftware.com> (raw)
In-Reply-To: <56950C21.3010805@laposte.net>
On 01/12/2016 06:22 AM, Sebastian Frias wrote:
> On 01/12/2016 10:37 AM, Mason wrote:
>> On 11/01/2016 20:06, Peter Hurley wrote:
>>
>>> I don't have enough information to suggest what you "should" use
>>> here.
>>>
>>> Is this going to be a shipping product?
>>> Is it single-core?
>>> etc.
>>>
>>> And what is your purpose for outputting early boot information
>>> before loading the serial driver which does provide console output?
>>
>> I'm not sure exactly which board Sebastian has in mind, but I've been
>> using the SERIAL_8250_RT288X driver on my Tango4 board.
>
> For the record, I'm using a SoC emulator, and thus do not have a bootloader per se and there are a bunch of other things that I cannot count on.
> The emulator has the UART pre-setup, so I just need Linux to take over without changing the parameters.
> Ideally, I would like to have the same image of Linux+DT to start in any instance of the emulator or real chips, regardless of the clock ratios, that's why I sort of need Linux to not change the UART speed, which is quite tricky because there are no clock generators in the emulator.
Got it, thanks for the info.
Please test the series I just cc'd you on plus the patch I sent
you yesterday.
That should get you an earlycon up and running on that simulator;
let me know if it doesn't and we'll go from there.
> NOTE: on my tree I'm using the patch I previously submitted here, so Linux is probing the UART so it works for all my cases, but I would like to go back to a standard tree.
I expect that patch to go into -next sometime during the 4.5-rc cycle.
Regards,
Peter Hurley
>> Note: calling the UART driver "Au1x00/RT288x" is a bit of a misnomer,
>> as these are names of SoCs using that distinct register layout.
>> The actual IP is probably the 16550-compatible Palmchip BK-3103.
>> https://sites.google.com/a/palmchiptech.com/palmchiptech/product-services/hardware-services/ip-cores/bk-3103
>> (Not sure that this website is legitimate, though.)
>>
>> When I need earlyprintk support, I use this patch from Mans:
>> http://thread.gmane.org/gmane.linux.kernel/2081016
>>
>> Regards.
>>
next prev parent reply other threads:[~2016-01-12 19:47 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <5672D18E.8000301@laposte.net>
2015-12-17 15:23 ` [RFC PATCH] always probe UART HW when options are not specified Måns Rullgård
2015-12-17 16:29 ` Peter Hurley
2015-12-17 16:48 ` Sebastian Frias
2015-12-17 17:21 ` Greg Kroah-Hartman
2015-12-17 19:05 ` Sebastian Frias
2015-12-17 17:48 ` Peter Hurley
2015-12-17 18:21 ` Sebastian Frias
2015-12-17 20:09 ` Peter Hurley
2015-12-18 13:53 ` Sebastian Frias
2015-12-18 15:03 ` Peter Hurley
2015-12-21 16:50 ` Sebastian Frias
2015-12-22 17:56 ` Sebastian Frias
2016-01-11 15:07 ` Sebastian Frias
2016-01-11 16:11 ` Peter Hurley
2016-01-11 17:56 ` Sebastian Frias
2016-01-11 19:06 ` Peter Hurley
2016-01-11 19:57 ` Peter Hurley
2016-01-11 20:21 ` Peter Hurley
2016-01-12 9:37 ` Mason
2016-01-12 14:22 ` Sebastian Frias
2016-01-12 19:47 ` Peter Hurley [this message]
2016-01-12 22:26 ` Mason
2016-01-12 22:42 ` Peter Hurley
2016-01-13 11:14 ` Sebastian Frias
2016-01-13 16:34 ` Peter Hurley
2016-01-18 11:52 ` Sebastian Frias
2016-01-12 14:14 ` Sebastian Frias
2016-01-12 21:18 ` Peter Hurley
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=5695584E.3040902@hurleysoftware.com \
--to=peter@hurleysoftware.com \
--cc=gregkh@linuxfoundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-serial@vger.kernel.org \
--cc=mans@mansr.com \
--cc=sf84@laposte.net \
--cc=slash.tmp@free.fr \
/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).