aboutsummaryrefslogtreecommitdiffstats
diff options
context:
space:
mode:
authorLinus Walleij <linus.walleij@stericsson.com>2009-10-01 14:31:22 +0100
committerRussell King <rmk+kernel@arm.linux.org.uk>2009-10-01 16:26:16 +0100
commit610ea6c671685a09afff7ba521bdccda21c84c76 (patch)
tree0df60ad1162489a9dad3ba75a93f3dd919f164de
parent6176d39471943a2e574782cbf62deded19b96aa0 (diff)
downloadkernel_samsung_smdk4412-610ea6c671685a09afff7ba521bdccda21c84c76.tar.gz
kernel_samsung_smdk4412-610ea6c671685a09afff7ba521bdccda21c84c76.tar.bz2
kernel_samsung_smdk4412-610ea6c671685a09afff7ba521bdccda21c84c76.zip
ARM: 5738/1: Correct TCM documentation
It turns out that the TCM memory can be remap:ed by the MMU just like any other memory. Signed-off-by: Linus Walleij <linus.walleij@stericsson.com> Signed-off-by: Russell King <rmk+kernel@arm.linux.org.uk>
-rw-r--r--Documentation/arm/tcm.txt10
1 files changed, 6 insertions, 4 deletions
diff --git a/Documentation/arm/tcm.txt b/Documentation/arm/tcm.txt
index 074f4be6667..77fd9376e6d 100644
--- a/Documentation/arm/tcm.txt
+++ b/Documentation/arm/tcm.txt
@@ -29,11 +29,13 @@ TCM location and size. Notice that this is not a MMU table: you
actually move the physical location of the TCM around. At the
place you put it, it will mask any underlying RAM from the
CPU so it is usually wise not to overlap any physical RAM with
-the TCM. The TCM memory exists totally outside the MMU and will
-override any MMU mappings.
+the TCM.
-Code executing inside the ITCM does not "see" any MMU mappings
-and e.g. register accesses must be made to physical addresses.
+The TCM memory can then be remapped to another address again using
+the MMU, but notice that the TCM if often used in situations where
+the MMU is turned off. To avoid confusion the current Linux
+implementation will map the TCM 1 to 1 from physical to virtual
+memory in the location specified by the machine.
TCM is used for a few things: