aboutsummaryrefslogtreecommitdiff
path: root/drivers/block/viodasd.c
diff options
context:
space:
mode:
authorAndy Green <andy@openmoko.com>2009-02-01 20:50:35 +0000
committerAndy Green <agreen@octopus.localdomain>2009-02-01 20:50:35 +0000
commit7f859d161097631a3c76ed1dbb1cfcb08ebe9759 (patch)
treefca04239e53b153a842eaa1c93d528b5fc0b8b67 /drivers/block/viodasd.c
parent9deff1b20f0c75b260522ec990a3c55863c30b89 (diff)
debug-add-more-glamo-mem-speed-options.patch
People on bug https://docs.openmoko.org/trac/ticket/2217 experiencing problems with default emmory settings on Glamo reported that changing reg 0x200 <- 0xef0 as in 2.6.24 made the problem not reproducible any more. However this changes three bitfields, two are to do with waitstates before sampling read and write cycles off the bus, and the last is to do with which PLL provides the clock to the memory interface unit logic. The old settings has all three of these very conservative, 3 waitstates and using the 50MHz PLL instead of the 90MHz one; the new default setting has all of these at their fastest of 0 wait states and the 90MHz PLL. This patch adds some more granular tests to the same glamo3362.slow_memory= parameter to see if we can find some middle ground. For example the issue may be the waitstates and not the PLL source, in which case even users with the bad Glamo behaviour can have the advantage of the faster PLL / bus bandwidth. 0 90MHz PLL, no wait states (default) 1 50MHz PLL, 3 wait states 2 50MHz PLL, 2 wait states 3 50MHz PLL, 1 wait state 4 50MHz PLL, no wait states 5 90MHz PLL, 3 wait states 6 90MHz PLL, 2 wait states 7 90MHz PLL, 1 wait state Signed-off-by: Andy Green <andy@openmoko.com>
Diffstat (limited to 'drivers/block/viodasd.c')
0 files changed, 0 insertions, 0 deletions