From: Joonas Lahtinen <joonas.lahtinen@linux.intel.com>
To: Dmitry Rogozhkin <dmitry.v.rogozhkin@intel.com>,
intel-gfx@lists.freedesktop.org
Subject: Re: [RFC 2/2] drm/i915/bdw: permit make_rpcs execution on BDW to enable slice shutdown
Date: Mon, 10 Apr 2017 14:55:43 +0300 [thread overview]
Message-ID: <1491825343.3364.8.camel@linux.intel.com> (raw)
In-Reply-To: <1491573329-7066-3-git-send-email-dmitry.v.rogozhkin@intel.com>
On pe, 2017-04-07 at 06:55 -0700, Dmitry Rogozhkin wrote:
> BDW supports RCS slices powering on/off. To do that we need make_rpcs
> executed on BDW to flash slices configuration.
>
> Change-Id: Ia80b1be329bedc57cc61078ea18ecb3d2580c16a
> Signed-off-by: Dmitry Rogozhkin <dmitry.v.rogozhkin@intel.com>
> CC: Tvrtko Ursulin <tvrtko.ursulin@intel.com>
> CC: Zhipeng Gong <zhipeng.gong@intel.com>
> CC: Joonas Lahtinen <joonas.lahtinen@linux.intel.com>
> CC: Chris Wilson <chris@chris-wilson.co.uk>
Maybe this patch should get rid of the "!IS_SKYLAKE(dev_priv)"
restriction in the setter function, too?
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
next prev parent reply other threads:[~2017-04-10 11:55 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-04-07 13:55 [RFC 0/2] slice shutdown debugfs interface for Gen8/Gen9 Dmitry Rogozhkin
2017-04-07 13:55 ` [RFC 1/2] drm/i915/skl: add slice shutdown debugfs interface Dmitry Rogozhkin
2017-04-07 13:55 ` [RFC 2/2] drm/i915/bdw: permit make_rpcs execution on BDW to enable slice shutdown Dmitry Rogozhkin
2017-04-10 11:55 ` Joonas Lahtinen [this message]
2017-04-07 22:14 ` ✓ Fi.CI.BAT: success for slice shutdown debugfs interface for Gen8/Gen9 Patchwork
2017-04-10 11:03 ` [RFC 0/2] " Chris Wilson
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=1491825343.3364.8.camel@linux.intel.com \
--to=joonas.lahtinen@linux.intel.com \
--cc=dmitry.v.rogozhkin@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.