From: Neil Armstrong <narmstrong@baylibre.com>
To: jbrunet@baylibre.com
Cc: Neil Armstrong <narmstrong@baylibre.com>,
linux-clk@vger.kernel.org, linux-amlogic@lists.infradead.org,
linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org
Subject: [PATCH 0/2] clk: meson: g12a: Add CPU Clock support
Date: Fri, 1 Mar 2019 11:21:38 +0100 [thread overview]
Message-ID: <20190301102140.7181-1-narmstrong@baylibre.com> (raw)
This patchset adds support for the clock tree feeding the 4xCortex A53
cpu cluster.
This patchet does not handle clock changing, this will be added in a
secondary patchset.
The CPU clock can either use the SYS_PLL for > 1GHz frequencies or
use a couple of div+mux from 1GHz/667MHz/24MHz source with 2 non-glitch
muxes.
The CPU clock must be switched to a safe clock while changing the clocks
before the non-glitch muxes. Proper support will be added later.
In this patchset, clocks are set read-only.
Neil Armstrong (2):
clk: meson-g12a: add cpu clock bindings
clk: meson: g12a: add cpu clocks
drivers/clk/meson/g12a.c | 348 ++++++++++++++++++++++++++
drivers/clk/meson/g12a.h | 25 +-
include/dt-bindings/clock/g12a-clkc.h | 1 +
3 files changed, 373 insertions(+), 1 deletion(-)
--
2.20.1
next reply other threads:[~2019-03-01 10:21 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-03-01 10:21 Neil Armstrong [this message]
2019-03-01 10:21 ` [PATCH 1/2] clk: meson-g12a: add cpu clock bindings Neil Armstrong
2019-03-01 15:26 ` Martin Blumenstingl
2019-03-01 16:43 ` Neil Armstrong
2019-03-01 17:05 ` Martin Blumenstingl
2019-03-01 10:21 ` [PATCH 2/2] clk: meson: g12a: add cpu clocks Neil Armstrong
2019-03-01 15:21 ` Martin Blumenstingl
2019-03-01 16:41 ` Neil Armstrong
2019-03-01 16:52 ` Martin Blumenstingl
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=20190301102140.7181-1-narmstrong@baylibre.com \
--to=narmstrong@baylibre.com \
--cc=jbrunet@baylibre.com \
--cc=linux-amlogic@lists.infradead.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-clk@vger.kernel.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).