2018-09-26 00:08:01 +08:00
|
|
|
// SPDX-License-Identifier: (GPL-2.0 OR MIT)
|
|
|
|
|
//
|
|
|
|
|
// Copyright 2013 Freescale Semiconductor, Inc.
|
|
|
|
|
|
2013-05-28 17:12:22 +08:00
|
|
|
|
2014-11-03 04:36:46 +08:00
|
|
|
#include "vf500.dtsi"
|
2013-05-28 17:12:22 +08:00
|
|
|
|
2014-11-03 04:36:46 +08:00
|
|
|
&a5_cpu {
|
|
|
|
|
next-level-cache = <&L2>;
|
|
|
|
|
};
|
2014-07-16 14:08:49 +08:00
|
|
|
|
2014-11-03 04:36:46 +08:00
|
|
|
&aips0 {
|
|
|
|
|
L2: l2-cache@40006000 {
|
|
|
|
|
compatible = "arm,pl310-cache";
|
|
|
|
|
reg = <0x40006000 0x1000>;
|
|
|
|
|
cache-unified;
|
|
|
|
|
cache-level = <2>;
|
ARM: dts: vf610: use reset values for L2 cache latencies
Linux on Vybrid used several different L2 latencies so far, none
of them seem to be the right ones. According to the application note
AN4947 ("Understanding Vybrid Architecture"), the tag portion runs
on CPU clock and is inside the L2 cache controller, whereas the data
portion is stored in the external SRAM running on platform clock.
Hence it is likely that the correct value requires a higher data
latency then tag latency.
These are the values which have been used so far:
- The mainline values:
arm,data-latency = <1 1 1>;
arm,tag-latency = <2 2 2>;
Those values have lead to problems on higher clocks. They look
like a poor translation from the reset values (missing +1 offset
and a mix up between tag/latency values).
- The Linux 3.0 (SoC vendor BSP) values (converted to DT notation):
arm,data-latency = <4 2 3>
arm,tag-latency = <4 2 3>
The cache initialization function along with the value matches the
i.MX6 code from the same kernel, so it seems that those values have
just been copied.
- The Colibri values:
arm,data-latency = <2 1 2>;
arm,tag-latency = <3 2 3>;
Those were a mix between the values of the Linux 3.0 based BSP and
the mainline values above.
- The SoC Reset values (converted to DT notation):
arm,data-latency = <3 3 3>;
arm,tag-latency = <2 2 2>;
So far there is no official statement on what the correct values are.
See also the related Freescale community thread:
https://community.freescale.com/message/579785#579785
For now, the reset values seem to be the best bet. Remove all other
"bogus" values and use the reset value on vf610.dtsi level.
Signed-off-by: Stefan Agner <stefan@agner.ch>
Cc: <stable@vger.kernel.org>
Signed-off-by: Shawn Guo <shawnguo@kernel.org>
2015-12-01 09:59:26 +08:00
|
|
|
arm,data-latency = <3 3 3>;
|
2014-11-03 04:36:46 +08:00
|
|
|
arm,tag-latency = <2 2 2>;
|
2013-05-28 17:12:22 +08:00
|
|
|
};
|
|
|
|
|
};
|
