public inbox for linux-arm-kernel@lists.infradead.org 
 help / color / mirror / Atom feed
From: tony@atomide•com (Tony Lindgren)
To: linux-arm-kernel@lists•infradead.org
Subject: [PATCH] ARM: OMAP4: Fix the boot regression with CPU_IDLE enabled
Date: Wed, 14 May 2014 08:22:07 -0700	[thread overview]
Message-ID: <20140514152206.GB18463@atomide.com> (raw)
In-Reply-To: <1399991966-14582-1-git-send-email-santosh.shilimkar@ti.com>

* Santosh Shilimkar <santosh.shilimkar@ti•com> [140513 07:40]:
> On OMAP4 panda board, there have been several bug reports about boot
> hang and lock-ups with CPU_IDLE enabled. The root cause of the issue
> is missing interrupts while in idle state. Commit cb7094e8 {cpuidle / omap4 :
> use CPUIDLE_FLAG_TIMER_STOP flag} moved the broadcast notifiers to common
> code for right reasons but on OMAP4 which suffers from a nasty ROM code
> bug with GIC, commit ff999b8a {ARM: OMAP4460: Workaround for ROM bug ..},
> we loose interrupts which leads to issues like lock-up, hangs etc.
> 
> Patch reverts commit cb7094 {cpuidle / omap4 : use CPUIDLE_FLAG_TIMER_STOP
> flag} to avoid the issue. With this change, OMAP4 panda boards, the mentioned
> issues are getting fixed. We no longer loose interrupts which was the cause
> of the regression.

Thanks for figuring this regression out. Applying into fixes with Cc
stable.

Regards,

Tony

  reply	other threads:[~2014-05-14 15:22 UTC|newest]

Thread overview: 32+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-05-13 14:39 [PATCH] ARM: OMAP4: Fix the boot regression with CPU_IDLE enabled Santosh Shilimkar
2014-05-14 15:22 ` Tony Lindgren [this message]
2014-05-14 19:44 ` Daniel Lezcano
2014-05-14 19:50   ` Santosh Shilimkar
2014-05-14 20:02     ` Daniel Lezcano
2014-05-14 20:56       ` Tony Lindgren
2014-05-14 23:31         ` Tony Lindgren
2014-05-16  0:13           ` Tony Lindgren
2014-05-16  0:40             ` Tony Lindgren
2014-05-14 21:18       ` Santosh Shilimkar
2014-05-15 17:03         ` Santosh Shilimkar
2014-05-15 17:50           ` Daniel Lezcano
2014-05-15 17:54             ` Santosh Shilimkar
2014-05-15 18:29               ` Santosh Shilimkar
2014-05-16  0:33                 ` Alex Shi
2014-05-16 13:43                 ` Santosh Shilimkar
2014-05-16 21:29                   ` Tony Lindgren
2014-05-19 16:45                     ` Daniel Lezcano
2014-05-19 17:23                       ` Tony Lindgren
2014-05-19 17:34                         ` Santosh Shilimkar
2014-05-19 17:51                           ` Tony Lindgren
2014-05-19 18:06                             ` Daniel Lezcano
2014-05-19 19:36                               ` Tony Lindgren
2014-05-19 19:45                                 ` Daniel Lezcano
2014-05-19 21:18                                   ` Tobias Jakobi
2014-05-19 22:42                                     ` Tony Lindgren
2014-05-23 14:44                                     ` Tony Lindgren
2014-05-23 18:32                                       ` Tony Lindgren
     [not found]                                         ` <CAKnoXLxj42veWCbRjX98iT3FNAb92J4yR+UAL716JFSOb=pcrQ@mail.gmail.com>
2014-05-27 20:34                                           ` Tony Lindgren
2014-05-27 21:03                                             ` Santosh Shilimkar
2014-05-27 21:06                                               ` Daniel Lezcano
2014-05-19 20:00                                 ` Santosh Shilimkar

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=20140514152206.GB18463@atomide.com \
    --to=tony@atomide$(echo .)com \
    --cc=linux-arm-kernel@lists$(echo .)infradead.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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