From: jamie@jamieiles.com (Jamie Iles)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCHv2 3/3] picoxcell: add the DTS for the PC7302 board
Date: Thu, 1 Sep 2011 08:58:15 +0100 [thread overview]
Message-ID: <20110901075815.GA2585@pulham.picochip.com> (raw)
In-Reply-To: <CAGsJ_4wp8aSJ2Kug2FkAznbVA9ifLfHt95P8+9bUijKAqJj5kA@mail.gmail.com>
On Thu, Sep 01, 2011 at 02:36:17PM +0800, Barry Song wrote:
> 2011/8/24 Jamie Iles <jamie@jamieiles.com>:
[...]
> > + ? ? ? clocks {
> > + ? ? ? ? ? ? ? ref_clk: clock at 10 {
> > + ? ? ? ? ? ? ? ? ? ? ? compatible = "fixed-clock";
> > + ? ? ? ? ? ? ? ? ? ? ? clock-outputs = "ref";
> > + ? ? ? ? ? ? ? ? ? ? ? clock-frequency = <20000000>;
> > + ? ? ? ? ? ? ? };
>
> ok. find it. is its name just "ref_clk"? could it be a pll/osc or some
> meaningful name?
Well it's the board reference clock. Typically this is a crystal, but
can also be an accurate, external reference or a VCTCXO so it didn't
feel right to encode that into the name for the SoC DTSI. I guess it
could be called board_clk if that makes things easier though.
Jamie
next prev parent reply other threads:[~2011-09-01 7:58 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-08-24 14:41 [PATCHv2 0/3] Initial support for Picochip picoxcell Jamie Iles
2011-08-24 14:41 ` [PATCHv2 1/3] picoxcell: support for Picochip picoxcell devices Jamie Iles
2011-08-24 14:41 ` [PATCHv2 2/3] picoxcell: add the DTS for pc3x2 and pc3x3 devices Jamie Iles
2011-09-01 6:30 ` Barry Song
2011-08-24 14:41 ` [PATCHv2 3/3] picoxcell: add the DTS for the PC7302 board Jamie Iles
2011-09-01 6:36 ` Barry Song
2011-09-01 7:58 ` Jamie Iles [this message]
2011-09-15 11:32 ` Benjamin Herrenschmidt
2011-09-15 12:15 ` Jamie Iles
2011-09-23 2:31 ` Barry Song
2011-09-23 2:48 ` Benjamin Herrenschmidt
2011-09-15 8:43 ` [PATCHv2 0/3] Initial support for Picochip picoxcell Jamie Iles
2011-09-26 9:20 ` Jamie Iles
2011-09-26 14:42 ` Arnd Bergmann
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=20110901075815.GA2585@pulham.picochip.com \
--to=jamie@jamieiles.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 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).