mhu/mcan-linux-driver
1
0
Fork 0
Code Issues Pull Requests Releases 1 Wiki Activity

Update page 'M_CAN Driver Usage Device Tree'

Mario Hüttel 2017-04-26 14:11:59 +02:00
parent a8f55df8f4
commit 712c005bdb
1 changed files with 14 additions and 4 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

18
M_CAN Driver Usage Device Tree.md

@ -63,15 +63,25 @@ The remaining values configure the amout of elments for different FIFOs and Buff
#### M_CAN version 3.0.x
For M_CAN versions 3.0.x, the driver only uses the RX FIFO 0 and 1(!) TX Buffer. Therefore
It is an array consisting of eight values:
For M_CAN versions 3.0.x, the driver only uses the RX FIFO 0 and *one*(!) TX Buffer.
Following line
```
bosch,mram-cfg = <0x0, 0, 0, 32, 0, 0, 0, 1>;
```
is a valid configuration with 32 RX FIFO elements. The other values cna be set to numbers greater than zero according to the user manual. The space will be reserved in the message RAM will not be used by the driver.
Also it is possible to configure more than 1 TX Buffer. However, only one will be used.
Also it is possible to configure more than one TX Buffer. However, only one will be used.
#### M_CAN version >3.1.x
For versions greater than 3.1.x the
For versions greater than 3.1.x, the driver uses the TX FIFO to improve performance. For correct operation it also needs th TX Event FIFO. Therefore the TX Event FIFO value has to be configured. To prevent overflows it is recommended to use at least as many TX Event FIFO elements as TX FIFO Elements.
Following line
```
bosch,mram-cfg = <0x0, 0, 0, 32, 0, 0, 10, 10>;
```
is a valid configuration. The M_CAN will use 32 RX FIFO elements in RX FIFO 0 and 10 TX FIFO Elements. To detect the sent messages a TX Event FIFO size of 10 is also configured.
Filters and RX FIFO 1/ RX Buffers are not used in this configuration as well.