summaryrefslogtreecommitdiff
path: root/mm/bounce.c
diff options
context:
space:
mode:
authorTimur Tabi <timur@freescale.com>2013-01-17 22:34:33 (GMT)
committerEmil Medve <Emilian.Medve@Freescale.com>2013-03-21 18:42:08 (GMT)
commit07ee7f04284c7afe92c9de3abc964ab1f9c69beb (patch)
tree1441a2373bd267c68f7db1e2582e7b99348b4793 /mm/bounce.c
parent8872252dfd6c3a6829b18f2f429bc01cf69b0021 (diff)
downloadlinux-fsl-qoriq-07ee7f04284c7afe92c9de3abc964ab1f9c69beb.tar.xz
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 'mm/bounce.c')
0 files changed, 0 insertions, 0 deletions