All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Mark A. Greer" <mgreer@animalcreek.com>
To: Paul Walmsley <paul@pwsan.com>
Cc: Joe Woodward <jw@terrafix.co.uk>, Kevin Hilman <khilman@ti.com>,
	linux-omap@vger.kernel.org
Subject: Re: PM/RTC 3.5-rc5: System suspends fails when not built with RTC?
Date: Mon, 16 Jul 2012 17:40:10 -0700	[thread overview]
Message-ID: <20120717004010.GA6612@animalcreek.com> (raw)
In-Reply-To: <alpine.DEB.2.00.1207131217590.25585@utopia.booyaka.com>

On Fri, Jul 13, 2012 at 12:26:13PM -0600, Paul Walmsley wrote:
> + Mark
> 
> On Fri, 13 Jul 2012, Joe Woodward wrote:
> 
> > Thanks Paul,
> > 
> > That patch does indeed seem to fix all my problems!
> > 
> > With it I can now suspend, and all power domains hit the target states.
> 
> OK, great.  That patch is basically a revert of 
> a819c4f16d5a2708c11e708fd59a96565c5384a8 ("ARM: OMAP3: PM: Only access IVA 
> if one exists").  Sounds like we need to discriminate between the case 
> where the IVA2 is present but has been efused off in some way (as in the 
> AM3703) vs. the case where the IVA2 is not present at all (as in the 
> AM35xx).
> 
> Mark, do you have the time to take a look at this?  Maybe omap3_has_iva() 
> needs to be split into omap3_has_iva() and omap3_has_usable_iva().  Or 
> maybe you can come up with a better idea...

Hi Joe.

I'm finally getting around to this...  Unfortunately, I don't have the
hardware to test it so I can't tell exactly what code needs to run to make
it work again.   Would you mind identifying the pieces of code need to run
for it to work?  omap3_has_iva() shows up in just a few places.

Thanks,

Mark

  parent reply	other threads:[~2012-07-17  0:40 UTC|newest]

Thread overview: 31+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-07-12  8:15 PM/RTC 3.5-rc5: System suspends fails when not built with RTC? Joe Woodward
2012-07-12 10:59 ` Paul Walmsley
2012-07-12 14:43   ` Joe Woodward
2012-07-12 19:35     ` Paul Walmsley
2012-07-13 10:57       ` Joe Woodward
2012-07-13 18:26         ` Paul Walmsley
2012-07-13 21:28           ` Mark A. Greer
2012-07-17  0:40           ` Mark A. Greer [this message]
2012-07-17  0:43             ` Paul Walmsley
2012-07-17 10:08               ` Joe Woodward
2012-07-17 19:28                 ` Paul Walmsley
2012-07-18  2:20                   ` Mark A. Greer
2012-07-18 10:06                     ` Joe Woodward
2012-07-18 17:26                       ` Mark A. Greer
2012-07-26 21:09                         ` Juha Kuikka
2012-07-26 23:06                           ` Mark A. Greer
2012-07-26 23:08                             ` Mark A. Greer
2012-07-12 18:25 ` Kevin Hilman
  -- strict thread matches above, loose matches on Subject: below --
2012-07-05 15:03 Joe Woodward
2012-07-10 23:58 ` Kevin Hilman
2012-07-11 10:50   ` Joe Woodward
2012-07-11 15:31     ` T Krishnamoorthy, Balaji
2012-07-11 17:07     ` Kevin Hilman
2012-07-11 17:51       ` Mark A. Greer
2012-07-11 18:38         ` Kevin Hilman
2012-07-11 18:48       ` Kevin Hilman
2012-07-11 20:52       ` Omar Ramirez Luna
2012-07-11 21:29         ` Kevin Hilman
2012-07-12  5:56           ` Shubhrajyoti
2012-07-13  6:34           ` Tony Lindgren
2012-07-16 17:18             ` Kevin Hilman

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=20120717004010.GA6612@animalcreek.com \
    --to=mgreer@animalcreek.com \
    --cc=jw@terrafix.co.uk \
    --cc=khilman@ti.com \
    --cc=linux-omap@vger.kernel.org \
    --cc=paul@pwsan.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.