From: Sebastian Andrzej Siewior <bigeasy@linutronix.de>
To: John Ogness <john.ogness@linutronix.de>
Cc: "Chang, Junxiao" <junxiao.chang@intel.com>,
"tglx@linutronix.de" <tglx@linutronix.de>,
"rostedt@goodmis.org" <rostedt@goodmis.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"Li, Hao3" <hao3.li@intel.com>, "Li, Lili" <lili.li@intel.com>,
"Gao, Jianfeng" <jianfeng.gao@intel.com>,
"linux-rt-users@vger.kernel.org" <linux-rt-users@vger.kernel.org>
Subject: Re: RE: [PATCH] printk: nbcon: check uart port is nbcon or not in nbcon_release
Date: Wed, 17 Jan 2024 11:24:46 +0100 [thread overview]
Message-ID: <20240117102446.itexUYMc@linutronix.de> (raw)
In-Reply-To: <87y1cos2dv.fsf@jogness.linutronix.de>
On 2024-01-17 11:09:24 [+0106], John Ogness wrote:
> On 2024-01-17, "Chang, Junxiao" <junxiao.chang@intel.com> wrote:
> > There are several serial ports in one Intel ADL hardware, they are
> > enumerated as ttyS0, ttyS1, ttyS4, and so on. Multiple console options
> > might be appended to kernel command line. For example,
> > "console=ttyS0,115200n8 console=ttyS4,115200n8
> > console=ttyS5,115200n8".
> >
> > In this case, several uarts "cons" pointers are same.
>
> So I ask again. Please explain how this is possible.
I have here
| 00:03: ttyS0 at I/O 0x3f8 (irq = 4, base_baud = 115200) is a 16550A
| 00:04: ttyS1 at I/O 0x2f8 (irq = 3, base_baud = 115200) is a 16550A
and I have
| root 2315 0.0 0.0 5480 1792 ttyS0 Ss+ 11:19 0:00 /sbin/agetty -o -p -- \u --keep-baud 115200,57600,38400,9600 - vt220
| root 2502 0.1 0.0 5480 1792 ttyS1 Ss+ 11:20 0:00 /sbin/agetty -o -p -- \u --keep-baud 115200,57600,38400,9600 - vt220
and I can stop both of them without any trouble.
Can this be reproduced on an ordinary x86 hardware given they have more
than one UART (up to four).
Is any of this ADL hardware upstream?
> John
Sebastian
next prev parent reply other threads:[~2024-01-17 10:24 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-01-17 6:52 [PATCH] printk: nbcon: check uart port is nbcon or not in nbcon_release Junxiao Chang
2024-01-17 8:23 ` John Ogness
2024-01-17 8:45 ` Chang, Junxiao
2024-01-17 10:03 ` John Ogness
2024-01-17 10:24 ` Sebastian Andrzej Siewior [this message]
2024-01-17 13:08 ` Chang, Junxiao
2024-01-17 13:42 ` John Ogness
2024-01-23 3:05 ` Chang, Junxiao
2024-01-23 5:40 ` [PATCH 0/2] nbcon locking issue with v6.6.10-rt18 kernel Junxiao Chang
2024-01-23 5:40 ` [PATCH 1/2] printk: nbcon: move locked_port flag to struct uart_port Junxiao Chang
2024-01-24 9:47 ` John Ogness
2024-01-24 10:05 ` Sebastian Andrzej Siewior
2024-01-25 1:08 ` Chang, Junxiao
2024-01-25 13:35 ` Sebastian Andrzej Siewior
2024-01-25 23:20 ` Chang, Junxiao
2024-01-26 7:58 ` John Ogness
2024-01-26 16:39 ` Sebastian Andrzej Siewior
2024-01-23 5:40 ` [PATCH 2/2] printk: nbcon: check uart port is nbcon or not in nbcon_release Junxiao Chang
2024-01-24 9:57 ` John Ogness
2024-01-26 2:33 ` Chang, Junxiao
2024-01-24 9:40 ` [PATCH 0/2] nbcon locking issue with v6.6.10-rt18 kernel John Ogness
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=20240117102446.itexUYMc@linutronix.de \
--to=bigeasy@linutronix.de \
--cc=hao3.li@intel.com \
--cc=jianfeng.gao@intel.com \
--cc=john.ogness@linutronix.de \
--cc=junxiao.chang@intel.com \
--cc=lili.li@intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-rt-users@vger.kernel.org \
--cc=rostedt@goodmis.org \
--cc=tglx@linutronix.de \
/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;
as well as URLs for NNTP newsgroup(s).