drivers: dma: stm32 dmamux device is passed to the dma device #30041
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
FRASTM
requested review from
ABOSTM,
cybertale,
erwango,
lowlander and
nashif
as code owners
github-actions
bot
added
area: Devicetree
area: Devicetree Binding
FRASTM
force-pushed
the
issue29992
branch
6 times, most recently
from
af1d2a8 to
ea8790b
Compare
|
testing tests/drivers/dma/loop_transfer on nucleo_wb55rg: |
erwango
requested changes
Nov 17, 2020
tests/drivers/dma/chan_blen_transfer/boards/nucleo_l476rg.overlay
Outdated
Show resolved
Hide resolved
tests/drivers/dma/chan_blen_transfer/boards/nucleo_wb55rg.overlay
Outdated
Show resolved
Hide resolved
FRASTM
force-pushed
the
issue29992
branch
2 times, most recently
from
9718f99 to
ed3ef43
Compare
erwango
requested changes
Nov 17, 2020
erwango
requested changes
Nov 17, 2020
erwango
approved these changes
Nov 18, 2020
|
this PR must be reworked as the tests/drivers/spi/spi_loopback now fails: |
|
@FRASTM please let us know when everything is fine |
It adds flexibility to test different dma channels The chan_blen_transfer is modified like the loop_transfer application to support stm32xx devices with dma and/or dmamux. On the stm32 devices, the first dma channel is 1. Signed-off-by: Francois Ramu <[email protected]>
The dma test applications for MEM-to-MEM transfers are modified to run on the stm32wb55 with a DMAMUX loop_transfer on any CONFIG_DMA_LOOP_TRANSFER_CHANNEL_NR from 0 to 13 chan_blen_trasnfer on CONFIG_DMA_TRANSFER_CHANNEL_NR_0 from 0 to 13 and on CONFIG_DMA_TRANSFER_CHANNEL_NR_1 from 0 to 13 Signed-off-by: Francois Ramu <[email protected]>
The dma test applications for MEM-to-MEM transfers are modified to run on the stm32l476 with a DMA. The CONFIG_DMA_LOOP_TRANSFER_DRV_NAME is either DMA_1 or DMA_2 CONFIG_DMA_LOOP_TRANSFER_CHANNEL_NR from 1 to 7 for DMA_1 CONFIG_DMA_LOOP_TRANSFER_CHANNEL_NR from 1 to 5 for DMA_2 Signed-off-by: Francois Ramu <[email protected]>
|
With this fix, only the tests/drivers/dma applications are modified to include the support of the DMAMUX on some stm32 devices (typ. stm32wb55rg). In this case, the callback function ( |
|
with this fix and connecting SPI 1 MISO to MOSI (PA7 = PA6 on CN10 of the nucleo_wb55rg board) |
erwango
requested changes
Dec 10, 2020
This will add the corresponding tests/drivers/dma/ tests to the sanity check Signed-off-by: Francois Ramu <[email protected]>
erwango
approved these changes
Dec 10, 2020
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
The dmamux device reference is passed to the associated dma device during the dmamux_stm32_configure()
through the user_data field of the dma_config structure.
So that, later on the incoming dma irq, the dma knows the dmamux where to route its callback function
This is demonstrated using the
tests/drivers/dma/loop_transferandtests/drivers/dma/chan_blen_transferrunning on the stm32wb55 nucleo board.fixes #29992