From: olof@lixom.net (Olof Johansson)
To: linux-arm-kernel@lists.infradead.org
Subject: [GIT PULL] Second Round of Renesas ARM64 Based SoC DT Updates for v4.8
Date: Wed, 6 Jul 2016 22:06:29 -0700 [thread overview]
Message-ID: <20160707050629.GD32389@localhost> (raw)
In-Reply-To: <cover.1467291676.git.horms+renesas@verge.net.au>
On Thu, Jun 30, 2016 at 04:15:06PM +0200, Simon Horman wrote:
> Hi Olof, Hi Kevin, Hi Arnd,
>
> Please consider these second round of Renesas ARM64 based SoC DT updates
> for v4.8.
>
> The support for the new r8a7796 SoC depends on clk definitions which
> I have taken the liberty of including in this branch to avoid depending
> on another branch. The definitions in question are derived from the
> datasheet and in keeping with the approach taken for other Renesas SoCs.
>
> This pull request is based on the previous round of
> such requests, tagged as renesas-arm64-dt-for-v4.8,
> which you have already pulled.
>
>
> The following changes since commit 21cc405c8a6332ddad2d2751a9723b2b3e227a05:
>
> arm64: dts: r8a7795: Drop 0x from unit address of gic (2016-05-30 10:18:01 +0900)
>
> are available in the git repository at:
>
> git://git.kernel.org/pub/scm/linux/kernel/git/horms/renesas.git tags/renesas-arm64-dt2-for-v4.8
>
> for you to fetch changes up to 2c9616a1fc01c656f04f03feb58fa12d9b30802a:
>
> arm64: dts: r8a7796/salvator-x: Enable watchdog timer (2016-06-28 07:04:44 +0200)
>
> ----------------------------------------------------------------
> Second Round of Renesas ARM64 Based SoC DT Updates for v4.8
>
> * Add support for r8a7796/salvator-x (R-Car Gen 3 M3-W)
> * Add CAN support to r8a7795 ((R-Car Gen 3 H3)
>
> ----------------------------------------------------------------
> Geert Uytterhoeven (6):
> arm64: dts: r8a7795: Add missing blank lines between cpu nodes
> clk: renesas: Add r8a7796 CPG Core Clock Definitions
This is just applied here as a patch, but will be needed on the clk
driver side too.
The patch should be shared between the two trees, not applied twice. So you'll
need to provide a stable branch from either side that has this applied, and
base the dts changes and the clk changes on that.
(Pull request not merged due to this).
-Olof
prev parent reply other threads:[~2016-07-07 5:06 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-06-30 14:15 [GIT PULL] Second Round of Renesas ARM64 Based SoC DT Updates for v4.8 Simon Horman
2016-06-30 14:14 ` [PATCH 1/9] arm64: dts: r8a7795: Add missing blank lines between cpu nodes Simon Horman
2016-06-30 14:15 ` [PATCH 2/9] arm64: dts: r8a7795: Add CAN FD support Simon Horman
2016-06-30 14:15 ` [PATCH 3/9] clk: renesas: Add r8a7796 CPG Core Clock Definitions Simon Horman
2016-06-30 14:15 ` [PATCH 4/9] arm64: dts: r8a7796: Add Renesas R8A7796 SoC support Simon Horman
2016-06-30 14:15 ` [PATCH 5/9] arm64: dts: salvator-x: add Salvator-X board on R8A7796 SoC Simon Horman
2016-06-30 14:15 ` [PATCH 6/9] arm64: dts: r8a7796: Add SYSC PM Domains Simon Horman
2016-06-30 14:15 ` [PATCH 7/9] arm64: dts: r8a7796: Use SYSC "always-on" PM Domain Simon Horman
2016-06-30 14:15 ` [PATCH 8/9] arm64: dts: r8a7796: Add RWDT node Simon Horman
2016-06-30 14:15 ` [PATCH 9/9] arm64: dts: r8a7796/salvator-x: Enable watchdog timer Simon Horman
2016-07-07 5:06 ` Olof Johansson [this message]
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=20160707050629.GD32389@localhost \
--to=olof@lixom.net \
--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).