From: Mark Brown <broonie@opensource.wolfsonmicro.com>
To: Axel Lin <axel.lin@ingics.com>
Cc: alsa-devel@alsa-project.org,
Rajeev Kumar <rajeev-dlh.kumar@st.com>,
Liam Girdwood <lrg@ti.com>
Subject: Re: [PATCH RFT] ASoC: sta529: Fix update register bits in sta529_set_dai_fmt
Date: Thu, 20 Dec 2012 16:01:40 +0000 [thread overview]
Message-ID: <20121220160140.GF4985@opensource.wolfsonmicro.com> (raw)
In-Reply-To: <1355991445.11688.2.camel@phoenix>
[-- Attachment #1.1: Type: text/plain, Size: 176 bytes --]
On Thu, Dec 20, 2012 at 04:17:25PM +0800, Axel Lin wrote:
> Both the mask and mode settings are wrong in current code.
>
> According to the datasheet:
Applied, thanks.
[-- Attachment #1.2: Digital signature --]
[-- Type: application/pgp-signature, Size: 836 bytes --]
[-- Attachment #2: Type: text/plain, Size: 0 bytes --]
prev parent reply other threads:[~2012-12-20 16:01 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-12-20 8:17 [PATCH RFT] ASoC: sta529: Fix update register bits in sta529_set_dai_fmt Axel Lin
2012-12-20 10:17 ` Rajeev kumar
2012-12-20 16:01 ` 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=20121220160140.GF4985@opensource.wolfsonmicro.com \
--to=broonie@opensource.wolfsonmicro.com \
--cc=alsa-devel@alsa-project.org \
--cc=axel.lin@ingics.com \
--cc=lrg@ti.com \
--cc=rajeev-dlh.kumar@st.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).