All of lore.kernel.org
 help / color / mirror / Atom feed
From: Nishanth Menon <nm@ti.com>
To: Jean Pihet <jean.pihet@newoldbits.com>
Cc: Vishwanath Sripathy <vishwanath.bs@ti.com>,
	linux-omap@vger.kernel.org,
	Kevin Hillman <khilman@deeprootsystems.com>,
	Jean Pihet-XID <j-pihet@ti.com>
Subject: RE: [PATCH 1/2] OMAP3 PM: move omap3 sleep to ddr
Date: Thu, 18 Nov 2010 09:33:42 -0600	[thread overview]
Message-ID: <5a0fdb97a16d4c23b22aeeed499ff188@mail.gmail.com> (raw)
In-Reply-To: <AANLkTinLqGaT3c-fiO=5FN881Bm7WCG05pnV72sfa1P4@mail.gmail.com>

> -----Original Message-----
> From: Jean Pihet [mailto:jean.pihet@newoldbits.com]
> Sent: Thursday, November 18, 2010 9:15 AM

[...]
> >> >>
> >> >> Tested on ZOOM3, OMAP3EVM, Beagleboard, n900
> >> >> with full RET and OFF modes.
> >> >
> >> > Sorry, But I disagree with this patch.
> >> >
> >> > There is a silicon errata which cannot be handled with this - RTA
> >> disable
> >> > - errata i608
> >> >
> >> > You need to disable RTA while coming out of OFF - we cannot handle
> > this
> >> on
> >> >
> >> > GP devices if this is not done.
> >> When you come out of Core off, SRAM contents are anyway lost. So you
> >> have to run from DDR after ROM Code completes. This behavior has not
> >> changed with this patch. I fail to understand your concern here.
> > I could potentially be mistaken. Let me do one thing - I will post out
> the
> >
> > patches that I have to the list and we can see how this all works
> > together
> Ok, fine.
> I did not find any 36xx specific workaround for the errata i608 issue.
> Is there one already available?

Yes, I have a series of patches addressing that as well.. hoping to test
On EMU/HS devices prior to posting - GP devices (3430/3630) tested.
Regards,
Nishanth Menon

  reply	other threads:[~2010-11-18 15:34 UTC|newest]

Thread overview: 35+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-11-18 14:51 OMAP3 sleep code clean-up Jean Pihet
2010-11-18 14:51 ` [PATCH 1/2] OMAP3 PM: move omap3 sleep to ddr Jean Pihet
2010-11-18 14:57   ` Nishanth Menon
2010-11-18 15:08     ` Sripathy, Vishwanath
2010-11-18 15:11       ` Nishanth Menon
2010-11-18 15:15         ` Jean Pihet
2010-11-18 15:33           ` Nishanth Menon [this message]
2010-11-18 15:52     ` Kevin Hilman
2010-11-18 16:55       ` Nishanth Menon
2010-11-18 17:52         ` Tony Lindgren
2010-11-18 18:13           ` Tony Lindgren
2010-11-18 18:15           ` Jean Pihet
2010-11-18 18:27             ` Tony Lindgren
2010-11-18 18:34               ` Jean Pihet
2010-11-19 15:37                 ` Jean Pihet
2010-11-19 16:09                   ` Tony Lindgren
2010-11-19 16:14                   ` Derrick, David
2010-11-19 16:26                     ` Jean Pihet
2010-11-22 10:07                     ` Peter 'p2' De Schrijver
2010-11-22 16:03                       ` Kevin Hilman
2010-11-22 16:08                         ` Jean Pihet
2010-11-22 16:22                         ` Peter 'p2' De Schrijver
2010-11-22 16:25                           ` Nishanth Menon
2010-11-22 18:23                             ` Kevin Hilman
2010-11-22 18:31                               ` Nishanth Menon
2010-11-18 14:51 ` [PATCH 2/2] OMAP3: clean up ASM idle code Jean Pihet
2010-11-18 17:41   ` Tony Lindgren
2010-11-18 18:19     ` Jean Pihet
  -- strict thread matches above, loose matches on Subject: below --
2010-09-24 10:56 [PATCH 0/2] OMAP3 PM: sleep code clean up Vishwanath BS
2010-09-24 10:56 ` [PATCH 1/2] OMAP3 PM: move omap3 sleep to ddr Vishwanath BS
2010-09-24 19:01   ` Tony Lindgren
2010-09-24 19:09     ` Tony Lindgren
     [not found]       ` <20100924190930.GH4211-4v6yS6AI5VpBDgjK7y7TUQ@public.gmane.org>
2010-09-25  5:52         ` Shilimkar, Santosh
2010-09-24 19:57   ` Kevin Hilman
2010-10-04  7:26     ` Sripathy, Vishwanath
2010-09-24 10:47 [PATCH 0/2] OMAP3 PM: sleep code clean up Vishwanath BS
2010-09-24 10:47 ` [PATCH 1/2] OMAP3 PM: move omap3 sleep to ddr Vishwanath BS

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=5a0fdb97a16d4c23b22aeeed499ff188@mail.gmail.com \
    --to=nm@ti.com \
    --cc=j-pihet@ti.com \
    --cc=jean.pihet@newoldbits.com \
    --cc=khilman@deeprootsystems.com \
    --cc=linux-omap@vger.kernel.org \
    --cc=vishwanath.bs@ti.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.