Re: Beagleboard rev C memory timings & suspend/resume

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



On Fri, 8 May 2009, Jean Pihet wrote:

> On Thursday 07 May 2009 21:18:41 Paul Walmsley wrote:
> > Hello Jean,
> >
> > one other suggestion.  You mentioned that you had self-refresh working on
> > another OMAP3430 board with two SDRAM chip-selects.  You might consider
> > dumping the SDRC registers from that board, and dumping the SDRC registers
> > on Beagle rev C, and comparing.  It could be that the bootloader on your
> > other board is setting some important bit.
> The comparison gives the following:
> - the timings are slightly different but given that the parts are not the same 
> I do not think it is a problem
> - the fields FIXEDDELAY and MODEFIXEDDELAYINITLAT are set in SDRC_DLLA_CTRL, 
> the register value is 0x2600000A. Does that affect the 166MHz operation?

It shouldn't.

> - the field DEEPPD of SDRC_MCFG_p is set to 0. That setting could affect the 
> suspend/resume

I don't think this should matter, since we never power off the SDRAM.

> - the MUX scheme is different: ADDRMUXLEGACY is set to 0
> - the field BANKALLOCATION of SDRC_MCFG_p is set to 0 instead of 2

- Paul
--
To unsubscribe from this list: send the line "unsubscribe linux-omap" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html

[Index of Archives]     [Linux Arm (vger)]     [ARM Kernel]     [ARM MSM]     [Linux Tegra]     [Linux WPAN Networking]     [Linux Wireless Networking]     [Maemo Users]     [Linux USB Devel]     [Video for Linux]     [Linux Audio Users]     [Yosemite Trails]     [Linux Kernel]     [Linux SCSI]

  Powered by Linux