From: Mark Brown <broonie@opensource.wolfsonmicro.com>
To: Jarkko Nikula <jarkko.nikula@nokia.com>
Cc: alsa-devel@alsa-project.org
Subject: Re: [PATCH] ASoC: Add support for 19.2 MHz MCLK in TLV320AIC3X
Date: Mon, 14 Apr 2008 14:50:46 +0100 [thread overview]
Message-ID: <20080414135046.GA25508@rakim.wolfsonmicro.main> (raw)
In-Reply-To: <1207902735-6660-1-git-send-email-jarkko.nikula@nokia.com>
On Fri, Apr 11, 2008 at 11:32:15AM +0300, Jarkko Nikula wrote:
> Signed-off-by: Jarkko Nikula <jarkko.nikula@nokia.com>
Thanks - I've added this to the ASoC tree and upstream queue.
Rather than maintaining this table it might be worth looking at adding
code to allow the driver to calculate a suitable configuration at run
time. The WM8753 and WM9713 drivers do this for the PLL configuration,
for example.
next prev parent reply other threads:[~2008-04-14 13:50 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-04-11 8:32 [PATCH] ASoC: Add support for 19.2 MHz MCLK in TLV320AIC3X Jarkko Nikula
2008-04-14 13:50 ` Mark Brown [this message]
2008-04-15 6:41 ` Jarkko Nikula
2008-04-15 12:34 ` Mark Brown
-- strict thread matches above, loose matches on Subject: below --
2008-04-14 11:34 Mark Brown
2008-04-14 12:29 ` Takashi Iwai
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=20080414135046.GA25508@rakim.wolfsonmicro.main \
--to=broonie@opensource.wolfsonmicro.com \
--cc=alsa-devel@alsa-project.org \
--cc=jarkko.nikula@nokia.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