From: Mark Brown <broonie@opensource.wolfsonmicro.com>
To: Andrew Paprocki <andrew@ishiboo.com>
Cc: ALSA development <alsa-devel@alsa-project.org>
Subject: Re: Embedded I2S / 192khz
Date: Thu, 8 May 2008 15:08:57 +0100 [thread overview]
Message-ID: <20080508140856.GC23041@sirena.org.uk> (raw)
In-Reply-To: <76366b180805080650p615851afi272602115ca1660a@mail.gmail.com>
On Thu, May 08, 2008 at 09:50:32AM -0400, Andrew Paprocki wrote:
> Is anyone aware of a Linux/ALSA capable chip that can drive 192khz
> I2S? I poked through the ASoC code and could only see 96khz
> capability.
The PowerPC code in sound/soc/fsl (as of 2.6.25) supports up to 192kHz,
though it appears to require the codec to clock the bus. The SuperH and
Alchemy code in:
git://opensource.wolfsonmicro.com/linux-2.6-asoc
says they support up to 192kHz too. PXA3xx should support this too when
it's done.
next prev parent reply other threads:[~2008-05-08 14:08 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-05-08 13:50 Embedded I2S / 192khz Andrew Paprocki
2008-05-08 14:08 ` Mark Brown [this message]
2008-05-08 14:22 ` Liam Girdwood
2008-05-10 18:15 ` Andrew Paprocki
2008-05-11 12:55 ` Liam Girdwood
2008-05-08 14:56 ` Timur Tabi
2008-05-08 14:09 ` Liam Girdwood
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=20080508140856.GC23041@sirena.org.uk \
--to=broonie@opensource.wolfsonmicro.com \
--cc=alsa-devel@alsa-project.org \
--cc=andrew@ishiboo.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