All of lore.kernel.org
 help / color / mirror / Atom feed
From: Paul Walmsley <paul@pwsan.com>
To: Tero Kristo <t-kristo@ti.com>
Cc: linux-omap@vger.kernel.org, khilman@ti.com,
	linux-arm-kernel@lists.infradead.org,
	Colin Cross <ccross@android.com>, Sebastien Jan <s-jan@ti.com>,
	tony@atomide.com
Subject: Re: [PATCHv9 6/8] ARM: OMAP4: retrigger localtimers after re-enabling gic
Date: Sat, 27 Oct 2012 02:51:16 +0000 (UTC)	[thread overview]
Message-ID: <alpine.DEB.2.00.1210270250140.27071@utopia.booyaka.com> (raw)
In-Reply-To: <1350552010-28760-7-git-send-email-t-kristo@ti.com>

Hi

On Thu, 18 Oct 2012, Tero Kristo wrote:

> From: Colin Cross <ccross@android.com>
> 
> 'Workaround for ROM bug because of CA9 r2pX gic control'
> register change disables the gic distributor while the secondary
> cpu is being booted.  If a localtimer interrupt on the primary cpu
> occurs when the distributor is turned off, the interrupt is lost,
> and the localtimer never fires again.

Looks like this one should go in separately via Tony.


- Paul

WARNING: multiple messages have this Message-ID (diff)
From: paul@pwsan.com (Paul Walmsley)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCHv9 6/8] ARM: OMAP4: retrigger localtimers after re-enabling gic
Date: Sat, 27 Oct 2012 02:51:16 +0000 (UTC)	[thread overview]
Message-ID: <alpine.DEB.2.00.1210270250140.27071@utopia.booyaka.com> (raw)
In-Reply-To: <1350552010-28760-7-git-send-email-t-kristo@ti.com>

Hi

On Thu, 18 Oct 2012, Tero Kristo wrote:

> From: Colin Cross <ccross@android.com>
> 
> 'Workaround for ROM bug because of CA9 r2pX gic control'
> register change disables the gic distributor while the secondary
> cpu is being booted.  If a localtimer interrupt on the primary cpu
> occurs when the distributor is turned off, the interrupt is lost,
> and the localtimer never fires again.

Looks like this one should go in separately via Tony.


- Paul

  reply	other threads:[~2012-10-27  2:51 UTC|newest]

Thread overview: 68+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-10-18  9:20 [PATCHv9 0/8] ARM: OMAP4: core retention support Tero Kristo
2012-10-18  9:20 ` Tero Kristo
2012-10-18  9:20 ` [PATCHv9 1/8] ARM: OMAP: hwmod: Add support for per hwmod/module context lost count Tero Kristo
2012-10-18  9:20   ` Tero Kristo
2012-10-27  3:00   ` Paul Walmsley
2012-10-27  3:00     ` Paul Walmsley
2012-11-21 23:05   ` Paul Walmsley
2012-11-21 23:05     ` Paul Walmsley
2012-10-18  9:20 ` [PATCHv9 2/8] ARM: OMAP4: PM: add errata support Tero Kristo
2012-10-18  9:20   ` Tero Kristo
2012-11-05 22:36   ` Kevin Hilman
2012-11-05 22:36     ` Kevin Hilman
2012-11-06 21:52     ` Kevin Hilman
2012-11-06 21:52       ` Kevin Hilman
2012-11-07 10:11       ` Tero Kristo
2012-11-07 10:11         ` Tero Kristo
2012-10-18  9:20 ` [PATCHv9 3/8] ARM: OMAP4460: Workaround for ROM bug because of CA9 r2pX GIC control register change Tero Kristo
2012-10-18  9:20   ` Tero Kristo
2012-10-18  9:20 ` [PATCHv9 4/8] ARM: OMAP4: suspend: Program all domains to retention Tero Kristo
2012-10-18  9:20   ` Tero Kristo
2012-10-18  9:20 ` [PATCHv9 5/8] ARM: OMAP4: PM: put all domains to OSWR during suspend Tero Kristo
2012-10-18  9:20   ` Tero Kristo
2012-10-18  9:20 ` [PATCHv9 6/8] ARM: OMAP4: retrigger localtimers after re-enabling gic Tero Kristo
2012-10-18  9:20   ` Tero Kristo
2012-10-27  2:51   ` Paul Walmsley [this message]
2012-10-27  2:51     ` Paul Walmsley
2012-11-05 22:25   ` Kevin Hilman
2012-11-05 22:25     ` Kevin Hilman
2012-11-06  9:15     ` Tero Kristo
2012-11-06  9:15       ` Tero Kristo
2012-10-18  9:20 ` [PATCHv9 7/8] ARM: OMAP: PM: update target fpwrst to what pwrdm can reach Tero Kristo
2012-10-18  9:20   ` Tero Kristo
2012-10-18  9:20 ` [PATCHv9 8/8] ARM: OMAP4: USB: power down MUSB PHY if not used Tero Kristo
2012-10-18  9:20   ` Tero Kristo
2012-10-18 10:33   ` Felipe Balbi
2012-10-18 10:33     ` Felipe Balbi
2012-10-18 12:18     ` Tero Kristo
2012-10-18 12:18       ` Tero Kristo
2012-10-18 13:53       ` Felipe Balbi
2012-10-18 13:53         ` Felipe Balbi
2012-10-18 14:39         ` Tero Kristo
2012-10-18 14:39           ` Tero Kristo
2012-10-18 14:41           ` Felipe Balbi
2012-10-18 14:41             ` Felipe Balbi
2012-10-22  8:54           ` kishon
2012-10-22  8:54             ` kishon
2012-10-22  9:07             ` Felipe Balbi
2012-10-22  9:07               ` Felipe Balbi
2012-10-22  9:25               ` kishon
2012-10-22  9:25                 ` kishon
2012-10-27  2:52   ` Paul Walmsley
2012-10-27  2:52     ` Paul Walmsley
2012-10-27  3:02 ` [PATCHv9 0/8] ARM: OMAP4: core retention support Paul Walmsley
2012-10-27  3:02   ` Paul Walmsley
2012-11-05 22:23 ` Kevin Hilman
2012-11-05 22:23   ` Kevin Hilman
2012-11-06  9:18   ` Tero Kristo
2012-11-06  9:18     ` Tero Kristo
2012-11-06 21:19     ` Kevin Hilman
2012-11-06 21:19       ` Kevin Hilman
2012-11-07 10:17       ` Tero Kristo
2012-11-07 10:17         ` Tero Kristo
2012-11-12 14:41       ` Tero Kristo
2012-11-12 14:41         ` Tero Kristo
2012-11-13 19:18         ` Kevin Hilman
2012-11-13 19:18           ` Kevin Hilman
2012-11-07 18:35   ` Paul Walmsley
2012-11-07 18:35     ` Paul Walmsley

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=alpine.DEB.2.00.1210270250140.27071@utopia.booyaka.com \
    --to=paul@pwsan.com \
    --cc=ccross@android.com \
    --cc=khilman@ti.com \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-omap@vger.kernel.org \
    --cc=s-jan@ti.com \
    --cc=t-kristo@ti.com \
    --cc=tony@atomide.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.