Lines Matching full:cache

3 Cache Interface
6 This is a high-level guide to cache interface and Kconfig options related to
7 cache controllers. See :ref:`cache_api` for API reference material.
9 Zephyr has different Kconfig options to control how the cache controller is
15   instruction cache. The cache controller can be in the core or can be an
16   external cache controller for which a driver is provided.
22   options must be selected when support for data or instruction cache is
25   All the code paths related to cache control must be conditionally enabled
26   depending on these symbols. When the symbol is set the cache is considered
30   For example a platform using the data cache can enable the
32   some platform-specific code to enable and manage the d-cache.
35   the cache operations are exposed to the user through a standard API (see
38   When this option is enabled we assume that all the cache functions are
39   implemented in the architectural code or in an external cache controller
44   whether the cache operations are implemented at arch level or using an
45   external cache controller with a provided driver.
47   * :kconfig:option:`CONFIG_ARCH_CACHE`: the cache API is implemented by the
50   * :kconfig:option:`CONFIG_EXTERNAL_CACHE`: the cache API is implemented by a
51     driver that supports the external cache controller. In this case the driver
52     must be located as usual in the :file:`drivers/cache/` directory
56 Cache API