From: horms@verge.net.au (Simon Horman)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH v3 0/3] arm64: Add Renesas R8A7796 SoC support
Date: Mon, 6 Jun 2016 10:52:01 +0900 [thread overview]
Message-ID: <20160606015201.GA2317@verge.net.au> (raw)
In-Reply-To: <20160606013345.GB6258@verge.net.au>
On Mon, Jun 06, 2016 at 10:33:45AM +0900, Simon Horman wrote:
> On Tue, May 24, 2016 at 10:54:37AM +0900, Simon Horman wrote:
> > Hi,
> >
> > this short series aims to add basic support for the
> > Gen 3 R-Car M3-W (r8a7796) SoC.
> >
> > It has few bells and whistles but is sufficient to bring up
> > an r8a7795/salvator-x. I have provided a boot-log at the bottom
> > of this email in case it is of interest.
> >
> >
> > Dependency:
> >
> > "[PATCH 0/4] clk: renesas: cpg-mssr: Add support for R-Car M3-W"
> >
> >
> > Availability:
> >
> > In order to aid review this series, its dependency (above)
> > and the related patch "serial: sh-sci: Document SoC specific bindings for
> > r8a7796", which has been posted separately, are available at:
> >
> > git://git.kernel.org/pub/scm/linux/kernel/git/horms/renesas.git topic/r8a7796-v3
> >
> > To be entirely clear, at the time of writing I have _not_ queued up this
> > series for mainline.
>
> I have queued this up for v4.8.
>
>
> I acknowledge that there has been some discussion of sharing DT between
> the r8a7795 and r8a7796. However it is my considered opinion that the level
> of duplication in the approach taken by this patchset is in keeping with
> the practice already used in the tree. And that material benefits in terms
> of ease of maintenance can only be realised with a solution that goes
> beyond breaking common nodes into a shared dtsi file.
>
> It is my request that my decision as co-maintainer of the files
> in question be respected.
Bother, I spoke to soon.
There is a compile-time dependency on 8a7796-cpg-mssr.h
so "[PATCH 0/4] clk: renesas: cpg-mssr: Add support for R-Car M3-W"
needs to be present. I have deferred these patches pending that.
next prev parent reply other threads:[~2016-06-06 1:52 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-05-24 1:54 [PATCH v3 0/3] arm64: Add Renesas R8A7796 SoC support Simon Horman
2016-05-24 1:54 ` [PATCH v3 1/3] arm64: dts: r8a7796: " Simon Horman
2016-05-24 5:30 ` Dirk Behme
2016-05-25 0:48 ` Simon Horman
2016-05-25 5:10 ` Dirk Behme
2016-05-25 7:32 ` Dirk Behme
2016-05-26 7:03 ` Geert Uytterhoeven
2016-05-26 7:32 ` Dirk Behme
2016-05-26 8:05 ` Geert Uytterhoeven
2016-05-26 8:11 ` Dirk Behme
2016-05-26 2:28 ` Simon Horman
2016-05-26 7:14 ` Dirk Behme
2016-05-27 0:42 ` Simon Horman
2016-05-27 6:39 ` Geert Uytterhoeven
2016-05-27 7:32 ` Dirk Behme
2016-06-29 8:15 ` Dirk Behme
2016-07-20 23:51 ` Simon Horman
2016-07-21 5:20 ` Dirk Behme
2016-07-22 1:47 ` Simon Horman
2016-05-25 7:38 ` Dirk Behme
2016-05-26 2:31 ` Simon Horman
2016-05-24 1:54 ` [PATCH v3 2/3] arm64: dts: salvator-x: add Salvator-X board on R8A7796 SoC Simon Horman
2016-05-24 1:54 ` [PATCH v3 3/3] arm64: defconfig: enable Renesas " Simon Horman
2016-06-06 1:33 ` [PATCH v3 0/3] arm64: Add Renesas R8A7796 SoC support Simon Horman
2016-06-06 1:52 ` Simon Horman [this message]
2016-06-24 3:05 ` Simon Horman
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=20160606015201.GA2317@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).