aboutsummaryrefslogtreecommitdiffstats
path: root/arch/arm/mach-omap1/clock_data.c
diff options
context:
space:
mode:
authorPaul Walmsley <paul@pwsan.com>2010-12-21 21:08:14 -0700
committerPaul Walmsley <paul@pwsan.com>2010-12-21 21:08:14 -0700
commit1124d2f9186ec9e42e1c3f78c20199ba2cb597e2 (patch)
tree03bc5dea770709662e4a0eeeadd2b9d94a4c1120 /arch/arm/mach-omap1/clock_data.c
parentOMAP3: clock: fix incorrect rate display when switching MPU rate at boot (diff)
downloadlinux-dev-1124d2f9186ec9e42e1c3f78c20199ba2cb597e2.tar.xz
linux-dev-1124d2f9186ec9e42e1c3f78c20199ba2cb597e2.zip
OMAP2/3: SRAM: add comment about crashes during a TLB miss
Some users were observing crashes during the execution of CORE DVFS code from OCM RAM -- a locally-modified copy of the linux-omap code. Richard Woodruff tracked this down to a DTLB miss which had been inadvertently and intermittently caused by the local modifications. (The TLB miss caused the ARM MMU to attempt to walk the page tables stored in SDRAM, which was not possible since SDRAM is off-line for a portion of the CORE DVFS OCM RAM code.) Add a note to the OMAP2 & OMAP3 CORE DVFS SRAM code to warn others that changes may result in crashes here if they are not carefully tested. Signed-off-by: Paul Walmsley <paul@pwsan.com> Cc: Richard Woodruff <r-woodruff2@ti.com> Cc: Jon Hunter <jon-hunter@ti.com> Cc: Nishanth Menon <nm@ti.com>
Diffstat (limited to 'arch/arm/mach-omap1/clock_data.c')
0 files changed, 0 insertions, 0 deletions