| /Zephyr-Core-3.6.0/subsys/bindesc/ |
| D | Kconfig.version | 14 The kernel version string, such as "3.4.0"
19 The major version number, such as 3 in 3.4.0
24 The minor version number, such as 4 in 3.4.0
29 The patchlevel version number, such as 0 in 3.4.0
34 The kernel version as binary coded decimal, computed as
36 3.4.0 would be represented as 0x30400
41 The app version string, such as "1.0.0"
46 The app major version number, such as 1 in 1.0.0
51 The app minor version number, such as 0 in 1.0.0
56 The app patchlevel version number, such as 0 in 1.0.0
[all …]
|
| D | Kconfig.build_time | 28 The year the image was compiled, such as 2023
33 The month the image was compiled, such as 5 (May)
38 The day of the month the image was compiled, such as 9
43 The hour of the day the image was compiled, such as 13 in 13:34:52
48 The minute the image was compiled, such as 34 in 13:34:52
53 The second the image was compiled, such as 52 in 13:34:52
56 bool "Build time as UNIX time"
62 bool "Build date and time as string"
64 The date and time of compilation as a string, such as "2023-09-29T17:43:14+0000"
67 bool "Build date as string"
[all …]
|
| D | Kconfig.host_info | 19 The C compiler name, such as "GNU"
24 The C compiler version, such as "12.3.0"
29 The C++ compiler name, such as "GNU"
34 The C++ compiler version, such as "12.3.0"
|
| /Zephyr-Core-3.6.0/drivers/clock_control/ |
| D | Kconfig.stm32 | 64 Use EXT_HSE as source of MCO1
74 Use LSE as source of MCO1
85 Use HSE as source of MCO1
91 Use LSI as source of MCO1
97 Use MSI as source of MCO1
107 Use HSI as source of MCO1
113 Use HSI16 as source of MCO1
121 Use HSI48 as source of MCO1
127 Use PLLCLK as source of MCO1
134 Use PLLQ as source of MCO1
[all …]
|
| /Zephyr-Core-3.6.0/dts/bindings/ethernet/ |
| D | silabs,gecko-ethernet.yaml | 30 description: location of RMII pins, configuration defined as <location>
36 description: location of MDC and MDIO pins, configuration defined as <location>
42 description: PHY MDC individual pin configuration defined as <location port pin>
47 description: PHY MDIO individual pin configuration defined as <location port pin>
53 description: Reference clock individual pin configuration defined as <location port pin>
58 description: Receive data valid individual pin configuration defined as <location port pin>
63 description: Transmit data 0 individual pin configuration defined as <location port pin>
68 description: Transmit data 1 individual pin configuration defined as <location port pin>
73 description: Transmit enable individual pin configuration defined as <location port pin>
78 description: Receive data 0 individual pin configuration defined as <location port pin>
[all …]
|
| /Zephyr-Core-3.6.0/doc/connectivity/networking/conn_mgr/figures/ |
| D | integration_diagram_detailed.drawio | 8 <mxGeometry x="516" y="-192" width="465" height="407" as="geometry" />
11 <mxGeometry x="544" y="260" width="310" height="177" as="geometry" />
14 <mxGeometry x="646" y="-68" width="164" height="30" as="geometry" />
17 <mxGeometry x="285" y="-122" width="116" height="559" as="geometry" />
20 <mxGeometry x="634" y="273" width="208" height="75" as="geometry" />
23 <mxGeometry x="641" y="289" width="60" height="30" as="geometry" />
26 <mxGeometry x="775" y="289" width="60" height="30" as="geometry" />
29 <mxGeometry x="708" y="289" width="60" height="30" as="geometry" />
32 <mxGeometry x="634" y="361" width="208" height="70" as="geometry" />
35 <mxGeometry x="641" y="389" width="60" height="30" as="geometry" />
[all …]
|
| D | integration_diagram_simplified.drawio | 8 <mxGeometry x="527" y="-207" width="195" height="261" as="geometry" />
11 <mxGeometry x="574" y="-81" width="164" height="30" as="geometry" />
14 <mxGeometry x="271" y="-122" width="116" height="348" as="geometry" />
17 <mxGeometry x="714" y="173" width="108" height="51" as="geometry" />
20 <mxGeometry x="584" y="22" width="164" height="30" as="geometry" />
23 <mxGeometry x="596" y="128" width="164" height="30" as="geometry" />
26 <mxGeometry x="397" y="208" width="164" height="30" as="geometry" />
29 <mxGeometry relative="1" as="geometry" />
32 <mxGeometry x="552" y="-35" width="147" height="50" as="geometry" />
35 <mxGeometry relative="1" as="geometry" />
[all …]
|
| /Zephyr-Core-3.6.0/doc/connectivity/networking/api/ |
| D | gptp.rst | 13 This gPTP stack supports the protocol and procedures as defined in
14 the `IEEE 802.1AS-2011 standard`_ (Timing and Synchronization for
21 `IEEE 802.1AS-2011 standard`_. Mandatory requirements for a full-duplex
22 point-to-point link endpoint, as defined in Annex A of the standard,
26 interfaces (also defined as "ports" in the standard) and thus act as
27 a 802.1AS bridge. However, this mode of operation has not been validated on
57 Only two Application Interfaces as defined in section 9 of the standard
72 .. _IEEE 802.1AS-2011 standard:
73 https://standards.ieee.org/findstds/standard/802.1AS-2011.html
|
| /Zephyr-Core-3.6.0/doc/kernel/data_structures/ |
| D | rbtree.rst | 11 conventional red/black tree as described by multiple academic sources.
19 within an rbtree must be provided as a predicate function by the user.
22 operations are attempted. This function should, as its name suggests,
28 As with the slist and dlist containers, nodes within an rbtree are
29 represented as a :c:struct:`rbnode` structure which exists in
33 the binary tree topology and "manually" traverse the tree as it is for
41 provided node pointer exists as an element within the tree. As
61 buffer instead where needed to avoid the dynamic allocation). As with
69 As described, the Zephyr rbtree implementation is a conventional
70 red/black tree as described pervasively in academic sources. Low
[all …]
|
| /Zephyr-Core-3.6.0/samples/net/lwm2m_client/ |
| D | Kconfig | 12 This is used as client endpoint name as well as PSK ID.
20 PSK key as a hex string.
36 LwM2M server address. Write as a full URI including optional port number.
38 When DNS resolver is enabled, DNS domain names could be used as well.
|
| /Zephyr-Core-3.6.0/samples/subsys/portability/cmsis_rtos_v2/philosophers/ |
| D | README.rst | 12 threads of differing priorities, as well as mutex/semaphore and thread sleeping
18 are shown as well, such as STARVING when the philosopher is hungry but the
29 on QEMU as follows:
56 priorities, as well as semaphores and thread sleeping.
|
| /Zephyr-Core-3.6.0/tests/posix/eventfd/ |
| D | Kconfig | 31 In order to get a true benchmark, there should be as few branches
32 as possible on the hot path. Say 'y' here to add extra assertions
33 on the hot path as well to verify functionality.
38 In order to get a true benchmark, there should be as few branches
39 as possible on the hot path. Say 'y' here to skip reporting.
|
| /Zephyr-Core-3.6.0/samples/drivers/dac/ |
| D | README.rst | 24 :ref:`nucleo_l073rz_board` as follows:
35 :ref:`nucleo_l152re_board` as follows:
46 :ref:`nucleo_f767zi_board` as follows:
57 :ref:`stm32f3_disco_board` as follows:
68 :ref:`nucleo_f429zi_board` as follows:
79 :ref:`stm32l562e_dk_board` as follows:
90 :ref:`nucleo_l552ze_q_board` as follows:
100 The sample can be built and executed for the :ref:`twr_ke18f` as
114 The sample can be built and executed for the :ref:`frdm_k64f` as
127 The BL652 DVK PCB contains a footprint for a MCP4725 to use as an external
[all …]
|
| /Zephyr-Core-3.6.0/tests/drivers/gpio/gpio_api_1pin/src/ |
| D | test_config.c | 43 * - Verify that configuring the pin as an output without initializing it
46 * gpio_pin_set_raw function if pin is configured as an input.
59 zassert_equal(ret, 0, "Failed to configure the pin as an output"); in ZTEST()
92 /* Verify that configuring the pin as an output without initializing it in ZTEST()
108 /* Verify that configuring the pin as an output without initializing it in ZTEST()
117 * gpio_pin_set_raw function if pin is configured as an input. in ZTEST()
120 zassert_equal(ret, 0, "Failed to configure the pin as an input"); in ZTEST()
139 * used as a sign off test.
143 * as input is high. Drivers that do not support Open Drain flag
146 * pin low value if the same pin configured as input is high.
[all …]
|
| /Zephyr-Core-3.6.0/samples/subsys/portability/cmsis_rtos_v1/philosophers/ |
| D | README.rst | 12 threads of differing priorities, as well as mutex/semaphore and thread sleeping
18 are shown as well, such as STARVING when the philosopher is hungry but the
29 on QEMU as follows:
56 priorities, as well as semaphores and thread sleeping.
|
| /Zephyr-Core-3.6.0/include/zephyr/arch/arc/ |
| D | arc_addr_types.h | 13 * - Zephyr defines paddr_t as a uintptr_t
14 * - MWDT defines paddr_t as a unsigned long
16 * paddr_t as a unsigned long for the case when MWDT toolchain is used as
|
| /Zephyr-Core-3.6.0/tests/drivers/gpio/gpio_basic_api/dts/bindings/ |
| D | test-gpio-basic-api.yaml | 18 Identity of a GPIO that will be configured as an output. This
19 must be on the same device as in-gpios, and physically
26 Identity of a GPIO that will be configured as an input. This
27 must be on the same device as out-gpios,and physically
|
| /Zephyr-Core-3.6.0/doc/develop/languages/c/ |
| D | index.rst | 11 available as part of the C header files under the :file:`include` directory, so
15 The ``main()`` function must have the return type of ``int`` as Zephyr
16 applications run in a "hosted" environment as defined by the C
28 as C99) such as those listed below, effectively requiring the use of a compiler
39 release of the ISO C standard (ISO/IEC 9899:2011, hereinafter referred to as
40 C11) such as the type-generic expressions using the ``_Generic`` keyword. For
41 example, the :c:func:`cbprintf` component, used as the default formatted output
78 C defines standard formatted output functions such as ``printf`` and
114 <memory_management_api>` supported by the Zephyr kernel such as
118 C standard dynamic memory management interface functions such as
|
| /Zephyr-Core-3.6.0/doc/_scripts/ |
| D | gen_helpers.py | 12 Writes 's' as the contents of <out_dir>/<filename>, but only if it
20 with open(path, "r", encoding="utf-8") as f:
23 except OSError as e:
27 with open(path, "w", encoding="utf-8") as f:
|
| /Zephyr-Core-3.6.0/dts/bindings/serial/ |
| D | silabs,gecko-usart.yaml | 23 description: RX pin configuration defined as <location port pin>
27 description: TX pin configuration defined as <location port pin>
31 description: RTS pin configuration defined as <location port pin>
35 description: CTS pin configuration defined as <location port pin>
|
| /Zephyr-Core-3.6.0/drivers/sensor/iis2iclx/ |
| D | Kconfig | 77 bool "LIS2MDL as external sensor"
80 bool "IIS2MDC as external sensor"
83 bool "LPS22HH as external sensor"
86 bool "HTS221 as external sensor"
89 bool "LPS22HB as external sensor"
|
| /Zephyr-Core-3.6.0/doc/connectivity/bluetooth/api/ |
| D | connection_mgmt.rst | 9 (such as the remote address) can be acquired using the
21 define callbacks for connection & disconnection events, as well as other
22 events related to a connection such as a change in the security level or
23 the connection parameters. When acting as a central the application will
|
| /Zephyr-Core-3.6.0/.github/ISSUE_TEMPLATE/ |
| D | 007_ext-source.md | 22 or as a module, and why. If the mode of integration is a module, suggest a
29 choose to identify a single maintainer only or add collaborators as well
34 in the main tree or as a module (pointing to your own fork for now). Make sure
35 the PR is correctly labeled as "DNM"
57 will it be included via an abstraction layer with this component as a
66 Please use an SPDX identifier (https://spdx.org/licenses/), such as
|
| /Zephyr-Core-3.6.0/soc/arm/atmel_sam0/common/ |
| D | Kconfig.samd2x | 9 Wait states to set for NVM. Consult the datasheet as these are highly
16 This can then be selected as the main clock reference for the SOC.
22 This can then be selected as the main clock reference for the SOC.
28 This can then be selected as the main clock reference for the SOC.
42 This can then be selected as the main clock reference for the SOC.
65 Main clocks, such as the CPU and AHB clocks will be derived from
|
| /Zephyr-Core-3.6.0/doc/build/dts/ |
| D | dt-vs-kconfig.rst | 27 property) and certain settings such as the address range of the hardware
30 devicetree. This could include configuration such as the RX IRQ line's
38 As another example, consider a device with a 2.4GHz, multi-protocol radio
43 * **Boot-time configuration** for the radio, such as TX power in dBm, should
46 radio, such as selecting a BLE or 802.15.4 protocol stack.
48 As another example, Kconfig options that formerly enabled a particular
57 configuration parameters, such as the size of an internal buffer, these
65 of this is selecting a particular UART for use as the system's console.
|
