From: jeffy.chen@rock-chips.com (Jeffy Chen)
To: linux-arm-kernel@lists.infradead.org
Subject: [RFC PATCH 0/5] earlycon hang under some conditions
Date: Tue, 18 Jul 2017 12:29:58 +0800 [thread overview]
Message-ID: <1500352203-21513-1-git-send-email-jeffy.chen@rock-chips.com> (raw)
I was testing earlycon with 8250 dw serial console. And it hangs in
these cases:
1/ kernel hang when calling early write function after free_initmem:
a) the earlycon not disabled after the init code(due to keep_bootcon or
not specify a real console to switch to)
b) the early write func is marked as __init, for example 8250_early.
2/ kernel hang when calling early write function after disable unused
clks/pm domain:
a) the earlycon not disabled after the init code
b) the disable unused clks/pm domain kill the requiered clks/pm
domain, since they are not referenced by the earlycon.
3/ kernel hang when calling early write function after the serial
console driver runtime suspended:
a) the earlycon not disabled after the init code
b) the serial console driver's runtime suspend kills the requiered
clks/pm domain, since they are not referenced by the earlycon.
This serial fix 1/ case only.
Jeffy Chen (5):
serial: arc: Remove __init marking from early write
serial: omap: Remove __init marking from early write
serial: xuartps: Remove __init marking from early write
serial: 8250_ingenic: Remove __init marking from early write
serial: 8250_early: Remove __init marking from early write
drivers/tty/serial/8250/8250_early.c | 8 ++++----
drivers/tty/serial/8250/8250_ingenic.c | 8 ++++----
drivers/tty/serial/arc_uart.c | 4 ++--
drivers/tty/serial/omap-serial.c | 13 ++++++-------
drivers/tty/serial/xilinx_uartps.c | 2 +-
5 files changed, 17 insertions(+), 18 deletions(-)
--
2.1.4
next reply other threads:[~2017-07-18 4:29 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-07-18 4:29 Jeffy Chen [this message]
2017-07-18 4:30 ` [RFC PATCH 3/5] serial: xuartps: Remove __init marking from early write Jeffy Chen
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=1500352203-21513-1-git-send-email-jeffy.chen@rock-chips.com \
--to=jeffy.chen@rock-chips.com \
--cc=linux-arm-kernel@lists.infradead.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;
as well as URLs for NNTP newsgroup(s).