From: Simon Horman <horms@verge.net.au>
To: Geert Uytterhoeven <geert+renesas@glider.be>
Cc: Magnus Damm <magnus.damm@gmail.com>,
Rob Herring <robh+dt@kernel.org>,
Mark Rutland <mark.rutland@arm.com>,
linux-renesas-soc@vger.kernel.org,
linux-arm-kernel@lists.infradead.org, devicetree@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH 0/4] arm64: renesas: Add support for Salvator-XS
Date: Mon, 12 Jun 2017 11:10:20 +0200 [thread overview]
Message-ID: <20170612091019.GC15434@verge.net.au> (raw)
In-Reply-To: <1497008629-3974-1-git-send-email-geert+renesas@glider.be>
On Fri, Jun 09, 2017 at 01:43:45PM +0200, Geert Uytterhoeven wrote:
> Hi Simon, Magnus,
>
> The Renesas Salvator-XS (Salvator-X 2nd version) development board can
> be equipped with either an R-Car H3 ES2.0 or M3-W ES1.x SiP, which are
> pin-compatible.
>
> This patch series adds initial support for the Renesas Salvator-XS
> development board equipped with an R-Car H3 ES2.0 SiP. The support
> level is similar to the existing support for Salvator-X with the same
> SiP. See below for exceptions.
>
> The Salvator-XS board is similar but not identical to the already
> supported Salvator-X board. To avoid duplication, the common parts are
> extracted first into its own .dtsi file.
> Noteworthy differences are:
> - The main clock crystal ticks at a slightly different rate.
> - On R-Car H3 ES2.0, SATA no longer uses dedicated pins, but shares
> them with the second PCIe channel. To cater for this, a MAX4888B
> multiplexer has been added to Salvator-XS. As the default hardware
> configuration enables PCIe, I disabled SATA.
> - The Versaclock5 clock generator has been replaced by a similar
> member of the Versaclock6 family. As the latter is not supported by
> Linux yet, I left it out.
> - The USB3.0 micro-B connector is replaced by a USB2.0 micro-AB
> connector (both are not yet supported, so no change is needed now).
>
> Dependencies:
> - renesas-devel-20170608-v4.12-rc4,
> - "arm64: dts: salvator-x: Add missing index to PWM pinctrl subnode
> name".
>
> For your convenience, I've pushed this series, its dependencies, and a
> few related driver changes to the topic/r8a7795-salvator-xs branch of
> the git repository at
> https://git.kernel.org/cgit/linux/kernel/git/geert/renesas-drivers.git
>
> This has been tested on Salvator-XS with R-Car H3 ES2.0, and Salvator-X
> with R-Car H3 ES1.0.
>
> Thanks!
Thanks, I have queued this up for v4.13.
prev parent reply other threads:[~2017-06-12 9:10 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-06-09 11:43 Geert Uytterhoeven
2017-06-09 11:43 ` [PATCH 1/4] ARM: shmobile: Document Renesas H3-based Salvator-XS board DT bindings Geert Uytterhoeven
2017-06-18 14:04 ` Rob Herring
2017-06-09 11:43 ` [PATCH 2/4] arm64: dts: renesas: Extract common Salvator-X/XS board support Geert Uytterhoeven
2017-06-09 11:43 ` [PATCH 3/4] arm64: dts: renesas: Add common Salvator-XS " Geert Uytterhoeven
2017-06-09 11:43 ` [PATCH 4/4] arm64: dts: renesas: Add support for Salvator-XS with R-Car H3 ES2.0 Geert Uytterhoeven
2017-06-12 9:10 ` Simon Horman [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=20170612091019.GC15434@verge.net.au \
--to=horms@verge.net.au \
--cc=devicetree@vger.kernel.org \
--cc=geert+renesas@glider.be \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-renesas-soc@vger.kernel.org \
--cc=magnus.damm@gmail.com \
--cc=mark.rutland@arm.com \
--cc=robh+dt@kernel.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
all inboxes | Powered by JetHome®