public inbox for intel-gfx@lists.freedesktop.org
 help / color / mirror / Atom feed
From: Joonas Lahtinen <joonas.lahtinen@linux.intel.com>
To: Wang Elaine <elaine.wang@intel.com>, intel-gfx@lists.freedesktop.org
Subject: Re: [PATCH] drm/i915: Respect ring_mask when initializing forcewake domains
Date: Wed, 07 Dec 2016 15:54:18 +0200	[thread overview]
Message-ID: <1481118858.5745.9.camel@linux.intel.com> (raw)
In-Reply-To: <1480943760-8689-1-git-send-email-elaine.wang@intel.com>

On ma, 2016-12-05 at 21:16 +0800, Wang Elaine wrote:
> From: Elaine Wang <elaine.wang@intel.com>
> 
> Some platforms don't have render or blitter. So no need to call
> render domain or blitter domain forcewake init function.
> 
> Cc: Joonas Lahtinen <joonas.lahtinen@linux.intel.com>
> Signed-off-by: Elaine Wang <elaine.wang@intel.com>

I sent an additional patch to the mailing list that would catch any
rogue accesses. If you could test with it in combination to this
change, I would be ready to merge this patch if no problems arise.

The patch is;

    Author: Joonas Lahtinen <joonas.lahtinen@linux.intel.com>
    Date:   Wed Dec 7 15:40:13 2016 +0200

        drm/i915: Catch non-existent registers in find_fw_domain

Regards, Joonas
-- 
Joonas Lahtinen
Open Source Technology Center
Intel Corporation
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/intel-gfx

      parent reply	other threads:[~2016-12-07 13:54 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-12-05 13:16 [PATCH] drm/i915: Respect ring_mask when initializing forcewake domains Wang Elaine
2016-12-05 18:57 ` ✓ Fi.CI.BAT: success for " Patchwork
2016-12-07 13:54 ` Joonas Lahtinen [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=1481118858.5745.9.camel@linux.intel.com \
    --to=joonas.lahtinen@linux.intel.com \
    --cc=elaine.wang@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