From: Charles Keepax <ckeepax@opensource.wolfsonmicro.com>
To: Robert Jarzmik <robert.jarzmik@free.fr>
Cc: Liam Girdwood <lgirdwood@gmail.com>,
Mark Brown <broonie@kernel.org>, Jaroslav Kysela <perex@perex.cz>,
Takashi Iwai <tiwai@suse.com>,
Lars-Peter Clausen <lars@metafoo.de>,
<alsa-devel@alsa-project.org>, <linux-kernel@vger.kernel.org>,
<patches@opensource.wolfsonmicro.com>
Subject: Re: [PATCH v3 1/2] ASoC: wm9713: convert to regmap
Date: Thu, 29 Oct 2015 17:06:12 +0000 [thread overview]
Message-ID: <20151029170612.GL10520@ck-lbox> (raw)
In-Reply-To: <87io5qka06.fsf@belgarion.home>
On Wed, Oct 28, 2015 at 09:34:33PM +0100, Robert Jarzmik wrote:
> Charles Keepax <ckeepax@opensource.wolfsonmicro.com> writes:
> >> /* Disable everything except touchpanel - that will be handled
> >> * by the touch driver and left disabled if touch is not in
> >> * use. */
> >> @@ -1173,14 +1217,14 @@ static int wm9713_soc_suspend(struct snd_soc_codec *codec)
> >
> > I would have expected to see the cache being put into cache only
> > mode at some point during suspend, am I missing something here as
> > well?
> Why ? Once suspended, why would you expect an access to be done to the regmap ?
> What is the case this "cache only" protects us from ?
Ah sorry this one is my bad, I was assuming these where the
runtime suspend/resume a closer look shows these are the system
suspend/resume. So yes it is pretty reasonable nothing will touch
the registers.
>
> > Again this feels like you are getting confused on the
> > functionality of the API, bypassing the cache makes all
> > reads/writes go to the hardware, suspend normally turns the
> > hardware off. Directing all reads/writes to go to the hardware in
> > a function that normally turns the hardware off looks odd.
> Yes, I must certainly misunderstand something.
> Once again I must understand first why you expect accesses to be done after a
> suspend function was called ...
>
> >> + if (ret == 0)
> >> + regcache_mark_dirty(codec->component.regmap);
> >> +
> >> + snd_soc_cache_sync(codec);
> >
> > Probably best to have both the mark_dirty and the cache_sync in
> > the if. Whilst the cache sync is a no-op if it hasn't been marked
> > as dirty, will just be a bit clearer this is indentical to the
> > pre-regmap code and more likely to remain that way under future
> > changes.
> I must admit I was expecting that the 4 registers I wrote directly to hardware
> in bypass mode were marked as "dirty", and this sync() would restore them ...
>
> Anyway, I have another idea to simplify the code greatly, it's only I'm not sure
> if my thinking is right. The idea is that these 3 registers (AC97_EXTENDED_MID,
> AC97_EXTENDED_MSTATUS, AC97_POWERDOWN) should never land in the regmap
> cache. What I think is that because they are in regmap_ac97_default_volatile(),
> they already have this property. Therefore, there is no need to do the bypass
> thing, and I could end up with :
Ah ok yes these are all volatile registers in which cause they
will bypass the naturally.
>
> static int wm9713_soc_suspend(struct snd_soc_codec *codec)
> {
> /* Disable everything except touchpanel - that will be handled
> * by the touch driver and left disabled if touch is not in
> * use. */
> snd_soc_update_bits(codec, AC97_EXTENDED_MID, 0x7fff,
> 0x7fff);
> snd_soc_write(codec, AC97_EXTENDED_MSTATUS, 0xffff);
> snd_soc_write(codec, AC97_POWERDOWN, 0x6f00);
> snd_soc_write(codec, AC97_POWERDOWN, 0xffff);
>
> /*
> * RJK: still need to be convinced why this is necessary for this
> * next line
> */
> regcache_cache_only(codec->regmap, true);
Yes you are correct you can just drop this line.
>
> return 0;
> }
>
> static int wm9713_soc_resume(struct snd_soc_codec *codec)
> {
> struct wm9713_priv *wm9713 = snd_soc_codec_get_drvdata(codec);
> int ret;
>
> /*
> * RJK: still need to be convinced why this is necessary for this
> * next line
> */
> regcache_cache_only(codec->regmap, false);
ditto.
>
> ret = snd_ac97_reset(wm9713->ac97, true, WM9713_VENDOR_ID,
> WM9713_VENDOR_ID_MASK);
> if (ret < 0)
> return ret;
>
> snd_soc_codec_force_bias_level(codec, SND_SOC_BIAS_STANDBY);
>
> /* do we need to re-start the PLL ? */
> if (wm9713->pll_in)
> wm9713_set_pll(codec, 0, wm9713->pll_in, 0);
>
> /* only synchronise the codec if warm reset failed */
> if (ret == 0) {
> regcache_mark_dirty(codec->component.regmap);
> snd_soc_cache_sync(codec);
> }
>
> return ret;
> }
>
> Thanks for your reviews.
Yeah that solution looks a lot more like what I was expecting.
Thanks,
Charles
next prev parent reply other threads:[~2015-10-29 17:23 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-10-27 21:58 [PATCH v3 1/2] ASoC: wm9713: convert to regmap Robert Jarzmik
2015-10-27 21:58 ` [PATCH v3 2/2] ASoC: wm9713: use snd_soc_*() calls to update ac97 registers Robert Jarzmik
2015-10-28 12:43 ` [PATCH v3 1/2] ASoC: wm9713: convert to regmap Charles Keepax
2015-10-28 20:34 ` Robert Jarzmik
2015-10-29 17:06 ` Charles Keepax [this message]
2015-10-29 20:03 ` Robert Jarzmik
2015-10-28 23:47 ` 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=20151029170612.GL10520@ck-lbox \
--to=ckeepax@opensource.wolfsonmicro.com \
--cc=alsa-devel@alsa-project.org \
--cc=broonie@kernel.org \
--cc=lars@metafoo.de \
--cc=lgirdwood@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=patches@opensource.wolfsonmicro.com \
--cc=perex@perex.cz \
--cc=robert.jarzmik@free.fr \
--cc=tiwai@suse.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