Refresh submodules + Update comments in SPI slave header file
This commit is contained in:
parent
7d04104485
commit
7791b2a62e
2
arch
2
arch
|
@ -1 +1 @@
|
|||
Subproject commit 6190d664666b19580969c4e620646ef4e54f0182
|
||||
Subproject commit da550063e6081057d2324b76c8ac065ed6fe1d6f
|
2
configs
2
configs
|
@ -1 +1 @@
|
|||
Subproject commit ac4035687c824bb4a573e06feb017cb4f3ce7626
|
||||
Subproject commit c779f69eb4070272ef136a27124223bddafec5a1
|
|
@ -398,8 +398,10 @@
|
|||
* the first word send is a command to read or write something following
|
||||
* by a sequence of transfers to implement the write. So you have very,
|
||||
* very limited time window to setup the correct DMA to respond to the
|
||||
* command. DMA setup time can be longer. And I am not sure it I can
|
||||
* make it reliable.
|
||||
* command. I am not certain that it can be done reliably.
|
||||
*
|
||||
* Inserting dummy words into the protocol between the first command word
|
||||
* and the remaining data transfer could allow time to set up the DMA.
|
||||
*
|
||||
* 3) I mentioned that you do not know the size of the transfer in advance.
|
||||
* If you set up the DMA to terminate to soon, then you lose the last part
|
||||
|
|
Loading…
Reference in New Issue