From: Rajendra Nayak <rnayak@ti.com>
To: tony@atomide.com, linux-omap@vger.kernel.org
Cc: paul@pwsan.com, balbi@ti.com, mpfj-list@newflow.co.uk,
vaibhav.bedia@ti.com, khilman@linaro.org, sourav.poddar@ti.com,
linux-arm-kernel@lists.infradead.org, gregkh@linuxfoundation.org,
linux-serial@vger.kernel.org, grygorii.strashko@ti.com,
Rajendra Nayak <rnayak@ti.com>
Subject: [PATCH 0/4] OMAP2+: Fix boot hang with earlycon enabled
Date: Mon, 22 Jul 2013 15:31:13 +0530 [thread overview]
Message-ID: <1374487277-26099-1-git-send-email-rnayak@ti.com> (raw)
Boot on all OMAP2+ devices is broken with earlycon enabled
as discussed here [1]
There were 2 issues which were rootcaused
1. Issue caused due to hwmod doing a reset of console uart while
earlycon was using it (seen only on am335x devices)
2. omap serial causing a NULL context restore with context loss
count missing.
This patch set attempts to fix both the issues and is one of the
different approaches discussed [1] on how to fix these issues.
Boot tested on omap4 panda es with and without earlycon (DT boot)
Boot tested on am335x bone black with and without earlycon (DT boot)
Boot tested on OMAP3 beagle XM with and without earlycon (non-DT boot)
[1] http://www.mail-archive.com/linux-omap@vger.kernel.org/msg91662.html
Grygorii Strashko (1):
serial: omap: enable PM runtime only when its fully configured
Rajendra Nayak (3):
ARM: OMAP2+: hwmod: Fix a crash in _setup_reset() with DEBUG_LL
ARM: OMAP2+: Avoid idling memory controllers with no drivers
ARM: OMAP2+: Sync hwmod state with the pm_runtime and omap_device
state
arch/arm/mach-omap2/omap_device.c | 18 ++++++++
arch/arm/mach-omap2/omap_hwmod.h | 48 ++++++++++++++++++++
arch/arm/mach-omap2/omap_hwmod_2xxx_ipblock_data.c | 6 +--
arch/arm/mach-omap2/omap_hwmod_33xx_data.c | 2 +-
arch/arm/mach-omap2/omap_hwmod_3xxx_data.c | 9 ++--
arch/arm/mach-omap2/omap_hwmod_44xx_data.c | 5 +-
arch/arm/mach-omap2/omap_hwmod_54xx_data.c | 3 +-
arch/arm/mach-omap2/serial.c | 11 -----
drivers/tty/serial/omap-serial.c | 3 +-
9 files changed, 81 insertions(+), 24 deletions(-)
--
1.7.9.5
next reply other threads:[~2013-07-22 10:02 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-07-22 10:01 Rajendra Nayak [this message]
2013-07-22 10:01 ` [PATCH 1/4] ARM: OMAP2+: hwmod: Fix a crash in _setup_reset() with DEBUG_LL Rajendra Nayak
2013-07-22 10:01 ` [PATCH 2/4] serial: omap: enable PM runtime only when its fully configured Rajendra Nayak
2013-07-29 8:44 ` Paul Walmsley
2013-07-29 8:50 ` Rajendra Nayak
2013-07-30 5:16 ` Rajendra Nayak
2013-07-30 10:20 ` Paul Walmsley
2013-07-22 10:01 ` [PATCH 3/4] ARM: OMAP2+: Avoid idling memory controllers with no drivers Rajendra Nayak
2013-07-22 17:48 ` Paul Walmsley
2013-07-23 4:59 ` Rajendra Nayak
2013-07-22 10:01 ` [PATCH 4/4] ARM: OMAP2+: Sync hwmod state with the pm_runtime and omap_device state Rajendra Nayak
2013-08-05 15:43 ` Kevin Hilman
2013-07-22 14:52 ` [PATCH 0/4] OMAP2+: Fix boot hang with earlycon enabled Mark Jackson
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=1374487277-26099-1-git-send-email-rnayak@ti.com \
--to=rnayak@ti.com \
--cc=balbi@ti.com \
--cc=gregkh@linuxfoundation.org \
--cc=grygorii.strashko@ti.com \
--cc=khilman@linaro.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-omap@vger.kernel.org \
--cc=linux-serial@vger.kernel.org \
--cc=mpfj-list@newflow.co.uk \
--cc=paul@pwsan.com \
--cc=sourav.poddar@ti.com \
--cc=tony@atomide.com \
--cc=vaibhav.bedia@ti.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).