diff options
Diffstat (limited to 'Documentation')
-rw-r--r-- | Documentation/arm/tcm.txt | 10 |
1 files changed, 6 insertions, 4 deletions
diff --git a/Documentation/arm/tcm.txt b/Documentation/arm/tcm.txt index 074f4be6667f..77fd9376e6d7 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 | |||
29 | actually move the physical location of the TCM around. At the | 29 | actually move the physical location of the TCM around. At the |
30 | place you put it, it will mask any underlying RAM from the | 30 | place you put it, it will mask any underlying RAM from the |
31 | CPU so it is usually wise not to overlap any physical RAM with | 31 | CPU so it is usually wise not to overlap any physical RAM with |
32 | the TCM. The TCM memory exists totally outside the MMU and will | 32 | the TCM. |
33 | override any MMU mappings. | ||
34 | 33 | ||
35 | Code executing inside the ITCM does not "see" any MMU mappings | 34 | The TCM memory can then be remapped to another address again using |
36 | and e.g. register accesses must be made to physical addresses. | 35 | the MMU, but notice that the TCM if often used in situations where |
36 | the MMU is turned off. To avoid confusion the current Linux | ||
37 | implementation will map the TCM 1 to 1 from physical to virtual | ||
38 | memory in the location specified by the machine. | ||
37 | 39 | ||
38 | TCM is used for a few things: | 40 | TCM is used for a few things: |
39 | 41 | ||