diff options
| author | Harald Welte <laforge@gnumonks.org> | 2012-02-26 22:00:35 +0100 |
|---|---|---|
| committer | Harald Welte <laforge@gnumonks.org> | 2012-02-26 22:00:35 +0100 |
| commit | e3a39f0d8b3174ea4d266069f13c40485ea7e16c (patch) | |
| tree | 91a626ab7cb1e0e706a2dd856958017d2e9ebce3 /boards/at91sam3u-ek/board.h | |
| parent | 35055940944b62166fd2a202195f3abfe411bb27 (diff) | |
SAM3U: Use correct DMAC peripheral ID for SSC receive
It seems like the SSC Rx channel has a different DMAC peripheral ID (4)
than the transmit side.
The official Atmel sam3u documentation (doc6403e) doesn't document that
fact, and it also doesn't even state any DMAC peripheral identifiers.
The at91lib code release by Atmel claims it is 3, when in reality it is
4!
I found this by brute-forcing all possible peripheral identifiers.
Diffstat (limited to 'boards/at91sam3u-ek/board.h')
| -rw-r--r-- | boards/at91sam3u-ek/board.h | 2 |
1 files changed, 1 insertions, 1 deletions
diff --git a/boards/at91sam3u-ek/board.h b/boards/at91sam3u-ek/board.h index 7ce478c..fa5c37f 100644 --- a/boards/at91sam3u-ek/board.h +++ b/boards/at91sam3u-ek/board.h @@ -578,7 +578,7 @@ #define BOARD_SD_DMA_HW_SRC_REQ_ID DMA_HW_SRC_REQ_ID_MCI0
#define BOARD_SD_DMA_HW_DEST_REQ_ID DMA_HW_DEST_REQ_ID_MCI0
/// SSC DMA hardware handshaking ID
-#define BOARD_SSC_DMA_HW_SRC_REQ_ID AT91C_HDMA_SRC_PER_3
+#define BOARD_SSC_DMA_HW_SRC_REQ_ID AT91C_HDMA_SRC_PER_4
#define BOARD_SSC_DMA_HW_DEST_REQ_ID AT91C_HDMA_DST_PER_3
/// Rtc
|