/Zephyr-latest/samples/subsys/zbus/work_queue/ |
D | README.rst | 9 …ifferent reaction options. First, the observer can react "instantaneously" by using a listener cal… 28 I: Sensor msg processed by CALLBACK fh1: temp = 10, press = 1, humidity = 100 29 I: Sensor msg processed by CALLBACK fh2: temp = 10, press = 1, humidity = 100 30 I: Sensor msg processed by CALLBACK fh3: temp = 10, press = 1, humidity = 100 31 I: Sensor msg processed by WORK QUEUE handler dh1: temp = 10, press = 1, humidity = 100 32 I: Sensor msg processed by WORK QUEUE handler dh2: temp = 10, press = 1, humidity = 100 33 I: Sensor msg processed by WORK QUEUE handler dh3: temp = 10, press = 1, humidity = 100 34 I: Sensor msg processed by THREAD handler 1: temp = 10, press = 1, humidity = 100 35 I: Sensor msg processed by THREAD handler 2: temp = 10, press = 1, humidity = 100 36 I: Sensor msg processed by THREAD handler 3: temp = 10, press = 1, humidity = 100 [all …]
|
D | sample.yaml | 12 - "I: Sensor msg processed by CALLBACK fh1: temp = 10, press = 1, humidity = 100" 13 - "I: Sensor msg processed by CALLBACK fh2: temp = 10, press = 1, humidity = 100" 14 - "I: Sensor msg processed by CALLBACK fh3: temp = 10, press = 1, humidity = 100" 15 - "I: Sensor msg processed by WORK QUEUE handler dh1: temp = 10, press = 1, humidity = 100" 16 - "I: Sensor msg processed by WORK QUEUE handler dh2: temp = 10, press = 1, humidity = 100" 17 - "I: Sensor msg processed by WORK QUEUE handler dh3: temp = 10, press = 1, humidity = 100" 18 - "I: Sensor msg processed by THREAD handler 1: temp = 10, press = 1, humidity = 100" 19 - "I: Sensor msg processed by THREAD handler 2: temp = 10, press = 1, humidity = 100" 20 - "I: Sensor msg processed by THREAD handler 3: temp = 10, press = 1, humidity = 100" 21 - "I: Sensor msg processed by CALLBACK fh1: temp = 20, press = 2, humidity = 200" [all …]
|
/Zephyr-latest/tests/cmake/snippets/src/ |
D | main.c | 9 /* Initial test config values set by `prj.conf` */ 14 /* Test config values set by the `foo` snippet */ 18 /* Test config values set by the `bar` snippet */ 29 * correspond to the initial values set by `prj.conf`. in ZTEST() 37 * config values correspond to the values set by the `foo` in ZTEST() 46 * config values correspond to the values set by the `bar` in ZTEST() 56 * corresponds to the value set by the `bar` snippet. in ZTEST() 65 * corresponds to the value set by the `foo` snippet. in ZTEST() 79 * When no snippet is applied, test that both `deleted-by-foo` in ZTEST() 80 * and `deleted-by-bar` nodes exist, and that none of the nodes in ZTEST() [all …]
|
/Zephyr-latest/tests/cmake/snippets/ |
D | Kconfig | 10 # Snippet test types used by the test implementation to steer the test logic 42 # Test values set by the snippet config overlays and tested by the test logic 44 int "Test value set by the 'foo' snippet config overlay" 46 This option's value should be overridden by the 'foo' snippet config 50 int "Test value set by the 'foo' snippet config overlay" 52 This option's value should be overridden by the 'foo' snippet config 56 int "Test value set by the snippet config overlays" 58 This option's value should be overridden by the snippet config
|
D | app.overlay | 2 /* This node will be deleted by the `foo` snippet. */ 3 deleted-by-foo {}; 5 /* This node will be deleted by the `bar` snippet. */ 6 deleted-by-bar {};
|
/Zephyr-latest/scripts/ |
D | requirements-base.txt | 6 # used by various build scripts 9 # used by dts generation to parse binding YAMLs, also used by 10 # twister to parse YAMLs, by west, zephyr_module,... 13 # YAML validation. Used by zephyr_module. 16 # used by west_commands 30 # intelhex used by mergehex.py
|
/Zephyr-latest/include/zephyr/crypto/ |
D | cipher.h | 113 * cipher operation. To be populated by crypto driver on return from 114 * begin_session() based on the algo/mode chosen by the app. 118 /** To be populated by the app before calling begin_session() */ 129 * populated by the begin_session() API. 138 * by the driver on return from begin_session(). 143 * completion callback happens for async ops. Totally managed by the 149 * in a session. To be populated by the app before calling 158 /** Cryptographic keylength in bytes. To be populated by the app 165 * To be populated by the app before calling begin_session(). 166 * An app can obtain the capability flags supported by a hw/driver [all …]
|
/Zephyr-latest/doc/connectivity/networking/api/ |
D | net_if.rst | 19 Network interfaces are created by ``NET_DEVICE_INIT()`` macro. 25 The network interface can be turned ON by calling ``net_if_up()`` and OFF 26 by calling ``net_if_down()``. When the device is powered ON, the network 27 interface is also turned ON by default. 29 The network interfaces can be referenced either by a ``struct net_if *`` 30 pointer or by a network interface index. The network interface can be 31 resolved from its index by calling ``net_if_get_by_index()`` and from interface 32 pointer by calling ``net_if_get_by_iface()``. 38 by DHCPv4, for example. If needed though, the application can set a device's 52 lower priority packets. The traffic class setup can be configured by [all …]
|
/Zephyr-latest/scripts/west_commands/zspdx/ |
D | licenses.py | 85 "CC-BY-1.0", 86 "CC-BY-2.0", 87 "CC-BY-2.5", 88 "CC-BY-3.0", 89 "CC-BY-3.0-AT", 90 "CC-BY-3.0-US", 91 "CC-BY-4.0", 92 "CC-BY-NC-1.0", 93 "CC-BY-NC-2.0", 94 "CC-BY-NC-2.5", [all …]
|
/Zephyr-latest/drivers/sensor/st/lsm6ds0/ |
D | Kconfig | 22 Enable/disable accelerometer X axis totally by stripping everything 29 Enable/disable accelerometer Y axis totally by stripping everything 36 Enable/disable accelerometer Z axis totally by stripping everything 43 Enable/disable gyroscope X axis totally by stripping everything 50 Enable/disable gyroscope Y axis totally by stripping everything 57 Enable/disable gyroscope Z axis totally by stripping everything 63 Enable/disable temperature totally by stripping everything related in 82 Data rates supported by the chip are 0, 15, 60, 119, 238, 476, 99 Data rates supported by the chip are 0, 10, 50, 119, 238, 476, 952.
|
/Zephyr-latest/samples/arch/smp/pi/ |
D | README.rst | 13 By changing the value of CONFIG_MP_MAX_NUM_CPUS on SMP systems, you 24 This project outputs Pi values calculated by each thread and in the end total time 40 Calculate first 240 digits of Pi independently by 16 threads. 41 Pi value calculated by thread #0: 3141592653589793238462643383279502884197... 42 Pi value calculated by thread #1: 3141592653589793238462643383279502884197... 44 Pi value calculated by thread #14: 314159265358979323846264338327950288419... 45 Pi value calculated by thread #15: 314159265358979323846264338327950288419... 46 All 16 threads executed by 4 cores in 28 msec
|
/Zephyr-latest/doc/services/portability/ |
D | cmsis_rtos_v2.rst | 21 ``osMutexPrioInherit`` is supported by default and is not configurable, 24 ``osMutexRecursive`` is also supported by default. If this attribute is 37 ``osErrorResource`` (the semaphore specified by parameter 41 ``osErrorResource`` (mutex specified by parameter mutex_id 45 ``osErrorResource`` (the timer specified by parameter timer_id 49 ``osErrorResource`` (the message queue specified by 54 ``osErrorResource`` (the message queue specified by 59 ``osErrorResource`` (the memory pool specified by 64 ``osErrorResource`` (the memory pool specified by 70 and osFlagsErrorResource (Event flags object specified by [all …]
|
/Zephyr-latest/doc/develop/optimizations/ |
D | footprint.rst | 11 should start the optimization process by reviewing all stack sizes and adjusting 15 Set to 2048 by default 18 Set to 1024 by default 21 Set to 320 by default 24 Set to 1024 by default 27 Set to 1024 by default, depends on userspace feature. 33 Some peripherals are enabled by default. You can disable unused 43 The following options are enabled by default to provide more information about
|
/Zephyr-latest/modules/trusted-firmware-m/ |
D | Kconfig.tfm.crypto_modules | 22 Unset this option if the functionality provided by 'crypto_key_management.c' 30 Unset this option if the functionality provided by 'crypto_aead.c' 38 Unset this option if the functionality provided by 'crypto_mac.c' 46 Unset this option if the functionality provided by 'crypto_hash.c' 54 Unset this option if the functionality provided by 'crypto_cipher.c' 62 Unset this option if the encrypt functionality provided by 'crypto_asymmetric.c' 70 Unset this option if the sign functionality provided by 'crypto_asymmetric.c' 78 Unset this option if the functionality provided by 'crypto_key_derivation.c'
|
/Zephyr-latest/doc/connectivity/bluetooth/api/mesh/ |
D | proxy.rst | 8 option is set. The Proxy feature state is controlled by the :ref:`bluetooth_mesh_models_cfg_srv`, 12 which is controlled by the :ref:`bluetooth_mesh_models_cfg_cli`. 20 advertise with Private Network Identity and Private Node Identity types, which is controlled by the 21 :ref:`bluetooth_mesh_models_priv_beacon_cli`. By advertising with this set of identification types, 33 To solicit the node, the legacy device can send a Solicitation PDU by calling the 40 sequence number is maintained by the legacy device and is incremented for every new Solicitation PDU 44 List (SRPL). The SRPL protects the solicitation mechanism from replay attacks by storing 46 processed by the node. The delay between updating the SRPL and storing the change to the persistent 47 storage is defined by :kconfig:option:`CONFIG_BT_MESH_RPL_STORE_TIMEOUT`. 52 SRPL on the target by calling the :func:`bt_mesh_sol_pdu_rpl_clear` function. Communication between [all …]
|
/Zephyr-latest/tests/cmake/snippets/extra_snippet_root/snippets/bar/ |
D | bar.overlay | 2 /delete-node/ deleted-by-bar; 3 /delete-node/ added-by-foo; 5 /* This node will be deleted by the `foo` snippet if applied. */ 6 added-by-bar {};
|
/Zephyr-latest/dts/bindings/dma/ |
D | dma-controller.yaml | 20 not reserved by firmware and are available to the 25 description: Number of DMA channels supported by the controller 29 description: Number of DMA request signals supported by the controller. 33 description: Memory address alignment requirement for DMA buffers used by the controller. 37 description: Memory size alignment requirement for DMA buffers used by the controller. 41 description: Minimal chunk of data possible to be copied by the controller.
|
/Zephyr-latest/soc/raspberrypi/rpi_pico/rp2040/ |
D | Kconfig | 25 # Flash type used by the SoC. The board should select the one used. 31 by the board definition, not the user. 37 Should be selected by the board definition, not the user. 43 by the board definition, not the user. 49 by the board definition, not the user. 55 by the board definition, not the user.
|
/Zephyr-latest/drivers/display/ |
D | Kconfig.mcux_elcdif | 25 framebuffers are allocated by the driver, and the application 26 implements double framebuffering by always calling display_write with 37 int "Framebuffer size required by the eLCDIF driver" 73 bool "Rotate display by 0 degrees" 75 Rotate display by 0 degrees. Primarily useful for testing, 79 bool "Rotate display by 90 degrees" 81 Rotate display counter-clockwise by 90 degrees. 85 bool "Rotate display by 180 degrees" 87 Rotate display counter-clockwise by 180 degrees 90 bool "Rotate display by 270 degrees" [all …]
|
/Zephyr-latest/tests/bsim/ |
D | generate_coverage_report.sh | 15 Coverage files will be searched for in the folder pointed by 16 the variable WORK_DIR which by default is 19 By default the output will be placed in \${WORK_DIR}/lcov_html/. 20 You can override this by setting the variable OUTPUT_DIR 22 By default it takes all coverage information generated by all run tests 23 but you can limit the search by setting WORK_DIR to some subfolder 25 You can also merge in the twister coverage report by setting
|
/Zephyr-latest/tests/cmake/snippets/snippets/foo/ |
D | foo.overlay | 2 /delete-node/ deleted-by-foo; 3 /delete-node/ added-by-bar; 5 /* This node will be deleted by the `bar` snippet if applied. */ 6 added-by-foo {};
|
/Zephyr-latest/doc/ |
D | requirements.txt | 14 # YAML validation. Used by zephyr_module. 18 # Used by pytest-twister-harness plugin (imported by autodoc) 25 # Used by the Zephyr domain to organize code samples
|
/Zephyr-latest/ |
D | LICENSE | 10 and distribution as defined by Sections 1 through 9 of this document. 12 "Licensor" shall mean the copyright owner or entity authorized by 16 other entities that control, are controlled by, or are under common 19 direction or management of such entity, whether by contract or 24 exercising permissions granted by this License. 36 Object form, made available under the License, as indicated by a 45 separable from, or merely link (or bind by name) to the interfaces of, 51 submitted to Licensor for inclusion in the Work by the copyright owner 52 or by an individual or Legal Entity authorized to submit on behalf of 57 and issue tracking systems that are managed by, or on behalf of, the [all …]
|
/Zephyr-latest/drivers/dma/ |
D | Kconfig.nxp_sof_host_dma | 5 bool "NXP DMA driver used by SOF's host component" 9 Enable NXP's DMA driver used by 12 is used by the SOF host component to 25 which shall be used by entities employing 30 no alignment restrictions imposed by memcpy.
|
/Zephyr-latest/doc/kernel/data_structures/ |
D | index.rst | 7 used within the kernel, but useful by application code in general. 13 data structures. The "node" data is the only struct used by the 15 indicate what user data is "owned" by that node. Instead, the 21 allocate node objects because the memory is provided by the user). 24 them is not threadsafe by default. These are data structures, not 26 needed will be provided by the user. Some of the provided data
|