From: icenowy@aosc.io
To: Maxime Ripard <maxime.ripard@free-electrons.com>
Cc: Chen-Yu Tsai <wens@csie.org>,
linux-arm-kernel@lists.infradead.org, devicetree@vger.kernel.org,
linux-kernel@vger.kernel.org, linux-clk@vger.kernel.org,
linux-sunxi@googlegroups.com
Subject: Re: [PATCH 0/3] Simple DVFS support for Allwinner A64 SoC
Date: Wed, 27 Sep 2017 19:51:30 +0800 [thread overview]
Message-ID: <9b3aeb6cb155bb2f9a7cee438de82ccb@aosc.io> (raw)
In-Reply-To: <20170925102744.qixfwlheeimemhcf@flea.home>
在 2017-09-25 18:27,Maxime Ripard 写道:
> On Mon, Sep 25, 2017 at 10:12:09AM +0000, Icenowy Zheng wrote:
>> 于 2017年9月25日 GMT+08:00 下午6:10:27, Maxime Ripard
>> <maxime.ripard@free-electrons.com> 写到:
>> >Hi,
>> >
>> >On Sat, Sep 23, 2017 at 12:15:28AM +0000, Icenowy Zheng wrote:
>> >> This patchset imports simple DVFS support for Allwinner A64 SoC.
>> >>
>> >> As the thermal sensor driver is not yet implemented and some boards
>> >> have still no AXP PMIC support, now only two OPPs are present --
>> >> 648MHz@1.04V and 816MHz@1.1V to prevent overheat or undervoltage.
>> >>
>> >> PATCH 1 is a fix to the CCU driver of A64, and the remaining patches
>> >> set up the device tree bits of the DVFS on Pine64.
>> >
>> >How has this been tested?
>> >
>> >What tasks did you run, with what governor, etc...
>>
>> I only tested manual frequency switching between 648MHz and
>> 816MHz, and tested the PLL stuck issue by change the OPPs to
>> some random value.
>
> Ideally, we should test that it's actually reliable. Poorly chosen
> OPPs might lead to corrupt data that you might not get before a while.
>
> Please test using:
> https://linux-sunxi.org/Hardware_Reliability_Tests#Reliability_of_cpufreq_voltage.2Ffrequency_settings
>
> And post the report.
```
root@p64 [ cpuburn-arm@master ] # ./cpuburn-a53 &
[1] 2543
root@p64 [ cpuburn-arm@master ] # ./cpufreq-ljt-stress-test
Creating './whitenoise-1920x1080.jpg' ... done
CPU stress test, which is doing JPEG decoding by libjpeg-turbo
at different cpufreq operating points.
Testing CPU 0
816 MHz ............................................................
OK
648 MHz ............................................................
OK
Testing CPU 1
816 MHz ............................................................
OK
648 MHz ............................................................
OK
Testing CPU 2
816 MHz ............................................................
OK
648 MHz ............................................................
OK
Testing CPU 3
816 MHz ............................................................
OK
648 MHz ............................................................
OK
Overall result : PASSED
```
>
> Maxime
WARNING: multiple messages have this Message-ID (diff)
From: icenowy@aosc.io (icenowy at aosc.io)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 0/3] Simple DVFS support for Allwinner A64 SoC
Date: Wed, 27 Sep 2017 19:51:30 +0800 [thread overview]
Message-ID: <9b3aeb6cb155bb2f9a7cee438de82ccb@aosc.io> (raw)
In-Reply-To: <20170925102744.qixfwlheeimemhcf@flea.home>
? 2017-09-25 18:27?Maxime Ripard ???
> On Mon, Sep 25, 2017 at 10:12:09AM +0000, Icenowy Zheng wrote:
>> ? 2017?9?25? GMT+08:00 ??6:10:27, Maxime Ripard
>> <maxime.ripard@free-electrons.com> ??:
>> >Hi,
>> >
>> >On Sat, Sep 23, 2017 at 12:15:28AM +0000, Icenowy Zheng wrote:
>> >> This patchset imports simple DVFS support for Allwinner A64 SoC.
>> >>
>> >> As the thermal sensor driver is not yet implemented and some boards
>> >> have still no AXP PMIC support, now only two OPPs are present --
>> >> 648MHz at 1.04V and 816MHz at 1.1V to prevent overheat or undervoltage.
>> >>
>> >> PATCH 1 is a fix to the CCU driver of A64, and the remaining patches
>> >> set up the device tree bits of the DVFS on Pine64.
>> >
>> >How has this been tested?
>> >
>> >What tasks did you run, with what governor, etc...
>>
>> I only tested manual frequency switching between 648MHz and
>> 816MHz, and tested the PLL stuck issue by change the OPPs to
>> some random value.
>
> Ideally, we should test that it's actually reliable. Poorly chosen
> OPPs might lead to corrupt data that you might not get before a while.
>
> Please test using:
> https://linux-sunxi.org/Hardware_Reliability_Tests#Reliability_of_cpufreq_voltage.2Ffrequency_settings
>
> And post the report.
```
root at p64 [ cpuburn-arm at master ] # ./cpuburn-a53 &
[1] 2543
root at p64 [ cpuburn-arm at master ] # ./cpufreq-ljt-stress-test
Creating './whitenoise-1920x1080.jpg' ... done
CPU stress test, which is doing JPEG decoding by libjpeg-turbo
at different cpufreq operating points.
Testing CPU 0
816 MHz ............................................................
OK
648 MHz ............................................................
OK
Testing CPU 1
816 MHz ............................................................
OK
648 MHz ............................................................
OK
Testing CPU 2
816 MHz ............................................................
OK
648 MHz ............................................................
OK
Testing CPU 3
816 MHz ............................................................
OK
648 MHz ............................................................
OK
Overall result : PASSED
```
>
> Maxime
WARNING: multiple messages have this Message-ID (diff)
From: icenowy-h8G6r0blFSE@public.gmane.org
To: Maxime Ripard
<maxime.ripard-wi1+55ScJUtKEb57/3fJTNBPR1lH4CV8@public.gmane.org>
Cc: Chen-Yu Tsai <wens-jdAy2FN1RRM@public.gmane.org>,
linux-arm-kernel-IAPFreCvJWM7uuMidbF8XUB+6BGkLq7r@public.gmane.org,
devicetree-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
linux-clk-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
linux-sunxi-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org
Subject: Re: [PATCH 0/3] Simple DVFS support for Allwinner A64 SoC
Date: Wed, 27 Sep 2017 19:51:30 +0800 [thread overview]
Message-ID: <9b3aeb6cb155bb2f9a7cee438de82ccb@aosc.io> (raw)
In-Reply-To: <20170925102744.qixfwlheeimemhcf-YififvaboMKzQB+pC5nmwQ@public.gmane.org>
在 2017-09-25 18:27,Maxime Ripard 写道:
> On Mon, Sep 25, 2017 at 10:12:09AM +0000, Icenowy Zheng wrote:
>> 于 2017年9月25日 GMT+08:00 下午6:10:27, Maxime Ripard
>> <maxime.ripard-wi1+55ScJUtKEb57/3fJTNBPR1lH4CV8@public.gmane.org> 写到:
>> >Hi,
>> >
>> >On Sat, Sep 23, 2017 at 12:15:28AM +0000, Icenowy Zheng wrote:
>> >> This patchset imports simple DVFS support for Allwinner A64 SoC.
>> >>
>> >> As the thermal sensor driver is not yet implemented and some boards
>> >> have still no AXP PMIC support, now only two OPPs are present --
>> >> 648MHz@1.04V and 816MHz@1.1V to prevent overheat or undervoltage.
>> >>
>> >> PATCH 1 is a fix to the CCU driver of A64, and the remaining patches
>> >> set up the device tree bits of the DVFS on Pine64.
>> >
>> >How has this been tested?
>> >
>> >What tasks did you run, with what governor, etc...
>>
>> I only tested manual frequency switching between 648MHz and
>> 816MHz, and tested the PLL stuck issue by change the OPPs to
>> some random value.
>
> Ideally, we should test that it's actually reliable. Poorly chosen
> OPPs might lead to corrupt data that you might not get before a while.
>
> Please test using:
> https://linux-sunxi.org/Hardware_Reliability_Tests#Reliability_of_cpufreq_voltage.2Ffrequency_settings
>
> And post the report.
```
root@p64 [ cpuburn-arm@master ] # ./cpuburn-a53 &
[1] 2543
root@p64 [ cpuburn-arm@master ] # ./cpufreq-ljt-stress-test
Creating './whitenoise-1920x1080.jpg' ... done
CPU stress test, which is doing JPEG decoding by libjpeg-turbo
at different cpufreq operating points.
Testing CPU 0
816 MHz ............................................................
OK
648 MHz ............................................................
OK
Testing CPU 1
816 MHz ............................................................
OK
648 MHz ............................................................
OK
Testing CPU 2
816 MHz ............................................................
OK
648 MHz ............................................................
OK
Testing CPU 3
816 MHz ............................................................
OK
648 MHz ............................................................
OK
Overall result : PASSED
```
>
> Maxime
--
You received this message because you are subscribed to the Google Groups "linux-sunxi" group.
To unsubscribe from this group and stop receiving emails from it, send an email to linux-sunxi+unsubscribe-/JYPxA39Uh5TLH3MbocFF+G/Ez6ZCGd0@public.gmane.org
For more options, visit https://groups.google.com/d/optout.
next prev parent reply other threads:[~2017-09-27 11:51 UTC|newest]
Thread overview: 48+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-09-23 0:15 [PATCH 0/3] Simple DVFS support for Allwinner A64 SoC Icenowy Zheng
2017-09-23 0:15 ` Icenowy Zheng
2017-09-23 0:15 ` Icenowy Zheng
2017-09-23 0:15 ` [PATCH 1/3] clk: sunxi-ng: add mux and pll notifiers for A64 CPU clock Icenowy Zheng
2017-09-23 0:15 ` Icenowy Zheng
2017-09-23 0:15 ` Icenowy Zheng
2017-09-28 10:27 ` Maxime Ripard
2017-09-28 10:27 ` Maxime Ripard
2017-09-28 10:27 ` Maxime Ripard
2017-09-28 10:42 ` icenowy
2017-09-28 10:42 ` icenowy-h8G6r0blFSE
2017-09-28 10:42 ` icenowy at aosc.io
2017-09-28 14:20 ` Maxime Ripard
2017-09-28 14:20 ` Maxime Ripard
2017-09-28 14:20 ` Maxime Ripard
2017-09-28 14:24 ` icenowy
2017-09-28 14:24 ` icenowy at aosc.io
2017-09-28 14:31 ` Maxime Ripard
2017-09-28 14:31 ` Maxime Ripard
2017-09-23 0:15 ` [PATCH 2/3] arm64: allwinner: a64: add CPU opp table Icenowy Zheng
2017-09-23 0:15 ` Icenowy Zheng
2017-09-23 0:15 ` Icenowy Zheng
2017-09-25 17:38 ` [linux-sunxi] " Samuel Holland
2017-09-25 17:38 ` Samuel Holland
2017-09-25 17:38 ` Samuel Holland
2017-09-23 0:15 ` [PATCH 3/3] arm64: allwinner: a64: set CPU regulator for Pine64 Icenowy Zheng
2017-09-23 0:15 ` Icenowy Zheng
2017-09-25 10:10 ` [PATCH 0/3] Simple DVFS support for Allwinner A64 SoC Maxime Ripard
2017-09-25 10:10 ` Maxime Ripard
2017-09-25 10:10 ` Maxime Ripard
2017-09-25 10:12 ` Icenowy Zheng
2017-09-25 10:12 ` Icenowy Zheng
2017-09-25 10:12 ` Icenowy Zheng
2017-09-25 10:27 ` Maxime Ripard
2017-09-25 10:27 ` Maxime Ripard
2017-09-25 10:27 ` Maxime Ripard
2017-09-25 10:27 ` Maxime Ripard
2017-09-25 10:29 ` [linux-sunxi] " Icenowy Zheng
2017-09-25 10:29 ` Icenowy Zheng
2017-09-25 10:29 ` Icenowy Zheng
2017-09-25 10:43 ` Maxime Ripard
2017-09-25 10:43 ` Maxime Ripard
2017-09-27 11:51 ` icenowy [this message]
2017-09-27 11:51 ` icenowy-h8G6r0blFSE
2017-09-27 11:51 ` icenowy at aosc.io
2017-09-28 10:28 ` Maxime Ripard
2017-09-28 10:28 ` Maxime Ripard
2017-09-28 10:28 ` 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=9b3aeb6cb155bb2f9a7cee438de82ccb@aosc.io \
--to=icenowy@aosc.io \
--cc=devicetree@vger.kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-clk@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-sunxi@googlegroups.com \
--cc=maxime.ripard@free-electrons.com \
--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 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.