From: "Kumar, Abhijeet" <abhijeet.kumar@intel.com>
To: Chris Wilson <chris@chris-wilson.co.uk>,
"intel-gfx@lists.freedesktop.org"
<intel-gfx@lists.freedesktop.org>, Takashi Iwai <tiwai@suse.de>
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 14:36:19 +0530 [thread overview]
Message-ID: <8b5d152b-da2e-2ac2-b709-0f3d48f3ec37@intel.com> (raw)
In-Reply-To: <151859802599.31524.15465029186500886192@mail.alporthouse.com>
On 2/14/2018 2:17 PM, Chris Wilson wrote:
> Quoting Kumar, Abhijeet (2018-02-14 04:53:57)
>>
>> 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
> Where did you run this against CI? (Due to the nature of patchwork it
> will not have picked this up as a new revision.)
You can find it here https://patchwork.freedesktop.org/series/38212/.
I've reverted my patch and made my changes in hda_codec inorder to
demonstrate my changes is not
breaking it.
>
>> 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).
> If you have no answer, we will apply the revert to our CI so that we do
> not lose coverage.
I guess, I don't have any issue by reverting this single patch alone as
i already said this patch had
no functional change! It just had few optimization which i believe we
can skip for now. :)
+Takashi to comment.
-Abhijeet
> -Chris
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/intel-gfx
next prev parent reply other threads:[~2018-02-14 9:06 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
2018-02-14 8:47 ` Chris Wilson
2018-02-14 9:06 ` Kumar, Abhijeet [this message]
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=8b5d152b-da2e-2ac2-b709-0f3d48f3ec37@intel.com \
--to=abhijeet.kumar@intel.com \
--cc=chris@chris-wilson.co.uk \
--cc=intel-gfx@lists.freedesktop.org \
--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.