public inbox for intel-gfx@lists.freedesktop.org
 help / color / mirror / Atom feed
From: Lucas De Marchi <lucas.demarchi@intel.com>
To: intel-gfx@lists.freedesktop.org
Cc: Lucas De Marchi <lucas.demarchi@intel.com>
Subject: [PATCH 0/9] Add support for new DMC headers
Date: Fri,  7 Jun 2019 02:12:21 -0700	[thread overview]
Message-ID: <20190607091230.1489-1-lucas.demarchi@intel.com> (raw)

This is v2 of https://patchwork.freedesktop.org/series/61016/
Last patch as moved as the first and sent separately so it can be
backported. That one is already applied.

Rodrigo and Anusha gave their r-b on all these, but given the rebase, the
patches changed considerably (and the end result is not even the same).
So I didn't add them here, except for the first that is a trivial one.

Lucas De Marchi (9):
  drm/i915/dmc: use kernel types
  drm/i915/dmc: extract fw_info and table walk from intel_package_header
  drm/i915/dmc: add support for package_header with version 2
  drm/i915/dmc: extract function to parse css header
  drm/i915/dmc: extract function to parse package_header
  drm/i915/dmc: extract function to parse dmc_header
  drm/i915/dmc: add support to load dmc_header version 3
  drm/i915/dmc: remove redundant return in parse_csr_fw()
  drm/i915/dmc: protect against loading wrong firmware

 drivers/gpu/drm/i915/i915_drv.h  |   4 +-
 drivers/gpu/drm/i915/intel_csr.c | 407 ++++++++++++++++++++++---------
 2 files changed, 290 insertions(+), 121 deletions(-)

-- 
2.21.0

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

             reply	other threads:[~2019-06-07  9:12 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-06-07  9:12 Lucas De Marchi [this message]
2019-06-07  9:12 ` [PATCH 1/9] drm/i915/dmc: use kernel types Lucas De Marchi
2019-06-07  9:12 ` [PATCH 2/9] drm/i915/dmc: extract fw_info and table walk from intel_package_header Lucas De Marchi
2019-06-10 18:16   ` Srivatsa, Anusha
2019-06-07  9:12 ` [PATCH 3/9] drm/i915/dmc: add support for package_header with version 2 Lucas De Marchi
2019-06-10 18:22   ` Srivatsa, Anusha
2019-06-07  9:12 ` [PATCH 4/9] drm/i915/dmc: extract function to parse css header Lucas De Marchi
2019-06-14 19:30   ` Srivatsa, Anusha
2019-06-07  9:12 ` [PATCH 5/9] drm/i915/dmc: extract function to parse package_header Lucas De Marchi
2019-06-14 20:09   ` Srivatsa, Anusha
2019-06-07  9:12 ` [PATCH 6/9] drm/i915/dmc: extract function to parse dmc_header Lucas De Marchi
2019-06-14 20:24   ` Srivatsa, Anusha
2019-06-07  9:12 ` [PATCH 7/9] drm/i915/dmc: add support to load dmc_header version 3 Lucas De Marchi
2019-06-14 20:03   ` Srivatsa, Anusha
2019-06-07  9:12 ` [PATCH 8/9] drm/i915/dmc: remove redundant return in parse_csr_fw() Lucas De Marchi
2019-06-14 19:51   ` Srivatsa, Anusha
2019-06-07  9:12 ` [PATCH 9/9] drm/i915/dmc: protect against loading wrong firmware Lucas De Marchi
2019-06-14 19:44   ` Srivatsa, Anusha
2019-06-14 21:37     ` Lucas De Marchi
2019-06-17 17:46       ` Srivatsa, Anusha
2019-06-07 10:40 ` ✓ Fi.CI.BAT: success for Add support for new DMC headers Patchwork
2019-06-09 17:17 ` ✓ Fi.CI.IGT: " 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=20190607091230.1489-1-lucas.demarchi@intel.com \
    --to=lucas.demarchi@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