From: Andy Shevchenko <andriy.shevchenko@linux.intel.com>
To: "Ilpo Järvinen" <ilpo.jarvinen@linux.intel.com>
Cc: "Uwe Kleine-König" <u.kleine-koenig@pengutronix.de>,
"Tharun Kumar P" <tharunkumar.pasumarthi@microchip.com>,
"Liang He" <windhl@126.com>,
linux-serial <linux-serial@vger.kernel.org>,
"Geert Uytterhoeven" <geert+renesas@glider.be>,
"Rob Herring" <robh@kernel.org>,
"Greg Kroah-Hartman" <gregkh@linuxfoundation.org>,
"Helge Deller" <deller@gmx.de>,
"Randy Dunlap" <rdunlap@infradead.org>,
linuxppc-dev@lists.ozlabs.org,
"Nicholas Piggin" <npiggin@gmail.com>,
LKML <linux-kernel@vger.kernel.org>,
"Kumaravel Thiagarajan" <kumaravel.thiagarajan@microchip.com>,
"Christophe Leroy" <christophe.leroy@csgroup.eu>,
kernel@pengutronix.de, "Michael Ellerman" <mpe@ellerman.id.au>,
"Matthew Gerlach" <matthew.gerlach@linux.intel.com>,
"Jiri Slaby" <jirislaby@kernel.org>
Subject: Re: [PATCH v3 2/2] serial: 8250: Apply FSL workarounds also without SERIAL_8250_CONSOLE
Date: Mon, 5 Jun 2023 17:01:08 +0300 [thread overview]
Message-ID: <ZH3qpAw9+dDzGVzf@smile.fi.intel.com> (raw)
In-Reply-To: <f01b13f5-34c9-62fc-52fd-33e923e2a2ba@linux.intel.com>
On Mon, Jun 05, 2023 at 04:44:08PM +0300, Ilpo Järvinen wrote:
> On Mon, 5 Jun 2023, Uwe Kleine-König wrote:
> > On Mon, Jun 05, 2023 at 04:22:55PM +0300, Ilpo Järvinen wrote:
> > > On Mon, 5 Jun 2023, Uwe Kleine-König wrote:
> > > > The need to handle the FSL variant of 8250 in a special way is also
> > > > present without console support. So soften the dependency for
> > > > SERIAL_8250_FSL accordingly. Note that with the 8250 driver compiled as
> > > > a module, some devices still might not make use of the needed
> > > > workarounds. That affects the ports instantiated in
> > > > arch/powerpc/kernel/legacy_serial.c.
> > > >
> > > > This issue was identified by Dominik Andreas Schorpp.
> > > >
> > > > To cope for CONFIG_SERIAL_8250=m + CONFIG_SERIAL_8250_FSL=y, 8250_fsl.o
> > > > must be put in the same compilation unit as 8250_port.o because the
> > > > latter defines some functions needed in the former and so 8250_fsl.o
> > > > must not be built-in if 8250_port.o is available in a module.
> > > >
> > > > Acked-by: Ilpo Järvinen <ilpo.jarvinen@linux.intel.com>
> > > > Link: https://lore.kernel.org/r/20230531083230.2702181-1-u.kleine-koenig@pengutronix.de
> > > > Signed-off-by: Uwe Kleine-König <u.kleine-koenig@pengutronix.de>
> > > > ---
> > > > drivers/tty/serial/8250/Kconfig | 2 +-
> > > > drivers/tty/serial/8250/Makefile | 2 +-
> > > > 2 files changed, 2 insertions(+), 2 deletions(-)
> > > >
> > > > diff --git a/drivers/tty/serial/8250/Kconfig b/drivers/tty/serial/8250/Kconfig
> > > > index 5313aa31930f..10c09b19c871 100644
> > > > --- a/drivers/tty/serial/8250/Kconfig
> > > > +++ b/drivers/tty/serial/8250/Kconfig
> > > > @@ -378,7 +378,7 @@ config SERIAL_8250_BCM2835AUX
> > > >
> > > > config SERIAL_8250_FSL
> > > > bool "Freescale 16550 UART support" if COMPILE_TEST && !(PPC || ARM || ARM64)
> > > > - depends on SERIAL_8250_CONSOLE
> > > > + depends on SERIAL_8250
> > >
> > > Just one additional thought: After the adding the arch side
> > > workaround/hack, SERIAL_8250_FSL could become a tristate?
> >
> > I see no benefit for a module separate from 8250_base.ko. There are
> > dependencies in both directions between 8250_port.o and 8250_fsl.o[1].
> > So in my book a bool SERIAL_8250_FSL that modifies 8250_base.ko (with
> > SERIAL_8250=m) is fine.
> > [1] 8250_port.o uses fsl8250_handle_irq() from 8250_fsl.o
>
> Is that after some fix which isn't in tty-next? I see only these:
>
> $ git grep -l fsl8250_handle_irq
> arch/powerpc/kernel/legacy_serial.c
> drivers/tty/serial/8250/8250_fsl.c
> drivers/tty/serial/8250/8250_of.c
> include/linux/serial_8250.h
>
> No users of fsl8250_handle_irq in 8250_port.c.
> >, and 8250_fsl.o uses serial8250_modem_status from 8250_port.o.
I don't like 8250_base to be fattened by some stuff that has no
generic meaning. Can we avoid putting every quirk there?
--
With Best Regards,
Andy Shevchenko
WARNING: multiple messages have this Message-ID (diff)
From: Andy Shevchenko <andriy.shevchenko@linux.intel.com>
To: "Ilpo Järvinen" <ilpo.jarvinen@linux.intel.com>
Cc: "Rob Herring" <robh@kernel.org>,
kernel@pengutronix.de,
"Geert Uytterhoeven" <geert+renesas@glider.be>,
"Tharun Kumar P" <tharunkumar.pasumarthi@microchip.com>,
"Greg Kroah-Hartman" <gregkh@linuxfoundation.org>,
"Helge Deller" <deller@gmx.de>,
"Randy Dunlap" <rdunlap@infradead.org>,
linuxppc-dev@lists.ozlabs.org,
"Nicholas Piggin" <npiggin@gmail.com>,
LKML <linux-kernel@vger.kernel.org>,
"Kumaravel Thiagarajan" <kumaravel.thiagarajan@microchip.com>,
linux-serial <linux-serial@vger.kernel.org>,
"Uwe Kleine-König" <u.kleine-koenig@pengutronix.de>,
"Matthew Gerlach" <matthew.gerlach@linux.intel.com>,
"Jiri Slaby" <jirislaby@kernel.org>, "Liang He" <windhl@126.com>
Subject: Re: [PATCH v3 2/2] serial: 8250: Apply FSL workarounds also without SERIAL_8250_CONSOLE
Date: Mon, 5 Jun 2023 17:01:08 +0300 [thread overview]
Message-ID: <ZH3qpAw9+dDzGVzf@smile.fi.intel.com> (raw)
In-Reply-To: <f01b13f5-34c9-62fc-52fd-33e923e2a2ba@linux.intel.com>
On Mon, Jun 05, 2023 at 04:44:08PM +0300, Ilpo Järvinen wrote:
> On Mon, 5 Jun 2023, Uwe Kleine-König wrote:
> > On Mon, Jun 05, 2023 at 04:22:55PM +0300, Ilpo Järvinen wrote:
> > > On Mon, 5 Jun 2023, Uwe Kleine-König wrote:
> > > > The need to handle the FSL variant of 8250 in a special way is also
> > > > present without console support. So soften the dependency for
> > > > SERIAL_8250_FSL accordingly. Note that with the 8250 driver compiled as
> > > > a module, some devices still might not make use of the needed
> > > > workarounds. That affects the ports instantiated in
> > > > arch/powerpc/kernel/legacy_serial.c.
> > > >
> > > > This issue was identified by Dominik Andreas Schorpp.
> > > >
> > > > To cope for CONFIG_SERIAL_8250=m + CONFIG_SERIAL_8250_FSL=y, 8250_fsl.o
> > > > must be put in the same compilation unit as 8250_port.o because the
> > > > latter defines some functions needed in the former and so 8250_fsl.o
> > > > must not be built-in if 8250_port.o is available in a module.
> > > >
> > > > Acked-by: Ilpo Järvinen <ilpo.jarvinen@linux.intel.com>
> > > > Link: https://lore.kernel.org/r/20230531083230.2702181-1-u.kleine-koenig@pengutronix.de
> > > > Signed-off-by: Uwe Kleine-König <u.kleine-koenig@pengutronix.de>
> > > > ---
> > > > drivers/tty/serial/8250/Kconfig | 2 +-
> > > > drivers/tty/serial/8250/Makefile | 2 +-
> > > > 2 files changed, 2 insertions(+), 2 deletions(-)
> > > >
> > > > diff --git a/drivers/tty/serial/8250/Kconfig b/drivers/tty/serial/8250/Kconfig
> > > > index 5313aa31930f..10c09b19c871 100644
> > > > --- a/drivers/tty/serial/8250/Kconfig
> > > > +++ b/drivers/tty/serial/8250/Kconfig
> > > > @@ -378,7 +378,7 @@ config SERIAL_8250_BCM2835AUX
> > > >
> > > > config SERIAL_8250_FSL
> > > > bool "Freescale 16550 UART support" if COMPILE_TEST && !(PPC || ARM || ARM64)
> > > > - depends on SERIAL_8250_CONSOLE
> > > > + depends on SERIAL_8250
> > >
> > > Just one additional thought: After the adding the arch side
> > > workaround/hack, SERIAL_8250_FSL could become a tristate?
> >
> > I see no benefit for a module separate from 8250_base.ko. There are
> > dependencies in both directions between 8250_port.o and 8250_fsl.o[1].
> > So in my book a bool SERIAL_8250_FSL that modifies 8250_base.ko (with
> > SERIAL_8250=m) is fine.
> > [1] 8250_port.o uses fsl8250_handle_irq() from 8250_fsl.o
>
> Is that after some fix which isn't in tty-next? I see only these:
>
> $ git grep -l fsl8250_handle_irq
> arch/powerpc/kernel/legacy_serial.c
> drivers/tty/serial/8250/8250_fsl.c
> drivers/tty/serial/8250/8250_of.c
> include/linux/serial_8250.h
>
> No users of fsl8250_handle_irq in 8250_port.c.
> >, and 8250_fsl.o uses serial8250_modem_status from 8250_port.o.
I don't like 8250_base to be fattened by some stuff that has no
generic meaning. Can we avoid putting every quirk there?
--
With Best Regards,
Andy Shevchenko
next prev parent reply other threads:[~2023-06-05 14:02 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-06-05 13:08 [PATCH v3 0/2] serial: 8250: Apply FSL workarounds also without SERIAL_8250_CONSOLE Uwe Kleine-König
2023-06-05 13:08 ` Uwe Kleine-König
2023-06-05 13:08 ` [PATCH v3 1/2] powerpc/legacy_serial: Warn about 8250 devices operated without active FSL workarounds Uwe Kleine-König
2023-06-05 13:08 ` Uwe Kleine-König
2023-06-05 13:08 ` [PATCH v3 2/2] serial: 8250: Apply FSL workarounds also without SERIAL_8250_CONSOLE Uwe Kleine-König
2023-06-05 13:08 ` Uwe Kleine-König
2023-06-05 13:22 ` Ilpo Järvinen
2023-06-05 13:22 ` Ilpo Järvinen
2023-06-05 13:34 ` Uwe Kleine-König
2023-06-05 13:34 ` Uwe Kleine-König
2023-06-05 13:44 ` Ilpo Järvinen
2023-06-05 13:44 ` Ilpo Järvinen
2023-06-05 14:01 ` Andy Shevchenko [this message]
2023-06-05 14:01 ` Andy Shevchenko
2023-06-05 14:22 ` Uwe Kleine-König
2023-06-05 14:22 ` Uwe Kleine-König
2023-06-05 14:38 ` Ilpo Järvinen
2023-06-05 14:38 ` Ilpo Järvinen
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=ZH3qpAw9+dDzGVzf@smile.fi.intel.com \
--to=andriy.shevchenko@linux.intel.com \
--cc=christophe.leroy@csgroup.eu \
--cc=deller@gmx.de \
--cc=geert+renesas@glider.be \
--cc=gregkh@linuxfoundation.org \
--cc=ilpo.jarvinen@linux.intel.com \
--cc=jirislaby@kernel.org \
--cc=kernel@pengutronix.de \
--cc=kumaravel.thiagarajan@microchip.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-serial@vger.kernel.org \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=matthew.gerlach@linux.intel.com \
--cc=mpe@ellerman.id.au \
--cc=npiggin@gmail.com \
--cc=rdunlap@infradead.org \
--cc=robh@kernel.org \
--cc=tharunkumar.pasumarthi@microchip.com \
--cc=u.kleine-koenig@pengutronix.de \
--cc=windhl@126.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.