Lines Matching full:cache

3 Cache Control Configuration
6 This is a high-level guide to Zephyr's 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.
19   should be set whether we plan to support and use the cache control in Zephyr
23   options must be selected when support for data or instruction cache is
27   All the code paths related to cache control must be conditionally enabled
28   depending on these symbols. When the symbol is set the cache is considered
32   For example a platform using the data cache can enable the
34   some platform-specific code to enable and manage the d-cache.
37   the cache operations are exposed to the user through a standard API (see
40   When this option is enabled we assume that all the cache functions are
41   implemented in the architectural code or in an external cache controller
55   whether the cache operations are implemented at arch level or using an
56   external cache controller with a provided driver.
58   * :kconfig:option:`CONFIG_ARCH_CACHE`: the cache API is implemented by the
61   * :kconfig:option:`CONFIG_EXTERNAL_CACHE`: the cache API is implemented by a
62     driver that supports the external cache controller. In this case the driver
63     must be located as usual in the :file:`drivers/cache/` directory
67 Cache API