Skip to contentSkip to conversation

arm64: renesas: Add support for R-Car V3M

PATCH New Geert Uytterhoeven 5 participants 9 messages Aug 25, 2017 – Sep 1, 2017 1 message not in the archive

Subsystems (2)
Device tree bindings arm64
lore
Share & tools
lore

Geert Uytterhoeven

author
#0 lore raw

cover arm64: renesas: Add support for R-Car V3M

Hi all,

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.

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!

Geert Uytterhoeven (2):
ARM: shmobile: Document R-Car V3M SoC DT bindings
arm64: renesas: Add Renesas R8A77970 Kconfig support

 Documentation/devicetree/bindings/arm/shmobile.txt | 2 ++
 arch/arm64/Kconfig.platforms                       | 6 ++++++
 2 files changed, 8 insertions(+)
Signature · 12 lines
2.7.4

Gr{oetje,eeting}s,

						Geert

--
Geert Uytterhoeven -- There's lots of Linux beyond ia32 -- [email protected]

In personal conversations with technical people, I call myself a hacker. But
when I'm talking to journalists I just say "programmer" or something like that.
							    -- Linus Torvalds
author
#1 lore raw

PATCH 1/2 ARM: shmobile: Document R-Car V3M SoC DT bindings

Signed-off-by Geert Uytterhoeven <[email protected]>
---
 Documentation/devicetree/bindings/arm/shmobile.txt | 2 ++
 1 file changed, 2 insertions(+)
Documentation/devicetree/bindings/arm/shmobile.txt +2 -0
index 275cda1469b8b95c..387cbd1a10375f2b 100644
@@ -39,6 +39,8 @@ SoCs:
     compatible = "renesas,r8a7795"
   - R-Car M3-W (R8A77960)
     compatible = "renesas,r8a7796"
+  - R-Car V3M (R8A77970)
+    compatible = "renesas,r8a77970"
   - R-Car D3 (R8A77995)
     compatible = "renesas,r8a77995"
Signature · 1 line
2.7.4

A message that is not in the archive (sent off-list or not yet received): 1503665810-13945-1-git-send-email-geert+renesas-gXvu3+zWzMSzQB+pC5nmwQ@public.gmane.org

#4 lore raw

PATCH 2/2 arm64: renesas: Add Renesas R8A77970 Kconfig support

Add a configuration option for the R-Car V3M SoC.

Signed-off-by Geert Uytterhoeven <[email protected]>
---
 arch/arm64/Kconfig.platforms | 6 ++++++
 1 file changed, 6 insertions(+)
arch/arm64/Kconfig.platforms +6 -0
index a1c9f4ed7a887ab2..8a19015311a35d47 100644
@@ -184,6 +184,12 @@ config ARCH_R8A7796
 	help
 	  This enables support for the Renesas R-Car M3-W SoC.
 
+config ARCH_R8A77970
+	bool "Renesas R-Car V3M SoC Platform"
+	depends on ARCH_RENESAS
+	help
+	  This enables support for the Renesas R-Car V3M SoC.
+
 config ARCH_R8A77995
 	bool "Renesas R-Car D3 SoC Platform"
 	depends on ARCH_RENESAS
Signature · 6 lines
2.7.4

--
To unsubscribe from this list: send the line "unsubscribe devicetree" in
the body of a message to [email protected]
More majordomo info at  http://vger.kernel.org/majordomo-info.html
#5 lore raw

cover arm64: renesas: Add support for R-Car V3M

In reply to Geert Uytterhoeven
Quoted 11 lines · Geert Uytterhoeven

Hi all,

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..

#6 lore raw

cover arm64: renesas: Add support for R-Car V3M

Quoted 18 lines · Simon Horman
Quoted 17 lines · Geert Uytterhoeven

Hi all,

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.

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.

Quoted 7 lines
Quoted 1 line

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.

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

#7 lore raw

cover arm64: renesas: Add support for R-Car V3M

Hi Simon,

Quoted 19 lines · Simon Horman
Quoted 18 lines · Simon Horman
Quoted 16 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.

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!

Quoted 8 lines
Quoted 5 lines

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.

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.

Gr{oetje,eeting}s,

Geert

--
Geert Uytterhoeven -- There's lots of Linux beyond ia32 -- geert at linux-m68k.org

In personal conversations with technical people, I call myself a hacker. But when I'm talking to journalists I just say "programmer" or something like that.
-- Linus Torvalds

#8 lore raw

cover arm64: renesas: Add support for R-Car V3M

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 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.

#9 lore raw

cover 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.