Home
last modified time | relevance | path

Searched +full:forward +full:- +full:cells (Results 1 – 9 of 9) sorted by relevance

/Zephyr-latest/tests/drivers/i2c/i2c_emul/boards/
Dnative_sim.overlay3 * SPDX-License-Identifier: Apache-2.0
9 compatible = "zephyr,i2c-emul-controller";
10 clock-frequency = <I2C_BITRATE_STANDARD>;
11 #address-cells = <1>;
12 #size-cells = <0>;
13 #forward-cells = <1>;
19 compatible = "zephyr,i2c-emul-controller";
20 clock-frequency = <I2C_BITRATE_STANDARD>;
21 #address-cells = <1>;
22 #size-cells = <0>;
[all …]
/Zephyr-latest/dts/bindings/i2c/
Dzephyr,i2c-emul-controller.yaml2 # SPDX-License-Identifier: Apache-2.0
6 compatible: "zephyr,i2c-emul-controller"
8 include: i2c-controller.yaml
13 target-buffered-mode:
20 type: phandle-array
24 example, if we wanted to forward any requests from i2c0@0x20 to i2c1, we
28 forward = <&i2c1 0x20>;
31 forward-cells:
32 - addr
/Zephyr-latest/doc/hardware/emulator/
Dbus_emulators.rst20 been completed. This allows for testing that high-level code can
27 The diagram below shows application code / high-level tests at the top.
49 Controller) on native_sim using emulators for all non-chip drivers.
63 native_sim. We can develop on a host, use source-level debugging, etc.
79 .. code-block:: C
89 #. ``bus_api`` - This points to the API for the upstream bus that the emulator
92 #. ``_backend_api`` - This points to the device-class specific backend API for
97 device-class.
113 functions focus on high-level behavior and do not provide hooks for specific
148 ----------------------
[all …]
/Zephyr-latest/boards/native/native_sim/
Dnative_sim.dts4 * SPDX-License-Identifier: Apache-2.0
7 /dts-v1/;
9 #include <zephyr/dt-bindings/adc/adc.h>
10 #include <zephyr/dt-bindings/i2c/i2c.h>
11 #include <zephyr/dt-bindings/gpio/gpio.h>
19 zephyr,shell-uart = &uart0;
20 zephyr,uart-mcumgr = &uart0;
23 zephyr,flash-controller = &flashcontroller0;
26 zephyr,code-partition = &slot0_partition;
27 zephyr,bt-hci = &bt_hci_userchan;
[all …]
/Zephyr-latest/doc/services/storage/zms/
Dzms.rst5 Zephyr Memory Storage is a new key-value storage system that is designed to work with all types
6 of non-volatile storage technologies. It supports classical on-chip NOR flash as well as new
12 ZMS divides the memory space into sectors (minimum 2), and each sector is filled with key-value
15 The key-value pair is divided into two parts:
17 - The key part is written in an ATE (Allocation Table Entry) called "ID-ATE" which is stored
19 - The value part is defined as "DATA" and is stored raw starting from the top of the sector
21 Additionally, for each sector we store at the last positions Header-ATEs which are ATEs that
28 Afterwards we move forward to the next sector and start writing entries again.
37 .. list-table::
39 :header-rows: 1
[all …]
/Zephyr-latest/doc/releases/
Dmigration-guide-3.7.rst22 out-of-tree SoCs and boards to be ported to the new model. See the
25 * The following build-time generated headers:
27 .. list-table::
28 :header-rows: 1
30 * - Affected header files
31 * - ``app_version.h``
32 * - ``autoconf.h``
33 * - ``cmake_intdef.h``
34 * - ``core-isa-dM.h``
35 * - ``devicetree_generated.h``
[all …]
Dmigration-guide-4.0.rst39 to define default flash and ram partitioning based on TF-M.
60 specify it using the west ``--runner`` or ``-r`` option. (:github:`75284`)
61 * ADC: Domain clock needs to be explicitly defined if property st,adc-clock-source = <ASYNC> is use…
85 Trusted Firmware-M
108 If a removed variant is strictly needed, add your own forward declaration in your code.
130 Chip variants with open-drain outputs (``mcp23x09``, ``mcp23x18``) now correctly reflect this in
134 * The ``power-domain`` property has been removed in favor of ``power-domains``.
136 ``power-domain-names`` is also available to optionally name each entry in
137 ``power-domains``. The number of cells in the ``power-domains`` property need
138 to be defined using ``#power-domain-cells``.
[all …]
Drelease-notes-3.1.rst61 * Split CAN classic and CAN-FD APIs:
90 was moved from Kconfig to :ref:`devicetree <dt-guide>`.
91 See the :dtcompatible:`st,stm32f1-pinctrl` devicetree binding for more information.
182 * MIPI-DSI
184 * Added a :ref:`MIPI-DSI api <mipi_dsi_api>`. This is an experimental API,
196 * Added support for enabling/disabling CAN-FD mode at runtime using :c:macro:`CAN_MODE_FD`.
220 * Added support for Provisioners over PB-GATT
231 * Implemented ISO-AL TX unframed fragmentation
232 * Added support for back-to-back receiving of PDUs on nRF5x platforms
249 newly created informational-only callback struct :c:struct:`bt_conn_auth_info_cb`.
[all …]
/Zephyr-latest/include/zephyr/drivers/
Dadc.h10 * SPDX-License-Identifier: Apache-2.0
17 #include <zephyr/dt-bindings/adc/adc.h>
71 * @retval -EINVAL if the gain could not be interpreted
104 * Value range is 0-16383 for a given unit.
110 * This value primarily identifies the channel within the ADC API - when
125 * While this API allows identifiers from range 0-31, particular drivers
132 /** Channel type: single-ended or differential. */
185 * #address-cells = <1>;
186 * #size-cells = <0>;
192 * zephyr,acquisition-time = <ADC_ACQ_TIME(ADC_ACQ_TIME_MICROSECONDS, 20)>;
[all …]