On 10/21/2015 11:38 AM, Masahiro Yamada wrote:
> Hi Peter.
>
> 2015-10-21 21:46 GMT+09:00 Peter Hurley <peter@xxxxxxxxxxxxxxxxxx>:
>> On 10/21/2015 04:58 AM, Sudeep Holla wrote:
>>> On 21/10/15 06:09, Masahiro Yamada wrote:
>>>> I think there exist two ways to specify the console port and baudrate.
>>>>
>>>>
>>>> [1] Specify console in bootargs
>>>>
>>>> chosen {
>>>> bootargs = "console=ttyS0,115200";
>>>> };
>>>>
>>>>
>>>> [2] Specify stdout-path
>>>>
>>>> chosen {
>>>> stdout-path = "serial0:115200n8";
>>>
>>> This will work for even early/boot console, so this is better than
>>> option [1]
>>
>> Be aware that options specified via /chosen/stdout-path are
>> currently ignored by earlycon. There were some hiccups getting the
>> initial support upstream; when 4.4 hits mainline, I'll resubmit
>> my series that implements the of_serial i/o properties and
>> options passthrough to earlycon setup.
>
>
> As I said in another thread ("serial: earlycon: allow to specify
> uartclk in earlycon kernel-parameter"),
> stdout-path can pass dev->baud, but not port->uartclk.
That's true but I'm not seeing in that thread where you wrote that?
My replies there were specific to uartclk on the kernel command line,
which isn't necessary if the bootloader has already initialized the
uart.
> It is usually specified "clocks" phandle, but
> clk is not ready at the point of earlycon.
>
> It seems impossible to set up the baudrate even if the options are passed.
It's difficult to understand what you're trying to do when I can't
see the code you're referring to. For example, I only recently
understood that you're talking about a earlycon implementation
that you're working on and not the 8250 earlycon itself.
If you look at other non-8250 earlycons, you'll see they all ignore
the baud rate, on the assumption the bootloader already set it up.
The 8250 earlycon is a little different because legacy platforms
do not initialize the uart.
Regards,
Peter Hurley
--
To unsubscribe from this list: send the line "unsubscribe linux-serial" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
