From: Greg KH <gregkh@linuxfoundation.org>
To: Sherry Sun <sherry.sun@nxp.com>
Cc: "jirislaby@kernel.org" <jirislaby@kernel.org>,
"linux-serial@vger.kernel.org" <linux-serial@vger.kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"imx@lists.linux.dev" <imx@lists.linux.dev>
Subject: Re: [PATCH] tty: serial: fsl_lpuart: increase maximum uart_nr to 12
Date: Mon, 6 Jan 2025 14:44:53 +0100 [thread overview]
Message-ID: <2025010602-cozily-rind-c2c6@gregkh> (raw)
In-Reply-To: <DB9PR04MB842950C5700AEE30968FA1CC92102@DB9PR04MB8429.eurprd04.prod.outlook.com>
On Mon, Jan 06, 2025 at 10:24:52AM +0000, Sherry Sun wrote:
>
>
> > -----Original Message-----
> > From: Greg KH <gregkh@linuxfoundation.org>
> > Sent: Friday, January 3, 2025 5:08 PM
> > To: Sherry Sun <sherry.sun@nxp.com>
> > Cc: jirislaby@kernel.org; linux-serial@vger.kernel.org; linux-
> > kernel@vger.kernel.org; imx@lists.linux.dev
> > Subject: Re: [PATCH] tty: serial: fsl_lpuart: increase maximum uart_nr to 12
> >
> > On Fri, Jan 03, 2025 at 03:11:54PM +0800, Sherry Sun wrote:
> > > Some SoCs like the i.MX943 have aliases for up to 12 UARTs, need to
> > > increase UART_NR from 8 to 12 to support lpuart9-12 to avoid
> > > initialization failures.
> > >
> > > Signed-off-by: Sherry Sun <sherry.sun@nxp.com>
> > > ---
> > > drivers/tty/serial/fsl_lpuart.c | 2 +-
> > > 1 file changed, 1 insertion(+), 1 deletion(-)
> > >
> > > diff --git a/drivers/tty/serial/fsl_lpuart.c
> > > b/drivers/tty/serial/fsl_lpuart.c index 57b0632a3db6..7cb1e36fdaab
> > > 100644
> > > --- a/drivers/tty/serial/fsl_lpuart.c
> > > +++ b/drivers/tty/serial/fsl_lpuart.c
> > > @@ -245,7 +245,7 @@
> > >
> > > #define DRIVER_NAME "fsl-lpuart"
> > > #define DEV_NAME "ttyLP"
> > > -#define UART_NR 8
> > > +#define UART_NR 12
> >
> > Why not fix this properly and make this dynamic and get rid of the static array
> > causing all of this problem? That way when you get a system with 13 uarts,
> > you will be ok :)
> >
>
> Hi Greg,
>
> Thanks for your comment.
> But I checked all the uart drivers under drivers/tty/serial/, UART_NR
> is widely used, currently almost every uart driver that supports
> multiple uart ports defines this macro, this value is needed for the
> nr parameter of struct uart_driver, also for console index checking
> and setup.
Yeah, it's messy, but it can be done (for example see all of the
usb-serial devices, we don't limit the number of those ports in the
system except to 256 I think.)
> This patch just refers to many other uart driver patches to extend
> maximum uart number, such as
> https://lore.kernel.org/all/20240112095300.2004878-3-valentin.caron@foss.st.com/.
> Agree that it will be nice to dynamically allocate everything, but for
> now I prefer to simply change this value as there doesn't seem to be a
> good uart implementation at the moment, not sure what you prefer? :)
I'd prefer not hard-coding stuff like this but if it's going to be too
much of a pain I guess I'll take this for now...
thanks,
greg k-h
next prev parent reply other threads:[~2025-01-06 13:44 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-01-03 7:11 [PATCH] tty: serial: fsl_lpuart: increase maximum uart_nr to 12 Sherry Sun
2025-01-03 9:08 ` Greg KH
2025-01-06 10:24 ` Sherry Sun
2025-01-06 13:44 ` Greg KH [this message]
2025-01-07 8:16 ` Sherry Sun
2025-01-07 8:29 ` Sherry Sun
2025-01-07 8:43 ` Greg KH
2025-01-07 9:54 ` Sherry Sun
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=2025010602-cozily-rind-c2c6@gregkh \
--to=gregkh@linuxfoundation.org \
--cc=imx@lists.linux.dev \
--cc=jirislaby@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-serial@vger.kernel.org \
--cc=sherry.sun@nxp.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