From: Jiri Slaby <jirislaby@kernel.org>
To: Ricardo Ribalda <ribalda@chromium.org>,
Jonathan Corbet <corbet@lwn.net>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Cc: linux-doc@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-serial@vger.kernel.org
Subject: Re: [PATCH v3 2/2] earlycon: Increase options size
Date: Tue, 6 Dec 2022 07:53:00 +0100 [thread overview]
Message-ID: <df281b81-ba6c-4ca8-3da6-135d4ae09861@kernel.org> (raw)
In-Reply-To: <20221123-serial-clk-v3-2-49c516980ae0@chromium.org>
On 24. 11. 22, 13:39, Ricardo Ribalda wrote:
> Now that the clock frequency is also part of the options, 16 bytes is
> too little.
>
> Without this patch dmesg does not show the whole options, Eg:
>
> earlycon: uart0 at MMIO32 0x00000000fedc9000 (options '115200n8,480000')
>
> instead of: '115200n8,48000000'
>
> Signed-off-by: Ricardo Ribalda <ribalda@chromium.org>
Reviewed-by: Jiri Slaby <jirislaby@kernel.org>
> diff --git a/include/linux/serial_core.h b/include/linux/serial_core.h
> index d657f2a42a7b..f555927195da 100644
> --- a/include/linux/serial_core.h
> +++ b/include/linux/serial_core.h
> @@ -701,7 +701,7 @@ static inline int uart_poll_timeout(struct uart_port *port)
> struct earlycon_device {
> struct console *con;
> struct uart_port port;
> - char options[16]; /* e.g., 115200n8 */
> + char options[32]; /* e.g., 115200n8 */
> unsigned int baud;
> };
>
>
--
js
suse labs
prev parent reply other threads:[~2022-12-06 6:53 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-24 12:39 [PATCH v3 0/2] earlycon: Let users set the clock frequency Ricardo Ribalda
2022-11-24 12:39 ` [PATCH v3 1/2] " Ricardo Ribalda
2022-12-02 17:24 ` Ricardo Ribalda
2022-12-12 13:39 ` Greg Kroah-Hartman
2022-12-06 6:52 ` Jiri Slaby
2022-11-24 12:39 ` [PATCH v3 2/2] earlycon: Increase options size Ricardo Ribalda
2022-12-06 6:53 ` Jiri Slaby [this message]
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=df281b81-ba6c-4ca8-3da6-135d4ae09861@kernel.org \
--to=jirislaby@kernel.org \
--cc=corbet@lwn.net \
--cc=gregkh@linuxfoundation.org \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-serial@vger.kernel.org \
--cc=ribalda@chromium.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 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).