From: alexandre.belloni@free-electrons.com (Alexandre Belloni)
To: linux-arm-kernel@lists.infradead.org
Subject: linux-next: manual merge of the rtc tree with the arm-soc tree
Date: Fri, 28 Aug 2015 10:08:09 +0200 [thread overview]
Message-ID: <20150828080809.GU13155@piout.net> (raw)
In-Reply-To: <20150827162229.10fe7255@canb.auug.org.au>
Hi Stephen,
On 27/08/2015 at 16:22:29 +1000, Stephen Rothwell wrote :
> clock-frequency = <12000000>;
> };
>
> + sound0: sound at 0 {
> + compatible = "simple-audio-card";
> + simple-audio-card,name = "AM437x-GP-EVM";
> + simple-audio-card,widgets =
> + "Headphone", "Headphone Jack",
> + "Line", "Line In";
> + simple-audio-card,routing =
> + "Headphone Jack", "HPLOUT",
> + "Headphone Jack", "HPROUT",
> + "LINE1L", "Line In",
> + "LINE1R", "Line In";
> + simple-audio-card,format = "dsp_b";
> + simple-audio-card,bitclock-master = <&sound0_master>;
> + simple-audio-card,frame-master = <&sound0_master>;
> + simple-audio-card,bitclock-inversion;
> +
> + simple-audio-card,cpu {
> + sound-dai = <&mcasp1>;
> + system-clock-frequency = <12000000>;
> + };
> +
> + sound0_master: simple-audio-card,codec {
> + sound-dai = <&tlv320aic3106>;
> + system-clock-frequency = <12000000>;
> + };
> + };
> ++
> + /* fixed 32k external oscillator clock */
> + clk_32k_rtc: clk_32k_rtc {
> + #clock-cells = <0>;
> + compatible = "fixed-clock";
> + clock-frequency = <32768>;
> + };
It is just a matter of taste but maybe both oscillators/clocks can be
grouped.
--
Alexandre Belloni, Free Electrons
Embedded Linux, Kernel and Android engineering
http://free-electrons.com
prev parent reply other threads:[~2015-08-28 8:08 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-08-27 6:22 linux-next: manual merge of the rtc tree with the arm-soc tree Stephen Rothwell
2015-08-28 8:08 ` Alexandre Belloni [this message]
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=20150828080809.GU13155@piout.net \
--to=alexandre.belloni@free-electrons.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).