From: rnayak@ti.com (Rajendra Nayak)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 0/2] Fix omap serial early crash during hwmod _setup()
Date: Fri, 12 Jul 2013 13:03:13 +0530 [thread overview]
Message-ID: <51DFB139.8060408@ti.com> (raw)
In-Reply-To: <20130712072244.GB7656@atomide.com>
On Friday 12 July 2013 12:52 PM, Tony Lindgren wrote:
> * Rajendra Nayak <rnayak@ti.com> [130711 03:59]:
>> This series should fix the issue with the early serial crash seen
>> during hwmod _setup() as reported by [1]
>>
>> The issue was reported on a am33xx device and was not seen on omap4
>> or omap5 devices as the hwmod data for both omap4 and omap5 had
>> statically defined HWMOD_INIT_NO_IDLE and HWMOD_INIT_NO_RESET for
>> uart3 which happens to be the debug console used on omap4 panda and
>> omap5 uevm boards.
>
> The serial driver should be capable of setting this on it's own
> as it sets up the console.
These flags are used to avoid an early reset that hwmod does to all devices
on the SoC and is done much before serial driver is initialized.
>
> Regards,
>
> Tony
>
next prev parent reply other threads:[~2013-07-12 7:33 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-07-11 10:53 [PATCH 0/2] Fix omap serial early crash during hwmod _setup() Rajendra Nayak
2013-07-11 10:53 ` [PATCH 1/2] Revert "ARM: OMAP2+: Fix serial init for device tree based booting" Rajendra Nayak
2013-07-12 7:20 ` Tony Lindgren
2013-07-12 7:31 ` Rajendra Nayak
2013-07-12 8:03 ` Tony Lindgren
2013-07-12 8:59 ` Rajendra Nayak
2013-07-12 9:18 ` Tony Lindgren
2013-07-12 9:22 ` Rajendra Nayak
2013-07-12 9:46 ` Tony Lindgren
2013-07-12 12:12 ` Rajendra Nayak
2013-07-12 12:33 ` Tony Lindgren
2013-07-11 10:53 ` [PATCH 2/2] ARM: OMAP4+: Get rid of the HWMOD_INIT_NO_IDLE and HWMOD_INIT_NO_RESET flags for uart Rajendra Nayak
2013-07-11 13:28 ` [PATCH 0/2] Fix omap serial early crash during hwmod _setup() Felipe Balbi
2013-07-12 7:22 ` Tony Lindgren
2013-07-12 7:33 ` Rajendra Nayak [this message]
2013-07-12 8:03 ` Tony Lindgren
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=51DFB139.8060408@ti.com \
--to=rnayak@ti.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).