All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Ramirez Luna, Omar" <omar.ramirez@ti.com>
To: venki kaps <venkiece2005@gmail.com>,
	"Kanigeri, Hari" <h-kanigeri2@ti.com>,
	"ameya.palande@nokia.com" <ameya.palande@nokia.com>,
	"Guzman Lugo, Fernando" <fernando.lugo@ti.com>,
	Hebb
Subject: RE: OMAP3 DSP MMU fault + off mode issue
Date: Wed, 15 Sep 2010 10:39:49 -0500	[thread overview]
Message-ID: <27F9C60D11D683428E133F85D2BB4A530450C3265B__3346.63200560517$1284565240$gmane$org@dlee03.ent.ti.com> (raw)
In-Reply-To: <AANLkTimO1UK+WA8Mc3Myi3gWBpD=D7tXDOX104a8NMKW@mail.gmail.com>

venki kaps wrote:
...
> 
> My problem is resolved.GPtimer7 was not reset during the MMU FAULT
> occurrence before the first power cycle. So this pending interrupt is
> preventing the system sleep entry. 
> Now it works fine after resetting Gptimer7 in pm suspend path.
> 

That's doesn't sound right, why the problem is not occurring after the first suspend-resume cycle.

DSP is in charge of clearing the overflow interrupt and if it is doing it after the first transition to Core OFF, why wouldn't be doing it for the first one.

Moreover from the logs sent internally (since it is the same issue and oddly the same resolution), the trace log dump printed is generated in the dsp after clearing the interrupts, so the problem could be the gptimer is configured to autoreload instead of oneshoot or the dsp write is not posted to clear the interrupt (which might be valid issues), but also they could happen after the first transition to OFF.

I'm sorry if I didn't ask you for logs but I was seeing this issue internally (and assumed you'll be in the same team of people :)), and given that more information was posted there than here..., but still, if available send the changes you have made.

Regards,

Omar


  parent reply	other threads:[~2010-09-15 15:40 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-09-13 19:58 OMAP3 DSP MMU fault + off mode issue venki kaps
2010-09-14 15:24 ` venki kaps
2010-09-15 13:55   ` venki kaps
2010-09-15 13:55   ` venki kaps
2010-09-15 14:32     ` Kevin Hilman
2010-09-15 14:32       ` Kevin Hilman
2010-09-15 15:42       ` venki kaps
2010-09-15 15:42         ` venki kaps
2010-09-15 16:03         ` venki kaps
2010-09-15 16:03           ` venki kaps
2010-09-15 22:34           ` Felipe Contreras
2010-09-15 22:34             ` Felipe Contreras
2010-09-16  2:59             ` venki kaps
2010-09-16  2:59               ` venki kaps
2010-09-15 15:39     ` Ramirez Luna, Omar [this message]
2010-09-15 15:39     ` Ramirez Luna, Omar
2010-09-14 15:24 ` venki kaps
2010-09-13 19:58 venki kaps

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='27F9C60D11D683428E133F85D2BB4A530450C3265B__3346.63200560517$1284565240$gmane$org@dlee03.ent.ti.com' \
    --to=omar.ramirez@ti.com \
    --cc=ameya.palande@nokia.com \
    --cc=fernando.lugo@ti.com \
    --cc=h-kanigeri2@ti.com \
    --cc=venkiece2005@gmail.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.