From: robh@kernel.org (Rob Herring)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 2/3] clk: mvebu: add AP806 core clock driver
Date: Sun, 21 Feb 2016 20:53:57 -0600 [thread overview]
Message-ID: <20160222025357.GE15973@rob-hp-laptop> (raw)
In-Reply-To: <1455521698-7905-3-git-send-email-thomas.petazzoni@free-electrons.com>
On Mon, Feb 15, 2016 at 08:34:57AM +0100, Thomas Petazzoni wrote:
> This commit adds a new driver to handle the core clocks found in the
> AP806 HW block, which is the core block of all Armada 7K and 8K
> Marvell 64-bits processors. This core clock driver reads the
> Sample-At-Reset register to determine the frequencies of several core
> clocks: DDR, Ring and CPU clocks.
>
> Signed-off-by: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
> ---
> .../clock/mvebu-armada-ap806-core-clock.txt | 33 ++++++
> drivers/clk/mvebu/Kconfig | 3 +
> drivers/clk/mvebu/Makefile | 2 +-
> drivers/clk/mvebu/ap806-core.c | 112 +++++++++++++++++++++
> 4 files changed, 149 insertions(+), 1 deletion(-)
> create mode 100644 Documentation/devicetree/bindings/clock/mvebu-armada-ap806-core-clock.txt
> create mode 100644 drivers/clk/mvebu/ap806-core.c
>
> diff --git a/Documentation/devicetree/bindings/clock/mvebu-armada-ap806-core-clock.txt b/Documentation/devicetree/bindings/clock/mvebu-armada-ap806-core-clock.txt
> new file mode 100644
> index 0000000..b2131bb
> --- /dev/null
> +++ b/Documentation/devicetree/bindings/clock/mvebu-armada-ap806-core-clock.txt
> @@ -0,0 +1,33 @@
> +* Clock bindings for Marvell MVEBU AP806 Core clocks
> +
> +The Marvell MVEBU Armada 7K/8K SoCs contain a block called AP806,
> +hosting the CPU and other core components of the CPU. This Device Tree
> +binding allows to describe the core clocks of the AP806, whose
> +frequencies are determined by reading the Sample-At-Reset (SAR)
> +register.
What else is in the AP806?
> +
> +Clock consumers must specify the desired clock by having the clock ID
> +in its "clocks" phandle cell.
> +
> +The following is a list of provided IDs and clock names for the core
> +Armada AP806 clocks:
> +
> + 0 = DDR
> + 1 = Ring
> + 2 = CPU
> +
> +Required properties:
> +- compatible: must be be one of the following:
> + "marvell,armada-ap806-core-clock"
I'd expect this to be a sub-node of a syscon block or just a single
clock provider for the full block. Hard to tell reviewing this without
context of what the full clock tree looks like.
> +- reg: must be the register address of the Sample-At-Reset (SAR) register
> +- #clock-cells: from common clock binding; shall be set to 1
> +- clock-output-names: name of the output clocks
> +
> +Example:
> +
> + coreclk: clk at 0x6F8204 {
Drop 0x and lowercase hex.
> + compatible = "marvell,armada-ap806-core-clock";
> + reg = <0x6F8204 0x04>;
lowercase hex.
> + #clock-cells = <1>;
> + clock-output-names = "ddr", "ring", "cpu";
> + };
next prev parent reply other threads:[~2016-02-22 2:53 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 [this message]
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 ` [PATCH 0/3] clk: mvebu: initial support for AP806 clocks Michael Turquette
2016-02-15 23:36 ` 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=20160222025357.GE15973@rob-hp-laptop \
--to=robh@kernel.org \
--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