From: Michael Turquette <mturquette@baylibre.com>
To: Linus Walleij <linus.walleij@linaro.org>,
"Stephen Boyd" <sboyd@codeaurora.org>,
"Ulf Hansson" <ulf.hansson@linaro.org>
Cc: linux-clk@vger.kernel.org, devicetree@vger.kernel.org,
"Linus Walleij" <linus.walleij@linaro.org>
Subject: Re: [PATCH 3/3] clk: add bindings for the Ux500 clocks
Date: Tue, 11 Aug 2015 16:39:05 -0700 [thread overview]
Message-ID: <20150811233905.31346.32970@quantum> (raw)
In-Reply-To: <1438262400-29213-1-git-send-email-linus.walleij@linaro.org>
Quoting Linus Walleij (2015-07-30 06:20:00)
> These Ux500 clocks have been around for years and were never
> properly documented. Add the proper binding documentation.
> =
> Cc: Ulf Hansson <ulf.hansson@linaro.org>
> Signed-off-by: Linus Walleij <linus.walleij@linaro.org>
This type of binding description isn't preferred but I guess we've been
supporting it all this time:
Acked-by: Michael Turquette <mturquette@baylibre.com>
> ---
> Ulf/Mike: please ACK this patch so I can take it through
> ARM SoC.
> ---
> Documentation/devicetree/bindings/clock/ux500.txt | 64 +++++++++++++++++=
++++++
> 1 file changed, 64 insertions(+)
> create mode 100644 Documentation/devicetree/bindings/clock/ux500.txt
> =
> diff --git a/Documentation/devicetree/bindings/clock/ux500.txt b/Document=
ation/devicetree/bindings/clock/ux500.txt
> new file mode 100644
> index 000000000000..e52bd4b72348
> --- /dev/null
> +++ b/Documentation/devicetree/bindings/clock/ux500.txt
> @@ -0,0 +1,64 @@
> +Clock bindings for ST-Ericsson Ux500 clocks
> +
> +Required properties :
> +- compatible : shall contain only one of the following:
> + "stericsson,u8500-clks"
> + "stericsson,u8540-clks"
> + "stericsson,u9540-clks"
> +- reg : shall contain base register location and length for
> + CLKRST1, 2, 3, 5, and 6 in an array. Note the absence of
> + CLKRST4, which does not exist.
> +
> +Required subnodes:
> +- prcmu-clock: a subnode with one clock cell for PRCMU (power,
> + reset, control unit) clocks. The cell indicates which PRCMU
> + clock in the prcmu-clock node the consumer wants to use.
> +- prcc-periph-clock: a subnode with two clock cells for
> + PRCC (programmable reset- and clock controller) peripheral clocks.
> + The first cell indicates which PRCC block the consumer
> + wants to use, possible values are 1, 2, 3, 5, 6. The second
> + cell indicates which clock inside the PRCC block it wants,
> + possible values are 0 thru 31.
> +- prcc-kernel-clock: a subnode with two clock cells for
> + PRCC (programmable reset- and clock controller) kernel clocks
> + The first cell indicates which PRCC block the consumer
> + wants to use, possible values are 1, 2, 3, 5, 6. The second
> + cell indicates which clock inside the PRCC block it wants,
> + possible values are 0 thru 31.
> +- rtc32k-clock: a subnode with zero clock cells for the 32kHz
> + RTC clock.
> +- smp-twd-clock: a subnode for the ARM SMP Timer Watchdog cluster
> + with zero clock cells.
> +
> +Example:
> +
> +clocks {
> + compatible =3D "stericsson,u8500-clks";
> + /*
> + * Registers for the CLKRST block on peripheral
> + * groups 1, 2, 3, 5, 6,
> + */
> + reg =3D <0x8012f000 0x1000>, <0x8011f000 0x1000>,
> + <0x8000f000 0x1000>, <0xa03ff000 0x1000>,
> + <0xa03cf000 0x1000>;
> +
> + prcmu_clk: prcmu-clock {
> + #clock-cells =3D <1>;
> + };
> +
> + prcc_pclk: prcc-periph-clock {
> + #clock-cells =3D <2>;
> + };
> +
> + prcc_kclk: prcc-kernel-clock {
> + #clock-cells =3D <2>;
> + };
> +
> + rtc_clk: rtc32k-clock {
> + #clock-cells =3D <0>;
> + };
> +
> + smp_twd_clk: smp-twd-clock {
> + #clock-cells =3D <0>;
> + };
> +};
> -- =
> 2.4.3
>=20
next prev parent reply other threads:[~2015-08-11 23:39 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-07-30 13:20 [PATCH 3/3] clk: add bindings for the Ux500 clocks Linus Walleij
2015-08-11 23:39 ` Michael Turquette [this message]
2015-08-13 18:30 ` Stephen Boyd
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=20150811233905.31346.32970@quantum \
--to=mturquette@baylibre.com \
--cc=devicetree@vger.kernel.org \
--cc=linus.walleij@linaro.org \
--cc=linux-clk@vger.kernel.org \
--cc=sboyd@codeaurora.org \
--cc=ulf.hansson@linaro.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