From: Mark Brown <broonie@kernel.org>
To: Russell King - ARM Linux <linux@arm.linux.org.uk>
Cc: Jean-Francois Moine <moinejf@free.fr>,
alsa-devel@alsa-project.org, Takashi Iwai <tiwai@suse.de>,
Liam Girdwood <lgirdwood@gmail.com>,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] ASoC: kirkwood-i2s: fix a compilation warning
Date: Tue, 16 Jul 2013 00:29:21 +0100 [thread overview]
Message-ID: <20130715232921.GH11538@sirena.org.uk> (raw)
In-Reply-To: <20130715225836.GG11538@sirena.org.uk>
[-- Attachment #1.1: Type: text/plain, Size: 975 bytes --]
On Mon, Jul 15, 2013 at 11:58:36PM +0100, Mark Brown wrote:
> On Mon, Jul 15, 2013 at 10:37:27PM +0100, Russell King - ARM Linux wrote:
> > I suggest you go back and re-read the driver because it most certainly
> > does use extclk. What makes you think it won't?
> The only thing I can see which is pushing a constraint up the stack is
> KIRKWOOD_I2S_RATES in the DAIs which only allows 44.1kHz, 48kHz and
> 96kHz, the rates for which the internal clock is used. The driver will
Ugh, I just saw the dai_extclk stuff. That's probably also problematic
the other way - it'll break if someone decides to put a non-programmable
clock on there, or something that can't generate arbatrary frequencies
like a crystal plus divider. It's also not clear to me why the driver
ever uses the internal clocks if something external has been provided.
This does mean the change is safe, though - but it needs to be called
out in both the code and the changelog how this is happening.
[-- Attachment #1.2: Digital signature --]
[-- Type: application/pgp-signature, Size: 836 bytes --]
[-- Attachment #2: Type: text/plain, Size: 0 bytes --]
prev parent reply other threads:[~2013-07-15 23:29 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-07-15 8:36 [PATCH] ASoC: kirkwood-i2s: fix a compilation warning Jean-Francois Moine
2013-07-15 15:31 ` Mark Brown
2013-07-15 18:37 ` Jean-Francois Moine
2013-07-15 20:08 ` Mark Brown
2013-07-15 21:37 ` Russell King - ARM Linux
2013-07-15 22:58 ` Mark Brown
2013-07-15 23:04 ` Russell King - ARM Linux
2013-07-15 23:29 ` Mark Brown [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=20130715232921.GH11538@sirena.org.uk \
--to=broonie@kernel.org \
--cc=alsa-devel@alsa-project.org \
--cc=lgirdwood@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@arm.linux.org.uk \
--cc=moinejf@free.fr \
--cc=tiwai@suse.de \
/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