public inbox for intel-gfx@lists.freedesktop.org
 help / color / mirror / Atom feed
From: "Kamble, Sagar A" <sagar.a.kamble@intel.com>
To: akash.goel@intel.com, intel-gfx@lists.freedesktop.org
Subject: Re: [PATCH] drm/i915/gen9: Update the forcewake range
Date: Fri, 29 Apr 2016 10:23:03 +0530	[thread overview]
Message-ID: <5722E8AF.9020007@intel.com> (raw)
In-Reply-To: <1461903869-15534-1-git-send-email-akash.goel@intel.com>

Reviewed-by: Sagar Arun Kamble <sagar.a.kamble@intel.com>

On 4/29/2016 9:54 AM, akash.goel@intel.com wrote:
> From: Akash Goel <akash.goel@intel.com>
>
> Update made to the Gen9 forcewake range to cover the OA registers.
> MMIO locations 0x2700-0x2FFF belong to the same power domain
> as 0x2000-0x26FF.
>
> Signed-off-by: Akash Goel <akash.goel@intel.com>
> ---
>   drivers/gpu/drm/i915/intel_uncore.c | 3 +--
>   1 file changed, 1 insertion(+), 2 deletions(-)
>
> diff --git a/drivers/gpu/drm/i915/intel_uncore.c b/drivers/gpu/drm/i915/intel_uncore.c
> index 4f1dfe6..7387426 100644
> --- a/drivers/gpu/drm/i915/intel_uncore.c
> +++ b/drivers/gpu/drm/i915/intel_uncore.c
> @@ -699,8 +699,7 @@ static bool is_gen8_shadowed(u32 offset)
>   	REG_RANGE((reg), 0xB00,  0x2000)
>   
>   #define FORCEWAKE_GEN9_RENDER_RANGE_OFFSET(reg) \
> -	(REG_RANGE((reg), 0x2000, 0x2700) || \
> -	 REG_RANGE((reg), 0x3000, 0x4000) || \
> +	(REG_RANGE((reg), 0x2000, 0x4000) || \
>   	 REG_RANGE((reg), 0x5200, 0x8000) || \
>   	 REG_RANGE((reg), 0x8140, 0x8160) || \
>   	 REG_RANGE((reg), 0x8300, 0x8500) || \

_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/intel-gfx

      reply	other threads:[~2016-04-29  4:53 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-04-29  4:24 [PATCH] drm/i915/gen9: Update the forcewake range akash.goel
2016-04-29  4:53 ` Kamble, Sagar A [this message]

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=5722E8AF.9020007@intel.com \
    --to=sagar.a.kamble@intel.com \
    --cc=akash.goel@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