From: Rob Herring <robh@kernel.org>
To: "Rafał Miłecki" <zajec5@gmail.com>
Cc: "Michael Turquette" <mturquette@baylibre.com>,
"Stephen Boyd" <sboyd@codeaurora.org>,
linux-clk@vger.kernel.org, bcm-kernel-feedback-list@broadcom.com,
"Rafał Miłecki" <rafal@milecki.pl>,
"Mark Rutland" <mark.rutland@arm.com>,
"Jon Mason" <jonmason@broadcom.com>,
"Florian Fainelli" <f.fainelli@gmail.com>,
"Eric Anholt" <eric@anholt.net>,
"open list:OPEN FIRMWARE AND FLATTENED DEVICE TREE BINDINGS"
<devicetree@vger.kernel.org>,
"open list" <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH V7] clk: bcm: Add driver for BCM53573 ILP clock
Date: Mon, 12 Sep 2016 11:56:37 -0500 [thread overview]
Message-ID: <20160912165637.GA4462@rob-hp-laptop> (raw)
In-Reply-To: <20160905142935.4550-1-zajec5@gmail.com>
On Mon, Sep 05, 2016 at 04:29:27PM +0200, Rafał Miłecki wrote:
> From: Rafał Miłecki <rafal@milecki.pl>
>
> This clock is present on BCM53573 devices (including BCM47189) that use
> Cortex-A7. ILP is a part of PMU (Power Management Unit) multi-function
> device so we use syscon (and regmap) for it.
>
> Signed-off-by: Rafał Miłecki <rafal@milecki.pl>
> ---
> V2: Rebase on top of clk-next
> Use ALP as parent clock
> Improve comments
> Switch from ioremap_nocache to ioremap
> Check of_clk_add_provide result for error
> V3: Drop #include <linux/moduleh>
> Make ILP DT entry part of PMU
> Describe ILP as subdevice of PMU in Documentation
> V4: Use BCM53573 name as suggested by Jon and Ray. It seems "Northstar"
> (even if used in some resources) should be used in relation to
> Cortex-A9 devices only.
> V5: Rename remaining "ns" references to "bcm53573", sorry, I sent V4 too
> early.
> V6: Drop #include <linux/clk.h>
> Use "int" as type where it matches usage
> Add cpu_relax() in the loop
> Add disable callback
> Use _hw_ functions for registering struct clk_hw (new API)
>
> Thanks a lot Stephen!
> V7: Use syscon and regmap (thanks Rob!)
> ---
> .../bindings/clock/brcm,bcm53573-ilp.txt | 36 +++++
> drivers/clk/bcm/Makefile | 1 +
> drivers/clk/bcm/clk-bcm53573-ilp.c | 148 +++++++++++++++++++++
> 3 files changed, 185 insertions(+)
> create mode 100644 Documentation/devicetree/bindings/clock/brcm,bcm53573-ilp.txt
> create mode 100644 drivers/clk/bcm/clk-bcm53573-ilp.c
>
> diff --git a/Documentation/devicetree/bindings/clock/brcm,bcm53573-ilp.txt b/Documentation/devicetree/bindings/clock/brcm,bcm53573-ilp.txt
> new file mode 100644
> index 0000000..4554f70
> --- /dev/null
> +++ b/Documentation/devicetree/bindings/clock/brcm,bcm53573-ilp.txt
> @@ -0,0 +1,36 @@
> +Broadcom BCM53573 ILP clock
> +===========================
> +
> +This binding uses the common clock binding:
> + Documentation/devicetree/bindings/clock/clock-bindings.txt
> +
> +This binding is used for ILP clock (sometimes referred as "slow clock")
> +on Broadcom BCM53573 devices using Cortex-A7 CPU.
> +
> +ILP's rate has to be calculated on runtime and it depends on ALP clock
> +which has to be referenced.
> +
> +This clock is part of PMU (Power Management Unit), a Broadcom's device
> +handing power-related aspects. Its node must be sub-node of the PMU
> +device.
> +
> +Required properties:
> +- compatible: "brcm,bcm53573-ilp"
> +- reg: iomem address range of PMU (Power Management Unit)
> +- reg-names: "pmu", the only needed & supported reg right now
There's no reg prop in the example.
> +- clocks: has to reference an ALP clock
> +- #clock-cells: should be <0>
> +
> +Example:
> +
> +pmu@18012000 {
> + compatible = "simple-mfd", "syscon";
> + reg = <0x18012000 0x00001000>;
> +
> + ilp: ilp@0 {
Drop the unit address if there is in fact no reg prop.
> + compatible = "brcm,bcm53573-ilp";
> + clocks = <&alp>;
> + #clock-cells = <0>;
> + clock-output-names = "ilp";
> + };
> +};
next prev parent reply other threads:[~2016-09-12 16:56 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-08-10 12:05 [PATCH V3] clk: bcm: Add driver for Northstar ILP clock Rafał Miłecki
2016-08-10 17:22 ` Jon Mason
2016-08-10 17:28 ` Rafał Miłecki
2016-08-10 17:44 ` Ray Jui
2016-08-10 18:21 ` Jon Mason
2016-08-11 8:49 ` Rafał Miłecki
2016-08-11 14:25 ` Jon Mason
2016-08-12 6:26 ` Rafał Miłecki
2016-08-23 6:17 ` [PATCH V4] clk: bcm: Add driver for BCM53573 " Rafał Miłecki
2016-08-23 6:25 ` [PATCH V5] " Rafał Miłecki
2016-08-23 19:55 ` Rob Herring
2016-08-25 12:42 ` Rafał Miłecki
2016-08-31 16:16 ` Rob Herring
2016-09-05 12:12 ` Rafał Miłecki
[not found] ` <20160823062613.13865-1-zajec5-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
2016-08-24 8:47 ` Stephen Boyd
2016-08-25 13:28 ` Rafał Miłecki
2016-08-25 19:57 ` Stephen Boyd
2016-08-25 14:11 ` Rafał Miłecki
2016-08-25 19:58 ` Stephen Boyd
2016-08-26 12:25 ` [PATCH V6] " Rafał Miłecki
2016-09-05 14:29 ` [PATCH V7] " Rafał Miłecki
2016-09-12 16:56 ` Rob Herring [this message]
2016-09-13 7:06 ` [PATCH V8] " Rafał Miłecki
[not found] ` <20160913070722.5867-1-zajec5-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
2016-09-14 23:44 ` Rob Herring
2016-09-16 23:23 ` Stephen Boyd
[not found] ` <20160916232332.GB7243-sgV2jX0FEOL9JmXXK+q4OQ@public.gmane.org>
2016-09-17 19:20 ` Rafał Miłecki
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=20160912165637.GA4462@rob-hp-laptop \
--to=robh@kernel.org \
--cc=bcm-kernel-feedback-list@broadcom.com \
--cc=devicetree@vger.kernel.org \
--cc=eric@anholt.net \
--cc=f.fainelli@gmail.com \
--cc=jonmason@broadcom.com \
--cc=linux-clk@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mark.rutland@arm.com \
--cc=mturquette@baylibre.com \
--cc=rafal@milecki.pl \
--cc=sboyd@codeaurora.org \
--cc=zajec5@gmail.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).