public inbox for linux-omap@vger.kernel.org
 help / color / mirror / Atom feed
From: Tero Kristo <t-kristo@ti.com>
To: Rajendra Nayak <rnayak@ti.com>
Cc: Omar Ramirez Luna <omar.luna@linaro.org>,
	Kevin Hilman <khilman@ti.com>, Tony Lindgren <tony@atomide.com>,
	loml <linux-omap@vger.kernel.org>
Subject: Re: suspend broken on 3.5-rc1?
Date: Thu, 12 Jul 2012 11:31:11 +0300	[thread overview]
Message-ID: <1342081871.4672.32.camel@sokoban> (raw)
In-Reply-To: <4FFE6049.7040908@ti.com>

On Thu, 2012-07-12 at 10:57 +0530, Rajendra Nayak wrote:
> On Thursday 12 July 2012 05:28 AM, Omar Ramirez Luna wrote:
> > I suspect this might be specific to 4460 as Rajendra reported it was
> > working for him on 4430 but not on 4460, I haven't tried 4430 but let
> > me see if I can find one.
> 
> Yes, this is an issue specific to 4460. The patch 'ARM: OMAP4460:
> Workaround for ROM bug because of CA9 r2pX GIC control register change'
> from Tero's Core retention series [1] fixes it. Unfortunately the patch
> does not apply on it own and has dependencies with other patches in the
> series.
> 
> [1] http://comments.gmane.org/gmane.linux.ports.arm.omap/78399

The dependencies are by design, I am trying to force maintainers to get
that stuff in. ;)

-Tero



  reply	other threads:[~2012-07-12  8:31 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-06-08 10:35 suspend broken on 3.5-rc1? Rajendra Nayak
2012-06-08 10:56 ` Tony Lindgren
2012-06-08 12:25   ` Rajendra Nayak
2012-06-08 13:05     ` Tero Kristo
2012-06-08 13:16       ` Rajendra Nayak
2012-06-12 12:01         ` Rajendra Nayak
2012-07-11 21:06           ` Omar Ramirez Luna
2012-07-11 21:42             ` Kevin Hilman
2012-07-11 23:58               ` Omar Ramirez Luna
2012-07-12  5:27                 ` Rajendra Nayak
2012-07-12  8:31                   ` Tero Kristo [this message]
2012-07-12 19:49                   ` Omar Ramirez Luna

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=1342081871.4672.32.camel@sokoban \
    --to=t-kristo@ti.com \
    --cc=khilman@ti.com \
    --cc=linux-omap@vger.kernel.org \
    --cc=omar.luna@linaro.org \
    --cc=rnayak@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox