From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on aws-us-west-2-korg-lkml-1.web.codeaurora.org Received: from bombadil.infradead.org (bombadil.infradead.org [198.137.202.133]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by smtp.lore.kernel.org (Postfix) with ESMTPS id 71726C4167B for ; Sat, 2 Dec 2023 11:51:37 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=lists.infradead.org; s=bombadil.20210309; h=Sender: Content-Transfer-Encoding:Content-Type:List-Subscribe:List-Help:List-Post: List-Archive:List-Unsubscribe:List-Id:In-Reply-To:MIME-Version:References: Message-ID:Subject:Cc:To:From:Date:Reply-To:Content-ID:Content-Description: Resent-Date:Resent-From:Resent-Sender:Resent-To:Resent-Cc:Resent-Message-ID: List-Owner; bh=mnLSwJHr6V01IQ1F5s7rnUTm6XazuzUXoxLHrEG5QGs=; b=RdeRWntxJCwQqD o8jD/MqTyjeDtoEyYjInfxd9hudCCBeUgjmv9jCTiHdLCOk1q6Jw9SX/PjTtOf7gJp3fT42C95Kn0 d8l29BuLWR9uRI/wedTEpMBmRXFdI57ZfaOHrrxVv+fCe5+LvxYFtcEqC/tyoOyHt0m1ZgIOYXgh3 lcElH/s5i/EKdbS+Ii0rkzV8/gqma7mw+85PbHVRaT9yg+fxPNv1fBaB9Xf2HYVaqYBdjsOOk9eKE /VL23ESUz4XOZdyxsjHdk+oEKJL56JpLM6GCkZnIsXIw6BXiCB4KaY9Dkfcs4mAw5q1MkE6hFqL6J 9zaRAU9cBYom2S5+TzMg==; Received: from localhost ([::1] helo=bombadil.infradead.org) by bombadil.infradead.org with esmtp (Exim 4.96 #2 (Red Hat Linux)) id 1r9OWm-00Fe2a-0P; Sat, 02 Dec 2023 11:51:20 +0000 Received: from mail11.truemail.it ([217.194.8.81]) by bombadil.infradead.org with esmtps (Exim 4.96 #2 (Red Hat Linux)) id 1r9OWh-00Fe1r-0p; Sat, 02 Dec 2023 11:51:17 +0000 Received: from gaggiata.pivistrello.it (93-49-2-63.ip317.fastwebnet.it [93.49.2.63]) by mail11.truemail.it (Postfix) with ESMTPA id 4731520144; Sat, 2 Dec 2023 12:51:04 +0100 (CET) Received: from livingston (unknown [192.168.42.11]) by gaggiata.pivistrello.it (Postfix) with ESMTP id E9C2F7F8F3; Sat, 2 Dec 2023 12:51:03 +0100 (CET) Received: from pivi by livingston with local (Exim 4.96) (envelope-from ) id 1r9OWV-0000tw-2Z; Sat, 02 Dec 2023 12:51:03 +0100 Date: Sat, 2 Dec 2023 12:51:03 +0100 From: Francesco Dolcini To: Heiko =?iso-8859-1?Q?St=FCbner?= Cc: Florian Fainelli , Francesco Dolcini , linux-rockchip@lists.infradead.org, Francesco Dolcini , linux-arm-kernel@lists.infradead.org, quentin.schulz@theobroma-systems.com, Heiko Stuebner Subject: Re: [PATCH] arm64: defconfig: Increase SERIAL_8250_NR_UARTS to 10 Message-ID: References: <20231201191228.343230-1-heiko@sntech.de> <4075500.2IRrRt1zHL@diego> MIME-Version: 1.0 Content-Disposition: inline In-Reply-To: <4075500.2IRrRt1zHL@diego> X-CRM114-Version: 20100106-BlameMichelson ( TRE 0.8.0 (BSD) ) MR-646709E3 X-CRM114-CacheID: sfid-20231202_035115_481804_399C88FD X-CRM114-Status: GOOD ( 25.92 ) X-BeenThere: linux-rockchip@lists.infradead.org X-Mailman-Version: 2.1.34 Precedence: list List-Id: Upstream kernel work for Rockchip platforms List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Sender: "Linux-rockchip" Errors-To: linux-rockchip-bounces+linux-rockchip=archiver.kernel.org@lists.infradead.org On Fri, Dec 01, 2023 at 09:56:27PM +0100, Heiko St=FCbner wrote: > Hi, > = > Am Freitag, 1. Dezember 2023, 21:09:29 CET schrieb Francesco Dolcini: > > On Fri, Dec 01, 2023 at 11:57:53AM -0800, Florian Fainelli wrote: > > > +Francesco, > > > = > > > On 12/1/23 11:12, Heiko Stuebner wrote: > > > > From: Heiko Stuebner > > > > = > > > > Boards using socs like the rk3588 can use up to 10 uarts, so the de= fault > > > > of 4 is way too low. Therefore increase the maximum number to 10. > > Do you have an actual need of 10, e.g. an existing board with 10 uarts > > enabled supported by the mainline kernel? Just thinking at the last arm= 64 SoC I > > am working with it should be 12 if we use this as a metric. > = > The rk3588 can do 10 (0-9), the board I'm working on is using up to uart7= (aka 8 uarts). > Reasoning below in the 3rd paragraph. > = > = > > > > 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 S= ERIAL_8250_RUNTIME_UARTS") > > > > = > > > > the kernel can register uarts dynamically that are above the > > > > SERIAL_8250_RUNTIME_UARTS threshold. > > > > = > > > > Signed-off-by: Heiko Stuebner > > > = > > > There is a competing patch set from Francesco being submitted as well: > > > https://lore.kernel.org/all/20231201171544.1901-1-francesco@dolcini.i= t/ > > > > > > looks like some coordination is necessary. > = > = > So TL;DR: > I could live with the 8 from your original patch, but I guess would prefer > going with a safer value, so the 10 or your 12 from above. > = > Because I guess if a controller is present, someone will use it > eventually ;-). There was an explicit push back on this approach from Arnd, see https://lore.kernel.org/all/CAK8P3a2VSBvOn1o+q1PYZaQ6LS9U4cz+DZGuDbisHkwNs2= dAAw@mail.gmail.com/ I would propose that we stay with my current proposal of 8. Francesco _______________________________________________ Linux-rockchip mailing list Linux-rockchip@lists.infradead.org http://lists.infradead.org/mailman/listinfo/linux-rockchip