From: Mark Brown <broonie@opensource.wolfsonmicro.com>
To: Nitin PAI <nitinmpai@gmail.com>
Cc: alsa-devel@alsa-project.org, swarren@nvidia.com, lrg@ti.com
Subject: Re: ASOC - Codecs : Renaming of spdif_tranceiver.c
Date: Wed, 7 Mar 2012 19:19:50 +0000 [thread overview]
Message-ID: <20120307191949.GZ3107@opensource.wolfsonmicro.com> (raw)
In-Reply-To: <CAJDSjBiH7=btSWPX-zh8FLokKGDVVD52ngdiv1fvd7QpkV3ZyA@mail.gmail.com>
[-- Attachment #1.1: Type: text/plain, Size: 597 bytes --]
On Wed, Mar 07, 2012 at 11:28:49PM +0530, Nitin PAI wrote:
> >>Perhaps your BSP is doing things differently to mainline here; it's
> >>vanishingly rare in mainline for machine drivers to enforce any limits
> >>themselves. Usually the CODEC and SoC drivers do this.
> I meant the SoC drivers can still enforce these limits, and need not rely
> on CODEC driver.
Usually the CODEC will be way more limited than the SoC, for example the
WM8727 (which is one of these dumb drivers) only supports sample rates
down to 32kHz but I'd be astonished if a SoC didn't do standard audio
rates from 8kHz up.
[-- Attachment #1.2: Digital signature --]
[-- Type: application/pgp-signature, Size: 836 bytes --]
[-- Attachment #2: Type: text/plain, Size: 0 bytes --]
next prev parent reply other threads:[~2012-03-07 19:19 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-03-07 6:45 ASOC - Codecs : Renaming of spdif_tranceiver.c Nitin PAI
2012-03-07 12:18 ` Nitin PAI
2012-03-07 13:43 ` Mark Brown
2012-03-07 14:15 ` Nitin PAI
2012-03-07 14:24 ` Mark Brown
2012-03-07 15:18 ` Nitin PAI
2012-03-07 15:39 ` Mark Brown
2012-03-07 16:28 ` Nitin PAI
2012-03-07 16:34 ` Mark Brown
2012-03-07 16:53 ` Nitin PAI
2012-03-07 17:04 ` Nitin PAI
2012-03-07 17:11 ` Mark Brown
2012-03-07 17:58 ` Nitin PAI
2012-03-07 19:19 ` Mark Brown [this message]
2012-03-07 17:09 ` 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=20120307191949.GZ3107@opensource.wolfsonmicro.com \
--to=broonie@opensource.wolfsonmicro.com \
--cc=alsa-devel@alsa-project.org \
--cc=lrg@ti.com \
--cc=nitinmpai@gmail.com \
--cc=swarren@nvidia.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;
as well as URLs for NNTP newsgroup(s).