All of lore.kernel.org
 help / color / mirror / Atom feed
From: Gustavo Sousa <gustavo.sousa@intel.com>
To: intel-gfx@lists.freedesktop.org
Cc: Rodrigo Vivi <rodrigo.vivi@intel.com>
Subject: [Intel-gfx] [PATCH 0/2] drm/i915/dmc: Make firmware loading backwards-compatible
Date: Tue, 20 Dec 2022 17:11:02 -0300	[thread overview]
Message-ID: <20221220201104.339399-1-gustavo.sousa@intel.com> (raw)

This patch series changes DMC loading to be backwards-compatible by removing
version checking and loading blobs from unversioned filenames.

Should this be accepted, the next step would be to update linux-firmware to
start using the unversioned filenames. That said, this change still allows to
use the previously versioned paths as fallback, allowing DMC loading to still
work with the current state of linux-firmware.

Signed-off-by: Gustavo Sousa <gustavo.sousa@intel.com>

Gustavo Sousa (2):
  drm/i915/dmc: Do not require specific versions
  drm/i915/dmc: Use unversioned firmware paths

 drivers/gpu/drm/i915/display/intel_dmc.c | 133 ++++++++++++++---------
 drivers/gpu/drm/i915/display/intel_dmc.h |   1 -
 2 files changed, 82 insertions(+), 52 deletions(-)

-- 
2.38.1


             reply	other threads:[~2022-12-20 20:11 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-12-20 20:11 Gustavo Sousa [this message]
2022-12-20 20:11 ` [Intel-gfx] [PATCH 1/2] drm/i915/dmc: Do not require specific versions Gustavo Sousa
2022-12-20 20:11 ` [Intel-gfx] [PATCH 2/2] drm/i915/dmc: Use unversioned firmware paths Gustavo Sousa
2022-12-21 10:26   ` Jani Nikula
2022-12-21 15:08     ` Gustavo Sousa
2022-12-22  0:23     ` Lucas De Marchi
2022-12-22 22:12       ` Gustavo Sousa
2022-12-23  0:52         ` Lucas De Marchi
2022-12-23 11:51           ` Gustavo Sousa
2022-12-23 15:36             ` Rodrigo Vivi
2022-12-28 22:00               ` Gustavo Sousa
2022-12-28 22:04                 ` Vivi, Rodrigo
2022-12-28 22:19                   ` Gustavo Sousa

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=20221220201104.339399-1-gustavo.sousa@intel.com \
    --to=gustavo.sousa@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 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.