From: sebastian.hesselbarth@gmail.com (Sebastian Hesselbarth)
To: linux-arm-kernel@lists.infradead.org
Subject: [RFC] Common clock framework for external clock generators
Date: Sun, 14 Oct 2012 18:16:39 +0200 [thread overview]
Message-ID: <507AE567.7040701@gmail.com> (raw)
In-Reply-To: <507A9E72.2030800@gmail.com>
On 10/14/2012 01:13 PM, Daniel Mack wrote:
> I think the sub-node style above it nicer because it allows referencing
> the individual clocks outputs with a phandle. We use this chip to
> generate base-frequencies for audio clocks, and so we have to switch
> between two freqs for the multiples of 22.5KHz and 24KHz at runtime.
Both examples allow you to have a phandle for all individual clock-outputs.
The examples weren't complete but with the sub-node style you'll reference
with e.g. <&clkout0> while the flat one will use <&si5351 0>. I still prefer
the flat-style as it will not allow to have a phandle of plls.
Sebastian
WARNING: multiple messages have this Message-ID (diff)
From: Sebastian Hesselbarth <sebastian.hesselbarth@gmail.com>
To: Daniel Mack <zonque@gmail.com>
Cc: linux-kernel@vger.kernel.org,
Mark Brown <broonie@opensource.wolfsonmicro.com>,
Mike Turquette <mturquette@ti.com>,
linux ARM <linux-arm-kernel@lists.infradead.org>,
Grant Likely <grant.likely@secretlab.ca>,
Rob Herring <rob.herring@calxeda.com>,
devicetree-discuss@lists.ozlabs.org
Subject: Re: [RFC] Common clock framework for external clock generators
Date: Sun, 14 Oct 2012 18:16:39 +0200 [thread overview]
Message-ID: <507AE567.7040701@gmail.com> (raw)
In-Reply-To: <507A9E72.2030800@gmail.com>
On 10/14/2012 01:13 PM, Daniel Mack wrote:
> I think the sub-node style above it nicer because it allows referencing
> the individual clocks outputs with a phandle. We use this chip to
> generate base-frequencies for audio clocks, and so we have to switch
> between two freqs for the multiples of 22.5KHz and 24KHz at runtime.
Both examples allow you to have a phandle for all individual clock-outputs.
The examples weren't complete but with the sub-node style you'll reference
with e.g. <&clkout0> while the flat one will use <&si5351 0>. I still prefer
the flat-style as it will not allow to have a phandle of plls.
Sebastian
next prev parent reply other threads:[~2012-10-14 16:16 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-05-10 1:11 [RFC] Common clock framework for external clock generators Sebastian Hesselbarh
2012-05-13 12:29 ` Mark Brown
2012-05-13 16:30 ` Sebastian Hesselbarh
2012-05-13 16:43 ` Mark Brown
2012-05-13 17:11 ` Sebastian Hesselbarh
2012-05-13 17:16 ` Mark Brown
2012-05-14 18:08 ` Turquette, Mike
2012-05-14 18:12 ` Mark Brown
2012-10-11 8:34 ` Daniel Mack
2012-10-11 16:00 ` Sebastian Hesselbarth
2012-10-12 18:17 ` Daniel Mack
2012-10-14 10:59 ` Sebastian Hesselbarth
2012-10-14 10:59 ` Sebastian Hesselbarth
2012-10-14 11:13 ` Daniel Mack
2012-10-14 11:13 ` Daniel Mack
2012-10-14 16:16 ` Sebastian Hesselbarth [this message]
2012-10-14 16:16 ` Sebastian Hesselbarth
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=507AE567.7040701@gmail.com \
--to=sebastian.hesselbarth@gmail.com \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.