[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <83146e51-2b63-c2eb-65e3-8122921a89ea@kernel.org>
Date: Thu, 24 Nov 2022 06:58:20 +0100
From: Jiri Slaby <jirislaby@...nel.org>
To: Ricardo Ribalda <ribalda@...omium.org>,
Greg Kroah-Hartman <gregkh@...uxfoundation.org>,
Jonathan Corbet <corbet@....net>
Cc: linux-serial@...r.kernel.org, linux-kernel@...r.kernel.org,
linux-doc@...r.kernel.org
Subject: Re: [PATCH v1 1/1] earlycon: Let users set the clock frequency
Hi,
On 24. 11. 22, 0:29, Ricardo Ribalda wrote:
> Some platforms, namely AMD Picasso, use non standard uart clocks (48M),
> witch makes it impossible to use with earlycon.
>
> Let the user select its own frequency.
...
> --- a/drivers/tty/serial/earlycon.c
> +++ b/drivers/tty/serial/earlycon.c
> @@ -120,7 +120,11 @@ static int __init parse_options(struct earlycon_device *device, char *options)
> }
>
> if (options) {
> + char *uartclk;
> device->baud = simple_strtoul(options, NULL, 0);
> + uartclk = strchr(options, ',');
> + if (uartclk)
> + port->uartclk = simple_strtoull(uartclk + 1, NULL, 0);
uartclk is uint. So why does it make sense to do ull parsing?
thanks,
--
js
suse labs
Powered by blists - more mailing lists