From: Tony Lindgren <tony@atomide.com>
To: Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
Jiri Slaby <jirislaby@kernel.org>, Petr Mladek <pmladek@suse.com>,
Steven Rostedt <rostedt@goodmis.org>,
John Ogness <john.ogness@linutronix.de>,
Sergey Senozhatsky <senozhatsky@chromium.org>
Cc: "David S . Miller" <davem@davemloft.net>,
"Andy Shevchenko" <andriy.shevchenko@intel.com>,
"Dhruva Gole" <d-gole@ti.com>,
"Ilpo Järvinen" <ilpo.jarvinen@linux.intel.com>,
"Johan Hovold" <johan@kernel.org>,
"Sebastian Andrzej Siewior" <bigeasy@linutronix.de>,
"Vignesh Raghavendra" <vigneshr@ti.com>,
linux-kernel@vger.kernel.org, linux-serial@vger.kernel.org
Subject: [PATCH v4 3/4] serial: core: Handle serial console options
Date: Tue, 5 Dec 2023 09:32:35 +0200 [thread overview]
Message-ID: <20231205073255.20562-4-tony@atomide.com> (raw)
In-Reply-To: <20231205073255.20562-1-tony@atomide.com>
In order to start moving the serial console quirks out of console_setup(),
let's add parsing for the quirks to the serial core layer. We can use
add_preferred_console_match() to handle the quirks.
At this point we can't drop the quirks from console_setup() because it
would confuse add_preferred_console(). And try_enable_default_console()
would get called before try_enable_preferred_console().
Note that eventually we may want to set up driver specific console quirk
handling for the serial port device drivers to use. But we need to figure
out which driver(s) need to call the quirk. So for now, we just handle the
sparc quirk directly.
Signed-off-by: Tony Lindgren <tony@atomide.com>
---
drivers/tty/serial/serial_base_bus.c | 67 ++++++++++++++++++++++++++++
1 file changed, 67 insertions(+)
diff --git a/drivers/tty/serial/serial_base_bus.c b/drivers/tty/serial/serial_base_bus.c
--- a/drivers/tty/serial/serial_base_bus.c
+++ b/drivers/tty/serial/serial_base_bus.c
@@ -207,6 +207,43 @@ void serial_base_port_device_remove(struct serial_port_device *port_dev)
#ifdef CONFIG_SERIAL_CORE_CONSOLE
+#ifdef __sparc__
+
+/* Handle Sparc ttya and ttyb options as done in console_setup() */
+static int serial_base_add_sparc_console(struct uart_driver *drv,
+ struct uart_port *port)
+{
+ const char *name = NULL;
+ int ret;
+
+ switch (port->line) {
+ case 0:
+ name = "ttya";
+ break;
+ case 1:
+ name = "ttyb";
+ break;
+ default:
+ return 0;
+ }
+
+ ret = add_preferred_console_match(name, drv->dev_name, port->line);
+ if (ret && ret != -ENOENT)
+ return ret;
+
+ return 0;
+}
+
+#else
+
+static inline int serial_base_add_sparc_console(struct uart_driver *drv,
+ struct uart_port *port)
+{
+ return 0;
+}
+
+#endif
+
static int serial_base_add_one_prefcon(const char *match, const char *dev_name,
int port_id)
{
@@ -240,12 +277,42 @@ int serial_base_add_preferred_console(struct uart_driver *drv,
struct uart_port *port)
{
const char *port_match __free(kfree);
+ const char *char_match __free(kfree) = NULL;
+ const char *nmbr_match __free(kfree) = NULL;
+ int ret;
port_match = kasprintf(GFP_KERNEL, "%s:%i.%i", dev_name(port->dev),
port->ctrl_id, port->port_id);
if (!port_match)
return -ENOMEM;
+ char_match = kasprintf(GFP_KERNEL, "%s%i", drv->dev_name, port->line);
+ if (!char_match)
+ return -ENOMEM;
+
+ /* Handle ttyS specific options */
+ if (!strncmp(drv->dev_name, "ttyS", 4)) {
+ /* No name, just a number */
+ nmbr_match = kasprintf(GFP_KERNEL, "%i", port->line);
+ if (!nmbr_match)
+ return -ENODEV;
+
+ ret = serial_base_add_one_prefcon(nmbr_match, drv->dev_name,
+ port->line);
+ if (ret)
+ return ret;
+
+ /* Sparc ttya and ttyb */
+ ret = serial_base_add_sparc_console(drv, port);
+ if (ret)
+ return ret;
+ }
+
+ /* Handle the traditional character device name style console=ttyS0 */
+ ret = serial_base_add_one_prefcon(char_match, drv->dev_name, port->line);
+ if (ret)
+ return ret;
+
/* Translate a hardware addressing style console=DEVNAME:0.0 */
return serial_base_add_one_prefcon(port_match, drv->dev_name, port->line);
}
--
2.43.0
next prev parent reply other threads:[~2023-12-05 7:35 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-12-05 7:32 [PATCH v4 0/4] Add support for DEVNAME:0.0 style hardware based addressing Tony Lindgren
2023-12-05 7:32 ` [PATCH v4 1/4] printk: Save console options for add_preferred_console_match() Tony Lindgren
2023-12-05 7:32 ` [PATCH v4 2/4] serial: core: Add support for DEVNAME:0.0 style naming for kernel console Tony Lindgren
2023-12-05 7:32 ` Tony Lindgren [this message]
2023-12-05 16:06 ` [PATCH v4 3/4] serial: core: Handle serial console options Andy Shevchenko
2023-12-05 7:32 ` [PATCH v4 4/4] serial: 8250: Add preferred console in serial8250_isa_init_ports() Tony Lindgren
2023-12-05 16:08 ` Andy Shevchenko
2023-12-05 16:10 ` Andy Shevchenko
2023-12-07 7:23 ` Tony Lindgren
2023-12-05 18:07 ` kernel test robot
2023-12-05 18:29 ` kernel test robot
2023-12-05 7:45 ` [PATCH v4 0/4] Add support for DEVNAME:0.0 style hardware based addressing Tony Lindgren
2023-12-08 8:28 ` Tony Lindgren
2023-12-18 6:38 ` Tony Lindgren
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=20231205073255.20562-4-tony@atomide.com \
--to=tony@atomide.com \
--cc=andriy.shevchenko@intel.com \
--cc=bigeasy@linutronix.de \
--cc=d-gole@ti.com \
--cc=davem@davemloft.net \
--cc=gregkh@linuxfoundation.org \
--cc=ilpo.jarvinen@linux.intel.com \
--cc=jirislaby@kernel.org \
--cc=johan@kernel.org \
--cc=john.ogness@linutronix.de \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-serial@vger.kernel.org \
--cc=pmladek@suse.com \
--cc=rostedt@goodmis.org \
--cc=senozhatsky@chromium.org \
--cc=vigneshr@ti.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