* [PATCH 0/2] arm64: renesas: Add support for R-Car V3M [not found] <1503665810-13945-1-git-send-email-geert+renesas@glider.be> @ 2017-08-28 7:44 ` Simon Horman 2017-08-30 7:26 ` Simon Horman [not found] ` <1503665810-13945-2-git-send-email-geert+renesas@glider.be> 1 sibling, 1 reply; 6+ messages in thread From: Simon Horman @ 2017-08-28 7:44 UTC (permalink / raw) To: linux-arm-kernel On Fri, Aug 25, 2017 at 02:56:48PM +0200, Geert Uytterhoeven wrote: > 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! 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.. ^ permalink raw reply [flat|nested] 6+ messages in thread
* [PATCH 0/2] arm64: renesas: Add support for R-Car V3M 2017-08-28 7:44 ` [PATCH 0/2] arm64: renesas: Add support for R-Car V3M Simon Horman @ 2017-08-30 7:26 ` Simon Horman 2017-08-30 8:21 ` Geert Uytterhoeven 0 siblings, 1 reply; 6+ messages in thread From: Simon Horman @ 2017-08-30 7:26 UTC (permalink / raw) To: linux-arm-kernel On Mon, Aug 28, 2017 at 09:44:54AM +0200, Simon Horman wrote: > On Fri, Aug 25, 2017 at 02:56:48PM +0200, Geert Uytterhoeven wrote: > > 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! > > 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. ^ permalink raw reply [flat|nested] 6+ messages in thread
* [PATCH 0/2] arm64: renesas: Add support for R-Car V3M 2017-08-30 7:26 ` Simon Horman @ 2017-08-30 8:21 ` Geert Uytterhoeven 2017-08-30 9:28 ` Simon Horman 0 siblings, 1 reply; 6+ messages in thread From: Geert Uytterhoeven @ 2017-08-30 8:21 UTC (permalink / raw) To: linux-arm-kernel Hi Simon, On Wed, Aug 30, 2017 at 9:26 AM, Simon Horman <horms@verge.net.au> wrote: > On Mon, Aug 28, 2017 at 09:44:54AM +0200, Simon Horman wrote: >> On Fri, Aug 25, 2017 at 02:56:48PM +0200, Geert Uytterhoeven wrote: >> > 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. 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 ^ permalink raw reply [flat|nested] 6+ messages in thread
* [PATCH 0/2] arm64: renesas: Add support for R-Car V3M 2017-08-30 8:21 ` Geert Uytterhoeven @ 2017-08-30 9:28 ` Simon Horman 2017-09-01 8:59 ` Simon Horman 0 siblings, 1 reply; 6+ messages in thread From: Simon Horman @ 2017-08-30 9:28 UTC (permalink / raw) To: linux-arm-kernel 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 <horms@verge.net.au> wrote: > > On Mon, Aug 28, 2017 at 09:44:54AM +0200, Simon Horman wrote: > >> On Fri, Aug 25, 2017 at 02:56:48PM +0200, Geert Uytterhoeven wrote: > >> > 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. ^ permalink raw reply [flat|nested] 6+ messages in thread
* [PATCH 0/2] arm64: renesas: Add support for R-Car V3M 2017-08-30 9:28 ` Simon Horman @ 2017-09-01 8:59 ` Simon Horman 0 siblings, 0 replies; 6+ messages in thread From: Simon Horman @ 2017-09-01 8:59 UTC (permalink / raw) To: linux-arm-kernel 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: > > Hi Simon, > > > > On Wed, Aug 30, 2017 at 9:26 AM, Simon Horman <horms@verge.net.au> wrote: > > > On Mon, Aug 28, 2017 at 09:44:54AM +0200, Simon Horman wrote: > > >> On Fri, Aug 25, 2017 at 02:56:48PM +0200, Geert Uytterhoeven wrote: > > >> > 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. ^ permalink raw reply [flat|nested] 6+ messages in thread
[parent not found: <1503665810-13945-2-git-send-email-geert+renesas@glider.be>]
* [PATCH 1/2] ARM: shmobile: Document R-Car V3M SoC DT bindings [not found] ` <1503665810-13945-2-git-send-email-geert+renesas@glider.be> @ 2017-08-31 20:08 ` Rob Herring 0 siblings, 0 replies; 6+ messages in thread From: Rob Herring @ 2017-08-31 20:08 UTC (permalink / raw) To: linux-arm-kernel On Fri, Aug 25, 2017 at 02:56:49PM +0200, Geert Uytterhoeven wrote: > Signed-off-by: Geert Uytterhoeven <geert+renesas@glider.be> > --- > Documentation/devicetree/bindings/arm/shmobile.txt | 2 ++ > 1 file changed, 2 insertions(+) Acked-by: Rob Herring <robh@kernel.org> ^ permalink raw reply [flat|nested] 6+ messages in thread
end of thread, other threads:[~2017-09-01 8:59 UTC | newest]
Thread overview: 6+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
[not found] <1503665810-13945-1-git-send-email-geert+renesas@glider.be>
2017-08-28 7:44 ` [PATCH 0/2] arm64: renesas: Add support for R-Car V3M Simon Horman
2017-08-30 7:26 ` Simon Horman
2017-08-30 8:21 ` Geert Uytterhoeven
2017-08-30 9:28 ` Simon Horman
2017-09-01 8:59 ` Simon Horman
[not found] ` <1503665810-13945-2-git-send-email-geert+renesas@glider.be>
2017-08-31 20:08 ` [PATCH 1/2] ARM: shmobile: Document R-Car V3M SoC DT bindings Rob Herring
This is a public inbox, see mirroring instructions for how to clone and mirror all data and code used for this inbox; as well as URLs for NNTP newsgroup(s).