From: "Heiko Stübner" <heiko@sntech.de>
To: linux-arm-kernel@lists.infradead.org
Cc: Joel Stanley <joel@jms.id.au>,
arnd@arndb.de, benh@kernel.crashing.org, jk@ozlabs.org,
mturquette@baylibre.com, sboyd@codeaurora.org,
linux-clk@vger.kernel.org
Subject: Re: [PATCH v2 03/11] doc/devicetree: Add Aspeed clock bindings
Date: Thu, 21 Apr 2016 13:20:11 +0200 [thread overview]
Message-ID: <4956403.scaVRGhPEf@diego> (raw)
In-Reply-To: <1461225849-28074-4-git-send-email-joel@jms.id.au>
[+clock-related patches should include clock-maintainers and lists]
Am Donnerstag, 21. April 2016, 17:34:01 schrieb Joel Stanley:
> +For example:
> +
> + clk_clkin: clk_clkin {
> + #clock-cells = <0>;
> + compatible = "fixed-clock";
> + clock-frequency = <48000000>;
> + };
> +
> + clk_hpll: clk_hpll {
> + compatible = "aspeed,g4-hpll-clock";
> + #clock-cells = <0>;
> + reg = <0x1e6e2008 0x4>;
> + };
> +
> + clk_apb: clk_apb@1e6e2008 {
> + #clock-cells = <0>;
> + compatible = "aspeed,g4-apb-clock";
> + reg = <0x1e6e2008 0x4>;
> + clocks = <&clk_hpll>;
> + };
You have both the hpll and apb_clk in the same register (probably even more
clocks?) and separate clock instances where each instance will of_iomap the
register itself (and thus multiple times in general).
>From what I remember exposing the clock controller as one block (instead of
declaring each clock individually in the dts) is still the preferred way but I
don't think I can find Mike's mail from back then easily.
And I think most clock-controller implementations actually use that paradigm.
Heiko
next parent reply other threads:[~2016-04-21 11:20 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1461225849-28074-1-git-send-email-joel@jms.id.au>
[not found] ` <1461225849-28074-4-git-send-email-joel@jms.id.au>
2016-04-21 11:20 ` Heiko Stübner [this message]
2016-04-27 8:31 ` [PATCH v2 03/11] doc/devicetree: Add Aspeed clock bindings Joel Stanley
2016-04-27 9:12 ` Heiko Stübner
2016-04-28 6:50 ` Joel Stanley
2016-04-28 7:25 ` Heiko Stübner
2016-04-28 8:38 ` Benjamin Herrenschmidt
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=4956403.scaVRGhPEf@diego \
--to=heiko@sntech.de \
--cc=arnd@arndb.de \
--cc=benh@kernel.crashing.org \
--cc=jk@ozlabs.org \
--cc=joel@jms.id.au \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-clk@vger.kernel.org \
--cc=mturquette@baylibre.com \
--cc=sboyd@codeaurora.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).