Skip to content

arm64: renesas: Add support for R-Car V3M

Simon Horman linux-arm-kernel linux-devicetree linux-renesas-soc 1 version New

Get series with b4
b4 am [email protected]

Versions newest first

  1. v1 Latest0 of 2 patches 0 repliesNew

Patches in v1 No applies recorded yet

None of the 2 patches the cover letter announces are in this archive.

Reviews trailers per patch

No Reviewed-by, Acked-by or Tested-by trailers for v1 yet.

Read the v1 thread

Cover letter [PATCH 0/2] arm64: renesas: Add support for R-Car V3M
Quoted 29 lines · Simon Horman
Quoted 28 lines · Geert Uytterhoeven

Hi Simon,

Quoted 25 lines · Simon Horman
Quoted 23 lines · Simon Horman
Quoted 9 lines · Geert Uytterhoeven

This patch series adds initial R-Car V3M infrastructure:
1. SoC DT bindings,
2. Main Kconfig symbol.

Both follow the example set by R-Car D3 aka r8a77995, using 5-digit instead of 4-digit part numbers.
Alternatively, we could stick to 4-digit part numbers if the fifth digit is a zero.

Quoted 7 lines

For your convenience, a branch with more preliminary work (thanks Sergei, for posting the clock driver!) for testing on v3m/eagle is also available in the topic/r8a77970-integration branch of my renesas-drivers git repository at
git://git.kernel.org/pub/scm/linux/kernel/git/geert/renesas-drivers.git.

Thanks for your comments!

This looks good to me.

I am in favour of using the 5-digit scheme for all new R-Car Gen 3 SoCs as it seems the safest option with regards to as yet unknown (to me) part numbers.

Quoted 7 lines
Quoted 5 lines
Quoted 2 lines

Geert, any objections to me applying these?
I'm happy to wait longer if you prefer.

It would be good to have an ack from Rob.
No need to hurry.

Understood, I will wait.

Rob has acked the DT binding patch and I have applied the series.