DMA move API tracking issue

[bugadani]

Basics

• [1/3] DMA Move API: Pull out driver specific state in DMA driver into… #1716
• [2/3] DMA Move API: Move DMA descriptors to peripheral drivers #1719
• [3/3] DMA Move API: Introduce DMA buffer objects #1856
• Introduce traits for the DMA buffer objects #1976

Peripheral support

• SPI master
• SPI slave
• I8080 Migrate I8080 driver to a move based API #2191
  • Add DMA buffer view support to I8080 driver #2268
• Camera Migrate Camera to a move based API #2242
• AES
• PARL IO
• I2S
• Memcpy

Buffer features

• Support PSRAM in DmaTxBuf #2161
• Support other slice types besides u8.
• Support configuring burst mode
• Support configuring the "check descriptor ownership" feature on the DMA channel
• Support configuring the ownership write back feature in the DMA channel
• Allow users to create the Preparation struct (make it public)
• Expose an unsafe constructor for people to create buffers on the stack.
• Place the buffer view methods in internal ram since they're likely to be called in interrupts

Buffer types

• DmaTxStreamingBuf
• DmaTxCircularBuf
• DmaRxCircularBuf
• DmaReadOnlyBuf (for creating multiple bufs that point to the same buffer)
• Compressed buffer? Not sure if this should be in the hal

Note: This issue can be closed once the DescriptorChain struct is deleted.

[bugadani]

I thought we might want to track work that needs to be done in this area, but I'm unsure what that work actually is.

[Dominaezzz]

I've added all the stuff I had at the back of my mind