Home
last modified time | relevance | path

Searched full:demand (Results 1 – 25 of 76) sorted by relevance

1234

/Zephyr-latest/doc/connectivity/bluetooth/api/mesh/
Dod_cli.rst3 On-Demand Private Proxy Client
6 The On-Demand Private Proxy Client model is a foundation model defined by the Bluetooth Mesh
10 The On-Demand Private Proxy Client model was introduced in the Bluetooth Mesh Protocol Specification
11 version 1.1, and is used to set and retrieve the On-Demand Private GATT Proxy state. The state
15 The On-Demand Private Proxy Client model communicates with an On-Demand Private Proxy Server model
16 using the device key of the node containing the target On-Demand Private Proxy Server model
19 If present, the On-Demand Private Proxy Client model must only be instantiated on the primary
25 The On-Demand Private Proxy Client model behavior can be configured with the transmission timeout
Dod_srv.rst3 On-Demand Private Proxy Server
6 The On-Demand Private Proxy Server model is a foundation model defined by the Bluetooth Mesh
9 The On-Demand Private Proxy Server model was introduced in the Bluetooth Mesh Protocol Specification
11 node that is a recipient of Solicitation PDUs by managing its On-Demand Private GATT Proxy state.
13 When enabled, the :ref:`bluetooth_mesh_srpl_srv` is also enabled. The On-Demand Private Proxy Server
16 The On-Demand Private Proxy Server does not have an API of its own, and relies on a
17 :ref:`bluetooth_mesh_od_cli` to control it. The On-Demand Private Proxy Server model only accepts
20 If present, the On-Demand Private Proxy Server model must only be instantiated on the primary
Dproxy.rst59 advertisement can be configured by the On-Demand Private Proxy Client model.
/Zephyr-latest/include/zephyr/bluetooth/mesh/
Dod_priv_proxy_cli.h17 * @defgroup bt_mesh_od_priv_proxy_cli Bluetooth Mesh On-Demand Private GATT Proxy Client
22 /** On-Demand Private Proxy Client Model Context */
30 /** @brief Optional callback for On-Demand Private Proxy Status messages.
32 * Handles received On-Demand Private Proxy Status messages from a On-Demand Private Proxy
33 * server.The @c state param represents state of On-Demand Private Proxy server.
35 * @param cli On-Demand Private Proxy client that received the status message.
43 * @brief On-Demand Private Proxy Client model composition data entry.
50 /** @brief Get the target's On-Demand Private GATT Proxy state.
61 * @param val_rsp Response buffer for On-Demand Private GATT Proxy value.
67 /** @brief Set the target's On-Demand Private GATT Proxy state.
[all …]
Dod_priv_proxy_srv.h17 * @defgroup bt_mesh_od_priv_proxy_srv Bluetooth Mesh On-Demand Private GATT Proxy Server
23 * @brief On-Demand Private Proxy Server model composition data entry.
Dcfg.h148 /** @brief Get the current Mesh On-Demand Private Proxy state.
150 * @retval 0 or positive value represents On-Demand Private Proxy feature state
151 * @retval -ENOTSUP The On-Demand Private Proxy feature is not supported.
155 /** @brief Set state of Mesh On-Demand Private Proxy.
157 * Support for the On-Demand Private Proxy state must be enabled with @c
160 * @param on_demand_proxy New Mesh On-Demand Private Proxy state. Value of 0x00 means that
161 * advertising with Private Network Identity cannot be enabled on demand.
165 * @retval 0 Successfully changed the Mesh On-Demand Private Proxy feature state.
166 * @retval -ENOTSUP The On-Demand Private Proxy feature is not supported.
/Zephyr-latest/samples/subsys/demand_paging/
DREADME.rst1 .. zephyr:code-sample:: demand-paging
2 :name: Demand paging
3 :relevant-api: mem-demand-paging
5 Leverage demand paging to deal with code bigger than available RAM.
10 This sample demonstrates how demand paging can be leveraged to deal with
12 can be tagged to be loaded into memory on demand, and also be automatically
49 To actually view the underlying demand paging subsystem at work, debug
Dsample.yaml2 description: On-Demand paging of firmware larger than available memory
3 name: demand-paging
/Zephyr-latest/subsys/demand_paging/backing_store/
DKconfig20 demonstration and testing of the demand paging feature.
27 for demand paging. The qemu_x86_tiny.ld linker script puts
29 area, allowing testing of the demand paging mechanism on
33 bool "Backing store for on-demand linker section using semihosting"
36 This is used to do on-demand paging of code and data marked with
49 cases for demand paging assume that there are at least 16 pages of
Dbacking_store_qemu_x86_tiny.c12 * for demand paging. The qemu_x86_tiny.ld linker script puts
14 * area, allowing testing of the demand paging mechanism on
Dram.c17 * demand paging feature. In production there are basically two types of
/Zephyr-latest/kernel/
DKconfig.vm27 as their physical address (demand paging at runtime may later modify
120 bool "Demand paging [EXPERIMENTAL]"
123 Enable demand paging. Requires architecture support in how the kernel
129 bool "Allow on-demand memory mappings"
135 at access time using the demand paging mechanism instead.
164 bool "Gather Demand Paging Statistics"
166 This enables gathering various statistics related to demand paging,
173 bool "Use Timing Functions to Gather Demand Paging Statistics"
176 Use timing functions to gather various demand paging statistics.
179 bool "Gather per Thread Demand Paging Statistics"
[all …]
/Zephyr-latest/subsys/bluetooth/mesh/shell/
Dod_priv_proxy.c36 shell_print(sh, "Unable to send On-Demand Private GATT Proxy Get/Set (err %d)", in cmd_od_priv_gatt_proxy_set()
41 shell_print(sh, "On-Demand Private GATT Proxy is set to 0x%02x", val_rsp); in cmd_od_priv_gatt_proxy_set()
52 "On-Demand Private Proxy Cli commands",
/Zephyr-latest/subsys/bluetooth/mesh/
Dod_priv_proxy_cli.c18 /** On-Demand Private Proxy Client Model Context */
32 LOG_DBG("On-Demand Private Proxy status received: state: %u", state_rsp); in handle_proxy_status()
99 LOG_ERR("On-Demand Private Proxy client not in primary element"); in on_demand_proxy_cli_init()
Dod_priv_proxy_srv.c92 LOG_ERR("On-Demand Private Proxy server cannot extend Private Beacon server"); in od_priv_proxy_srv_init()
104 LOG_WRN("On-Demand Private Proxy server cannot be corresponded by Solicitation PDU " in od_priv_proxy_srv_init()
/Zephyr-latest/subsys/demand_paging/
DKconfig4 menu "Demand Paging modules"
/Zephyr-latest/doc/kernel/memory_management/
Dvirtual_memory.rst15 between physical and virtual memory address spaces, if demand paging
27 Note that demand paging needs to be explicitly enabled.
30 memory space, without enabling demand paging, all virtually
130 some addresses are reserved to support demand paging.
170 The unused physical memory can be mapped in virtual address space on demand.
Ddemand_paging.rst3 Demand Paging
6 Demand paging provides a mechanism where data is only brought into physical
188 mapped and paged-in on demand. Most useful with
212 .. doxygengroup:: mem-demand-paging
217 .. doxygengroup:: mem-demand-paging-eviction
222 .. doxygengroup:: mem-demand-paging-backing-store
/Zephyr-latest/include/zephyr/kernel/mm/
Ddemand_paging.h16 * @defgroup demand_paging Demand Paging
21 * @defgroup mem-demand-paging Demand Paging APIs
215 * @defgroup mem-demand-paging-eviction Eviction Algorithm APIs
317 * @defgroup mem-demand-paging-backing-store Backing Store APIs
374 * Obtain persistent location token for on-demand content
378 * to some fixed storage content to be paged in on demand. This is expected
380 * K_MEM_MAP_UNPAGED flag to create demand mappings at boot time. This may
/Zephyr-latest/include/zephyr/kernel/internal/
Dmm.h34 * Note that when demand paging is active, these will only work with page
133 * the above checks won't be sufficient with demand paging in k_mem_phys_addr()
170 * the above check won't be sufficient with demand paging in k_mem_virt_addr()
210 * frames. It may conflict with anonymous memory mappings and demand paging
244 * It may conflict with anonymous memory mappings and demand paging and
/Zephyr-latest/subsys/demand_paging/eviction/
DKconfig4 # Demand paging sample eviction algorithms
Dnru.c6 * Not Recently Used (NRU) eviction algorithm for demand paging
/Zephyr-latest/samples/subsys/demand_paging/src/
Dmain.c22 * at boot time but rather page-by-page on demand when actually executed.
/Zephyr-latest/kernel/include/
Dmmu.h120 * properties and shouldn't be used generically for demand paging or
337 * @brief Location of the scratch page used for demand paging.
348 * Core kernel demand paging APIs
354 * Counts only those page faults that were handled successfully by the demand
/Zephyr-latest/include/zephyr/kernel/
Dmm.h123 * be allocated initially. Allocation will happen through demand paging when
142 * If demand paging is enabled, it may still be possible to allocate more.
201 * be allocated initially. Allocation will happen through demand paging when

1234