max/embassy
1
0
Fork 0
Code Issues Pull Requests Packages Projects Releases Wiki Activity

Workaround duplicity of DMA channel declaration when the target chip specifies more than one request, by processing only the first declared request for the channel.

Browse Source
This commit is contained in:
Matous Hybl 2021-10-22 11:35:46 +02:00
parent b22c472af3
commit 4fbac40120
1 changed files with 16 additions and 8 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

24
stm32-metapac-gen/src/lib.rs
View File

@ -379,19 +379,27 @@ pub fn gen(options: Options) {
row.push(bi.module.clone());
row.push(bi.block.clone());
row.push(request.clone());
if let Some(channel) = &channel.channel {
row.push(format!("{{channel: {}}}", channel));
row.push(if let Some(channel) = &channel.channel {
format!("{{channel: {}}}", channel)
} else if let Some(dmamux) = &channel.dmamux {
row.push(format!("{{dmamux: {}}}", dmamux));
format!("{{dmamux: {}}}", dmamux)
} else {
unreachable!();
}
if let Some(request) = channel.request {
row.push(request.to_string());
});
row.push(if let Some(request) = channel.request {
request.to_string()
} else {
row.push("()".to_string());
"()".to_string()
});
if peripheral_dma_channels_table
.iter()
.find(|a| a[..a.len() - 1] == row[..row.len() - 1])
.is_none()
{
peripheral_dma_channels_table.push(row);
}
peripheral_dma_channels_table.push(row);
}
}