intel-gfx.lists.freedesktop.org archive mirror
 help / color / mirror / Atom feed
From: Jani Nikula <jani.nikula@intel.com>
To: Gaurav K Singh <gaurav.k.singh@intel.com>,
	intel-gfx@lists.freedesktop.org
Cc: dhinakaran.pandiyan@intel.com
Subject: Re: [PATCH] drm/i915/audio: Fix audio detection issue on GLK
Date: Tue, 17 Apr 2018 11:02:57 +0300	[thread overview]
Message-ID: <87tvsafefi.fsf@intel.com> (raw)
In-Reply-To: <1523949504-6428-1-git-send-email-gaurav.k.singh@intel.com>

On Tue, 17 Apr 2018, Gaurav K Singh <gaurav.k.singh@intel.com> wrote:
> On Geminilake, sometimes audio card is not getting
> detected after reboot. This is a spurious issue happening on
> Geminilake. HW codec and HD audio controller link was going
> out of sync for which there was a fix in i915 driver but
> was not getting invoked for GLK. Extending this fix to GLK as well.
>
> Tested by Du,Wenkai on GLK board.
>
> Bspec: 21829
>
> v2: Instead of checking GEN9_BC, BXT and GLK macros, use IS_GEN9 macro
>
> Signed-off-by: Gaurav K Singh <gaurav.k.singh@intel.com>
> Reviewed-by: Jani Nikula <jani.nikula@intel.com>

That Reviewed-by is jumping to conclusions I'm afraid. Giving review
comments does not mean Reviewed-by. Only explicit Reviewed-by reply
does.

I can only say that this is the right approach *if* glk is to be covered
here, but I have no data to actually say if that's the right thing to
do.

BR,
Jani.

> ---
>  drivers/gpu/drm/i915/intel_audio.c | 2 +-
>  1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/drivers/gpu/drm/i915/intel_audio.c b/drivers/gpu/drm/i915/intel_audio.c
> index 656f6c931341..3ea566f99450 100644
> --- a/drivers/gpu/drm/i915/intel_audio.c
> +++ b/drivers/gpu/drm/i915/intel_audio.c
> @@ -729,7 +729,7 @@ static void i915_audio_component_codec_wake_override(struct device *kdev,
>  	struct drm_i915_private *dev_priv = kdev_to_i915(kdev);
>  	u32 tmp;
>  
> -	if (!IS_GEN9_BC(dev_priv) && !IS_BROXTON(dev_priv))
> +	if (!IS_GEN9(dev_priv))
>  		return;
>  
>  	i915_audio_component_get_power(kdev);

-- 
Jani Nikula, Intel Open Source Technology Center
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/intel-gfx

  parent reply	other threads:[~2018-04-17  8:00 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-04-17  7:18 [PATCH] drm/i915/audio: Fix audio detection issue on GLK Gaurav K Singh
2018-04-17  8:00 ` ✗ Fi.CI.BAT: failure for drm/i915/audio: Fix audio detection issue on GLK (rev2) Patchwork
2018-04-17  8:05   ` Martin Peres
2018-04-17  8:02 ` Jani Nikula [this message]
2018-04-17  9:18 ` ✓ Fi.CI.BAT: success " Patchwork
2018-04-17 10:05 ` ✗ Fi.CI.IGT: failure " Patchwork
2018-04-17 18:00 ` [PATCH] drm/i915/audio: Fix audio detection issue on GLK Kumar, Abhay
  -- strict thread matches above, loose matches on Subject: below --
2018-04-17 18:22 Gaurav K Singh
2018-04-17 18:28 ` Du,Wenkai
2018-04-18  6:04   ` Singh, Gaurav K
2018-04-18  8:07     ` Jani Nikula
2018-04-08 13:36 Gaurav K Singh
2018-04-09 14:07 ` Jani Nikula
2018-04-09 19:10   ` Rodrigo Vivi
2018-04-09 19:18     ` Kumar, Abhay
2018-04-09 23:20       ` Dhinakaran Pandiyan
2018-04-09 23:13         ` Kumar, Abhay
2018-04-10 11:02           ` Jani Nikula
2018-04-11 19:27             ` Singh, Gaurav K

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=87tvsafefi.fsf@intel.com \
    --to=jani.nikula@intel.com \
    --cc=dhinakaran.pandiyan@intel.com \
    --cc=gaurav.k.singh@intel.com \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).