diff options
author | Timur Tabi <timur@freescale.com> | 2013-01-17 16:34:33 -0600 |
---|---|---|
committer | Kumar Gala <galak@kernel.crashing.org> | 2013-02-13 07:49:02 -0600 |
commit | 0408753faeb53b37628c71c92ee6a7a422042607 (patch) | |
tree | 57ad14c5f6e9e08f5aa3ed2fce774dc447450efd /arch/powerpc/platforms | |
parent | 2d1efdb232bbb4b5253147ead0c8ad8dc7f6c6c3 (diff) | |
download | talos-op-linux-0408753faeb53b37628c71c92ee6a7a422042607.tar.gz talos-op-linux-0408753faeb53b37628c71c92ee6a7a422042607.zip |
powerpc/85xx: describe the PAMU topology in the device tree
The PAMU caches use the LIODNs to determine which cache lines hold the
entries for the corresponding LIODs. The LIODNs must therefore be
carefully assigned to avoid cache thrashing -- two active LIODs with
LIODNs that put them in the same cache line.
Currently, LIODNs are statically assigned by U-Boot, but this has
limitations. LIODNs are assigned even for devices that may be disabled
or unused by the kernel. Static assignments also do not allow for device
drivers which may know which LIODs can be used simultaneously. In
other words, we really should assign LIODNs dynamically in Linux.
To do that, we need to describe the PAMU device and cache topologies in
the device trees.
Signed-off-by: Timur Tabi <timur@freescale.com>
Acked-by: Stuart Yoder <stuart.yoder@freescale.com>
Acked-by: Scott Wood <scottwood@freescale.com>
Signed-off-by: Kumar Gala <galak@kernel.crashing.org>
Diffstat (limited to 'arch/powerpc/platforms')
0 files changed, 0 insertions, 0 deletions