From: John Ogness <john.ogness@linutronix.de>
To: Ryo Takakura <ryotkkr98@gmail.com>
Cc: christophe.leroy@csgroup.eu, hbathini@linux.ibm.com,
leobras.c@gmail.com, linux-kernel@vger.kernel.org,
linuxppc-dev@lists.ozlabs.org, maddy@linux.ibm.com,
mpe@ellerman.id.au, naveen@kernel.org, npiggin@gmail.com,
pmladek@suse.com, ryotkkr98@gmail.com, sourabhjain@linux.ibm.com
Subject: Re: [PATCH] powerpc/crash: Allow direct printing on kexec
Date: Mon, 21 Oct 2024 14:33:46 +0206 [thread overview]
Message-ID: <847ca1fxod.fsf@jogness.linutronix.de> (raw)
In-Reply-To: <20241021121159.331940-1-ryotkkr98@gmail.com>
On 2024-10-21, Ryo Takakura <ryotkkr98@gmail.com> wrote:
>> Rather than removing the deferring, it would be better to convert the
>> console you are using to the new NBCON API. Then it would be able to
>> print direct and safe during panic. (printk_deferred does not affect
>> NBCON consoles.) What console driver are you using that you want to
>> see the messages on?
>
> I was working on qemu ppc64 this time but I am usually working on
> Raspberry Pi 4 (mostly for fun and study) which uses either of
> bcm2835-aux-uart or amba-pl011. It would be really nice to see them
> working as nbcon!
> I am thinking of taking a look at [0] but If there were any other
> references, I would really like to look into as well.
>
> [0] https://lore.kernel.org/lkml/87wn3zsz5x.fsf@jogness.linutronix.de/
The lastest version of the series is here [1]. The series is still
undergoing revisions, however the changes are 8250-specific. The API for
nbcon consoles is already available since 6.12-rc1. You are certainly
welcome to try to convert one of those Raspi 4 drivers to the nbcon
interface. I would be happy to review it.
John Ogness
[1] https://lore.kernel.org/lkml/20240913140538.221708-1-john.ogness@linutronix.de
next prev parent reply other threads:[~2024-10-21 12:28 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-10-20 7:17 [PATCH] powerpc/crash: Allow direct printing on kexec Ryo Takakura
2024-10-20 20:41 ` John Ogness
2024-10-21 12:11 ` Ryo Takakura
2024-10-21 12:27 ` John Ogness [this message]
2024-10-21 14:44 ` Ryo Takakura
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=847ca1fxod.fsf@jogness.linutronix.de \
--to=john.ogness@linutronix.de \
--cc=christophe.leroy@csgroup.eu \
--cc=hbathini@linux.ibm.com \
--cc=leobras.c@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=maddy@linux.ibm.com \
--cc=mpe@ellerman.id.au \
--cc=naveen@kernel.org \
--cc=npiggin@gmail.com \
--cc=pmladek@suse.com \
--cc=ryotkkr98@gmail.com \
--cc=sourabhjain@linux.ibm.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;
as well as URLs for NNTP newsgroup(s).