All of lore.kernel.org
 help / color / mirror / Atom feed
From: Peter Antoine <peter.antoine@intel.com>
To: intel-gfx@lists.freedesktop.org
Subject: [PATCH v2 0/2] HuC/GuC status to Get Params.
Date: Wed, 17 Aug 2016 13:06:03 +0100	[thread overview]
Message-ID: <1471435565-24374-1-git-send-email-peter.antoine@intel.com> (raw)

As it states on the tin. Add the HuC/GuC patches to the Get params so
that they can be accessed from userspace. This is a requirement for the
opensourcing of media codecs that require the HuC/GuC.

These patches require the HuC enabling patches. patchset: HuC Loading Patches.

v2: removed extra forcewakes that were not required. (T.Ursulin)

Peter Antoine (2):
  drm/i915/get_params: Add GuC status to getparams
  drm/i915/get_params: Add HuC status to getparams

 drivers/gpu/drm/i915/i915_drv.c         |  8 ++++++++
 drivers/gpu/drm/i915/intel_guc.h        |  2 +-
 drivers/gpu/drm/i915/intel_guc_loader.c | 19 +++++++++++++++++++
 drivers/gpu/drm/i915/intel_huc.h        |  2 +-
 drivers/gpu/drm/i915/intel_huc_loader.c | 19 +++++++++++++++++++
 include/uapi/drm/i915_drm.h             |  2 ++
 6 files changed, 50 insertions(+), 2 deletions(-)

-- 
1.9.1

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

             reply	other threads:[~2016-08-17 12:06 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-08-17 12:06 Peter Antoine [this message]
2016-08-17 12:06 ` [PATCH v2 1/2] drm/i915/get_params: Add GuC status to getparams Peter Antoine
2016-08-17 12:11   ` Chris Wilson
2016-08-17 12:06 ` [PATCH v2 2/2] drm/i915/get_params: Add HuC " Peter Antoine
2016-08-17 12:11   ` Chris Wilson
2016-08-17 12:22     ` Antoine, Peter
2016-08-17 12:50 ` ✗ Ro.CI.BAT: failure for HuC/GuC status to Get Params. (rev2) Patchwork

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=1471435565-24374-1-git-send-email-peter.antoine@intel.com \
    --to=peter.antoine@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.