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

[can] cfgs for naming inconsistencies

Browse Source 
Approach is similar to USB OTG.
STM32L49x and STML4Ax have CAN1 and CAN2.
All others STM32L4xx do only have CAN1.
STM32F72x and STM32F73x are the only F7 devices with only CAN1.
This commit is contained in:
Timo Kröger 2022-03-03 20:51:34 +01:00
parent 6929350552
commit d6d25e6470
1 changed files with 16 additions and 3 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

19
embassy-stm32/src/can/bxcan.rs
View File

@ -96,10 +96,23 @@ foreach_peripheral!(
// CAN1 owns the filter bank and needs to be enabled in order
// for CAN2 to receive messages.
(can, CAN1) => {
unsafe impl bxcan::FilterOwner for peripherals::CAN1 {
const NUM_FILTER_BANKS: u8 = 28;
cfg_if::cfg_if! {
if #[cfg(all(
any(stm32l4, stm32l72, stm32l73),
not(any(stm32l49, stm32l4a))
))] {
// Most L4 devices and some F7 devices use the name "CAN1"
// even if there is no "CAN2" peripheral.
unsafe impl bxcan::FilterOwner for peripherals::CAN1 {
const NUM_FILTER_BANKS: u8 = 14;
}
} else {
unsafe impl bxcan::FilterOwner for peripherals::CAN1 {
const NUM_FILTER_BANKS: u8 = 28;
}
unsafe impl bxcan::MasterInstance for peripherals::CAN1 {}
}
}
unsafe impl bxcan::MasterInstance for peripherals::CAN1 {}
};
(can, CAN3) => {
unsafe impl bxcan::FilterOwner for peripherals::CAN3 {