From: Rodrigo Vivi <rodrigo.vivi@intel.com>
To: Jani Nikula <jani.nikula@linux.intel.com>
Cc: intel-gfx@lists.freedesktop.org
Subject: Re: [PATCH] drm/i915/audio: Fix audio detection issue on GLK
Date: Mon, 9 Apr 2018 12:10:32 -0700 [thread overview]
Message-ID: <20180409191032.GL8964@intel.com> (raw)
In-Reply-To: <87a7ucjwws.fsf@intel.com>
On Mon, Apr 09, 2018 at 05:07:31PM +0300, Jani Nikula wrote:
> On Sun, 08 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.
> >
> > Signed-off-by: Gaurav K Singh <gaurav.k.singh@intel.com>
> > ---
> > drivers/gpu/drm/i915/intel_audio.c | 3 ++-
> > 1 file changed, 2 insertions(+), 1 deletion(-)
> >
> > diff --git a/drivers/gpu/drm/i915/intel_audio.c b/drivers/gpu/drm/i915/intel_audio.c
> > index 656f6c931341..73b1e0b96f88 100644
> > --- a/drivers/gpu/drm/i915/intel_audio.c
> > +++ b/drivers/gpu/drm/i915/intel_audio.c
> > @@ -729,7 +729,8 @@ 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_BC(dev_priv) && !IS_BROXTON(dev_priv) &&
> > + !IS_GEMINILAKE(dev_priv))
>
> That could be written as
>
> if (!IS_GEN9_BC(dev_priv) && !IS_GEN9_LP(dev_priv))
>
> which in turn could just be written as
>
> if (!IS_GEN9(dev_priv))
>
> ...but since GLK has gen 10 display, so I'm wondering if the same issue
> will be present in gen 10 too, and whether this should just become
>
> if (INTEL_GEN(dev_priv) < 9)
+1. I opened here to exactly add same comment.
>
> BR,
> Jani.
>
>
>
> > 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
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/intel-gfx
next prev parent reply other threads:[~2018-04-09 19:11 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-04-08 13:36 [PATCH] drm/i915/audio: Fix audio detection issue on GLK Gaurav K Singh
2018-04-08 13:45 ` ✗ Fi.CI.CHECKPATCH: warning for " Patchwork
2018-04-08 14:00 ` ✗ Fi.CI.BAT: failure " Patchwork
2018-04-09 14:07 ` [PATCH] " Jani Nikula
2018-04-09 19:10 ` Rodrigo Vivi [this message]
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
-- strict thread matches above, loose matches on Subject: below --
2018-04-17 7:18 Gaurav K Singh
2018-04-17 8:02 ` Jani Nikula
2018-04-17 18:00 ` Kumar, Abhay
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
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=20180409191032.GL8964@intel.com \
--to=rodrigo.vivi@intel.com \
--cc=intel-gfx@lists.freedesktop.org \
--cc=jani.nikula@linux.intel.com \
/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).