From: Imre Deak <imre.deak@intel.com>
To: Jani Nikula <jani.nikula@linux.intel.com>,
Sagar Arun Kamble <sagar.a.kamble@intel.com>,
intel-gfx@lists.freedesktop.org
Cc: shashidhar.hiremath@intel.com
Subject: Re: [PATCH v8 1/1] drm/i915/bxt: Check BIOS RC6 setup before enabling RC6
Date: Mon, 08 Feb 2016 16:18:57 +0200 [thread overview]
Message-ID: <1454941137.4968.6.camel@intel.com> (raw)
In-Reply-To: <87fux3wocx.fsf@intel.com>
On ma, 2016-02-08 at 11:19 +0200, Jani Nikula wrote:
> On Fri, 05 Feb 2016, Imre Deak <imre.deak@intel.com> wrote:
> > On la, 2016-02-06 at 00:13 +0530, Sagar Arun Kamble wrote:
> > > RC6 setup is shared between BIOS and Driver. BIOS sets up subset
> > > of
> > > RC6
> > > setup registers. If those are not setup Driver should not enable
> > > RC6.
> > > For implementing this, driver can check RC_CTRL0 and RC_CTRL1
> > > values
> > > to know if BIOS has enabled HW/SW RC6.
> > > This will also enable user to control RC6 using BIOS settings
> > > alone.
> > > RC6 related instability can be avoided by disabling via BIOS
> > > settings
> > > till driver fixes it.
> > >
> > > v2: Had placed logic in gen8 function by mistake. Fixed it.
> > > Ensuring RPM is not enabled in case BIOS disabled RC6.
> > >
> > > v3: Need to disable RPM if RC6 is disabled due to BIOS settings.
> > > (Daniel)
> > > Runtime PM enabling happens before gen9_enable_rc6.
> > > Moved the updation of enable_rc6 parameter in
> > > intel_uncore_sanitize.
> > >
> > > v4: Added elaborate check for BIOS RC6 setup. Prepared check_pctx
> > > for
> > > bxt.
> > > (Imre)
> > >
> > > v5: Caching reserved stolen base and size in the driver private
> > > data.
> > > Reorganized RC6 setup check. Moved from gen9_enable_rc6 to
> > > intel_uncore_sanitize. (Imre)
> > >
> > > v6: Rebasing on the patch submitted by Imre that moves
> > > gem_init_stolen
> > > earlier in the load.
> > >
> > > v7: Removed PWRCTX_MAXCNT_VCSUNIT1 check as it applies to SKL.
> > > (Imre)
> > >
> > > v8: Fixed formatting and checkpatch issues. Fixed functional
> > > issue
> > > where
> > > RC6 ctx size check was missing. (Imre)
> > >
> > > Cc: Imre Deak <imre.deak@intel.com>
> > > Signed-off-by: Sagar Arun Kamble <sagar.a.kamble@intel.com>
> >
> > Reviewed-by: Imre Deak <imre.deak@intel.com>
> >
> > Thanks for the patch, I pushed it to -dinq.
>
> The rule is, we should wait for the CI results before pushing.
Yes, I forgot to wait for the result for this version of the patch,
thanks for pointing it out. As a side-note the CI result still didn't
show up, what to do in that case? Resend the patch after a day or so?
--Imre
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/intel-gfx
next prev parent reply other threads:[~2016-02-08 14:19 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1454531039.12879.4.camel@intel.com>
2016-02-05 18:43 ` [PATCH v8 1/1] drm/i915/bxt: Check BIOS RC6 setup before enabling RC6 Sagar Arun Kamble
2016-02-05 21:38 ` Imre Deak
2016-02-08 9:19 ` Jani Nikula
2016-02-08 14:18 ` Imre Deak [this message]
2016-02-08 15:08 ` Jani Nikula
2016-02-15 17:07 ` Daniel Vetter
2016-02-16 7:52 ` Tomi Sarvela
2016-02-16 15:28 ` Daniel Vetter
2016-02-16 15:45 ` Tomi Sarvela
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=1454941137.4968.6.camel@intel.com \
--to=imre.deak@intel.com \
--cc=intel-gfx@lists.freedesktop.org \
--cc=jani.nikula@linux.intel.com \
--cc=sagar.a.kamble@intel.com \
--cc=shashidhar.hiremath@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