Re: [PATCH 0/2] arm64: renesas: Add support for R-Car V3M

2 messages, 2 authors, 2017-09-01 · open the first message on its own page

Re: [PATCH 0/2] arm64: renesas: Add support for R-Car V3M

From: Simon Horman <hidden>
Date: 2017-08-30 09:28:39

On Wed, Aug 30, 2017 at 10:21:46AM +0200, Geert Uytterhoeven wrote:
Hi Simon,

On Wed, Aug 30, 2017 at 9:26 AM, Simon Horman [off-list ref] wrote:
quoted
On Mon, Aug 28, 2017 at 09:44:54AM +0200, Simon Horman wrote:
quoted
On Fri, Aug 25, 2017 at 02:56:48PM +0200, Geert Uytterhoeven wrote:
quoted
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!
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.
Understood, I will wait.

Re: [PATCH 0/2] arm64: renesas: Add support for R-Car V3M

From: Simon Horman <horms@verge.net.au>
Date: 2017-09-01 08:59:02

On Wed, Aug 30, 2017 at 11:28:39AM +0200, Simon Horman wrote:
On Wed, Aug 30, 2017 at 10:21:46AM +0200, Geert Uytterhoeven wrote:
quoted
Hi Simon,

On Wed, Aug 30, 2017 at 9:26 AM, Simon Horman [off-list ref] wrote:
quoted
On Mon, Aug 28, 2017 at 09:44:54AM +0200, Simon Horman wrote:
quoted
On Fri, Aug 25, 2017 at 02:56:48PM +0200, Geert Uytterhoeven wrote:
quoted
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!
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.
Understood, I will wait.
Rob has acked the DT binding patch and I have applied the series.
Keyboard shortcuts
hback out one level
jnext message in thread
kprevious message in thread
ldrill in
Escclose help / fold thread tree
?toggle this help