From: Mark Brown <broonie@opensource.wolfsonmicro.com>
To: Peter Ujfalusi <peter.ujfalusi@ti.com>
Cc: alsa-devel@alsa-project.org, Liam Girdwood <lrg@ti.com>
Subject: Re: [PATCH] ASoC: omap-mcpdm: Set constraint for 24 msb
Date: Sun, 15 Jan 2012 03:22:26 -0800 [thread overview]
Message-ID: <20120115112224.GB3040@opensource.wolfsonmicro.com> (raw)
In-Reply-To: <1326557803-18728-1-git-send-email-peter.ujfalusi@ti.com>
On Sat, Jan 14, 2012 at 05:16:43PM +0100, Peter Ujfalusi wrote:
> OMAP McPDM supports 24 msb in the 32 bit sample.
> Make sure that applications get this information.
This is actually a pretty widespread configuration for hardware - I'd
guess most devices that support 32 bit DAI formats don't actually use
all 32 bits. If this is really useful to applications we should add a
framework feature letting drivers just set a number rather than adding
code individual drivers, I'll send a patch shortly adding a feature for
this.
prev parent reply other threads:[~2012-01-15 11:22 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-01-14 16:16 [PATCH] ASoC: omap-mcpdm: Set constraint for 24 msb Peter Ujfalusi
2012-01-15 11:22 ` Mark Brown [this message]
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=20120115112224.GB3040@opensource.wolfsonmicro.com \
--to=broonie@opensource.wolfsonmicro.com \
--cc=alsa-devel@alsa-project.org \
--cc=lrg@ti.com \
--cc=peter.ujfalusi@ti.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).