A proposed WebAssembly System Interface API.

[Fill in the current phase, e.g. Phase 1]

• jay94ks
• [Champion 2]
• [etc.]

TODO before entering Phase 2.

The WASI-SPI proposal defines an API for the SPI communication.

The primary goal is to provide an interface that WASI programs can use to read and write data over SPI peripherals.

SPI interfaces can be covered by GPIO toggling (bitbang) but it cannot be enough to replace hardware SPI's performance. the purpose of this proposal is to solely focus on SPI.

The full API documentation can be found here.

[Walk through of how someone would use this API.]

[Provide example code snippets and diagrams explaining how the API would be used to solve the given problem]

[etc.]

[This section should mostly refer to the .wit.md file that specifies the API. This section is for any discussion of the choices made in the API which don't make sense to document in the spec file itself.]

In software side, just class or interface type can share methods between different peripherals. but actually, their working ways are quiet different although concept is similar.

SPI resources will be constructed in many different ways on different devices, so worlds that include the SPI interface should also include a way to obtain SPI handles. Typically this will either be by having SPI handles passed into exported functions as parameters, or by having SPI handles returned from imported functions. (this paragraph is copied from wasi-i2c)

TODO before entering Phase 3.

This is not an official paper or, not written by expert. This is just written to fill empty page by hobbyist.

Many thanks for valuable feedback and advice from:

• [Person 1]
• [Person 2]
• [etc.]