From: Ross Zwisler <zwisler@google.com>
To: Cezary Rojewski <cezary.rojewski@intel.com>
Cc: alsa-devel@alsa-project.org, lgirdwood@gmail.com, tiwai@suse.com,
pierre-louis.bossart@linux.intel.com, vkoul@kernel.org,
broonie@kernel.org
Subject: Re: [PATCH] ASoC: Intel: haswell: Power transition refactor
Date: Mon, 6 Apr 2020 12:09:03 -0600 [thread overview]
Message-ID: <20200406180903.GA109941@google.com> (raw)
In-Reply-To: <20200330194520.13253-1-cezary.rojewski@intel.com>
On Mon, Mar 30, 2020 at 09:45:20PM +0200, Cezary Rojewski wrote:
> Update D0 <-> D3 sequence to correctly transition hardware and DSP core
> from and to D3. On top of that, set SHIM registers to their recommended
> defaults during D0 and D3 proceduces as HW does not reset registers for
> us.
>
> Connected to:
> [alsa-devel][BUG] bdw-rt5650 DSP boot timeout
> https://mailman.alsa-project.org/pipermail/alsa-devel/2019-July/153098.html
>
> Github issue ticket reference:
> https://github.com/thesofproject/linux/pull/1842
>
> Tested on:
> - BDW-Y RVP with rt286
> - SAMUS with rt5677
>
> Proposed solution (both in July 2019 and on github):
> 'Revert "ASoC: Intel: Work around to fix HW d3 potential crash issue"'
> is NAKed as it only covers the problem up and actually brings back the
> undefined behavior: some registers (e.g.: APLLSE) are describing LPT
> offsets rather than WPT ones. In consequence, during power-transitions
> driver issues incorrect writes and leaves the regs of interest alone.
>
> Existing patch - the non-revert - does not resolve the HW D3 issue at
> all as it ignores the recommended sequence and does not initialize
> hardware registers as expected. And thus, leaving things as are is also
> unacceptable.
>
> Signed-off-by: Cezary Rojewski <cezary.rojewski@intel.com>
Tested-by: Ross Zwisler <zwisler@google.com>
next prev parent reply other threads:[~2020-04-06 18:10 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-03-30 19:45 [PATCH] ASoC: Intel: haswell: Power transition refactor Cezary Rojewski
2020-04-06 8:48 ` Cezary Rojewski
2020-04-06 15:02 ` Pierre-Louis Bossart
2020-04-13 16:38 ` Cezary Rojewski
2020-06-19 1:18 ` Pierre-Louis Bossart
2020-06-19 1:21 ` Curtis Malainey
2020-06-19 8:34 ` Cezary Rojewski
2020-06-19 18:24 ` Curtis Malainey
2020-06-19 19:12 ` Cezary Rojewski
2020-06-19 21:41 ` Curtis Malainey
2020-04-06 18:09 ` Ross Zwisler [this message]
2020-04-17 18:56 ` 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=20200406180903.GA109941@google.com \
--to=zwisler@google.com \
--cc=alsa-devel@alsa-project.org \
--cc=broonie@kernel.org \
--cc=cezary.rojewski@intel.com \
--cc=lgirdwood@gmail.com \
--cc=pierre-louis.bossart@linux.intel.com \
--cc=tiwai@suse.com \
--cc=vkoul@kernel.org \
/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