From: Jarkko Nikula <jarkko.nikula@bitmer.com>
To: Axel Lin <axel.lin@gmail.com>
Cc: linux-kernel@vger.kernel.org,
Vladimir Barinov <vbarinov@embeddedalley.com>,
Liam Girdwood <lrg@ti.com>,
Mark Brown <broonie@opensource.wolfsonmicro.com>,
Peter Ujfalusi <peter.ujfalusi@ti.com>,
alsa-devel@alsa-project.org
Subject: Re: [PATCH 2/2] ASoC: tlv320aic3x: Clear BIT_CLK_MASTER and WORD_CLK_MASTER bits for for slave mode
Date: Thu, 27 Oct 2011 13:52:21 +0200 [thread overview]
Message-ID: <1319716341.4629.10.camel@puukko.homenet-68> (raw)
In-Reply-To: <1319704722.2673.5.camel@phoenix>
On Thu, 2011-10-27 at 16:38 +0800, Axel Lin wrote:
> According to the datasheet:
>
> Page0 / Register8: Audio Serial Data interface Control Register A
> BIT 7: Bit Clock Directional Control
> 0: Bit clock is an input (slave mode)
> 1: Bit clock is an output (master mode)
>
> BIT 6: Word Clock Directional Control
> 0: Word clock is an input (slave mode)
> 1: Word clock is an output (master mode)
>
> Current code sets BIT_CLK_MASTER and WORD_CLK_MASTER bits for master mode,
> but does not clear these bits for slave mode.
>
> Signed-off-by: Axel Lin <axel.lin@gmail.com>
> ---
> sound/soc/codecs/tlv320aic3x.c | 1 +
> 1 files changed, 1 insertions(+), 0 deletions(-)
>
This is not entirely true - there is this fussy '& 0x3f' operation that
does clear those bits a few code lines above your change. Now we can rid
of it thanks to your patch, hopefully for iface_breg too (in case if you
are going to send an another patch as this is applied) :-)
--
Jarkko
next prev parent reply other threads:[~2011-10-27 11:52 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-10-27 8:35 [PATCH 1/2] ASoC: tlv320aic23: Clear TLV320AIC23_MS_MASTER bit " Axel Lin
2011-10-27 8:38 ` [PATCH 2/2] ASoC: tlv320aic3x: Clear BIT_CLK_MASTER and WORD_CLK_MASTER bits for " Axel Lin
2011-10-27 9:17 ` Girdwood, Liam
2011-10-27 11:52 ` Jarkko Nikula [this message]
2011-10-27 10:00 ` [PATCH 1/2] ASoC: tlv320aic23: Clear TLV320AIC23_MS_MASTER bit " 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=1319716341.4629.10.camel@puukko.homenet-68 \
--to=jarkko.nikula@bitmer.com \
--cc=alsa-devel@alsa-project.org \
--cc=axel.lin@gmail.com \
--cc=broonie@opensource.wolfsonmicro.com \
--cc=linux-kernel@vger.kernel.org \
--cc=lrg@ti.com \
--cc=peter.ujfalusi@ti.com \
--cc=vbarinov@embeddedalley.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
all inboxes | Powered by JetHome®