Searched refs:aware (Results 26 – 50 of 58) sorted by relevance
123
184 Be aware that **async** is orthogonal to context-switching. Some APIs
43 value. Please be aware that increasing it for long-running test cases
163 a client until it becomes change-aware."
547 static bool set_change_aware_no_store(struct gatt_cf_cfg *cfg, bool aware) in set_change_aware_no_store() argument551 if (aware) { in set_change_aware_no_store()557 LOG_DBG("peer is now change-%saware", aware ? "" : "un"); in set_change_aware_no_store()562 static void set_change_aware(struct gatt_cf_cfg *cfg, bool aware) in set_change_aware() argument564 bool changed = set_change_aware_no_store(cfg, aware); in set_change_aware()
59 - TrustZone |reg| aware and securable peripherals
256 Be aware that the parameters passed to :command:`lfs` in the example
398 "Devicetree-aware" :ref:`device drivers <device_model_api>` should create a403 Writing a devicetree-aware driver begins by defining a :ref:`devicetree binding
57 - TrustZone |reg| aware and securable peripherals
61 - TrustZone |reg| aware and securable peripherals
143 the controller needs to be made aware of it.
419 locks (:c:struct:`k_spinlock`) or thread-aware locks (:c:struct:`k_sem`,445 Be aware that if the lock is held by a thread with a lower priority than the
18 core mode because the network stack is not aware of SMP
11 access the STM without being aware of each other. Each core has 65536 stimulus ports (identical
622 the log message is not aware of the number of backends in the root domain.
116 stakeholders are made aware of the change.
40 there are a few side effects to be aware of when migrating to Picolibc.
32 * SMP-aware scheduler
352 speed. Another downside of defaults is that user may not be aware of them,
328 Note when writing the tests with ``bs_tests`` one needs to be aware that other
777 will not be aware of the application. Instead, you must manually flash and
423 You can put them elsewhere, but be aware:
333 processor faults. Developers need to be aware of this limitation.
312 Common sense applies, but be aware that ``select`` often causes issues in
234 The Zephyr kernel is only aware of the simulated time as provided by the
