From: Vasily Khoruzhick <anarsoul@gmail.com>
To: Mark Brown <broonie@sirena.org.uk>
Cc: alsa-devel@alsa-project.org, pHilipp Zabel <philipp.zabel@gmail.com>
Subject: Re: asoc: s3c24xx+uda1380 - some questions
Date: Tue, 3 Feb 2009 13:57:12 +0200 [thread overview]
Message-ID: <200902031357.12297.anarsoul@gmail.com> (raw)
In-Reply-To: <20090203114136.GA23827@sirena.org.uk>
[-- Attachment #1.1: Type: text/plain, Size: 1296 bytes --]
On Tuesday 03 February 2009 13:41:37 Mark Brown wrote:
> > One more question: it seems that my rx1950 clocked in a way that I can't
> > get precise divisor for 44100 and 22050 rates, but uda1380 driver propose
> > them (look UDA1380_RATES define and struct snd_soc_dai uda1380_dai[]. How
> > to exclude all rates except 16000 and 48000? Should I declare my own
> > snd_soc_dai and copy necessary members from uda1380's one?
>
> Set up additional constraints in your machine driver - see how drivers
> like wm8903 enforce symmetric configurations for playback and record for
> an example.
Cool, thanks :)
> > /* FIXME enable DAC_CLK */
> > - uda1380_write(codec, UDA1380_CLK, clk | R00_DAC_CLK);
> > + uda1380_write(codec, UDA1380_CLK, clk);
>
> ..are you sure this fix won't break existing users? Based on your
> explanation above (which should *really* go into the commit) I'd expect
> this to be conditional on something. It looks like what you really want
> to do here is clean up the FIXMEs :)
Yep, I'm pretty sure. It will restore WSPLL bit if it was set before. It only
changes behavior of driver if SYSCLK was chosen. It seems that FIXMEs can be
removed, I can resubmit patch if you want.
Btw, Philipp, what do you think about it?
Regards
Vasily
[-- Attachment #1.2: This is a digitally signed message part. --]
[-- Type: application/pgp-signature, Size: 189 bytes --]
[-- Attachment #2: Type: text/plain, Size: 160 bytes --]
_______________________________________________
Alsa-devel mailing list
Alsa-devel@alsa-project.org
http://mailman.alsa-project.org/mailman/listinfo/alsa-devel
next prev parent reply other threads:[~2009-02-03 11:57 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-01-27 13:19 asoc: s3c24xx+uda1380 - some questions Vasily Khoruzhick
2009-01-27 15:00 ` Mark Brown
2009-01-27 15:19 ` Vasily Khoruzhick
2009-01-27 15:25 ` Mark Brown
2009-01-27 15:49 ` Vasily Khoruzhick
2009-01-27 16:06 ` pHilipp Zabel
2009-01-27 16:22 ` Vasily Khoruzhick
2009-01-27 19:49 ` pHilipp Zabel
2009-01-27 20:32 ` Vasily Khoruzhick
2009-02-02 23:46 ` Vasily Khoruzhick
2009-02-03 11:41 ` Mark Brown
2009-02-03 11:57 ` Vasily Khoruzhick [this message]
2009-02-03 12:05 ` Mark Brown
2009-02-03 13:52 ` Vasily Khoruzhick
2009-02-03 16:09 ` pHilipp Zabel
2009-02-03 17:21 ` Mark Brown
2009-01-27 20:00 ` Mark Brown
2009-01-27 20:14 ` Vasily Khoruzhick
2009-01-27 20:19 ` 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=200902031357.12297.anarsoul@gmail.com \
--to=anarsoul@gmail.com \
--cc=alsa-devel@alsa-project.org \
--cc=broonie@sirena.org.uk \
--cc=philipp.zabel@gmail.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.