From: "Ville Syrjälä" <ville.syrjala@linux.intel.com>
To: deepak.s@intel.com
Cc: intel-gfx@lists.freedesktop.org
Subject: Re: [PATCH 2/2] drm/i915: Enable PM Interrupts target via Display Interface.
Date: Wed, 16 Apr 2014 16:32:15 +0300 [thread overview]
Message-ID: <20140416133215.GJ18465@intel.com> (raw)
In-Reply-To: <20140414193655.GO18465@intel.com>
On Mon, Apr 14, 2014 at 10:36:55PM +0300, Ville Syrjälä wrote:
> On Mon, Apr 14, 2014 at 10:41:15PM +0530, deepak.s@intel.com wrote:
> > From: Deepak S <deepak.s@intel.com>
> >
> > In BDW, Apart from unmasking up/down threshold interrupts. we need
> > to umask bit 32 of PM_INTRMASK to route interrupts to target via Display
> > Interface.
> >
> > Signed-off-by: Deepak S <deepak.s@intel.com>
> > ---
> > drivers/gpu/drm/i915/i915_reg.h | 1 +
> > drivers/gpu/drm/i915/intel_pm.c | 2 ++
> > 2 files changed, 3 insertions(+)
> >
> > diff --git a/drivers/gpu/drm/i915/i915_reg.h b/drivers/gpu/drm/i915/i915_reg.h
> > index c2dd436..8c7841b 100644
> > --- a/drivers/gpu/drm/i915/i915_reg.h
> > +++ b/drivers/gpu/drm/i915/i915_reg.h
> > @@ -5105,6 +5105,7 @@ enum punit_power_well {
> > #define GEN6_RC6p_THRESHOLD 0xA0BC
> > #define GEN6_RC6pp_THRESHOLD 0xA0C0
> > #define GEN6_PMINTRMSK 0xA168
> > +#define GEN8_PMINTR_REDIRECT_TO_NON_DISP 0x7FFFFFFF
>
> Defining is as (1<<31) would make more sense to me.
>
> >
> > #define GEN6_PMISR 0x44020
> > #define GEN6_PMIMR 0x44024 /* rps_lock */
> > diff --git a/drivers/gpu/drm/i915/intel_pm.c b/drivers/gpu/drm/i915/intel_pm.c
> > index 27b64ab..6b123cd 100644
> > --- a/drivers/gpu/drm/i915/intel_pm.c
> > +++ b/drivers/gpu/drm/i915/intel_pm.c
> > @@ -3066,6 +3066,8 @@ static u32 gen6_rps_pm_mask(struct drm_i915_private *dev_priv, u8 val)
> > if (INTEL_INFO(dev_priv->dev)->gen <= 7 && !IS_HASWELL(dev_priv->dev))
> > mask |= GEN6_PM_RP_UP_EI_EXPIRED;
> >
> > + mask &= GEN8_PMINTR_REDIRECT_TO_NON_DISP;
> > +
> > return ~mask;
Oh and just noticed this doesn't actually do anything.
& must come after ~ to get the expected result.
> > }
> >
> > --
> > 1.8.5.2
> >
> > _______________________________________________
> > Intel-gfx mailing list
> > Intel-gfx@lists.freedesktop.org
> > http://lists.freedesktop.org/mailman/listinfo/intel-gfx
>
> --
> Ville Syrjälä
> Intel OTC
--
Ville Syrjälä
Intel OTC
next prev parent reply other threads:[~2014-04-16 13:32 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-04-14 17:11 [PATCH 0/2] Enable PM Interrupts for BDW deepak.s
2014-04-14 17:11 ` [PATCH 1/2] drm/i915/bdw: Implement a basic PM interrupt handler deepak.s
2014-04-14 19:55 ` Ville Syrjälä
2014-04-16 2:43 ` Ben Widawsky
2014-04-16 7:47 ` Daniel Vetter
2014-04-16 8:41 ` Ville Syrjälä
2014-04-18 12:39 ` S, Deepak
2014-04-18 12:40 ` S, Deepak
2014-04-14 17:11 ` [PATCH 2/2] drm/i915: Enable PM Interrupts target via Display Interface deepak.s
2014-04-14 19:36 ` Ville Syrjälä
2014-04-16 13:32 ` Ville Syrjälä [this message]
2014-04-18 8:20 ` Deepak S
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=20140416133215.GJ18465@intel.com \
--to=ville.syrjala@linux.intel.com \
--cc=deepak.s@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