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
Copy file name to clipboardExpand all lines: docs/reference/contributing/target/QuadSPI.md
+23-3Lines changed: 23 additions & 3 deletions
Original file line number
Diff line number
Diff line change
@@ -7,7 +7,7 @@ QSPI HAL defines API for targets that contain QSPI capable peripheral. The QSPI
7
7
##### Defined behavior
8
8
9
9
- a target implementaion should cover the most of QSPI frame format (some targets might not provide the flexibility for setting all frame parameters)
10
-
- command transfer - a target might provide additional API for sending device specific commands. In case it does not, it can be implemented via read/write functions
10
+
- command transfer - a target might provide additional API for sending device specific commands. In case it does not, it can be implemented via read/write functions (this is target/driver dependent)
11
11
12
12
##### Undefined behavior
13
13
@@ -19,9 +19,29 @@ QSPI peripheral
19
19
20
20
#### Implementing QuadSPI
21
21
22
-
The target needs to define `qspi_s` structure - target specific QSPI object, enable QSPI in targets.json file `device_has` and implement QSPI HAL functions defined in `hal/qspi_api.h` header file.
22
+
The target needs to define `qspi_s` structure - target specific QSPI object.
23
23
24
-
`qspi_write` and `qspi_read` are used for data transfers. For communicating with device, `qspi_command_transfer` should be used.
0 commit comments