From: Florian Fainelli <f.fainelli@gmail.com>
To: Heiko Stuebner <heiko@sntech.de>,
linux-rockchip@lists.infradead.org,
Francesco Dolcini <francesco.dolcini@toradex.com>
Cc: linux-arm-kernel@lists.infradead.org,
quentin.schulz@theobroma-systems.com,
Heiko Stuebner <heiko.stuebner@cherry.de>
Subject: Re: [PATCH] arm64: defconfig: Increase SERIAL_8250_NR_UARTS to 10
Date: Fri, 1 Dec 2023 11:57:53 -0800 [thread overview]
Message-ID: <bf5c7806-7405-4728-bb10-7913368f62a0@gmail.com> (raw)
In-Reply-To: <20231201191228.343230-1-heiko@sntech.de>
+Francesco,
On 12/1/23 11:12, Heiko Stuebner wrote:
> From: Heiko Stuebner <heiko.stuebner@cherry.de>
>
> Boards using socs like the rk3588 can use up to 10 uarts, so the default
> of 4 is way too low. Therefore increase the maximum number to 10.
>
> SERIAL_8250_RUNTIME_UARTS on the other hand describes the number of uart
> data structures to prepare before registering them. This option can stay
> at its default value of 4 since for one it can be changed via a boot
> parameter 8250.nr_uarts but also since
> commit 9d86719f8769 ("serial: 8250: Allow using ports higher than SERIAL_8250_RUNTIME_UARTS")
>
> the kernel can register uarts dynamically that are above the
> SERIAL_8250_RUNTIME_UARTS threshold.
>
> Signed-off-by: Heiko Stuebner <heiko.stuebner@cherry.de>
There is a competing patch set from Francesco being submitted as well:
https://lore.kernel.org/all/20231201171544.1901-1-francesco@dolcini.it/
looks like some coordination is necessary.
--
Florian
_______________________________________________
Linux-rockchip mailing list
Linux-rockchip@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-rockchip
next prev parent reply other threads:[~2023-12-01 19:58 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-12-01 19:12 [PATCH] arm64: defconfig: Increase SERIAL_8250_NR_UARTS to 10 Heiko Stuebner
2023-12-01 19:57 ` Florian Fainelli [this message]
2023-12-01 20:09 ` Francesco Dolcini
2023-12-01 20:56 ` Heiko Stübner
2023-12-01 21:03 ` Heiko Stübner
2023-12-01 21:12 ` Francesco Dolcini
2023-12-02 11:51 ` Francesco Dolcini
2023-12-02 12:12 ` Heiko Stübner
2023-12-04 9:32 ` Quentin Schulz
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=bf5c7806-7405-4728-bb10-7913368f62a0@gmail.com \
--to=f.fainelli@gmail.com \
--cc=francesco.dolcini@toradex.com \
--cc=heiko.stuebner@cherry.de \
--cc=heiko@sntech.de \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-rockchip@lists.infradead.org \
--cc=quentin.schulz@theobroma-systems.com \
/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