From: Martin Blumenstingl <martin.blumenstingl@googlemail.com>
To: linux-amlogic@lists.infradead.org, khilman@baylibre.com
Cc: Martin Blumenstingl <martin.blumenstingl@googlemail.com>,
linux-kernel@vger.kernel.org,
linux-arm-kernel@lists.infradead.org
Subject: [PATCH 0/3] ARM: dts: meson: fixes for GPU DVFS
Date: Wed, 25 Dec 2019 02:06:04 +0100 [thread overview]
Message-ID: <20191225010607.1504239-1-martin.blumenstingl@googlemail.com> (raw)
While testing my patch to add DVFS support to the lima driver [0] I
found one bug and two inconveniences with the GPU clocks in the
Meson8 and Meson8b .dts:
- the first patch is an actual fix so the two mali GPU clock trees can
actually be used on Meson8b
- patch two and three are to prevent confusion when comparing the
frequencies from the .dts with the actual ones on the system
Neither of these patches are critical, so I based them on top of
v5.6/dt (meaning they target Linux 5.6, not v5.5/fixes).
[0] https://patchwork.kernel.org/patch/11293193/
Martin Blumenstingl (3):
ARM: dts: meson8b: fix the clock controller compatible string
ARM: dts: meson8: use the actual frequency for the GPU's 182.1MHz OPP
ARM: dts: meson8b: use the actual frequency for the GPU's 364MHz OPP
arch/arm/boot/dts/meson8.dtsi | 4 ++--
arch/arm/boot/dts/meson8b.dtsi | 6 +++---
2 files changed, 5 insertions(+), 5 deletions(-)
--
2.24.1
_______________________________________________
linux-amlogic mailing list
linux-amlogic@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-amlogic
next reply other threads:[~2019-12-25 1:06 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-12-25 1:06 Martin Blumenstingl [this message]
2019-12-25 1:06 ` [PATCH 1/3] ARM: dts: meson8b: fix the clock controller compatible string Martin Blumenstingl
2019-12-25 1:06 ` [PATCH 2/3] ARM: dts: meson8: use the actual frequency for the GPU's 182.1MHz OPP Martin Blumenstingl
2019-12-25 1:06 ` [PATCH 3/3] ARM: dts: meson8b: use the actual frequency for the GPU's 364MHz OPP Martin Blumenstingl
2020-01-08 19:01 ` [PATCH 0/3] ARM: dts: meson: fixes for GPU DVFS Kevin Hilman
2020-01-09 18:21 ` patchwork-bot+linux-amlogic
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=20191225010607.1504239-1-martin.blumenstingl@googlemail.com \
--to=martin.blumenstingl@googlemail.com \
--cc=khilman@baylibre.com \
--cc=linux-amlogic@lists.infradead.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.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).