summaryrefslogtreecommitdiff
path: root/projects/linux/io/V3U-enable_CAN.yaml
blob: 2ae26186251be904862074c963c0947b88c5b334 (plain)
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
title: V3U; upport CAN driver additions and enable for V3U
team: IO
key: 125dd332-ae9e-11eb-bba9-13d957d1734c
status: Active
assignee: Ulrich

bsp41x:
 - 745cdc4ea76af480cb9c4a47f78a580e08ed03b6 # can: rcar_canfd: Add support for r8a779a0 SoC
 - 236a7d2185b21c46064ccf6ece8905ddda16d5e7 # arm64: dts: r8a779a0: Add CANFD device node
 - f229902ff4b71c0ca6fe53c0d58b422b99ef354d # arm64: dts: r8a779a0-falcon: Add CANFD support

bsp51x:
 - fad54852ed4e0199189cb79a1c19133347b4d4b2 # arm64: dts: r8a779a0: Add CANFD device node
 - 555f036fa9b0f289f44d57f4e823f835c76a10b5 # arm64: dts: r8a779a0-falcon: Add CANFD support

upstream:

comments:
 - we are waiting for physical HW for the developer
 - there will not be extra physical HW
 - 745cdc4ea76af480cb9c4a47f78a580e08ed03b6:
    - register layout probably needs to be converted to regmap
    - regmap conversion could be tested on Gen3 locally and on V3U by Renesas in Japan
    - waiting for budget
    - Ulrich was contracted
    - Ulrich found out that regmap is not suitable but the macros from the BSP can be greatly simplified
 - 745cdc4ea76af480cb9c4a47f78a580e08ed03b6, 236a7d2185b21c46064ccf6ece8905ddda16d5e7:
    - v1; https://lore.kernel.org/r/20210924153113.10046-1-uli+renesas@fpond.eu
    - Renesas Japan cannot test these changes, we have to find our own way
    - discussing with Kieran and Ulrich how to accomplish this
    - Kieran can connect CAN interfaces of the Falcon board now
    - Uli is working on scripts to ease testing