public inbox for linux-omap@vger.kernel.org
 help / color / mirror / Atom feed
From: "Rajendra Nayak" <rnayak@ti.com>
To: 'Paul Walmsley' <paul@pwsan.com>,
	"'Woodruff, Richard'" <r-woodruff2@ti.com>
Cc: linux-omap@vger.kernel.org, 'Igor Stoppa' <igor.stoppa@nokia.com>
Subject: RE: [PATCH 0/9] OMAP2/3 SDRC/clock: control CORE M2 divider, clean up SDRC
Date: Wed, 9 Jul 2008 10:12:03 +0530	[thread overview]
Message-ID: <03bf01c8e17e$2364da00$68bf18ac@ent.ti.com> (raw)
In-Reply-To: <alpine.DEB.1.00.0807081730590.12684@utopia.booyaka.com>

 

> -----Original Message-----
> From: Paul Walmsley [mailto:paul@pwsan.com] 
> Sent: Wednesday, July 09, 2008 5:17 AM
> To: Woodruff, Richard
> Cc: Nayak, Rajendra; linux-omap@vger.kernel.org; 'Igor Stoppa'
> Subject: RE: [PATCH 0/9] OMAP2/3 SDRC/clock: control CORE M2 
> divider, clean up SDRC
> 
> On Tue, 8 Jul 2008, Woodruff, Richard wrote:
> 
> > > > SRAM being mapped as cacheable could be a possible 
> reason for this.
> > 
> > Second this.
> 
> Yeah, agreed that it needs to be done, but SRAM in CDP 12.17 is still 
> marked cacheable too, right?  Did CORE M2 divider changes work in CDP 
> 12.17?
> 
> Also still curious why, if it's the cache line eviction 
> issue, it only 
> locks up on the low- to high-speed transition.

While we saw the issues due to cache line eviction, I remember it used 
to pop up both during a low-to-high and high-to-low transitions.
If you are seeing this only during a low-to-high, it probably could be something else.

> 
> > Can you ping the board by chance when you are locked?  Is only user 
> > space locked out or is the board dead. The SRAM thing 
> resulted in a dead 
> > lock where MPU was done.
> 
> The board doesn't respond to pings.
> 
> 
> - Paul
> 


  parent reply	other threads:[~2008-07-09  4:42 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-07-08  2:54 [PATCH 0/9] OMAP2/3 SDRC/clock: control CORE M2 divider, clean up SDRC Paul Walmsley
2008-07-08  2:54 ` [PATCH 1/9] OMAP2 SDRC: move mach-omap2/memory.h into include/asm-arm/arch-omap/sdrc.h Paul Walmsley
2008-07-08  2:54 ` [PATCH 2/9] OMAP2 SDRC: rename memory.c to sdrc2xxx.c Paul Walmsley
2008-07-08  2:54 ` [PATCH 3/9] OMAP2 SDRC: separate common OMAP2/3 code from OMAP2xxx code Paul Walmsley
2008-07-08  2:54 ` [PATCH 4/9] OMAP2 SDRC: add SDRAM timing parameter infrastructure Paul Walmsley
2008-07-08  2:54 ` [PATCH 5/9] OMAP2 SDRC: add timing data for Micron MT46H32M32LF-6 Paul Walmsley
2008-08-12 17:07   ` Steve Sakoman
2008-08-12 21:42     ` Paul Walmsley
2008-07-08  2:55 ` [PATCH 6/9] OMAP2 SDRC: add timing data for Qimonda HYB18M512160AF-6 Paul Walmsley
2008-07-08  2:55 ` [PATCH 7/9] OMAP3 SRAM: remove unused functions; rename remainder Paul Walmsley
2008-07-08  2:55 ` [PATCH 8/9] OMAP3 clock/SRAM: fix CORE DPLL M2 divider mask Paul Walmsley
2008-07-08  2:55 ` [PATCH 9/9] OMAP3 clock: add omap3_core_dpll_m2_set_rate() Paul Walmsley
2008-07-08  4:20   ` Paul Walmsley
2008-07-08  4:37 ` [PATCH 0/9] OMAP2/3 SDRC/clock: control CORE M2 divider, clean up SDRC Rajendra Nayak
2008-07-08 22:12   ` Paul Walmsley
2008-07-08 23:12     ` Woodruff, Richard
2008-07-08 23:46       ` Paul Walmsley
2008-07-08 23:55         ` Woodruff, Richard
2008-07-09  1:06           ` Paul Walmsley
2008-07-15  7:58             ` Paul Walmsley
2008-07-09  4:42         ` Rajendra Nayak [this message]
2008-08-05 12:13 ` Tony Lindgren

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='03bf01c8e17e$2364da00$68bf18ac@ent.ti.com' \
    --to=rnayak@ti.com \
    --cc=igor.stoppa@nokia.com \
    --cc=linux-omap@vger.kernel.org \
    --cc=paul@pwsan.com \
    --cc=r-woodruff2@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox