Home
last modified time | relevance | path

Searched refs:accessed (Results 1 – 25 of 93) sorted by relevance

1234

/Zephyr-Core-3.7.0/subsys/demand_paging/eviction/
DKconfig21 A periodic timer will clear the accessed state of all virtual pages.
25 - recently accessed, dirty
26 - recently accessed, clean
27 - not recently accessed, dirty
28 - not recently accessed, clean
37 algorithm: all operations are O(1), the accessed flag is cleared on
44 int "Recently accessed period, in milliseconds"
47 A periodic timer will fire that clears the accessed state of all virtual
49 still has the accessed property, it will be considered as recently used.
Dnru.c50 bool accessed; in k_mem_paging_eviction_select() local
71 accessed = (flags & ARCH_DATA_PAGE_ACCESSED) != 0UL; in k_mem_paging_eviction_select()
82 prec = (dirty ? 1U : 0U) + (accessed ? 2U : 0U); in k_mem_paging_eviction_select()
/Zephyr-Core-3.7.0/drivers/sensor/nordic/temp/
DKconfig23 bool "nRF Temperature Sensor accessed via nrfs"
28 Enable driver for nRF temperature sensor accessed through the nRF
/Zephyr-Core-3.7.0/subsys/debug/symtab/
DKconfig9 The symbol table can be accessed by including the
/Zephyr-Core-3.7.0/arch/x86/
Dgen_gdt.py119 accessed = 1
121 access = access | (present << 7) | (dpl << 5) | (desc_type << 4) | accessed
/Zephyr-Core-3.7.0/include/zephyr/arch/x86/ia32/
Dsegmentation.h153 uint8_t accessed:1; member
272 .accessed = 0, \
284 .accessed = 0, \
/Zephyr-Core-3.7.0/doc/hardware/peripherals/
Dbbram.rst7 common types of BBRAM properties are easily accessed via this API:
Dgnss.rst11 are usually accessed through GNSS modems which receive and
Dvideo.rst39 A video control is accessed and identified by a CID (control identifier). It
/Zephyr-Core-3.7.0/drivers/serial/
DKconfig.esp3227 USB host. The USB stack is built into the chip and accessed
/Zephyr-Core-3.7.0/drivers/dma/
DKconfig.nxp_sof_host_dma15 can be accessed without an actual
/Zephyr-Core-3.7.0/doc/kernel/services/threads/
Dnothread.rst92 drivers. Bus-accessed devices like serial memories may not be
101 drivers. Bus-accessed devices like GPIO extenders may not be supported.
/Zephyr-Core-3.7.0/doc/kernel/data_structures/
Dslist.rst18 before use. Its interior fields are opaque and should not be accessed
33 accessed with :c:func:`sys_slist_peek_next`.
110 "flags" with each list node. These can be accessed and modified with
/Zephyr-Core-3.7.0/doc/kernel/iterable_sections/
Dindex.rst52 The data can then be accessed using :c:macro:`STRUCT_SECTION_FOREACH`.
/Zephyr-Core-3.7.0/doc/services/retention/
Dindex.rst24 accessed or updated independently. The prefix and checksum can be set
107 The retention areas can then be accessed using the data retention API (once
188 :kconfig:option:`CONFIG_RETENTION_BOOT_MODE` and then accessed by using the
/Zephyr-Core-3.7.0/drivers/disk/
DKconfig.sdmmc51 File system on sdmmc accessed through stm32 sdmmc.
/Zephyr-Core-3.7.0/subsys/bluetooth/audio/
DKconfig.ascs66 an ASE read or dropping a notification if the ASE state is being accessed by another
/Zephyr-Core-3.7.0/doc/services/task_wdt/
Dindex.rst29 Instead, the task watchdog API can be accessed globally to add or delete new
/Zephyr-Core-3.7.0/doc/develop/languages/c/
Dcommon_libc.rst31 called ``z_malloc_partition``, which can be accessed from the user mode
/Zephyr-Core-3.7.0/drivers/pinctrl/
DKconfig25 a driver has to be accessed externally. This can happen, for example, when
/Zephyr-Core-3.7.0/subsys/bluetooth/host/
DCMakeLists.txt109 be accessed.
/Zephyr-Core-3.7.0/samples/subsys/llext/modules/
DREADME.rst13 their symbols can be accessed and functions called.
/Zephyr-Core-3.7.0/boards/arduino/opta/doc/
Dindex.rst104 accessed by both cores at run time. Accesses are protected by a hardware semaphore
118 can be accessed by connecting the device to the USB, and then pressing
/Zephyr-Core-3.7.0/doc/develop/api/
Ddesign_guidelines.rst36 cases further context can accessed by the callback indirectly by
82 * Any data that is accessed only when the feature is enabled should be
/Zephyr-Core-3.7.0/samples/boards/reel_board/mesh_badge/
DREADME.rst14 can also be accessed with any Bluetooth LE GATT client from your PC,

1234