From: Zeng Zhaoming <zengzm.kernel@gmail.com>
To: Dong Aisheng-B29396 <B29396@freescale.com>
Cc: "alsa-devel@alsa-project.org" <alsa-devel@alsa-project.org>,
Mark Brown <broonie@opensource.wolfsonmicro.com>,
Wolfram Sang <w.sang@pengutronix.de>,
Julia Lawall <julia.lawall@lip6.fr>,
Shawn Guo <shawn.guo@linaro.org>,
Fabio Estevam <festevam@gmail.com>, "lrg@ti.com" <lrg@ti.com>
Subject: Re: duplicated test in sound/soc/codecs/sgtl5000.c
Date: Fri, 13 Jan 2012 16:40:15 +0800 [thread overview]
Message-ID: <20120113083916.GA30341@zzm-ubuntu> (raw)
In-Reply-To: <7FE21149F4667147B645348EC605788508FBC9@039-SN2MPN1-013.039d.mgd.msft.net>
On Fri 2012-01-13 06:21:00, Dong Aisheng-B29396 wrote:
> > -----Original Message-----
> > From: Mark Brown [mailto:broonie@opensource.wolfsonmicro.com]
> > Sent: Friday, January 13, 2012 6:28 AM
> > To: Julia Lawall; Fabio Estevam; Wolfram Sang; Dong Aisheng-B29396; Shawn Guo
> > Cc: lrg@ti.com; alsa-devel@alsa-project.org
> > Subject: Re: duplicated test in sound/soc/codecs/sgtl5000.c
> > Importance: High
> >
> > On Thu, Jan 12, 2012 at 10:13:24PM +0100, Julia Lawall wrote:
> > > There is a duplicated test in the function sgtl5000_restore_regs in
> > > the file sound/soc/codecs/sgtl5000.c:
> >
> > > /* this regs depends on the others */
> > > if (reg == SGTL5000_CHIP_ANA_POWER ||
> > > reg == SGTL5000_CHIP_CLK_CTRL ||
> > > reg == SGTL5000_CHIP_LINREG_CTRL ||
> > > reg == SGTL5000_CHIP_LINE_OUT_CTRL ||
> > > reg == SGTL5000_CHIP_CLK_CTRL)
> > > continue;
> >
> > > I don't know if some constant other than SGTL5000_CHIP_CLK_CTRL should
> > > be tested, or if the second test should just be deleted.
> >
> > Adding the people who've been working on the driver. Generally this is a good
> > idea when reporting issues like this.
> Cc Zhaoming.
>
> Looking at the code, I guess it's a typo error and the second check should be
> SGTL5000_CHIP_REF_CTRL since it will restore it again.
Hi, Aisheng and Julia:
Yes, a typo, I will send patch to correct it.
And Julia, the five regs list there since it should be restore in a particular
order, the order is:
1. SGTL5000_CHIP_CLK_CTRL MCLK_FREQ bits (1:0) should be restore after
SGTL5000_CHIP_ANA_POWER PLL bits set.
2. SGTL5000_CHIP_LINREG_CTRL should be set before SGTL5000_CHIP_ANA_POWER LINREG_D
restored.
3. SGTL5000_CHIP_REF_CTRL controls Analog Ground Voltage, I prefer to resotre it
after SGTL5000_CHIP_ANA_POWER restored.
4. for SGTL5000_CHIP_LINE_OUT_CTRL, I forget the real reason, Aisheng, can you help
verify line-out if remove it?
>
> Hi Mark,
> Since zhaoming leaved Freescale a few month ago,
> would you mind if I send a patch to add my name under MODULE_AHTOER as
> Co-maintainer for this driver and update Zhaoming's email address?
>
> Regards
> Dong Aisheng
prev parent reply other threads:[~2012-01-13 8:40 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-01-12 21:13 duplicated test in sound/soc/codecs/sgtl5000.c Julia Lawall
2012-01-12 22:28 ` Mark Brown
2012-01-13 6:21 ` Dong Aisheng-B29396
2012-01-13 6:37 ` Mark Brown
2012-01-13 6:49 ` Dong Aisheng-B29396
2012-01-13 8:40 ` Zeng Zhaoming [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=20120113083916.GA30341@zzm-ubuntu \
--to=zengzm.kernel@gmail.com \
--cc=B29396@freescale.com \
--cc=alsa-devel@alsa-project.org \
--cc=broonie@opensource.wolfsonmicro.com \
--cc=festevam@gmail.com \
--cc=julia.lawall@lip6.fr \
--cc=lrg@ti.com \
--cc=shawn.guo@linaro.org \
--cc=w.sang@pengutronix.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;
as well as URLs for NNTP newsgroup(s).