mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: "Arnd Bergmann" <arnd@arndb.de>
To: "Peter Maydell" <peter.maydell@linaro.org>
Cc: linux-serial@vger.kernel.org, linux-kernel@vger.kernel.org,
	"Greg Kroah-Hartman" <gregkh@linuxfoundation.org>,
	"Jiri Slaby" <jirislaby@kernel.org>,
	"Thomas Gleixner" <tglx@kernel.org>,
	"Russell King" <linux@armlinux.org.uk>,
	"Miaoqian Lin" <linmq006@gmail.com>
Subject: Re: [PATCH] serial: amba-pl011: Enable UART in earlycon setup
Date: Tue, 10 Feb 2026 15:10:45 +0100	[thread overview]
Message-ID: <7a80b31d-f909-48fc-9856-37d698b448fb@app.fastmail.com> (raw)
In-Reply-To: <CAFEAcA_nUiQ9ROXBq6Q=3G1wzLtBHDEKSB+4OyYWkt-tR_ZTJA@mail.gmail.com>

On Tue, Feb 10, 2026, at 14:49, Peter Maydell wrote:
> On Tue, 10 Feb 2026 at 13:23, Arnd Bergmann <arnd@arndb.de> wrote:
>> On Tue, Feb 10, 2026, at 13:50, Peter Maydell wrote:
>>
>> One more question: what is the symptom without this patch with
>> qemu? You mentioned on IRC that qemu may warn about attempting
>> to write to the uart when it is disabled. Would we still get
>> the correct early console output before the uart is enabled?
>
> The symptom is that if you run QEMU with '-d guest_errors' to ask
> it to log things the guest does that it thinks are bugs in the
> guest, then you get a lot of "PL011 data written to disabled UART"
> warnings. The guest still boots fine, and assuming you directed
> the logging to a file rather than stdout you see the guest output.

Ok, thanks for the explanation! I still wonder whether we will
want a stable backport of the patch. It sounds like it won't
be needed for qemu (because most people won't see the harmless
warning especially after your patch) or most real hardware
(because the bootloader will have initialized the console),
but there may still be corner cases that need it.

      Arnd

      reply	other threads:[~2026-02-10 14:11 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-02-10 12:50 Peter Maydell
2026-02-10 13:22 ` Arnd Bergmann
2026-02-10 13:49   ` Peter Maydell
2026-02-10 14:10     ` Arnd Bergmann [this message]

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=7a80b31d-f909-48fc-9856-37d698b448fb@app.fastmail.com \
    --to=arnd@arndb.de \
    --cc=gregkh@linuxfoundation.org \
    --cc=jirislaby@kernel.org \
    --cc=linmq006@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-serial@vger.kernel.org \
    --cc=linux@armlinux.org.uk \
    --cc=peter.maydell@linaro.org \
    --cc=tglx@kernel.org \
    /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

all inboxes | Powered by JetHome®