From: "Kumar, Abhijeet" <abhijeet.kumar@intel.com>
To: Takashi Iwai <tiwai@suse.de>, "Saarinen, Jani" <jani.saarinen@intel.com>
Cc: "intel-gfx@lists.freedesktop.org" <intel-gfx@lists.freedesktop.org>
Subject: Re: [PATCH] AWOOGA: Revert "ALSA: hda: Make use of core codec functions to sync power state"
Date: Tue, 13 Feb 2018 13:57:13 +0530 [thread overview]
Message-ID: <59542154-bf64-b859-bb13-4870fd4fc194@intel.com> (raw)
In-Reply-To: <s5hwozh8fxz.wl-tiwai@suse.de>
On 2/13/2018 1:44 PM, Takashi Iwai wrote:
> On Tue, 13 Feb 2018 08:34:40 +0100,
> Saarinen, Jani wrote:
>> HI,
>>> -----Original Message-----
>>> From: Intel-gfx [mailto:intel-gfx-bounces@lists.freedesktop.org] On Behalf Of
>>> Takashi Iwai
>>> Sent: tiistai 13. helmikuuta 2018 7.11
>>> To: Chris Wilson <chris@chris-wilson.co.uk>
>>> Cc: intel-gfx@lists.freedesktop.org; Kumar, Abhijeet
>>> <abhijeet.kumar@intel.com>
>>> Subject: Re: [Intel-gfx] [PATCH] AWOOGA: Revert "ALSA: hda: Make use of core
>>> codec functions to sync power state"
>>>
>>> On Mon, 12 Feb 2018 18:29:53 +0100,
>>> Chris Wilson wrote:
>>>> This reverts commit 3b5b899ca67db07a4c4825911072221f99e157e2.
>>>>
>>>> Fixes: 3b5b899ca67d ("ALSA: hda: Make use of core codec functions to
>>>> sync power state")
>>>> Cc: Abhijeet Kumar <abhijeet.kumar@intel.com>
>>>> Cc: Takashi Iwai <tiwai@suse.de>
>>> Did the patch break anything?
>>> I don't understand it without any real context...
>> Yes. See resutls from link what is fixed by reverting:
>> https://patchwork.freedesktop.org/series/38097/
>> Test pm_rpm:
>> Subgroup basic-pci-d3-state:
>> fail -> PASS (fi-hsw-4770)
>> fail -> PASS (fi-bdw-5557u)
>> Subgroup basic-rte:
>> fail -> PASS (fi-hsw-4770)
>> fail -> PASS (fi-bdw-5557u)
> Could you investigate why does the revert fix?
> Two functions are almost identical. The difference is that the new
> one has a counter and quit at 500 iteration, and it has a msleep(200)
> at the error exit. But both shouldn't matter for the normal
> operation...
>
> FWIW, below is the patch to make the new function identical with the
> original function. Does it change the behavior?
>
>
> thanks,
>
> Takashi
>
>
> --- a/sound/hda/hdac_device.c
> +++ b/sound/hda/hdac_device.c
> @@ -1079,15 +1079,13 @@ unsigned int snd_hdac_sync_power_state(struct hdac_device *codec,
> hda_nid_t nid, unsigned int power_state)
> {
> unsigned long end_time = jiffies + msecs_to_jiffies(500);
> - unsigned int state, actual_state, count;
> + unsigned int state, actual_state;
>
> - for (count = 0; count < 500; count++) {
> + for (;;) {
I believe changing it back to finite should fix the regression.
> state = snd_hdac_codec_read(codec, nid, 0,
> AC_VERB_GET_POWER_STATE, 0);
> - if (state & AC_PWRST_ERROR) {
> - msleep(20);
When device raises the error state bit, we might endup sending two verbs
in back to
back manner.I would still recommend to have a 20ms sleep in-order to let
the device
clean up it's internal state.
> + if (state & AC_PWRST_ERROR)
> break;
> - }
> actual_state = (state >> 4) & 0x0f;
> if (actual_state == power_state)
> break;
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/intel-gfx
prev parent reply other threads:[~2018-02-13 8:27 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-02-12 17:29 [PATCH] AWOOGA: Revert "ALSA: hda: Make use of core codec functions to sync power state" Chris Wilson
2018-02-12 18:28 ` ✓ Fi.CI.BAT: success for " Patchwork
2018-02-12 22:19 ` ✓ Fi.CI.IGT: " Patchwork
2018-02-13 5:11 ` [PATCH] " Takashi Iwai
2018-02-13 5:18 ` Kumar, Abhijeet
2018-02-13 7:35 ` Saarinen, Jani
2018-02-13 7:40 ` Lofstedt, Marta
2018-02-13 8:06 ` Kumar, Abhijeet
2018-02-13 7:34 ` Saarinen, Jani
2018-02-13 8:14 ` Takashi Iwai
2018-02-13 8:26 ` Saarinen, Jani
2018-02-13 8:30 ` Takashi Iwai
2018-02-13 8:32 ` Kumar, Abhijeet
2018-02-13 8:37 ` Chris Wilson
2018-02-13 8:27 ` Kumar, Abhijeet [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=59542154-bf64-b859-bb13-4870fd4fc194@intel.com \
--to=abhijeet.kumar@intel.com \
--cc=intel-gfx@lists.freedesktop.org \
--cc=jani.saarinen@intel.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.