From: Charles Keepax <ckeepax@opensource.wolfsonmicro.com>
To: Rob Calhoun <rcalhoun@gmail.com>
Cc: alsa-devel@alsa-project.org, broonie@kernel.org,
patches@opensource.wolfsonmicro.com,
Matt Flax <flatmax@flatmax.org>
Subject: Re: [PATCH 2/2] ASoc: wm8731: add normal mode with 12MHz XTAL
Date: Mon, 20 Jun 2016 11:55:40 +0100 [thread overview]
Message-ID: <20160620105540.GI1552@localhost.localdomain> (raw)
In-Reply-To: <CAMv2zM8txnDEPh9Gebbt7KC7YuvEyOFxTomnnaRdu8SLyme5bw@mail.gmail.com>
On Sun, Jun 19, 2016 at 05:46:02PM -0400, Rob Calhoun wrote:
> Hi Matt,
>
> Based on my experience with the WM8737, the bitclock will always run
> at 12 MHz on these devices in USB mode. While the carrying capacity of
> the channel is always 12 Mbps, the data put on the wire by the codec
> depend on the sample rate, number of channels, and bit depth. This
> leaves some unused capacity in the channel. It is the responsibility
> of the receiving digital audio interface to pull off the appropriate
> number of bits every time the LRCLK/frameclock fires and ignore the
> rest of it. For example in I2S mode, 2-channel, 32-bit, the DAI should
> pull off the first 32 bits following each LRCLK transition.
Thanks very much for adding this, sounds like this is basically
how the part operates then. Although I feel the datasheet could
have been more clear, apologies for that.
Thanks,
Charles
prev parent reply other threads:[~2016-06-20 10:55 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1465517516-1917-1-git-send-email-flatmax@flatmax.org>
[not found] ` <1465517516-1917-2-git-send-email-flatmax@flatmax.org>
2016-06-11 9:16 ` [PATCH 2/2] ASoc: wm8731: add normal mode with 12MHz XTAL Matt Flax
2016-06-12 3:22 ` Matt Flax
2016-06-13 8:37 ` Charles Keepax
2016-06-13 9:45 ` Matt Flax
2016-06-13 11:59 ` Charles Keepax
2016-06-13 12:39 ` Matt Flax
2016-06-15 16:56 ` Charles Keepax
2016-06-19 21:46 ` Rob Calhoun
2016-06-19 22:23 ` Matt Flax
2016-06-20 10:55 ` Charles Keepax [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=20160620105540.GI1552@localhost.localdomain \
--to=ckeepax@opensource.wolfsonmicro.com \
--cc=alsa-devel@alsa-project.org \
--cc=broonie@kernel.org \
--cc=flatmax@flatmax.org \
--cc=patches@opensource.wolfsonmicro.com \
--cc=rcalhoun@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.