zephyr,mspi-emul-controller

Vendor: Zephyr-specific binding

Note

An implementation of a driver matching this compatible is available in drivers/mspi/mspi_emul.c.

Description

These nodes are “mspi” bus nodes.

Zephyr MSPI Emulation controller

Properties

Properties not inherited from the base binding file.

Name

Type

Details

clock-frequency

int

 
Clock frequency the MSPI peripheral is being driven at, in Hz.

op-mode

string

 
Indicate MSPI controller or peripheral mode of the controller.
The controller driver may use this during initialization.

Legal values: 'MSPI_CONTROLLER', 'MSPI_PERIPHERAL'

duplex

string

 
Indicate MSPI Duplex mode, full or half.
The controller driver may check this setting against its
capabilities.

Legal values: 'MSPI_HALF_DUPLEX', 'MSPI_FULL_DUPLEX'

dqs-support

boolean

 
Indicate whether the hardware supports DQS.
The controller driver may check this setting against its
capabilities.

software-multiperipheral

boolean

 
Indicate whether the controller driver enables support for
software managed multi peripheral feature.
At the minimum, the controller driver should use it to allow
or disallow calling mspi_dev_config with MSPI_DEVICE_CONFIG_NONE.

ce-gpios

phandle-array

 
An array of chip select GPIOs to use. Each element
in the array specifies a GPIO. The index in the array
corresponds to the child node that the CE gpio controls.

Example:

  mspi@... {
          ce-gpios = <&gpio0 23 GPIO_ACTIVE_LOW>,
                        <&gpio1 10 GPIO_ACTIVE_LOW>,
                        ...;

          mspi-device@0 {
                  reg = <0>;
                  ...
          };
          mspi-device@1 {
                  reg = <1>;
                  ...
          };
          ...
  };

The child node "mspi-device@0" specifies a mspi device with
chip select controller gpio0, pin 23, and devicetree
GPIO flags GPIO_ACTIVE_LOW. Similarly, "mspi-device@1" has CE GPIO
controller gpio1, pin 10, and flags GPIO_ACTIVE_LOW. Additional
devices can be configured in the same way.

If unsure about the flags cell, GPIO_ACTIVE_LOW is generally a safe
choice for a typical "CEn" pin. GPIO_ACTIVE_HIGH may be used if
intervening hardware inverts the signal to the peripheral device or
the line itself is active high.

Regardless of whether the CE pin may need software control or MSPI
controller has dedicated CE pin, this field should be defined to
help manage multiple devices on the same MSPI controller.