From: "chaithrika" <chaithrika@ti.com>
To: 'Mark Brown' <broonie@opensource.wolfsonmicro.com>
Cc: khilman@deeprootsystems.com, alsa-devel@alsa-project.org,
davinci-linux-open-source@linux.davincidsp.com
Subject: Re: [PATCH] ASoC: tlv320aic3x: Enable PLL when not bypassed
Date: Wed, 22 Jul 2009 18:30:09 +0530 [thread overview]
Message-ID: <01ff01ca0acc$580a8110$081f8330$@com> (raw)
In-Reply-To: <20090722124214.GA28188@rakim.wolfsonmicro.main>
On Wed, Jul 22, 2009 at 18:12:14, Mark Brown wrote:
> On Wed, Jul 22, 2009 at 07:45:04AM -0400, Chaithrika U S wrote:
> > PLL was not being enabled when it was not bypassed. This patch
> > enables the PLL when it is used. Additionally, it disables the PLL
> > when it is bypassed.
> >
> > Without this patch, the audio on TI DM646x EVM and DM355 EVM
> > does not work properly. The bit clocks and the frame sync signals
> > from the codec are not correct and hence the playback/record are faster
> > than usual for most sample rates. The reason for this was that the PLL
> > was not enabled when it was not bypassed.
>
> Looks reasonable though I've no knowledge of the CODEC. Sounds like
> this is needed in 2.6.31?
>
Yes, it is needed in 2.6.31.
Regards,
Chaithrika
next prev parent reply other threads:[~2009-07-22 13:01 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-07-22 11:45 [PATCH] ASoC: tlv320aic3x: Enable PLL when not bypassed Chaithrika U S
[not found] ` <1248263104-12142-1-git-send-email-chaithrika-l0cyMroinI0@public.gmane.org>
2009-07-22 12:39 ` Mani, Arun
2009-07-22 13:10 ` chaithrika
2009-07-22 12:42 ` Mark Brown
2009-07-22 13:00 ` chaithrika [this message]
2009-07-23 7:22 ` Mark Brown
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='01ff01ca0acc$580a8110$081f8330$@com' \
--to=chaithrika@ti.com \
--cc=alsa-devel@alsa-project.org \
--cc=broonie@opensource.wolfsonmicro.com \
--cc=davinci-linux-open-source@linux.davincidsp.com \
--cc=khilman@deeprootsystems.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