Searched full:ways (Results 1 – 25 of 139) sorted by relevance
123456
| /Zephyr-latest/soc/espressif/esp32s3/ |
| D | Kconfig | 39 prompt "Instruction cache associated ways"
42 Instruction cache associated ways to be set on application startup.
45 bool "4 ways"
47 bool "8 ways"
104 prompt "Data cache associated ways"
107 Data cache associated ways to be set on application startup.
110 bool "4 ways"
112 bool "8 ways"
|
| /Zephyr-latest/arch/arm/core/cortex_a_r/ |
| D | Kconfig | 115 bool "Control segregation of L1 I/D-Cache ways between Flash and AXIM"
118 Control segregation of L1 I/D-Cache ways between Flash and AXIM.
128 Configure L1 I-Cache ways for Flash interface. Default is reset value, all
129 I-Cache ways are allocated for AXIM interface.
137 Configure L1 D-Cache ways for Flash interface. Default is reset value,
138 all D-Cache ways are allocated for AXIM interface.
|
| /Zephyr-latest/soc/espressif/esp32s2/ |
| D | soc.h | 49 extern void esp_rom_Cache_Set_ICache_Mode(cache_size_t cache_size, cache_ways_t ways,
57 extern void esp_rom_Cache_Set_DCache_Mode(cache_size_t cache_size, cache_ways_t ways,
63 extern void esp_rom_Cache_Set_DCache_Mode(cache_size_t cache_size, cache_ways_t ways,
|
| D | soc.c | 85 * cache size, cache associated ways, cache line size. in __esp_platform_start()
92 * Configure the mode of data : cache size, cache associated ways, cache in __esp_platform_start()
|
| /Zephyr-latest/drivers/cache/ |
| D | cache_andes_l2.h | 82 unsigned long ways, sets, index, cmd; in nds_l2_cache_all() local
89 ways = 16; in nds_l2_cache_all()
91 ways = 8; in nds_l2_cache_all()
124 sets = l2_cache_cfg.size / (ways * l2_cache_cfg.line_size); in nds_l2_cache_all()
126 for (int j = 0; j < ways; j++) { in nds_l2_cache_all()
|
| /Zephyr-latest/tests/drivers/flash/common/ |
| D | Kconfig | 5 # other ways.
|
| /Zephyr-latest/doc/develop/toolchains/ |
| D | cadence_xcc.rst | 35 * There are two ways to specify the SoC ID and the SDK version to use.
53 setup the environment using the two above mentioned ways:
|
| /Zephyr-latest/include/zephyr/devicetree/ |
| D | port-endpoint.h | 44 * It handles various ways of how a port could be defined.
109 * It handles various ways of how a port and an endpoint could be defined as described in
172 * This handles various ways of how a port and an endpoint could be defined as described in
223 * local endpoint. This handles various ways of how a port and an endpoint could be defined as
|
| /Zephyr-latest/samples/net/promiscuous_mode/ |
| D | README.rst | 26 There are multiple ways to use this application. In this example QEMU
|
| /Zephyr-latest/doc/connectivity/usb/device/api/ |
| D | usb_device.rst | 9 There are two ways to transmit data, using the 'low' level read/write API or
|
| /Zephyr-latest/kernel/ |
| D | thread_monitor.c | 48 * The indirect ways are through calling k_thread_create and in k_thread_foreach()
100 * The indirect ways are through calling k_thread_create and in k_thread_foreach_filter_by_cpu()
|
| /Zephyr-latest/doc/build/dts/ |
| D | index.rst | 7 hardware. Zephyr uses devicetree in two main ways:
|
| D | api-usage.rst | 34 These are the main ways to get a node identifier:
81 Here are a few ways to get node identifiers for the ``i2c@40002000`` node:
314 See :ref:`dt-get-device` for ways to do that.
323 See :c:macro:`DT_PHA_HAS_CELL_AT_IDX` and :c:macro:`DT_PROP_HAS_IDX` for ways to
|
| /Zephyr-latest/samples/net/sockets/net_mgmt/ |
| D | README.rst | 24 There are multiple ways to use this application. One of the most common
|
| /Zephyr-latest/arch/xtensa/core/ |
| D | README_MMU.txt | 15 "special" ways storing mappings under OS control. Some of these are
109 non-automatically-refilled TLB ways to store bootstrap records.
118 ways (ways 7-9) with at least one 4k page mapping each. We can use
130 provide 4k "pinnable" ways in the instruction TLB (frankly this seems
|
| /Zephyr-latest/doc/services/ |
| D | secure_storage.rst | 35 | See below for important ways the implementation deviates from the specification.
46 Below are some ways the implementation deviates from the specification
|
| /Zephyr-latest/scripts/ |
| D | list_shields.py | 14 # sure to test both ways it can be used.
|
| /Zephyr-latest/doc/develop/manifest/ |
| D | index.rst | 53 recommended ways to do this while still inheriting the mandatory modules from
|
| /Zephyr-latest/doc/connectivity/bluetooth/api/mesh/ |
| D | heartbeat.rst | 32 be triggered in two ways:
|
| /Zephyr-latest/samples/subsys/usb/webusb-next/ |
| D | README.rst | 41 There are two ways to access this sample page:
|
| /Zephyr-latest/samples/subsys/llext/modules/ |
| D | README.rst | 17 This is achieved in two different ways, depending on the value of the Kconfig
|
| /Zephyr-latest/tests/boards/intel_adsp/hda/src/ |
| D | smoke.c | 42 * work in horrible and unexpected ways if not done as they are here.
119 * work in horrible and unexpected ways if not done as they are here.
|
| /Zephyr-latest/doc/hardware/peripherals/ |
| D | uart.rst | 9 Zephyr provides three different ways to access the UART peripheral. Depending
|
| /Zephyr-latest/tests/kernel/fatal/no-multithreading/src/ |
| D | main.c | 121 * @details Manually trigger the crash with various ways and check
|
| /Zephyr-latest/dts/bindings/mtd/ |
| D | jedec,jesd216.yaml | 66 of DW16 identifying ways a device can be placed into 4-byte addressing
|
123456
