stable.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Anshuman Gupta <anshuman.gupta@intel.com>
To: "Ville Syrjälä" <ville.syrjala@linux.intel.com>
Cc: intel-gfx@lists.freedesktop.org, stable@vger.kernel.org,
	Maarten Lankhorst <maarten.lankhorst@linux.intel.com>
Subject: Re: [RFC] drm/i915: lpsp with hdmi/dp outputs
Date: Tue, 2 Jun 2020 17:58:07 +0530	[thread overview]
Message-ID: <20200602122807.GN4452@intel.com> (raw)
In-Reply-To: <20200601141132.GK6112@intel.com>

On 2020-06-01 at 17:11:32 +0300, Ville Syrjälä wrote:
> On Mon, Jun 01, 2020 at 03:45:16PM +0530, Anshuman Gupta wrote:
> > Gen12 hw are failing to enable lpsp configuration due to PG3 was left on
> > due to valid usgae count of POWER_DOMAIN_AUDIO.
> > It is not required to get POWER_DOMAIN_AUDIO ref-count when enabling
> > a crtc, it should be always i915_audio_component request to get/put
> > AUDIO_POWER_DOMAIN.
> > 
> > Cc: stable@vger.kernel.org
> > Cc: Ville Syrjälä <ville.syrjala@linux.intel.com>
> > Cc: Maarten Lankhorst <maarten.lankhorst@linux.intel.com>
> > Signed-off-by: Anshuman Gupta <anshuman.gupta@intel.com>
> > ---
> >  drivers/gpu/drm/i915/display/intel_display.c | 6 +++++-
> >  1 file changed, 5 insertions(+), 1 deletion(-)
> > 
> > diff --git a/drivers/gpu/drm/i915/display/intel_display.c b/drivers/gpu/drm/i915/display/intel_display.c
> > index 6c3b11de2daf..f31a579d7a52 100644
> > --- a/drivers/gpu/drm/i915/display/intel_display.c
> > +++ b/drivers/gpu/drm/i915/display/intel_display.c
> > @@ -7356,7 +7356,11 @@ static u64 get_crtc_power_domains(struct intel_crtc_state *crtc_state)
> >  		mask |= BIT_ULL(intel_encoder->power_domain);
> >  	}
> >  
> > -	if (HAS_DDI(dev_priv) && crtc_state->has_audio)
> > +	/*
> > +	 * Gen12 can drive lpsp on hdmi/dp outpus, it doesn't require to
> > +	 * enable AUDIO power in order to enable a crtc
> 
> Nothing requires audio power to enable a crtc. What this is saying is
> that if we want audio then we must enable the audio power. If you
> didn't want audio then you wouldn't have .has_audio set.
IMO i915_audio_component_get_power also enables audio power, and
i915_audio_component_put_power releases the usage count based upon audio
runtime idleness but here get_crtc_power_domains() gets the POWER_DOMAIN_AUDIO usages
count, which will be released only when this crtc get disbaled.
It may enable AUDIO power despite of fact that audio driver has released the
usage count.
Please correct me if i am wrong here.

> 
> That said, looks like audio is moving into the always on well, but not
> yet in tgl.
Still some of audio functional stuff lies in PG3, not completely removed
from PG3.
Thanks,
Anshuman Gupta.
> 
> .
> > +	 */
> > +	if (INTEL_GEN(dev_priv) < 12 && HAS_DDI(dev_priv) && crtc_state->has_audio)
> >  		mask |= BIT_ULL(POWER_DOMAIN_AUDIO);
> >  
> >  	if (crtc_state->shared_dpll)
> > -- 
> > 2.26.2
> 
> -- 
> Ville Syrjälä
> Intel

  reply	other threads:[~2020-06-02 12:39 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-06-01 10:15 [RFC] drm/i915: lpsp with hdmi/dp outputs Anshuman Gupta
2020-06-01 12:49 ` [Intel-gfx] " Shankar, Uma
2020-06-02 12:06   ` Anshuman Gupta
2020-06-02 13:02     ` Shankar, Uma
2020-06-01 14:11 ` Ville Syrjälä
2020-06-02 12:28   ` Anshuman Gupta [this message]
2020-06-03 10:05     ` Ville Syrjälä

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=20200602122807.GN4452@intel.com \
    --to=anshuman.gupta@intel.com \
    --cc=intel-gfx@lists.freedesktop.org \
    --cc=maarten.lankhorst@linux.intel.com \
    --cc=stable@vger.kernel.org \
    --cc=ville.syrjala@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).