From: horms@verge.net.au (Simon Horman)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 0/2] arm64: renesas: Add support for R-Car V3M
Date: Mon, 28 Aug 2017 09:44:54 +0200 [thread overview]
Message-ID: <20170828074453.GA22421@verge.net.au> (raw)
In-Reply-To: <1503665810-13945-1-git-send-email-geert+renesas@glider.be>
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..
next parent reply other threads:[~2017-08-28 7:44 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1503665810-13945-1-git-send-email-geert+renesas@glider.be>
2017-08-28 7:44 ` Simon Horman [this message]
2017-08-30 7:26 ` [PATCH 0/2] arm64: renesas: Add support for R-Car V3M 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
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20170828074453.GA22421@verge.net.au \
--to=horms@verge.net.au \
--cc=linux-arm-kernel@lists.infradead.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
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).