Alsa-Devel Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Charles Keepax <ckeepax@opensource.wolfsonmicro.com>
To: Mark Brown <broonie@kernel.org>
Cc: alsa-devel@alsa-project.org, patches@opensource.wolfsonmicro.com,
	lee.jones@linaro.org, lgirdwood@gmail.com, sameo@linux.intel.com
Subject: Re: [PATCH 2/4 v2] ASoC: wm_adsp: Move DVFS control into codec	driver
Date: Mon, 23 Jun 2014 16:41:59 +0100	[thread overview]
Message-ID: <20140623154159.GC23517@opensource.wolfsonmicro.com> (raw)
In-Reply-To: <20140621205037.GB24291@sirena.org.uk>

On Sat, Jun 21, 2014 at 09:50:37PM +0100, Mark Brown wrote:
> On Fri, Jun 20, 2014 at 03:41:11PM +0100, Charles Keepax wrote:
> 
> > +	case SND_SOC_DAPM_PRE_PMD:
> > +		ret = arizona_dvfs_down(arizona, ARIZONA_DVFS_ADSP1_RQ);
> > +		if (ret != 0)
> > +			dev_warn(codec->dev,
> > +				 "Failed to lower DVFS: %d\n", ret);
> > +		break;
> 
> I would expect this to be _POST_PMD since it happens...

It might be a little more logical that way.

> 
> > +	default:
> > +		break;
> > +	}
> > +
> > +	return wm_adsp2_early_event(w, kcontrol, event);
> 
> ...before we even give the ADSP event a chance to run meaning the
> voltage will be ramped down prior to halting the DSP.  If there are any
> connected outputs still live this might result in audible issues as the
> device goes out of spec briefly prior to being halted and there is some
> remote chance that it could cause problems on next power up I guess (it
> did go out of spec after all).

Although this isn't actually an issue as this is the preloader
widget we added for the firmware, which is a dai_link widget so
the DSP will have been shutdown by the main widget before this is
ever called. That said _POST_PMD makes the intention much more
clear so worth changing too.

Thanks,
Charles

  reply	other threads:[~2014-06-23 15:42 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-06-20 14:41 [PATCH 0/4 v2] arizona: Improvements to codec DVFS control Charles Keepax
2014-06-20 14:41 ` [PATCH 1/4 v2] mfd: arizona: Export function to control subsystem DVFS Charles Keepax
2014-06-21 20:45   ` Mark Brown
2014-06-23 15:38     ` Charles Keepax
2014-06-20 14:41 ` [PATCH 2/4 v2] ASoC: wm_adsp: Move DVFS control into codec driver Charles Keepax
2014-06-21 20:50   ` Mark Brown
2014-06-23 15:41     ` Charles Keepax [this message]
2014-06-20 14:41 ` [PATCH 3/4 v2] ASoC: arizona: Add DVFS handling for sample rate control Charles Keepax
2014-06-21 20:51   ` Mark Brown
2014-06-20 14:41 ` [PATCH 4/4 v2] regulator: arizona-ldo1: Do not control clocking from regulator Charles Keepax
2014-06-21 20:53   ` Mark Brown
2014-06-23 15:53     ` Charles Keepax
2014-06-23 16:29       ` Charles Keepax
2014-06-23 16:35         ` 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=20140623154159.GC23517@opensource.wolfsonmicro.com \
    --to=ckeepax@opensource.wolfsonmicro.com \
    --cc=alsa-devel@alsa-project.org \
    --cc=broonie@kernel.org \
    --cc=lee.jones@linaro.org \
    --cc=lgirdwood@gmail.com \
    --cc=patches@opensource.wolfsonmicro.com \
    --cc=sameo@linux.intel.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