Lines Matching full:mspi
6 The MSPI (multi-bit SPI) is provided as a generic API to accommodate
18 MSPI Controller API
21 Zephyr's MSPI controller API may be used when a multi-bit SPI controller
22 is present. E.g. Ambiq MSPI, QSPI, OSPI, Flexspi, etc.
28 The MSPI interface contains controller drivers that are SoC platform specific
29 and implement the MSPI APIs, and device drivers that reference these APIs.
33 Here is a list of generic steps for initializing the MSPI controller and the
34 MSPI bus inside the device driver initialization function:
36 #. Initialize the data structure of the MSPI controller driver instance.
111 Here is an example for defining an MSPI controller in device tree:
112 The mspi controller's bindings should reference mspi-controller.yaml as one of the base.
116 mspi0: mspi@400 {
118 compatible = "zephyr,mspi-emul-controller";
134 Here is an example for defining an MSPI device in device tree:
135 The mspi device's bindings should reference mspi-device.yaml as one of the base.
143 compatible = "zephyr,mspi-emul-device";
148 mspi-max-frequency = < 0x2dc6c00 >;
149 mspi-io-mode = "MSPI_IO_MODE_QUAD";
150 mspi-data-rate = "MSPI_DATA_RATE_SINGLE";
151 mspi-hardware-ce-num = < 0x0 >;
164 User should specify target operating parameters in the DTS such as ``mspi-max-frequency``,
165 ``mspi-io-mode`` and ``mspi-data-rate`` even though they may subject to change during runtime.
178 other relevant mspi struct or private data structures. In particular, :c:struct:`mspi_dev_id`