From: Leo Yan <leo.yan@arm.com>
To: Breno Leitao <leitao@debian.org>
Cc: cov@codeaurora.org, rmk+kernel@armlinux.org.uk,
mark.rutland@arm.com, catalin.marinas@arm.com,
linux-serial@vger.kernel.org, rmikey@meta.com,
linux-arm-kernel@lists.infradead.org, usamaarif642@gmail.com,
linux-kernel@vger.kernel.org, paulmck@kernel.org
Subject: Re: arm64: csdlock at early boot due to slow serial (?)
Date: Thu, 3 Jul 2025 12:45:57 +0100 [thread overview]
Message-ID: <20250703114557.GD1039028@e132581.arm.com> (raw)
In-Reply-To: <aGZVP8A2a3VVQwzt@gmail.com>
On Thu, Jul 03, 2025 at 03:02:39AM -0700, Breno Leitao wrote:
[...]
> > In some cases, if normal world and secure world share the same UART
> > port, it can cause the UART state machine malfunction and long wait.
>
> I don't know how to check it for sure, but, looking at the serial
> console output, I don't see anything else using the UART. The only
> output I see on the console at that time is coming from linux kernel.
>
> Would you recommend any additional check?
I have no experience in the driver, I should avoid any noise. But two
things in my head for quick trying.
- First, you could try earlycon mode, e.g., add option in kernel
command line:
earlycon=pl011,mmio32,0xc280000
earlycon=pl011,0xc280000
This would be possible to give more printing logs. If earlycon works
well, then the issue might be caused by later init code (clock, or
UART driver itself).
- Try another UART port if this is possible.
Just curious, you mentioned you are working on the mainline kernel. If
you can confirm a workable kernel version, then this info can help to
rule out hardware issue and we can review the delta changes.
Thanks,
Leo
next prev parent reply other threads:[~2025-07-03 11:46 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-07-02 17:10 Breno Leitao
2025-07-02 17:20 ` Leo Yan
2025-07-03 10:02 ` Breno Leitao
2025-07-03 11:45 ` Leo Yan [this message]
2025-07-03 15:01 ` Breno Leitao
2025-07-03 16:17 ` Leo Yan
2025-07-03 10:28 ` Mark Rutland
2025-07-03 14:13 ` Breno Leitao
2025-07-03 16:31 ` Mark Rutland
2025-07-08 14:00 ` Breno Leitao
2025-07-09 14:23 ` Breno Leitao
2025-07-10 13:35 ` Leo Yan
2025-07-10 17:30 ` Breno Leitao
2025-07-11 9:50 ` Leo Yan
2025-07-11 10:45 ` Breno Leitao
2025-07-14 10:52 ` Leo Yan
2025-08-06 11:44 ` Nirmoy Das
2025-08-06 15:53 ` Breno Leitao
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=20250703114557.GD1039028@e132581.arm.com \
--to=leo.yan@arm.com \
--cc=catalin.marinas@arm.com \
--cc=cov@codeaurora.org \
--cc=leitao@debian.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-serial@vger.kernel.org \
--cc=mark.rutland@arm.com \
--cc=paulmck@kernel.org \
--cc=rmikey@meta.com \
--cc=rmk+kernel@armlinux.org.uk \
--cc=usamaarif642@gmail.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
all inboxes | Powered by JetHome®