From: Maxime Ripard <mripard@kernel.org>
To: Vasily Khoruzhick <anarsoul@gmail.com>
Cc: Chen-Yu Tsai <wens@csie.org>, Rob Herring <robh+dt@kernel.org>,
Mark Rutland <mark.rutland@arm.com>,
arm-linux <linux-arm-kernel@lists.infradead.org>,
devicetree <devicetree@vger.kernel.org>
Subject: Re: [PATCH v2 0/4] arm64: allwinner: a64: Enable DVFS on A64
Date: Thu, 9 Jan 2020 17:30:09 +0100 [thread overview]
Message-ID: <20200109163009.v4jc22jyjushbxxx@gilmour.lan> (raw)
In-Reply-To: <CA+E=qVeMvJ96OZ62E_B3byr4dGgtWd3NVD6qqB40gS7ExZy5uw@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1097 bytes --]
On Wed, Jan 08, 2020 at 08:38:10AM -0800, Vasily Khoruzhick wrote:
> On Wed, Jan 8, 2020 at 8:04 AM Maxime Ripard <mripard@kernel.org> wrote:
> >
> > Hi,
> >
> > On Tue, Jan 07, 2020 at 08:20:14PM -0800, Vasily Khoruzhick wrote:
> > > This series introduces new DTSI with operating points for A64,
> > > adds cooling maps and thermal tripping points and enables DVFS
> > > on all the supported A64-based boards
> >
> > Thanks for that new series.
> >
> > I'm not sure I've seen the answer, but how did you test that the OPPs
> > were stable?
>
> I've been using them for close to 2 years and haven't seen any
> issues so far.
I'm sure you did, but those issues can be easily masked depending on
your config (and the default governor you have) and the workload.
> > So far, the only method that proved to be reliable was to run
> > https://github.com/ssvb/cpuburn-arm/blob/master/cpufreq-ljt-stress-test
> >
> > Could you paste the result (one board should be enough) ?
>
> Here is a run on Pine64-LTS:
> https://gist.github.com/anarsoul/23c361b42bcdf4f2e23624f74c4c94bc
Awesome, thanks!
Maxime
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 228 bytes --]
next prev parent reply other threads:[~2020-01-09 16:30 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-01-08 4:20 [PATCH v2 0/4] arm64: allwinner: a64: Enable DVFS on A64 Vasily Khoruzhick
2020-01-08 4:20 ` [PATCH v2 1/4] arm64: dts: allwinner: a64: add CPU clock to CPU0-3 nodes Vasily Khoruzhick
2020-01-08 4:20 ` [PATCH v2 2/4] arm64: dts: allwinner: a64: add cooling maps and thermal tripping points Vasily Khoruzhick
2020-01-08 4:20 ` [PATCH v2 3/4] arm64: dts: allwinner: a64: add dtsi with CPU operating points Vasily Khoruzhick
2020-01-08 4:20 ` [PATCH v2 4/4] arm64: dts: allwinner: a64: enable DVFS Vasily Khoruzhick
2020-01-08 16:04 ` [PATCH v2 0/4] arm64: allwinner: a64: Enable DVFS on A64 Maxime Ripard
2020-01-08 16:38 ` Vasily Khoruzhick
2020-01-09 16:30 ` Maxime Ripard [this message]
2020-01-09 16:33 ` Maxime Ripard
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=20200109163009.v4jc22jyjushbxxx@gilmour.lan \
--to=mripard@kernel.org \
--cc=anarsoul@gmail.com \
--cc=devicetree@vger.kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=mark.rutland@arm.com \
--cc=robh+dt@kernel.org \
--cc=wens@csie.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).