All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Kumar, Abhijeet" <abhijeet.kumar@intel.com>
To: intel-gfx@lists.freedesktop.org, chris@chris-wilson.co.uk
Subject: Re: [PATCH 3/3] just some guess work to findout the culprit. If this breaks then we know what do.
Date: Wed, 14 Feb 2018 10:23:57 +0530	[thread overview]
Message-ID: <a52f5bdb-2e42-ea98-40bb-2f168d808079@intel.com> (raw)
In-Reply-To: <1518581192-26400-3-git-send-email-abhijeet.kumar@intel.com>


[-- Attachment #1.1: Type: text/plain, Size: 1153 bytes --]



On 2/14/2018 9:36 AM, abhijeet.kumar@intel.com wrote:
> From: Abhijeet Kumar <abhijeet.kumar@intel.com>
>
> ---
>   sound/pci/hda/hda_codec.c | 2 +-
>   1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/sound/pci/hda/hda_codec.c b/sound/pci/hda/hda_codec.c
> index 8c1b07e300a8..377d5719b4cd 100644
> --- a/sound/pci/hda/hda_codec.c
> +++ b/sound/pci/hda/hda_codec.c
> @@ -2714,7 +2714,7 @@ static unsigned int hda_sync_power_state(struct hda_codec *codec,
>   	int count;
>   
>   	for (count = 0;count < 500; count++) {
> -		state = snd_hda_codec_read(codec, fg, 0,
> +		state = snd_hdac_codec_read(&codec->core, fg, 0,
>   					   AC_VERB_GET_POWER_STATE, 0);
>   		if (state & AC_PWRST_ERROR){
>   			msleep(20);

Both tests are passing on hsw and bdw devices.I can conclude that none 
of my changes
in "ALSA: hda: Make use of core codec functions to sync power state" is 
"*directly*" causing the regression.
As this patch series changes the previously defined sync function 
similar to the latest one (the one defined
in the defaulter patch).

Sidenote- Sorry for the missing commit message, it was just a HACK patch. :)

-Abhijeet

[-- Attachment #1.2: Type: text/html, Size: 1766 bytes --]

[-- Attachment #2: Type: text/plain, Size: 160 bytes --]

_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/intel-gfx

  reply	other threads:[~2018-02-14  4:54 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-02-13 19:29 [PATCH 1/2] AWOOGA: Revert "ALSA: hda: Make use of core codec functions to sync power state" Chris Wilson
2018-02-13 19:29 ` [PATCH 2/2] redo Chris Wilson
2018-02-13 20:44   ` Chris Wilson
2018-02-14  4:06   ` [PATCH 1/3] Revert "ALSA: hda: Make use of core codec functions to sync power state" abhijeet.kumar
2018-02-14  4:06     ` [PATCH 2/3] redo abhijeet.kumar
2018-02-14  4:06     ` [PATCH 3/3] just some guess work to findout the culprit. If this breaks then we know what do abhijeet.kumar
2018-02-14  4:53       ` Kumar, Abhijeet [this message]
2018-02-14  8:47         ` Chris Wilson
2018-02-14  9:06           ` Kumar, Abhijeet
2018-02-14 11:18             ` Takashi Iwai
2018-02-14 13:11               ` Kumar, Abhijeet
2018-04-18 15:16                 ` Jani Nikula
2018-02-13 19:55 ` ✗ Fi.CI.BAT: failure for series starting with [1/2] AWOOGA: Revert "ALSA: hda: Make use of core codec functions to sync power state" Patchwork
  -- strict thread matches above, loose matches on Subject: below --
2018-02-14  4:08 [PATCH 1/3] " abhijeet.kumar
2018-02-14  4:08 ` [PATCH 3/3] just some guess work to findout the culprit. If this breaks then we know what do abhijeet.kumar

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=a52f5bdb-2e42-ea98-40bb-2f168d808079@intel.com \
    --to=abhijeet.kumar@intel.com \
    --cc=chris@chris-wilson.co.uk \
    --cc=intel-gfx@lists.freedesktop.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 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.