From: "Clément Péron" <peron.clem@gmail.com>
To: "Ondřej Jirman" <megous@megous.com>,
"Maxime Ripard" <maxime@cerno.tech>,
"Clément Péron" <peron.clem@gmail.com>,
"Chen-Yu Tsai" <wens@csie.org>,
"Rob Herring" <robh+dt@kernel.org>,
linux-arm-kernel <linux-arm-kernel@lists.infradead.org>,
devicetree <devicetree@vger.kernel.org>,
linux-kernel <linux-kernel@vger.kernel.org>,
linux-sunxi <linux-sunxi@googlegroups.com>
Subject: Re: [PATCH v3 0/7] Add support for Allwinner H6 DVFS
Date: Mon, 20 Apr 2020 14:36:32 +0200 [thread overview]
Message-ID: <CAJiuCcdDge21pRmN8LzKv_tMqBoD9KHg96MUxDS9gp0+xbroJg@mail.gmail.com> (raw)
In-Reply-To: <20200420103927.uvzotrolz2inz6q2@core.my.home>
Hi Ondrej, Maxime,
On Mon, 20 Apr 2020 at 12:39, Ondřej Jirman <megous@megous.com> wrote:
>
> Hi Maxime,
>
> On Mon, Apr 20, 2020 at 10:45:47AM +0200, Maxime Ripard wrote:
> > Hi,
> >
> > On Sun, Apr 19, 2020 at 03:50:04PM +0200, Clément Péron wrote:
> > > Now that required drivers are merged we can contibute on DVFS
> > > support for Allwinner H6.
> > >
> > > This serie is based on Yangtao Li serie[0] and Ondřej Jirman work[1].
> > >
> > > Most of the OPP tables are taken from original vendor kernel[2].
> > > Plus there are new CPU frequencies at 1.6GHz, 1.7GHz and 1.8GHz.
> > >
> > > I wrote a simple script to randomly set a frequency during
> > > a random time[3]. This script is quite stressfull and set some high
> > > frequency without checking temperature. This can result on behavior
> > > that whould not occurs with the real cpufreq framework.
> > > As Maxime point out I also tested with cpufreq-ljt-stress-test
> > > (found here https://github.com/ssvb/cpuburn-arm).
> > > This script doesn't trigger any issue.
> > > I also test that that offlining CPU0 and doing DVFS on other CPUs
> > > works. As CPU regulator is only set for CPU0.
> > >
> > > The GPU devfreq was drop as the regulator is still not properly
> > > drive by panfrost driver[4].
> > > I will re-introduce it later.
> > >
> > > Ondřej Jirman has an Orange Pi 3, Jernej has a PineH64 and a Tanix
> > > TX6 boards and I have a Beelink GS1 board so I have enable these
> > > boards. But CPU Devfreq is really touchy has it depends on:
> > > board design, SoC speed_grade and environement which can affect
> > > thermal cooling and have different behavior for different user.
> > >
> > > If people can test this serie and give feedback, I will try to
> > > introduce this in LibreElec tree, so LE community can test it.
> >
> > Applied all of them, thanks!
>
> Please also apply "[PATCH v2 1/7] arm64: dts: allwinner: h6: Add
> clock to CPU cores" from the v2 series, otherwise cpufreq will
> not work.
>
> I can also send a missing patch adding the trip points, and cpu
> as a cooling device, that I linked in my other reply to this patch
> series afterwards, if Clément wants.
Indeed I have sent using the following cmd : "git send-email --to=XXXX HEAD~7"
from the previous version.
I should had do Instead: "git send-email --to=XXXX next/master "
Sorry for that :(
Clément
>
> regards,
> o.
>
> > Maxime
>
>
next prev parent reply other threads:[~2020-04-20 12:36 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-04-19 13:50 [PATCH v3 0/7] Add support for Allwinner H6 DVFS Clément Péron
2020-04-19 13:50 ` [PATCH v3 1/7] arm64: dts: allwinner: h6: Add CPU Operating Performance Points table Clément Péron
2020-04-19 13:50 ` [PATCH v3 2/7] arm64: configs: Enable sun50i cpufreq nvmem Clément Péron
2020-04-19 13:50 ` [PATCH v3 3/7] arm64: dts: allwinner: h6: Enable CPU opp tables for Beelink GS1 Clément Péron
2020-04-19 13:50 ` [PATCH v3 4/7] arm64: dts: allwinner: h6: Enable CPU opp tables for Orange Pi 3 Clément Péron
2020-04-19 13:50 ` [PATCH v3 5/7] arm64: dts: allwinner: h6: Enable CPU opp tables for Tanix TX6 Clément Péron
2020-04-19 13:50 ` [PATCH v3 6/7] arm64: dts: allwinner: Sort Pine H64 device-tree nodes Clément Péron
2020-04-19 13:50 ` [PATCH v3 7/7] arm64: dts: allwinner: h6: Enable CPU and GPU opp tables for Pine H64 Clément Péron
2020-04-20 8:45 ` [PATCH v3 0/7] Add support for Allwinner H6 DVFS Maxime Ripard
2020-04-20 10:39 ` Ondřej Jirman
2020-04-20 12:36 ` Clément Péron [this message]
2020-04-20 12:47 ` Maxime Ripard
2020-04-20 12:49 ` Clément Péron
2020-04-20 9:48 ` [linux-sunxi] " Ondřej Jirman
2020-04-20 10:27 ` Ondřej Jirman
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=CAJiuCcdDge21pRmN8LzKv_tMqBoD9KHg96MUxDS9gp0+xbroJg@mail.gmail.com \
--to=peron.clem@gmail.com \
--cc=devicetree@vger.kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-sunxi@googlegroups.com \
--cc=maxime@cerno.tech \
--cc=megous@megous.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).