From: Charles Keepax <ckeepax@opensource.wolfsonmicro.com>
To: Mark Brown <broonie@kernel.org>
Cc: alsa-devel@alsa-project.org, tiwai@suse.de,
patches@opensource.wolfsonmicro.com, lgirdwood@gmail.com,
Nikesh Oswal <nikesh@opensource.wolfsonmicro.com>,
linux-kernel@vger.kernel.org, perex@perex.cz
Subject: Re: [PATCH] ASoC: wm_hubs: Fix DC Servo readback
Date: Wed, 13 Aug 2014 13:39:00 +0100 [thread overview]
Message-ID: <20140813123900.GL15833@opensource.wolfsonmicro.com> (raw)
In-Reply-To: <20140813121637.GH15833@opensource.wolfsonmicro.com>
On Wed, Aug 13, 2014 at 01:16:37PM +0100, Charles Keepax wrote:
> On Wed, Aug 13, 2014 at 12:38:41PM +0100, Mark Brown wrote:
> > On Wed, Aug 13, 2014 at 12:08:44PM +0100, Charles Keepax wrote:
> > > On Wed, Aug 13, 2014 at 11:47:20AM +0100, Nikesh Oswal wrote:
> >
> > > > case 2:
> > > > dcs_reg = WM8994_DC_SERVO_4E;
> > > > break;
> > > > - case 1:
> > > > - dcs_reg = WM8994_DC_SERVO_READBACK;
> > > > - break;
> > > > default:
> > > > dcs_reg = WM8993_DC_SERVO_3;
> > > > break;
> >
> > > This doesn't look right, firstly if it is the same register for
> > > all versions then surely we should change the code that sets
> > > dcs_readback_mode rather than setting that to different values
> > > but treating them the same. Although obviously if nothing still
> > > uses this case we could remove it as well.
> >
> > > Also I think the situation is more complex for example on version
> > > 4.4 of the datasheet for wm8994 the WR_VAL fields appear to be in
> > > register 59h. Which is not consistent with this.
> >
> > There was a change in the DC servo between revisions of the WM8994 (at
> > revision E from the look of the code). This isn't documented in the
> > datasheets as they only document current silicon.
>
> Indeed, but this patch sets all revs of wm8994 to use register 57h.
> The lastest version of the datasheet has this register at 59h
> although some of the older versions of the datasheet (which likely
> match some older revs of the chip although no way to tell which one
> just from the datasheet) have it at 57h.
>
> I think basically we need to get some clarity from hardware here
> on which revs use which address and update this patch to match,
> but either way it looks likely that this patch doesn't address
> the whole picture.
Sorry no ignore me I am talking non-sense here. It still treats
the newer revs correctly, I suspect this might be a nice change
though:
--- a/sound/soc/codecs/wm_hubs.c
+++ b/sound/soc/codecs/wm_hubs.c
@@ -209,7 +209,7 @@ static int wm_hubs_read_dc_servo(struct
snd_soc_codec *codec,
dcs_reg = WM8994_DC_SERVO_4E;
break;
case 1:
- dcs_reg = WM8994_DC_SERVO_READBACK;
+ dcs_reg = WM8994_DC_SERVO_4;
break;
Thanks,
Charles
next prev parent reply other threads:[~2014-08-13 12:39 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-08-13 10:47 Nikesh Oswal
2014-08-13 11:08 ` Charles Keepax
2014-08-13 11:38 ` Mark Brown
2014-08-13 12:16 ` Charles Keepax
2014-08-13 12:39 ` Charles Keepax [this message]
2014-08-13 12:40 ` 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=20140813123900.GL15833@opensource.wolfsonmicro.com \
--to=ckeepax@opensource.wolfsonmicro.com \
--cc=alsa-devel@alsa-project.org \
--cc=broonie@kernel.org \
--cc=lgirdwood@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=nikesh@opensource.wolfsonmicro.com \
--cc=patches@opensource.wolfsonmicro.com \
--cc=perex@perex.cz \
--cc=tiwai@suse.de \
/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
Powered by JetHome