Paul,
Sorry for late response. Here is the answer for some of the queries that you
had posted.
-Original Message-
From: linux-omap-ow...@vger.kernel.org [mailto:linux-omap-
ow...@vger.kernel.org] On Behalf Of Paul Walmsley
Sent: Tuesday, January 26, 2010 11:13 AM
To: Reddy, Teerth
Hello Teerth,
On Mon, 25 Jan 2010, Reddy, Teerth wrote:
From: Paul Walmsley [mailto:p...@pwsan.com]
I wonder if this also needs to make sure that all the other system
initiators are mute before continuing, for the same reason cited in commit
18862cbe47e37beba98f22c088fbe6fe029df889 ?
Hi Paul,
I wonder if this also needs to make sure that all the other system
initiators are mute before continuing, for the same reason cited in
commit
18862cbe47e37beba98f22c088fbe6fe029df889 ? I suppose that, for example,
if an interrupt occurs on the IVA2.2 or the DMA controller tries
On Fri, 15 Jan 2010, Reddy, Teerth wrote:
Will send the updated patch.
Thanks, all your above responses make sense. What do you think about some
of the other comments I had, re: disabling interrupts, etc?
- Paul
--
To unsubscribe from this list: send the line unsubscribe linux-omap in
the
Some more comments.
On Wed, 13 Jan 2010, Reddy, Teerth wrote:
From: Teerth Reddy tee...@ti.com
This patch has the workaround for errata 1.176.
In some cases, user is not able to access DDR memory after
warm-reset.This situation occurs while the warm-reset
happens during a read access to
Hello Teerth,
On Wed, 13 Jan 2010, Reddy, Teerth wrote:
-Original Message-
From: Paul Walmsley [mailto:p...@pwsan.com]
Your changes -
+/* Function for SDRC config for warm reset */
+static u32 (*_omap3_sram_warmreset)(void);
+
+void omap3_warmreset()
+{
+ if
Hello Teerth,
another question that just occurred to me.
On Wed, 13 Jan 2010, Paul Walmsley wrote:
@@ -147,10 +149,9 @@ void omap_prcm_arch_reset(char mode)
* cf. OMAP34xx TRM, Initialization / Software Booting
* Configuration. */
omap_writel(l,
On Wed, 13 Jan 2010, Paul Walmsley wrote:
Wouldn't this code need to enable interrupts before calling
omap3_sram_warmreset()?
Rather, this should have read, _disable_ interrupts...
- Paul
--
To unsubscribe from this list: send the line unsubscribe linux-omap in
the body of a message to
From: Teerth Reddy tee...@ti.com
This patch has the workaround for errata 1.176.
In some cases, user is not able to access DDR memory after
warm-reset.This situation occurs while the warm-reset
happens during a read access to DDR memory. In that
particular conditions, DDR memory does not respond
Hello Teerth,
On Tue, 5 Jan 2010, Reddy, Teerth wrote:
Can you please push this patch if it looks OK to you?
Thanks queued for .33-rc*.
- Paul
--
To unsubscribe from this list: send the line unsubscribe linux-omap in
the body of a message to majord...@vger.kernel.org
More majordomo info at
On Wed, 6 Jan 2010, Paul Walmsley wrote:
On Tue, 5 Jan 2010, Reddy, Teerth wrote:
Can you please push this patch if it looks OK to you?
Thanks queued for .33-rc*.
Well, I take that back. I must be going senile. During compile testing,
your patch generated a compile warning. This
Hi Tony,
Can you please push this patch if it looks OK to you?
Thanks and Regards,
Teerth
-Original Message-
From: Reddy, Teerth
Sent: Wednesday, December 16, 2009 4:13 PM
To: 'linux-omap@vger.kernel.org'
Subject: [PATCH] OMAP3: SDRC : Errata 1.176 Fix - Accesses to DDR stall in
12 matches
Mail list logo
