You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Hi, I am planning a MSPI driver for a SPI controller supporting full-duplex, dual, and quad I/O. I have looked over the MSPI documentation, header file, and the current drivers. I am not clear about the difference between struct mspi_xfer_packet cmd and struct mspi_dev_cfg read_cmd. I expected the driver would use struct mspi_xfr_packet cmd plus io_mode and cmd_length from struct mspi_dev_cfg to know how to transmit the command. What is the purpose of read_cmd and write_cmd in struct mspi_dev_cfg?
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
Uh oh!
There was an error while loading. Please reload this page.
-
Hi, I am planning a MSPI driver for a SPI controller supporting full-duplex, dual, and quad I/O. I have looked over the MSPI documentation, header file, and the current drivers. I am not clear about the difference between struct mspi_xfer_packet cmd and struct mspi_dev_cfg read_cmd. I expected the driver would use struct mspi_xfr_packet cmd plus io_mode and cmd_length from struct mspi_dev_cfg to know how to transmit the command. What is the purpose of read_cmd and write_cmd in struct mspi_dev_cfg?
Beta Was this translation helpful? Give feedback.
All reactions