intel-gfx.lists.freedesktop.org archive mirror
 help / color / mirror / Atom feed
From: Peter Antoine <peter.antoine@intel.com>
To: intel-gfx@lists.freedesktop.org
Cc: rodrigo.vivi@intel.com
Subject: [PATCH v2 0/6] HuC Loading Patches
Date: Fri,  1 Jul 2016 14:15:39 +0100	[thread overview]
Message-ID: <1467378945-14274-1-git-send-email-peter.antoine@intel.com> (raw)

This patch series enables the HuC loading. These patches are a port of the
patches that were created by Yu Dai (Alex) and have been ported to work with
the new GuC patches.

The series include a patch to enable the HuC on BXT. This is a separate patch
as the state of the BXT HuC firmware is still in flux, so the patch can be
dropped without delaying the series.

v2: rebased onto drm-intel-nightly.
    Also, patch 1 has been recreated as the upstream version of the function
    had change significantly making the old patch obsolete.
    Also, due to a code move i915_dma.c -> i915_drv.c some code was being
    applied to a deleted file.
    Also HuC file versions and formats changed.

    Feedback from D.Gordon and R.Vivi (Thanks).

Peter Antoine (6):
  drm/i915/guc: Make the GuC fw loading helper functions general
  drm/i915/huc: Unified css_header struct for GuC and HuC
  drm/i915/huc: Add HuC fw loading support
  drm/i915/huc: Add debugfs for HuC loading status check
  drm/i915/huc: Support HuC authentication
  drm/i915/huc: Add BXT HuC Loading Support

 drivers/gpu/drm/i915/Makefile              |   1 +
 drivers/gpu/drm/i915/i915_debugfs.c        |  44 ++++-
 drivers/gpu/drm/i915/i915_drv.c            |   3 +
 drivers/gpu/drm/i915/i915_drv.h            |   3 +
 drivers/gpu/drm/i915/i915_guc_reg.h        |   3 +
 drivers/gpu/drm/i915/i915_guc_submission.c |  69 +++++++-
 drivers/gpu/drm/i915/intel_guc.h           |  46 ++---
 drivers/gpu/drm/i915/intel_guc_fwif.h      |  17 +-
 drivers/gpu/drm/i915/intel_guc_loader.c    | 202 +++++++++++----------
 drivers/gpu/drm/i915/intel_huc.h           |  44 +++++
 drivers/gpu/drm/i915/intel_huc_loader.c    | 274 +++++++++++++++++++++++++++++
 11 files changed, 583 insertions(+), 123 deletions(-)
 create mode 100644 drivers/gpu/drm/i915/intel_huc.h
 create mode 100644 drivers/gpu/drm/i915/intel_huc_loader.c

-- 
1.9.1

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

             reply	other threads:[~2016-07-01 13:15 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-07-01 13:15 Peter Antoine [this message]
2016-07-01 13:15 ` [PATCH v2 1/6] drm/i915/guc: Make the GuC fw loading helper functions general Peter Antoine
2016-07-05 14:44   ` Dave Gordon
2016-07-01 13:15 ` [PATCH v2 2/6] drm/i915/huc: Unified css_header struct for GuC and HuC Peter Antoine
2016-07-01 13:15 ` [PATCH v2 3/6] drm/i915/huc: Add HuC fw loading support Peter Antoine
2016-07-01 13:15 ` [PATCH v2 4/6] drm/i915/huc: Add debugfs for HuC loading status check Peter Antoine
2016-07-01 13:15 ` [PATCH v2 5/6] drm/i915/huc: Support HuC authentication Peter Antoine
2016-07-01 13:15 ` [PATCH v2 6/6] drm/i915/huc: Add BXT HuC Loading Support Peter Antoine
2016-07-01 14:04 ` ✗ Ro.CI.BAT: warning for HuC Loading Patches (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=1467378945-14274-1-git-send-email-peter.antoine@intel.com \
    --to=peter.antoine@intel.com \
    --cc=intel-gfx@lists.freedesktop.org \
    --cc=rodrigo.vivi@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;
as well as URLs for NNTP newsgroup(s).