From: mturquette@baylibre.com (Michael Turquette)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 0/3] clk: mvebu: initial support for AP806 clocks
Date: Mon, 15 Feb 2016 15:31:02 -0800 [thread overview]
Message-ID: <20160215233102.2278.88855@quark.deferred.io> (raw)
In-Reply-To: <1455521698-7905-1-git-send-email-thomas.petazzoni@free-electrons.com>
Hi Thomas,
Quoting Thomas Petazzoni (2016-02-14 23:34:55)
> Hello,
>
> The following set of patches add initial support for the main clocks
> found in the AP806 hardware block, which is the central block used in
> the newest Marvell 7K and 8K 64-bits processors.
>
> Two new drivers are added, one for the so-called "core" clocks and one
> for the "ring" clocks. The latter are child clocks from one of the
> core clocks. The "core" clocks are fixed rate clocks, but their rate
> is calculated from values in the Sample At Reset register.
>
> The support for the Marvell 7K/8K platform (Device Tree, etc.) will be
> submitted as a separate patch series.
Yay, new SoC! Just FYI, we worked out an agreement in December[0] that
the clk git tree can take DT bindings and headers, and we'll always host
them in an immutable branch by default in case arm-soc (or anyone else)
needs them. Stephen and I are doing this now.
It's nice for us to review those bindings at the same time that we
review the driver.
[0] http://lkml.kernel.org/r/<20151231001859.19557.99512@quark.deferred.io>
Best regards,
Mike
>
> Thanks!
>
> Thomas
>
> Thomas Petazzoni (3):
> clk: unconditionally recurse into clk/mvebu/
> clk: mvebu: add AP806 core clock driver
> clk: mvebu: add AP806 ring clock driver
>
> .../clock/mvebu-armada-ap806-core-clock.txt | 33 ++++++
> .../clock/mvebu-armada-ap806-ring-clock.txt | 32 ++++++
> drivers/clk/Makefile | 2 +-
> drivers/clk/mvebu/Kconfig | 6 ++
> drivers/clk/mvebu/Makefile | 3 +-
> drivers/clk/mvebu/ap806-core.c | 112 +++++++++++++++++++++
> drivers/clk/mvebu/ap806-ring.c | 65 ++++++++++++
> 7 files changed, 251 insertions(+), 2 deletions(-)
> create mode 100644 Documentation/devicetree/bindings/clock/mvebu-armada-ap806-core-clock.txt
> create mode 100644 Documentation/devicetree/bindings/clock/mvebu-armada-ap806-ring-clock.txt
> create mode 100644 drivers/clk/mvebu/ap806-core.c
> create mode 100644 drivers/clk/mvebu/ap806-ring.c
>
> --
> 2.6.4
>
next prev parent reply other threads:[~2016-02-15 23:31 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-02-15 7:34 [PATCH 0/3] clk: mvebu: initial support for AP806 clocks Thomas Petazzoni
2016-02-15 7:34 ` [PATCH 1/3] clk: unconditionally recurse into clk/mvebu/ Thomas Petazzoni
2016-02-15 8:33 ` Marcin Wojtas
2016-02-15 11:06 ` Gregory CLEMENT
2016-02-15 7:34 ` [PATCH 2/3] clk: mvebu: add AP806 core clock driver Thomas Petazzoni
2016-02-22 2:53 ` Rob Herring
2016-02-22 8:14 ` Thomas Petazzoni
2016-02-22 14:16 ` Andrew Lunn
2016-02-22 18:32 ` Michael Turquette
2016-02-22 19:42 ` Rob Herring
2016-02-22 20:23 ` Michael Turquette
2016-02-23 9:25 ` Thomas Petazzoni
2016-02-23 15:56 ` Thomas Petazzoni
2016-02-15 7:34 ` [PATCH 3/3] clk: mvebu: add AP806 ring " Thomas Petazzoni
2016-02-22 2:54 ` Rob Herring
2016-02-22 8:15 ` Thomas Petazzoni
2016-02-15 23:31 ` Michael Turquette [this message]
2016-02-15 23:36 ` [PATCH 0/3] clk: mvebu: initial support for AP806 clocks Michael Turquette
2016-02-17 14:23 ` Thomas Petazzoni
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=20160215233102.2278.88855@quark.deferred.io \
--to=mturquette@baylibre.com \
--cc=linux-arm-kernel@lists.infradead.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).