From: Simon Horman <horms@verge.net.au>
To: Geert Uytterhoeven <geert+renesas@glider.be>
Cc: Magnus Damm <magnus.damm@gmail.com>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
Arnd Bergmann <arnd@arndb.de>, Kevin Hilman <khilman@kernel.org>,
Olof Johansson <olof@lixom.net>,
linux-renesas-soc@vger.kernel.org,
linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2 0/3] soc: renesas: rcar-sysc: Add support for R-Car H3 ES2.0
Date: Mon, 3 Apr 2017 06:29:37 -0400 [thread overview]
Message-ID: <20170403102936.GG31988@verge.net.au> (raw)
In-Reply-To: <1490950916-9576-1-git-send-email-geert+renesas@glider.be>
On Fri, Mar 31, 2017 at 11:01:53AM +0200, Geert Uytterhoeven wrote:
> Hi Simon, Magnus,
>
> This patch series adds power domain support for R-Car H3 ES2.0, which
> differs from ES1.x in some areas.
>
> The goal is twofold:
> 1. Support both the ES1.x and ES2.0 SoC revisions in a single binary
> for now,
> 2. Make it clear which code supports ES1.x, so it can easily be
> identified and removed later, when production SoCs are deemed
> ubiquitous.
>
> This is achieved by detecting the SoC revision at runtime using the
> soc_device_match() API, and fixing up the power area table to match the
> actual SoC revision.
>
> Changes compared to v1:
> - Minor changes to the patch descriptions.
>
> As PM Domains are initialized quite early, the Renesas SoC device must
> be initialized earlier, and this series thus depends on the pull
> request "[git pull] base: soc: Improvements for the SoC bus and
> soc_device_match()" I've just sent.
>
> For testers, this series and its dependencies are available in the
> topic/r8a7795es2-sysc-v2 branch of my renesas-drivers git repository at
> git://git.kernel.org/pub/scm/linux/kernel/git/geert/renesas-drivers.git.
> An integration branch for testing on the R-Car H3 ES2.0 based Salvator-X
> development board is provided as topic/r8a7795es2-integration.
>
> This has been tested on Salvator-X with R-Car H3 ES1.0, ES1.1, and ES2.0
> SoCs.
>
> Thanks for applying!
Thanks, done.
WARNING: multiple messages have this Message-ID (diff)
From: horms@verge.net.au (Simon Horman)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH v2 0/3] soc: renesas: rcar-sysc: Add support for R-Car H3 ES2.0
Date: Mon, 3 Apr 2017 06:29:37 -0400 [thread overview]
Message-ID: <20170403102936.GG31988@verge.net.au> (raw)
In-Reply-To: <1490950916-9576-1-git-send-email-geert+renesas@glider.be>
On Fri, Mar 31, 2017 at 11:01:53AM +0200, Geert Uytterhoeven wrote:
> Hi Simon, Magnus,
>
> This patch series adds power domain support for R-Car H3 ES2.0, which
> differs from ES1.x in some areas.
>
> The goal is twofold:
> 1. Support both the ES1.x and ES2.0 SoC revisions in a single binary
> for now,
> 2. Make it clear which code supports ES1.x, so it can easily be
> identified and removed later, when production SoCs are deemed
> ubiquitous.
>
> This is achieved by detecting the SoC revision at runtime using the
> soc_device_match() API, and fixing up the power area table to match the
> actual SoC revision.
>
> Changes compared to v1:
> - Minor changes to the patch descriptions.
>
> As PM Domains are initialized quite early, the Renesas SoC device must
> be initialized earlier, and this series thus depends on the pull
> request "[git pull] base: soc: Improvements for the SoC bus and
> soc_device_match()" I've just sent.
>
> For testers, this series and its dependencies are available in the
> topic/r8a7795es2-sysc-v2 branch of my renesas-drivers git repository at
> git://git.kernel.org/pub/scm/linux/kernel/git/geert/renesas-drivers.git.
> An integration branch for testing on the R-Car H3 ES2.0 based Salvator-X
> development board is provided as topic/r8a7795es2-integration.
>
> This has been tested on Salvator-X with R-Car H3 ES1.0, ES1.1, and ES2.0
> SoCs.
>
> Thanks for applying!
Thanks, done.
next prev parent reply other threads:[~2017-04-03 10:29 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-03-31 9:01 [PATCH v2 0/3] soc: renesas: rcar-sysc: Add support for R-Car H3 ES2.0 Geert Uytterhoeven
2017-03-31 9:01 ` Geert Uytterhoeven
2017-03-31 9:01 ` [PATCH v2 1/3] soc: renesas: Register SoC device early Geert Uytterhoeven
2017-03-31 9:01 ` [PATCH v2 2/3] soc: renesas: rcar-sysc: Add support for fixing up power area tables Geert Uytterhoeven
2017-03-31 9:01 ` [PATCH v2 3/3] soc: renesas: rcar-sysc: Add support for R-Car H3 ES2.0 Geert Uytterhoeven
2017-04-03 10:29 ` Simon Horman [this message]
2017-04-03 10:29 ` [PATCH v2 0/3] " 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=20170403102936.GG31988@verge.net.au \
--to=horms@verge.net.au \
--cc=arnd@arndb.de \
--cc=geert+renesas@glider.be \
--cc=gregkh@linuxfoundation.org \
--cc=khilman@kernel.org \
--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=olof@lixom.net \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.