Home
last modified time | relevance | path

Searched full:is (Results 1 – 25 of 5827) sorted by relevance

12345678910>>...234

/Zephyr-latest/modules/
DKconfig.mcux24 Set if the 12B1MSPS SAR ADC module is present in the SoC.
29 Set if the 12-bit ADC (ADC12) module is present in the SoC.
34 Set if the 16-bit ADC (ADC16) module is present in the SoC.
39 Set if the LPADC module is present in the SoC.
44 Set if the L1 or L2 cache is present in the SoC.
49 Set if the clock control module (CCM) module is present in the SoC.
54 Set if the revision 2 of clock control module (CCM) module is present in the SoC.
55 This is present in SoC's such as RT1170
60 Set if the syscon module is present in the SoC.
65 Set if the peripheral clock controller module (PCC) module is
[all …]
/Zephyr-latest/doc/services/portability/
Dcmsis_rtos_v2.rst6 Cortex-M Software Interface Standard (CMSIS) RTOS is a vendor-independent
21 ``osMutexPrioInherit`` is supported by default and is not configurable,
24 ``osMutexRecursive`` is also supported by default. If this attribute is
25 not set, an error is thrown when the same thread tries to acquire
28 ``osMutexRobust`` is not supported in Zephyr.
34 ``osError`` (Unspecified error) is not supported.
38 semaphore_id is in an invalid semaphore state) is not supported.
42 is in an invalid mutex state) is not supported.
46 is in an invalid timer state) is not supported.
50 parameter msgq_id is in an invalid message queue state)
[all …]
/Zephyr-latest/samples/sensor/dht_polling/
DREADME.rst30 It also requires a correct fixture setup when the sensor is present.
50 hs300x@44: temp is 25.31 °C humidity is 30.39 %RH
51 hs300x@44: temp is 25.51 °C humidity is 30.44 %RH
52 hs300x@44: temp is 25.51 °C humidity is 30.37 %RH
53 hs300x@44: temp is 25.51 °C humidity is 30.39 %RH
54 hs300x@44: temp is 25.31 °C humidity is 30.37 %RH
55 hs300x@44: temp is 25.31 °C humidity is 30.35 %RH
56 hs300x@44: temp is 25.51 °C humidity is 30.37 %RH
57 hs300x@44: temp is 25.51 °C humidity is 30.37 %RH
58 hs300x@44: temp is 25.51 °C humidity is 30.39 %RH
[all …]
/Zephyr-latest/tests/bluetooth/host/id/bt_le_oob_get_local/src/
Dtest_suite_invalid_inputs.c29 * - NULL reference is used as an argument for the OOB reference
32 * - An assertion is raised and execution stops
45 * - A valid reference is used as an argument for the OOB information reference
49 * - '-EAGAIN' error code is returned representing invalid values were used.
64 * Test trying to get the local LE Out of Band (OOB) information if the ID used is out of range.
67 * - A valid reference is used as an argument for the OOB information reference
68 * - ID used is out of range or exceeds the maximum value defined by 'CONFIG_BT_ID_MAX'
69 * - 'BT_DEV_READY' bit is set in bt_dev.flags
72 * - '-EINVAL' error code is returned representing invalid values were used.
87 * Test RPA can't be updated while a connection is being established
[all …]
/Zephyr-latest/doc/kernel/memory_management/
Ddemand_paging.rst6 Demand paging provides a mechanism where data is only brought into physical
7 memory as required by current execution context. The physical memory is
16 there is a free page frame. If there is no more free page frames,
17 the eviction algorithm is invoked to select a data page to be paged out,
19 page has been modified after it is first paged in, the data will be
20 written back into the backing store. If no modifications is done or
21 after written back into backing store, the data page is now considered
22 paged out and the corresponding page frame is now free. The paging code
25 page into the free page frame. Now the data page is in physical memory
31 in anticipation that they are required in the near future. This is used to
[all …]
/Zephyr-latest/lib/posix/options/
DKconfig.deprecated5 # This file should be removed after Zephyr 4.0 is released
14 This option is deprecated.
23 This option is deprecated.
32 This option is deprecated.
41 This option is deprecated.
50 This option is deprecated.
59 This option is deprecated.
68 This option is deprecated.
81 This option is deprecated.
90 This option is deprecated.
[all …]
/Zephyr-latest/samples/kernel/condition_variables/simple/
DREADME.rst16 execution based on when the worker thread signals the main thread that is
80 [thread zephyr_app_main] done is 0 which is < 20 so waiting on cond
141 [thread 0] done is now 1. Signalling cond.
143 [thread zephyr_app_main] done is 1 which is < 20 so waiting on cond
144 [thread 1] done is now 2. Signalling cond.
146 [thread zephyr_app_main] done is 2 which is < 20 so waiting on cond
147 [thread 2] done is now 3. Signalling cond.
149 [thread zephyr_app_main] done is 3 which is < 20 so waiting on cond
150 [thread 3] done is now 4. Signalling cond.
152 [thread zephyr_app_main] done is 4 which is < 20 so waiting on cond
[all …]
/Zephyr-latest/doc/services/storage/nvs/
Dnvs.rst7 FIFO-managed circular buffer. The flash area is divided into sectors. Elements
8 are appended to a sector until storage space in the sector is exhausted. Then a
9 new sector in the flash area is prepared for use (erased). Before erasing the
10 sector it is checked that identifier - data pairs exist in the sectors in use,
11 if not the id-data pair is copied.
13 The id is a 16-bit unsigned number. NVS ensures that for each used id there is
19 Each element is stored in flash as metadata (8 byte) and data. The metadata is
20 written in a table starting from the end of a nvs sector, the data is
22 of: id, data offset in sector, data length, part (unused), and a CRC. This CRC is
28 .. note:: The data CRC is checked only when the whole data of the element is read.
[all …]
/Zephyr-latest/tests/bsim/bluetooth/mesh/tests_scripts/priv_beacon/
Dpriv_beacon_interleave.sh10 # - First SNB is advertised after Beacon Interval
11 # - PRB is enabled, SNB disabled, before next interval
12 # - First PRB is advertised
13 # - IVU is initiated
14 # - Second PRB is advertised with IVU flag
15 # - PRB is disabled, SNB enabled: second SNB is advertised
16 # - KR is initiated, third SNB is advertised with new flags (IVU + KR)
17 # - PRB is enabled, SNB is disabled. Third PRB is advertised
/Zephyr-latest/doc/
Dzephyr.doxyfile.in6 # All text after a double hash (##) is considered a comment and is placed in
7 # front of the TAG it is preceding.
9 # All text after a single hash (#) is considered a comment and will be ignored.
10 # The format is:
31 # file that follow. The default is UTF-8 which is also the encoding used for all
35 # The default value is: UTF-8.
39 # The PROJECT_NAME tag is a single word (or a sequence of words surrounded by
41 # project for which the documentation is generated. This name is used in the
43 # The default value is: My Project.
49 # control system is used.
[all …]
/Zephyr-latest/doc/services/logging/
Dcs_stm.rst6 The Arm CoreSight SoC-400 is a comprehensive library of components for the creation of debug and
7 trace functionality within a system. The STM (System Trace Macrocell) is a trace source that
8 is integrated into a CoreSight system, designed primarily for high-bandwidth trace of
9 instrumentation embedded into software. This instrumentation is made up of memory-mapped writes to
12 register sets) which can be independently accessed thus there is no need for locking when various
24 TPIU (Trace Port Interface Unit) or saved in the RAM Circular Buffer which is called ETR (Embedded
25 Trace Router). TPIU is a 5 pin interface (4 data pins and clock) and external tool is required to
27 When ETR is used then one core in the system is responsible for processing that data, for example
33 ETR is a circular RAM buffer to which tracing data is saved. Since it may contain data from
34 various sources additional wrapping protocol is used to multiplex them. ``Coresight Trace
[all …]
/Zephyr-latest/samples/subsys/sip_svc/
DREADME.rst39 Got response of transaction id 0x00 and voltage is 0.846878v
40 Got response of transaction id 0x01 and voltage is 0.858170v
41 Got response of transaction id 0x02 and voltage is 0.860168v
42 Got response of transaction id 0x03 and voltage is 0.846832v
43 Got response of transaction id 0x04 and voltage is 0.858337v
44 Got response of transaction id 0x05 and voltage is 0.871704v
45 Got response of transaction id 0x06 and voltage is 0.859421v
46 Got response of transaction id 0x07 and voltage is 0.857254v
47 Got response of transaction id 0x08 and voltage is 0.858429v
48 Got response of transaction id 0x09 and voltage is 0.859879v
[all …]
/Zephyr-latest/dts/bindings/led/
Dgpio-leds.yaml5 This allows you to define a group of LEDs. Each LED in the group is
6 controlled by a GPIO. Each LED is defined in a child node of the
9 Here is an example which defines three LEDs in the node /leds:
28 - led_0 is pin 1 on gpio0. The LED is on when the pin is low,
29 and off when the pin is high.
30 - led_1 is pin 2 on gpio0. The LED is on when the pin is high,
31 and off when it is low.
32 - led_2 is pin 15 on gpio1. The LED is on when the pin is low,
/Zephyr-latest/tests/bluetooth/host/id/bt_id_create/src/
Dmain.c36 /* This is required to test when the generated address already exists in the ID list */ in bt_addr_le_create_static_custom_fake()
48 * As a NULL is passed to bt_id_create() for the address and 'BT_DEV_ENABLE' is set,
49 * a new random address is generated.
52 * - Input address is NULL
53 * - Input IRK is NULL
54 * - 'BT_DEV_ENABLE' flag is set in bt_dev.flags
58 * - A new identity is created and the address is loaded to bt_dev.id_addr[]
59 * - bt_dev.id_count is incremented
82 * As a NULL is passed to bt_id_create() for the address and 'BT_DEV_ENABLE' is set,
83 * a new random address is generated.
[all …]
/Zephyr-latest/drivers/watchdog/
DKconfig.nxp_fs2619 Device driver initialization priority. Device is connected to SPI bus,
28 watchdog error counter is decremented by 1 each time the watchdog is
38 watchdog is properly refreshed, this counter is incremented by 1. Each
39 time this counter reaches its maximum value and if the next refresh is
40 also good, the fault error counter is decremented by 1. Each time
41 there is a bad watchdog refresh, this counter is reset to 0.
53 watchdog configuration, value 0x0000 is not allowed.
58 If the device is started in DEBUG mode, the driver will exit this mode
59 so that the watchdog is enabled. Otherwise, if the device is in DEBUG
60 mode and this driver is enabled, it will fail to initialize.
[all …]
/Zephyr-latest/doc/connectivity/networking/api/
Dnet_if.rst13 The network interface is a nexus that ties the network device drivers
15 data is transferred via a network interface. The network interfaces cannot be
17 and that section is populated at linking time.
22 :kconfig:option:`CONFIG_NET_VLAN` is enabled. These macros are typically used in
26 by calling ``net_if_down()``. When the device is powered ON, the network
27 interface is also turned ON by default.
50 packet priority. This is typically done in Ethernet networks when virtual LANs
55 If the :kconfig:option:`CONFIG_NET_PROMISCUOUS_MODE` is enabled and if the underlying
56 network technology supports promiscuous mode, then it is possible to receive
57 all the network packets that the network device driver is able to receive.
[all …]
/Zephyr-latest/tests/bluetooth/host/id/bt_id_reset/src/
Dtest_suite_invalid_inputs.c26 * - BT_ID_DEFAULT value is used for the ID
27 * - Input address is NULL
28 * - Input IRK is NULL
31 * - '-EINVAL' error code is returned representing invalid values were used.
43 * Test resetting ID value that is equal to bt_dev.id_count
46 * - bt_dev.id_count is greater than 0
47 * - ID value used is equal to bt_dev.id_count
48 * - Input address is NULL
49 * - Input IRK is NULL
52 * - '-EINVAL' error code is returned representing invalid values were used.
[all …]
/Zephyr-latest/tests/cmake/hwm/board_extend/oot_root/boards/native/native_sim_extend/
DKconfig8 This kconfig is set when the extended variant board config fragment
9 is supposed to be sourced, that is when oot variant defines 'extends:'
15 This kconfig is promptless and is expected to be set through the
22 This kconfig is promptless and is expected to be set through the
29 This kconfig is set when the extended variant board defconfig fragment
30 is supposed to be sourced, that is when oot variant defines 'extends:'
/Zephyr-latest/drivers/timer/
DKconfig.nrf_xrtc14 System clock source is initiated but does not wait for clock readiness.
15 When this option is picked, system clock may not be ready when code relying
16 on kernel API is executed. Requested timeouts will be prolonged by the
22 System clock source initialization waits until clock is available. In some
25 it is ready. When this option is picked, system clock is available after
26 system clock driver initialization but it may be less accurate. Option is
33 System clock source initialization waits until clock is stable. When this
34 option is picked, system clock is available and stable after system clock
/Zephyr-latest/include/zephyr/net/
Dnet_event.h138 /** Event emitted when the network interface is taken down manually. */
146 /** Event emitted when an IPv6 address is added to the system. */
150 /** Event emitted when an IPv6 address is removed from the system. */
154 /** Event emitted when an IPv6 multicast address is added to the system. */
158 /** Event emitted when an IPv6 multicast address is removed from the system. */
162 /** Event emitted when an IPv6 prefix is added to the system. */
166 /** Event emitted when an IPv6 prefix is removed from the system. */
170 /** Event emitted when an IPv6 multicast group is joined. */
174 /** Event emitted when an IPv6 multicast group is left. */
178 /** Event emitted when an IPv6 router is added to the system. */
[all …]
/Zephyr-latest/include/zephyr/ipc/
Dipc_service.h43 * - INSTANCE: an instance is the external representation of a physical
47 * instance is peculiar to each backend. For example for
48 * OpenAMP-based backends, an instance is usually represented by a
52 * It's important to note that an instance per se is not used to
61 * The creation of the instances is left to the backend (usually at
62 * init time), while the registration of the endpoints is left to
65 * - ENDPOINT: an endpoint is the entity the user must use to send / receive
67 * endpoint is always associated to an instance.
91 * # is ready to be used
142 * It is registered during endpoint registration.
[all …]
/Zephyr-latest/soc/silabs/
DKconfig18 Set if the Back-Up Real Time Counter (BURTC) HAL module is used.
24 Set if the Core interrupt handling (CORE) HAL module is used.
29 Set if the Analog to Digital Converter (ADC) HAL module is used.
34 Set if the Incremental Analog to Digital Converter (IADC) HAL module is used.
39 Set if the Ultra Low Energy Timer/Counter (CRYOTIMER) HAL module is used.
44 Set if the Energy Management Unit (EMU) HAL module is used.
49 Set if the General Purpose Input/Output (GPIO) HAL module is used.
54 Set if the Inter-Integrated Circuit Interface (I2C) HAL module is used.
59 Set if the Low Energy Timer (LETIMER) HAL module is used.
65 HAL module is used.
[all …]
/Zephyr-latest/doc/connectivity/networking/
Dnet_config_guide.rst29 is used when :kconfig:option:`CONFIG_NET_BUF_FIXED_DATA_SIZE` is set.
30 This is the default setting. The default size of the buffer is 128 bytes.
32 The :kconfig:option:`CONFIG_NET_BUF_VARIABLE_DATA_SIZE` is an experimental
33 setting. There each net_buf data portion is allocated from a memory pool and
35 When data is received from the network, it is placed into net_buf data portion.
46 there is some overhead involved for each net_buf. For these reasons the default
47 network buffer size is set to 128 bytes.
49 The variable size data buffer feature is marked as experimental as it has not
52 data we need for the network data. The extra cost here is the amount of time
53 that is needed when dynamically allocating the buffer from the memory pool.
[all …]
/Zephyr-latest/dts/bindings/memory-controllers/
Datmel,sam-smc.yaml10 The SMC is clocked through the Master Clock (MCK) which is controlled by the
14 memory devices. The reg property is set to the device's Chip Select.
33 The above example configures a is66wv51216dbll-55 device. The device is a
35 and OE inputs respectively. Assuming that MCK is 120MHz (cpu at full speed)
36 each MCK cycle will be equivalent to 8ns. Since the memory full cycle is
38 7 pulses (56ns). The atmel,smc-cycle-timing is composed of three parts:
39 setup, pulse and hold. The setup is used to address the memory. The pulse
40 is the time used to read/write. The hold is used to release memory. For the
42 (6 cycles) for CPU read/write and no hold time is required.
43 Note: Since no hold parameter is available at SMC the atmel,smc-cycle-timing
[all …]
/Zephyr-latest/arch/arm/include/cortex_m/
Dcmse.h44 * Obtained region is valid only if:
45 * - the function is called from privileged mode
46 * - the MPU is implemented and enabled
49 * @param addr The address for which the MPU region is requested
65 * @param addr The address for which the readability is requested
68 * mode is privileged or unprivileged.
70 * @return 1 if address is readable, 0 otherwise.
85 * @param addr The address for which the RW ability is requested
88 * mode is privileged or unprivileged.
90 * @return 1 if address is Read and Writable, 0 otherwise.
[all …]

12345678910>>...234