From: Charles Keepax <ckeepax@opensource.wolfsonmicro.com>
To: Peter Chan <peter.chan@freescale.com>
Cc: "guangyu.chen@freescale.com" <guangyu.chen@freescale.com>,
Mark Brown <broonie@kernel.org>,
Nicolin Chen <nicoleotsuka@gmail.com>,
"alsa-devel@alsa-project.org" <alsa-devel@alsa-project.org>,
"tiwai@suse.de" <tiwai@suse.de>,
"patches@opensource.wolfsonmicro.com"
<patches@opensource.wolfsonmicro.com>,
"shengjiu.wang@freescale.com" <shengjiu.wang@freescale.com>,
"lgirdwood@gmail.com" <lgirdwood@gmail.com>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"rf@opensource.wolfsonmicro.com" <rf@opensource.wolfsonmicro.com>
Subject: Re: [alsa-devel] [PATCH] ASoC: wm8962: Correct the bit offset to enable mono speaker output
Date: Mon, 11 Aug 2014 14:19:49 +0100 [thread overview]
Message-ID: <20140811131949.GA28085@opensource.wolfsonmicro.com> (raw)
In-Reply-To: <39712b9fd56546f8a943d605230a2f18@BL2PR03MB371.namprd03.prod.outlook.com>
On Fri, Aug 08, 2014 at 09:55:43AM +0000, Peter Chan wrote:
> I have a question about the wm8962 mono speaker mode. In SPK_MONO description at table 73, it says "When SPK_MONO is enabled, both speakers output the signal from the left channel". Does it mean only the left channel control the output in mono speaker mode?
>
> Thanks,
> Peter
>
> -----Original Message-----
> From: Nicolin Chen [mailto:Guangyu.Chen@freescale.com]
> Sent: Friday, August 08, 2014 4:21 PM
> To: Mark Brown
> Cc: Nicolin Chen; alsa-devel@alsa-project.org; tiwai@suse.de; patches@opensource.wolfsonmicro.com; Wang Shengjiu-B02247; lgirdwood@gmail.com; linux-kernel@vger.kernel.org; CHAN Peter-B18700; ckeepax@opensource.wolfsonmicro.com; rf@opensource.wolfsonmicro.com
> Subject: Re: [alsa-devel] [PATCH] ASoC: wm8962: Correct the bit offset to enable mono speaker output
>
> On Thu, Aug 07, 2014 at 05:58:36PM +0100, Mark Brown wrote:
> > On Thu, Aug 07, 2014 at 07:55:49PM +0800, Nicolin Chen wrote:
> > > As WM8962 datasheet describes for SPK_MONO bit of R51: When SPK_MONO
> > > is set to '1', both speakers output the signal from the left channel.
> >
> > > So for mono speaker widget, we shall enable Left Channel whose
> > > enable bit is 6 instead of 7 (Right Channel).
> > >
> > > This patches just simply corrects the bit offset.
> >
> > > spkmixl, ARRAY_SIZE(spkmixl)), SND_SOC_DAPM_MUX_E("Speaker
> > > PGA", WM8962_PWR_MGMT_2, 4, 0, &spkoutl_mux,
> > > out_pga_event, SND_SOC_DAPM_POST_PMU),
> > > -SND_SOC_DAPM_PGA("Speaker Output", WM8962_CLASS_D_CONTROL_1, 7, 0,
> > > NULL, 0),
> > > +SND_SOC_DAPM_PGA("Speaker Output", WM8962_CLASS_D_CONTROL_1, 6, 0,
> > > +NULL, 0),
> > > SND_SOC_DAPM_OUTPUT("SPKOUT"),
> > > };
> >
> > Someone who's name I'd need to look up submitted an identical fix off
> > list recently - I checked the datasheet and it seems that in mono mode
> > the speaker output actually wants both left and right channels active
> > so there is a bug here but this isn't the fix.
>
> I rechecked the datasheet and found that the hardware needs to tie both outputs and enable both bits. So the patch should be invalid.
>
> But our customer reported that they did try to set both SPKOUTR_ENA and SPKOUTL_ENA bits in mono mode but the sound is lousy. If setting SPKOUTR_ENA alone, the speaker has no sound. Only setting SPKOUTL_ENA bit get the correct speaker output in mono mode.
>From the wording of "tie both outputs together" in the datasheet
I would assume that means both should be fed the same audio? Was
this done? I will try to give the hardware guys here a shout and
see if I can get some clarification on mono mode on this device.
Thanks,
Charles
next prev parent reply other threads:[~2014-08-11 13:19 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-08-07 11:55 [PATCH] ASoC: wm8962: Correct the bit offset to enable mono speaker output Nicolin Chen
2014-08-07 11:55 ` Nicolin Chen
2014-08-07 16:58 ` Mark Brown
2014-08-08 8:20 ` Nicolin Chen
2014-08-08 8:20 ` [alsa-devel] " Nicolin Chen
2014-08-08 9:55 ` Peter Chan
2014-08-11 13:19 ` Charles Keepax [this message]
2014-08-12 8:24 ` Charles Keepax
2014-08-12 21:57 ` Mark Brown
2014-08-13 10:10 ` Peter Chan
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=20140811131949.GA28085@opensource.wolfsonmicro.com \
--to=ckeepax@opensource.wolfsonmicro.com \
--cc=alsa-devel@alsa-project.org \
--cc=broonie@kernel.org \
--cc=guangyu.chen@freescale.com \
--cc=lgirdwood@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=nicoleotsuka@gmail.com \
--cc=patches@opensource.wolfsonmicro.com \
--cc=peter.chan@freescale.com \
--cc=rf@opensource.wolfsonmicro.com \
--cc=shengjiu.wang@freescale.com \
--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 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.