From: Simon Horman <horms@verge.net.au>
To: Geert Uytterhoeven <geert+renesas@glider.be>
Cc: devicetree@vger.kernel.org,
Takeshi Kihara <takeshi.kihara.df@renesas.com>,
Magnus Damm <magnus.damm@gmail.com>,
Dirk Behme <dirk.behme@gmail.com>,
linux-renesas-soc@vger.kernel.org,
linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH v4 0/2] arm64: dts: r8a7795: Add Cortex-A53 CPU cores and PMU
Date: Thu, 2 Mar 2017 16:05:45 +0100 [thread overview]
Message-ID: <20170302150545.GV6301@verge.net.au> (raw)
In-Reply-To: <1487944768-31983-1-git-send-email-geert+renesas@glider.be>
Hi Geert,
On Fri, Feb 24, 2017 at 02:59:26PM +0100, Geert Uytterhoeven wrote:
> Hi Simon, Magnus,
>
> This patch series adds the Cortex-A53 CPU cores and PMU on the Renesas
> R-Car H3 SoC to its DTS file.
>
> Note that these patches describes the hardware; actual enabling of the
> CPU depends on the PSCI firmware.
>
> With the current firmware version (v2.16.0), only the CA57 CPU cores are
> enabled, hence these patches do not introduce undeterministic scheduling
> behavior due to migration between big and LITTLE cores.
>
> Changes compared to v3:
> - Drop bogus links from the pmu_a57 node to the CA53 nodes,
> - Add Cortex-A53 PMU node.
>
> Tested on r8a7795/salvator-x, with CPU hot(un)plug and system suspend.
>
> Thanks for applying!
I believe this patch-set is in keeping with the face-to-face discussion
between Magnus, yourself, myself and others in Brussels last month.
With that in mind I have queued this up for v4.12.
prev parent reply other threads:[~2017-03-02 15:05 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-02-24 13:59 [PATCH v4 0/2] arm64: dts: r8a7795: Add Cortex-A53 CPU cores and PMU Geert Uytterhoeven
[not found] ` <1487944768-31983-1-git-send-email-geert+renesas-gXvu3+zWzMSzQB+pC5nmwQ@public.gmane.org>
2017-02-24 13:59 ` [PATCH v4 1/2] arm64: dts: r8a7795: Add Cortex-A53 CPU cores Geert Uytterhoeven
2017-02-24 13:59 ` [PATCH v4 2/2] arm64: dts: r8a7795: Add Cortex-A53 PMU node Geert Uytterhoeven
2017-03-02 15:05 ` 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=20170302150545.GV6301@verge.net.au \
--to=horms@verge.net.au \
--cc=devicetree@vger.kernel.org \
--cc=dirk.behme@gmail.com \
--cc=geert+renesas@glider.be \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-renesas-soc@vger.kernel.org \
--cc=magnus.damm@gmail.com \
--cc=takeshi.kihara.df@renesas.com \
/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).