From: Anand Moon <linux.amoon@gmail.com>
To: Rob Herring <robh+dt@kernel.org>,
Martin Blumenstingl <martin.blumenstingl@googlemail.com>,
Jerome Brunet <jbrunet@baylibre.com>,
Neil Armstrong <narmstrong@baylibre.com>,
Kevin Hilman <khilman@baylibre.com>
Cc: devicetree@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-arm-kernel@lists.infradead.org,
linux-amlogic@lists.infradead.org
Subject: [RFC-next 0/1] Odroid C2: Enable DVFS for cpu
Date: Fri, 1 Nov 2019 14:31:25 +0000 [thread overview]
Message-ID: <20191101143126.2549-1-linux.amoon@gmail.com> (raw)
Some how this patch got lost, so resend this again.
[0] https://patchwork.kernel.org/patch/11136545/
This patch enable DVFS on GXBB Odroid C2.
DVFS has been tested by running the arm64 cpuburn
[1] https://github.com/ssvb/cpuburn-arm/blob/master/cpuburn-a53.S
PM-QA testing
[2] https://git.linaro.org/power/pm-qa.git [cpufreq testcase]
Tested on latest U-Boot 2019.07-1 (Aug 01 2019 - 23:58:01 +0000) Arch Linux ARM
Patch based on my next-20191031 for 5.5.x kernel.
Hope this is not late entry.
Best Regards
-Anand
Anand Moon (1):
arm64: dts: meson: odroid-c2: Enable SCPI DVFS for cpu
arch/arm64/boot/dts/amlogic/meson-gxbb-odroidc2.dts | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
--
2.23.0
_______________________________________________
linux-amlogic mailing list
linux-amlogic@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-amlogic
next reply other threads:[~2019-11-01 14:31 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-11-01 14:31 Anand Moon [this message]
2019-11-01 14:31 ` [RFC-next 1/1] arm64: dts: meson: odroid-c2: Enable SCPI DVFS for cpu Anand Moon
2019-12-09 22:12 ` [RFC-next 0/1] Odroid C2: Enable " Kevin Hilman
2019-12-10 8:43 ` Neil Armstrong
2019-12-10 14:50 ` Anand Moon
2019-12-10 18:13 ` Kevin Hilman
2019-12-10 20:04 ` Martin Blumenstingl
2019-12-10 21:47 ` Kevin Hilman
2019-12-11 8:49 ` Neil Armstrong
2019-12-12 20:09 ` Martin Blumenstingl
2019-12-13 11:28 ` Anand Moon
2019-12-13 13:24 ` Neil Armstrong
2019-12-13 14:23 ` Anand Moon
2020-01-02 0:16 ` Brad
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=20191101143126.2549-1-linux.amoon@gmail.com \
--to=linux.amoon@gmail.com \
--cc=devicetree@vger.kernel.org \
--cc=jbrunet@baylibre.com \
--cc=khilman@baylibre.com \
--cc=linux-amlogic@lists.infradead.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=martin.blumenstingl@googlemail.com \
--cc=narmstrong@baylibre.com \
--cc=robh+dt@kernel.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).