From: Kevin Hilman <khilman@baylibre.com>
To: Neil Armstrong <narmstrong@baylibre.com>
Cc: linux-amlogic@lists.infradead.org,
linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org, Michal Lazo <michal.lazo@gmail.com>
Subject: Re: [PATCH] ARM64: dts: meson: bump mali450 clk to 744MHz
Date: Mon, 19 Mar 2018 16:39:57 -0700 [thread overview]
Message-ID: <7hbmfjskhe.fsf@baylibre.com> (raw)
In-Reply-To: <1520853021-5412-1-git-send-email-narmstrong@baylibre.com> (Neil Armstrong's message of "Mon, 12 Mar 2018 12:10:21 +0100")
Neil Armstrong <narmstrong@baylibre.com> writes:
> The Mali-450 IP can run up to 744MHz, bump the frequency using
> the GP0 PLL clock.
>
> Cc: Michal Lazo <michal.lazo@gmail.com>
> Signed-off-by: Neil Armstrong <narmstrong@baylibre.com>
Applied to v4.17/dt64,
Thanks,
Kevin
prev parent reply other threads:[~2018-03-19 23:40 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-03-12 11:10 [PATCH] ARM64: dts: meson: bump mali450 clk to 744MHz Neil Armstrong
2018-03-19 23:39 ` Kevin Hilman [this message]
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=7hbmfjskhe.fsf@baylibre.com \
--to=khilman@baylibre.com \
--cc=linux-amlogic@lists.infradead.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=michal.lazo@gmail.com \
--cc=narmstrong@baylibre.com \
/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).