This is based on the existing KF device tree sources:
$ ls -1 arch/arm64/boot/dts/renesas/*-kf.dts
arch/arm64/boot/dts/renesas/r8a7795-es1-h3ulcb-kf.dts
arch/arm64/boot/dts/renesas/r8a7795-h3ulcb-kf.dts
arch/arm64/boot/dts/renesas/r8a7796-m3ulcb-kf.dts
Signed-off-by: Eugeniu Rosca
---
Changes in
Fix below DTC error:
Error: arch/arm64/boot/dts/renesas/ulcb-kf.dtsi:36.1-8 Label or path hscif0 not
found
The DTC error occurs *after* the addition of r8a77965-m3nulcb-kf.dts.
Fix it beforehand.
Inspired from v4.12-rc1 commits:
- commit 68cd16107260 ("arm64: dts: r8a7796 dtsi: Add all HSCIF
According to R-Car Gen3 HW manual rev1.00, R-Car M3-N has two CAN
interfaces, similar to H3, M3-W and other SoCs from the same family.
Add CAN placeholder nodes to avoid below DTC errors:
Error: arch/arm64/boot/dts/renesas/ulcb-kf.dtsi:19.1-6 Label or path can0 not
found
Error:
Allow the bare M3-N-based ULCB board to boot.
Signed-off-by: Eugeniu Rosca
Reviewed-by: Jacopo Mondi
---
Changes in v2:
- [Jacopo Mondi] Removed redundant license text. Added Reviewed-by.
- [Simon Horman]
- Renamed DTS 's/r8a77965-ulcb.dts/r8a77965-m3nulcb.dts/'
- Renamed board name
According to R-Car Gen3 HW manual Rev.1.00 Apr 2018, M3-N SoC implements
five (0..4) HSCIF channels, similar to H3, M3-W and E3.
The story behind this patch is tackling below dmesg warnings, which pop
up when booting M3NULCB Kingfisher board:
$ dmesg | grep sh-pfc
sh-pfc e606.pin-controller:
In harmony with ATF and U-Boot outputs [1] and [2], the new board is
based on M3-N revision ES1.1 and the amount of memory present on SiP
is 2GiB, contiguously addressed.
The amount of RAM is mentioned based on the assumption that it is
encoded in the board id/string. There is some evidence
Document the support for rcar_can on R8A77965 SoC devices.
Add R8A77965 to the list of SoCs which require the "assigned-clocks" and
"assigned-clock-rates" properties (thanks, Sergei). Rewrap text.
Signed-off-by: Eugeniu Rosca
---
Changes in v2:
- [Kieran Bingham] Simplified commit description.
