From: Jerome Brunet <jbrunet@baylibre.com>
To: Stephen Boyd <sboyd@kernel.org>,
Michael Turquette <mturquette@baylibre.com>
Cc: linux-amlogic@lists.infradead.org, linux-clk@vger.kernel.org,
Neil Armstrong <narmstrong@baylibre.com>
Subject: [GIT PULL] clk: meson: fixes for v5.4
Date: Tue, 08 Oct 2019 09:26:12 +0200 [thread overview]
Message-ID: <1jzhibaeaz.fsf@starbuckisacylon.baylibre.com> (raw)
Hi Stephen,
Please pull these few fixes for the current release.
Thanks
Jerome
The following changes since commit 54ecb8f7028c5eb3d740bb82b0f1d90f2df63c5c:
Linux 5.4-rc1 (2019-09-30 10:35:40 -0700)
are available in the Git repository at:
git://github.com/BayLibre/clk-meson.git tags/clk-meson-fixes-v5.4-1
for you to fetch changes up to 90b171f6035688236a3f09117a683020be45603a:
clk: meson: g12a: set CLK_MUX_ROUND_CLOSEST on the cpu clock muxes (2019-10-01 14:51:15 +0200)
----------------------------------------------------------------
First round of amlogic clock fixes for v5.4.
This fixes the clock rate propagation for the g12a cpu clocks and
the gxbb adc clock.
----------------------------------------------------------------
Martin Blumenstingl (1):
clk: meson: gxbb: let sar_adc_clk_div set the parent clock rate
Neil Armstrong (2):
clk: meson: g12a: fix cpu clock rate setting
clk: meson: g12a: set CLK_MUX_ROUND_CLOSEST on the cpu clock muxes
drivers/clk/meson/g12a.c | 13 +++++++++++--
drivers/clk/meson/gxbb.c | 1 +
2 files changed, 12 insertions(+), 2 deletions(-)
_______________________________________________
linux-amlogic mailing list
linux-amlogic@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-amlogic
next reply other threads:[~2019-10-08 7:26 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-10-08 7:26 Jerome Brunet [this message]
2019-10-16 22:58 ` [GIT PULL] clk: meson: fixes for v5.4 Stephen Boyd
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=1jzhibaeaz.fsf@starbuckisacylon.baylibre.com \
--to=jbrunet@baylibre.com \
--cc=linux-amlogic@lists.infradead.org \
--cc=linux-clk@vger.kernel.org \
--cc=mturquette@baylibre.com \
--cc=narmstrong@baylibre.com \
--cc=sboyd@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).