From: Roger Quadros <rogerq@ti.com>
To: Paul Walmsley <paul@pwsan.com>
Cc: Roger Quadros <rogerq@ti.com>, <tony@atomide.com>,
<rnayak@ti.com>, <b-cousson@ti.com>, <santosh.shilimkar@ti.com>,
<linux-omap@vger.kernel.org>,
<linux-arm-kernel@lists.infradead.org>,
<devicetree-discuss@lists.ozlabs.org>,
<linux-kernel@vger.kernel.org>
Subject: Re: [PATCH v2] ARM: OMAP4: clock: Add device tree support for AUXCLKs
Date: Tue, 2 Apr 2013 11:23:39 +0300 [thread overview]
Message-ID: <515A958B.5080905@ti.com> (raw)
In-Reply-To: <1364293408-20677-1-git-send-email-rogerq@ti.com>
+ Paul
On 03/26/2013 12:23 PM, Roger Quadros wrote:
> Register a device tree clock provider for the clocks
> on the OMAP4 SoC. Also provide the binding information.
>
> For now we only provide AUXCLKs.
>
> Signed-off-by: Roger Quadros <rogerq@ti.com>
> ---
> .../devicetree/bindings/clock/omap4-clock.txt | 33 ++++++++++++++++
> arch/arm/boot/dts/omap4.dtsi | 5 ++
> arch/arm/mach-omap2/cclock44xx_data.c | 41 ++++++++++++++++++++
> 3 files changed, 79 insertions(+), 0 deletions(-)
> create mode 100644 Documentation/devicetree/bindings/clock/omap4-clock.txt
>
> diff --git a/Documentation/devicetree/bindings/clock/omap4-clock.txt b/Documentation/devicetree/bindings/clock/omap4-clock.txt
> new file mode 100644
> index 0000000..2845a3f
> --- /dev/null
> +++ b/Documentation/devicetree/bindings/clock/omap4-clock.txt
> @@ -0,0 +1,33 @@
> +* Clock bindings for Texas Instruments OMAP4 clocks
> +
> +Required properties:
> +- compatible: Should be "ti,omap4-clock"
> +- #clock-cells: Should be <1>
> +
> +The clock consumer should specify the desired clock by having the clock
> +ID in its "clocks" phandle cell. The following is a list of OMAP4 clocks
> +and IDs.
> +
> + Clock ID
> + ------------------
> + auxclk0_ck 0
> + auxclk1_ck 1
> + auxclk2_ck 2
> + auxclk3_ck 3
> + auxclk4_ck 4
> + auxclk5_ck 5
> +
> +Example:
> +
> +aux_clks: scrmclks {
> + compatible = "ti,omap4-clock";
> + #clock-cells = <1>;
> +};
> +
> +hsusb1_phy: hsusb1_phy {
> + compatible = "usb-nop-xceiv";
> + reset-supply = <&hsusb1_reset>;
> + clocks = <&aux_clks 3>;
> + clock-names = "main_clk";
> + clock-frequency = <19200000>;
> +};
> diff --git a/arch/arm/boot/dts/omap4.dtsi b/arch/arm/boot/dts/omap4.dtsi
> index 739bb79..f27548a 100644
> --- a/arch/arm/boot/dts/omap4.dtsi
> +++ b/arch/arm/boot/dts/omap4.dtsi
> @@ -101,6 +101,11 @@
> ti,hwmods = "counter_32k";
> };
>
> + clks: clocks {
> + compatible = "ti,omap4-clock";
> + #clock-cells = <1>;
> + };
> +
> omap4_pmx_core: pinmux@4a100040 {
> compatible = "ti,omap4-padconf", "pinctrl-single";
> reg = <0x4a100040 0x0196>;
> diff --git a/arch/arm/mach-omap2/cclock44xx_data.c b/arch/arm/mach-omap2/cclock44xx_data.c
> index 3d58f33..a93617b 100644
> --- a/arch/arm/mach-omap2/cclock44xx_data.c
> +++ b/arch/arm/mach-omap2/cclock44xx_data.c
> @@ -27,6 +27,7 @@
> #include <linux/clk-private.h>
> #include <linux/clkdev.h>
> #include <linux/io.h>
> +#include <linux/of.h>
>
> #include "soc.h"
> #include "iomap.h"
> @@ -1663,6 +1664,44 @@ static struct omap_clk omap44xx_clks[] = {
> CLK(NULL, "cpufreq_ck", &dpll_mpu_ck, CK_443X),
> };
>
> +/*
> + * List of clocks that can be referenced in device tree
> + * Must match with Documentation/devicetree/bindings/clock/omap4-clock.txt
> + */
> +static struct clk *dt_clks[] = {
> + &auxclk0_ck,
> + &auxclk1_ck,
> + &auxclk2_ck,
> + &auxclk3_ck,
> + &auxclk4_ck,
> + &auxclk5_ck,
> +};
> +
> +static struct clk_onecell_data clock_data;
> +
> +#ifdef CONFIG_OF
> +int __init omap4_clk_init_dt(void)
> +{
> + struct device_node *np;
> +
> + np = of_find_compatible_node(NULL, NULL, "ti,omap4-clock");
> + if (np) {
> + clock_data.clks = dt_clks;
> + clock_data.clk_num = ARRAY_SIZE(dt_clks);
> + of_clk_add_provider(np, of_clk_src_onecell_get, &clock_data);
> + }
> +
> + return 0;
> +}
> +
> +#else
> +
> +int __init omap4_clk_init_dt(void)
> +{
> + return 0;
> +}
> +#endif /* CONFIG_OF */
> +
> int __init omap4xxx_clk_init(void)
> {
> u32 cpu_clkflg;
> @@ -1693,6 +1732,8 @@ int __init omap4xxx_clk_init(void)
>
> omap2_clk_disable_autoidle_all();
>
> + omap4_clk_init_dt();
> +
> /*
> * On OMAP4460 the ABE DPLL fails to turn on if in idle low-power
> * state when turning the ABE clock domain. Workaround this by
>
next prev parent reply other threads:[~2013-04-02 8:23 UTC|newest]
Thread overview: 42+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-03-19 14:26 [RFC][PATCH 0/2] Device tree support for OMAP4 SCRM clocks Roger Quadros
2013-03-19 14:26 ` [RFC][PATCH 1/2] ARM: OMAP4: clock: Add device tree support for AUXCLKs Roger Quadros
2013-03-19 14:30 ` Roger Quadros
2013-03-21 13:08 ` Rajendra Nayak
2013-03-21 13:54 ` Roger Quadros
2013-03-21 14:04 ` Rajendra Nayak
2013-03-21 14:11 ` Roger Quadros
2013-03-21 14:07 ` Roger Quadros
2013-03-26 10:23 ` [PATCH v2] " Roger Quadros
2013-04-02 8:23 ` Roger Quadros [this message]
2013-04-05 8:47 ` Roger Quadros
2013-04-05 8:48 ` Nishanth Menon
2013-04-05 8:50 ` Roger Quadros
2013-04-03 23:42 ` [RFC][PATCH 1/2] " Tony Lindgren
2013-04-04 5:20 ` Rajendra Nayak
2013-04-04 16:33 ` Tony Lindgren
2013-04-04 7:35 ` Roger Quadros
2013-04-04 16:41 ` Tony Lindgren
2013-04-05 10:39 ` Roger Quadros
2013-04-05 15:58 ` Tony Lindgren
2013-04-09 9:55 ` Roger Quadros
2013-04-09 16:49 ` Tony Lindgren
2013-04-09 17:43 ` Tony Lindgren
2013-04-09 20:49 ` Nishanth Menon
2013-04-09 21:54 ` Nishanth Menon
2013-04-10 11:04 ` Roger Quadros
2013-04-09 22:22 ` Tony Lindgren
2013-04-10 8:06 ` Mike Turquette
2013-04-10 10:55 ` Roger Quadros
2013-04-10 17:39 ` Nishanth Menon
2013-04-10 18:49 ` Tony Lindgren
2013-04-10 19:19 ` Nishanth Menon
2013-04-10 20:21 ` Tony Lindgren
2013-04-11 7:48 ` Roger Quadros
2013-04-11 9:04 ` Grygorii Strashko
2013-04-11 22:45 ` Nishanth Menon
2013-04-11 18:46 ` Mike Turquette
2013-04-11 22:40 ` Nishanth Menon
2013-04-05 17:56 ` Grygorii Strashko
2013-04-09 10:16 ` Roger Quadros
2013-03-19 14:27 ` [PATCH 2/2] ARM: dts: omap4-panda: Provide PHY clock information Roger Quadros
2013-03-19 14:28 ` [RFC][PATCH 0/2] Device tree support for OMAP4 SCRM clocks Roger Quadros
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=515A958B.5080905@ti.com \
--to=rogerq@ti.com \
--cc=b-cousson@ti.com \
--cc=devicetree-discuss@lists.ozlabs.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-omap@vger.kernel.org \
--cc=paul@pwsan.com \
--cc=rnayak@ti.com \
--cc=santosh.shilimkar@ti.com \
--cc=tony@atomide.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).