RE: [PATCH -pm 1/2] SDRC: check for stuck DLL state machine and kick

Hi, On Tue, 23 Jun 2009, Woodruff, Richard wrote: From: Paul Walmsley [mailto:p...@pwsan.com] Sent: Tuesday, June 23, 2009 3:05 PM Looks like the significant difference is the use of CLKCTRL = 0x2 (+ AUTOCOUNT). Maybe there is some SDRC bug related to CLKCTRL = 0x2 that causes this

RE: [PATCH -pm 1/2] SDRC: check for stuck DLL state machine and kick

Hi Paul, On Tue, 23 Jun 2009, Woodruff, Richard wrote: From: Paul Walmsley [mailto:p...@pwsan.com] Sent: Tuesday, June 23, 2009 3:05 PM Looks like the significant difference is the use of CLKCTRL = 0x2 (+ AUTOCOUNT). Maybe there is some SDRC bug related to CLKCTRL = 0x2 that

RE: [PATCH -pm 1/2] SDRC: check for stuck DLL state machine and kick

Hello Richard, On Fri, 19 Jun 2009, Woodruff, Richard wrote: From: Paul Walmsley [mailto:p...@pwsan.com] Sent: Thursday, June 18, 2009 4:07 PM On Wed, 17 Jun 2009, Woodruff, Richard wrote: I've only seen the condition along side of very aggressive SDRC_POWER settings. Could

RE: [PATCH -pm 1/2] SDRC: check for stuck DLL state machine and kick

From: Paul Walmsley [mailto:p...@pwsan.com] Sent: Thursday, June 18, 2009 4:07 PM Hi Paul, On Wed, 17 Jun 2009, Woodruff, Richard wrote: I've only seen the condition along side of very aggressive SDRC_POWER settings. Could you send over the SDRC_POWER settings that cause this problem?

Re: [PATCH -pm 1/2] SDRC: check for stuck DLL state machine and kick

Woodruff, Richard r-woodru...@ti.com writes: Hi Paul, Hm, seems my mailing is out to lunch today... I'll be worse than normal in protocol and top post. I've seen this issue on a couple custom boards. In these instances I've not had access to boot loaders. I would expect this issue

RE: [PATCH -pm 1/2] SDRC: check for stuck DLL state machine and kick

Mike, From: Mike Chan [mailto:m...@android.com] Sent: Thursday, June 18, 2009 1:42 PM +/* Kick DLL state machine if lock not started */ +kick_dll: + ldr r4, sdrc_dlla_ctrl /* get dlla addr */ + ldr r5, [r4]/* grab value */ + mov r6, r5

RE: [PATCH -pm 1/2] SDRC: check for stuck DLL state machine and kick

From: Kevin Hilman [mailto:khil...@deeprootsystems.com] Sent: Thursday, June 18, 2009 10:03 AM I've seen this issue on a couple custom boards. In these instances I've not had access to boot loaders. I would expect this issue would show up in the wild in some devices. It might be ok to

RE: [PATCH -pm 1/2] SDRC: check for stuck DLL state machine and kick

-Original Message- From: linux-omap-ow...@vger.kernel.org [mailto:linux-omap-ow...@vger.kernel.org] On Behalf Of Woodruff, Richard Sent: 2009年6月19日 2:55 To: Mike Chan; Kevin Hilman Cc: linux-omap@vger.kernel.org; Mike Chan Subject: RE: [PATCH -pm 1/2] SDRC: check for stuck DLL

RE: [PATCH -pm 1/2] SDRC: check for stuck DLL state machine and kick

Hi, From: Wang Sawsd-A24013 [mailto:cqw...@motorola.com] Sent: Thursday, June 18, 2009 2:27 PM + str r6, [r4]/* restore old value */ Richard, I think here it should be: str r5, [r4], not r6. I modifed this when I was verifying your patch. You are correct that was

RE: [PATCH -pm 1/2] SDRC: check for stuck DLL state machine and kick

Hi Richard, On Wed, 17 Jun 2009, Woodruff, Richard wrote: I've only seen the condition along side of very aggressive SDRC_POWER settings. Could you send over the SDRC_POWER settings that cause this problem? thanks, - Paul -- To unsubscribe from this list: send the line unsubscribe

Re: [PATCH -pm 1/2] SDRC: check for stuck DLL state machine and kick

Hi, a few questions for Mike and Richard: On Mon, 15 Jun 2009, Kevin Hilman wrote: From: Richard Woodruff r-woodru...@ti.com I'm thinking DLL state is an exceptional condition which happens based on some wrong early programming when initially setting DLL up. Some kind of race between