From: "Jan Lübbe" <jlu@pengutronix.de>
To: "Sören Brinkmann" <soren.brinkmann@xilinx.com>,
"Sascha Hauer" <s.hauer@pengutronix.de>
Cc: Mike Turquette <mturquette@linaro.org>,
Josh Cartwright <josh.cartwright@ni.com>,
Michal Simek <michal.simek@xilinx.com>,
Peter Crosthwaite <pcrost@xilinx.com>,
Prashant Gaikwad <pgaikwad@nvidia.com>,
devicetree-discuss@lists.ozlabs.org,
linux-kernel@vger.kernel.org,
linux-arm-kernel@lists.infradead.org, git@xilinx.com
Subject: Re: RFC: Zynq Clock Controller
Date: Wed, 06 Mar 2013 12:51:21 +0100 [thread overview]
Message-ID: <1362570681.5269.98.camel@coredoba.hi.pengutronix.de> (raw)
In-Reply-To: <37032699-343e-485c-80e0-9b23e3706c58@VA3EHSMHS013.ehs.local>
Hi Sören,
On Tue, 2013-03-05 at 12:04 -0800, Sören Brinkmann wrote:
> For this reasons, I'd like to propose moving Zynq into the same
> direction. I.e. adding a clock controller with the following DT
> description (details may change but the general idea should become
> clear):
> clkc: clkc {
> #clock-cells = <1>;
> compatible = "xlnx,ps7-clkc";
> ps_clk_frequency = <33333333>; # board x-tal
> # optional props
> gem0_emio_clk_freq = <125000000>;
> gem1_emio_clk_freq = <50000000>;
> can_mio_clk_freq_xx = <1234>; # this is possible 54 times with xx = 00..53
> };
The clock controller should only contain properties for input frequency
(which can obviously not be calculated at run-time).
Are the gem*, can* properties inputs? If they are actually outputs, the
corresponding frequencies should be requested by the clock consumers and
not hard-coded in DT.
Please keep in mind that DT properties use dashes instead of
underscores.
Best regards,
Jan
--
Pengutronix e.K. | |
Industrial Linux Solutions | http://www.pengutronix.de/ |
Peiner Str. 6-8, 31137 Hildesheim, Germany | Phone: +49-5121-206917-0 |
Amtsgericht Hildesheim, HRA 2686 | Fax: +49-5121-206917-5555 |
next prev parent reply other threads:[~2013-03-06 11:51 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-03-05 20:04 RFC: Zynq Clock Controller Sören Brinkmann
2013-03-06 11:51 ` Jan Lübbe [this message]
2013-03-06 17:27 ` Sören Brinkmann
2013-03-07 9:36 ` Lars-Peter Clausen
2013-03-07 19:11 ` Sören Brinkmann
2013-03-07 22:02 ` Lars-Peter Clausen
2013-03-07 23:25 ` Sören Brinkmann
2013-03-08 7:12 ` Lars-Peter Clausen
2013-03-08 17:38 ` Sören Brinkmann
[not found] ` <ad0abbdf-b783-4c43-aa40-534f726fbfb7-6DEzpURlfbPT7m58JnLnSLjjLBE8jN/0@public.gmane.org>
2013-03-08 18:08 ` Lars-Peter Clausen
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=1362570681.5269.98.camel@coredoba.hi.pengutronix.de \
--to=jlu@pengutronix.de \
--cc=devicetree-discuss@lists.ozlabs.org \
--cc=git@xilinx.com \
--cc=josh.cartwright@ni.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=michal.simek@xilinx.com \
--cc=mturquette@linaro.org \
--cc=pcrost@xilinx.com \
--cc=pgaikwad@nvidia.com \
--cc=s.hauer@pengutronix.de \
--cc=soren.brinkmann@xilinx.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).