Searched refs:policies (Results 1 – 25 of 27) sorted by relevance
12
8 # For translating POSIX scheduler policies and priorities to
464 static const int policies[] = { in ZTEST() local494 ARRAY_FOR_EACH(policies, policy) { in ZTEST()499 pmin = sched_get_priority_min(policies[policy]); in ZTEST()502 pmax = sched_get_priority_max(policies[policy]); in ZTEST()553 pthread_attr_setschedpolicy(&attr, policies[policy])); in ZTEST()562 zassert_ok(pthread_attr_setschedpolicy(&attr, policies[policy]), in ZTEST()
45 bool "Generate VIF policies of USB-C in XML format"48 Generate XML file containing VIF policies during project build.
4 # Generates USB-C VIF policies in XML format from device tree.
13 system security policies that are applied to applications launched from the
11 how to generate USB VIF policies in XML format using the USB-C subsystem. The
7 maintenance and enhancements there are some general policies that should14 configuration structure. The following policies should be followed when
34 Accepted policies
13 Zephyr provides managers for several coordination policies. These
18 policies whenever the kernel becomes idle. The kernel informs the
21 * Following policies can be applied when requested space cannot be allocated:
84 The power management subsystem supports the following power management policies:
148 Adding more constraints, the Zephyr project has demanding policies164 enforces policies and maintains such combinatorial explosions under some
171 used to set Flash and SRAM default access policies and
38 This page summarizes a list of policies and best practices which aim at202 counterpart following the policies described in296 Licensing requirements and policies326 License policies argument
930 have the following access policies applied for all threads, including940 impose additional policies on the memory map, which may be global
403 same device policies for initialization level and priority apply.
25 write-back policies for basic hardware and driver function. Note that most
606 There are some known exceptions to these policies currently in Zephyr:
444 Arm memory map policies, allowing for privileged-only RWX permissions on SRAM).
177 :ref:`modifying_contributions` describes additional recommended policies
463 policies that could include locking interrupts and spinning forever
2048 # Generate USB-C VIF policies in XML format
1373 * :github:`13075` - Review memory protection Kconfig policies for consistency and sanity
1443 * :github:`26172` - Zephyr Master/Slave not conforming with Core Spec. 5.2 connection policies
