From: Jean-Francois Moine <moinejf@free.fr>
To: Russell King - ARM Linux <linux@arm.linux.org.uk>
Cc: Sebastian Hesselbarth <sebastian.hesselbarth@gmail.com>,
linux-arm-kernel@lists.infradead.org,
Jason Cooper <jason@lakedaemon.net>,
Rob Herring <rob.herring@calxeda.com>,
Pawel Moll <pawel.moll@arm.com>,
Mark Rutland <mark.rutland@arm.com>,
Stephen Warren <swarren@wwwdotorg.org>,
Ian Campbell <ian.campbell@citrix.com>,
devicetree@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH 2/2] ARM: Dove: Add the audio device to the Cubox DT
Date: Sat, 31 Aug 2013 13:55:19 +0200 [thread overview]
Message-ID: <20130831135519.6ab0e163@armhf> (raw)
In-Reply-To: <20130831112430.GD6617@n2100.arm.linux.org.uk>
On Sat, 31 Aug 2013 12:24:31 +0100
Russell King - ARM Linux <linux@arm.linux.org.uk> wrote:
> > According to the Dove specification, the audio controller works with
> > the samples rates 44.1, 48 and 96 kHz, so, I don't see the usage of the
> > external clock, except when using the two audio controllers with
> > different sample rates.
[snip]
> > But, BTW, as the kirkwood-i2 driver is written, this last case does not
> > work: for 44.1, 48 and 96 kHz, the external clock is never used and
> > there is only one DCO.
>
> This doesn't make sense. "this last case" - what "case" are you referring
> to? "there is only one DCO" ? Yes, there is only one DCO, what is its
> relevance to the statement you're making? And yes, in mainline we
> currently use the DCO for the standard 44.1, 48 and 96kHz sample rates.
> That's fine. Confused.
Sorry, it was clear in my head :)
The last case was "when using the two audio controllers with different
sample rates" (I should have added "in the set [44.1, 48, 96 kHz]").
Then, with or without the availability of external clocks, both
controllers will set the unique DCO to two different rates.
--
Ken ar c'hentañ | ** Breizh ha Linux atav! **
Jef | http://moinejf.free.fr/
next prev parent reply other threads:[~2013-08-31 11:55 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-08-28 9:35 [PATCH 2/2] ARM: Dove: Add the audio device to the Cubox DT Jean-Francois Moine
2013-08-28 10:14 ` Sebastian Hesselbarth
2013-08-31 10:51 ` Jean-Francois Moine
2013-08-31 11:24 ` Russell King - ARM Linux
2013-08-31 11:55 ` Jean-Francois Moine [this message]
2013-08-31 12:17 ` Russell King - ARM Linux
2013-09-01 9:26 ` Sebastian Hesselbarth
[not found] ` <140d8d8a23f.2784.107cef0f820c2f5d7b7f41463071c310-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
2013-09-26 8:11 ` Jean-Francois Moine
2013-09-26 8:31 ` Sebastian Hesselbarth
[not found] ` <5243F0CE.9000301-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
2013-09-26 11:28 ` Jean-Francois Moine
2013-09-26 12:42 ` Sebastian Hesselbarth
2013-09-28 14:27 ` Sebastian Hesselbarth
[not found] ` <5246E747.6020103-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
2013-10-03 16:17 ` Jean-Francois Moine
2013-10-08 16:11 ` Jason Cooper
[not found] ` <20131008161145.GJ5402-u4khhh1J0LxI1Ri9qeTfzeTW4wlIGRCZ@public.gmane.org>
2013-10-08 17:59 ` Jean-Francois Moine
2013-10-08 18:00 ` Jason Cooper
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=20130831135519.6ab0e163@armhf \
--to=moinejf@free.fr \
--cc=devicetree@vger.kernel.org \
--cc=ian.campbell@citrix.com \
--cc=jason@lakedaemon.net \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@arm.linux.org.uk \
--cc=mark.rutland@arm.com \
--cc=pawel.moll@arm.com \
--cc=rob.herring@calxeda.com \
--cc=sebastian.hesselbarth@gmail.com \
--cc=swarren@wwwdotorg.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).