All of lore.kernel.org
 help / color / mirror / Atom feed
From: Gustavo Sousa <gustavo.sousa@intel.com>
To: intel-gfx@lists.freedesktop.org
Cc: Jani Nikula <jani.nikula@intel.com>,
	Lucas De Marchi <lucas.demarchi@intel.com>,
	Rodrigo Vivi <rodrigo.vivi@intel.com>
Subject: [Intel-gfx] [PATCH v4 0/1] drm/i915/dmc: Make firmware loading backwards-compatible
Date: Fri, 30 Dec 2022 15:24:21 -0300	[thread overview]
Message-ID: <20221230182422.29680-1-gustavo.sousa@intel.com> (raw)

This patch series changes DMC loading to be partially backwards-compatible by
removing version checking. Future patches in linux-firmware should start using
unversioned filenames and we will gradually adapt i915 to use them.

For platforms already supported, the change to unversioned paths will require a
fallback mechanism (alternatively load from versioned paths) to avoid
regression. Let's do that when the time comes.

This version differs from v3 in that we are postponing reorganization of macros
and implementation of the fallback mechanism to when we need it.

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

Gustavo Sousa (1):
  drm/i915/dmc: Do not require specific versions

 drivers/gpu/drm/i915/display/intel_dmc.c | 35 ------------------------
 drivers/gpu/drm/i915/display/intel_dmc.h |  1 -
 2 files changed, 36 deletions(-)

-- 
2.39.0


             reply	other threads:[~2022-12-30 18:25 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-12-30 18:24 Gustavo Sousa [this message]
2022-12-30 18:24 ` [Intel-gfx] [PATCH v4 1/1] drm/i915/dmc: Do not require specific versions Gustavo Sousa
2023-01-03 16:34   ` Rodrigo Vivi
2023-01-03 16:57     ` Gustavo Sousa
2022-12-30 18:41 ` [Intel-gfx] ✗ Fi.CI.CHECKPATCH: warning for drm/i915/dmc: Make firmware loading backwards-compatible (rev4) Patchwork
2022-12-30 18:41 ` [Intel-gfx] ✗ Fi.CI.SPARSE: " Patchwork
2022-12-30 18:56 ` [Intel-gfx] ✓ Fi.CI.BAT: success " Patchwork
2022-12-30 21:03 ` [Intel-gfx] ✓ 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=20221230182422.29680-1-gustavo.sousa@intel.com \
    --to=gustavo.sousa@intel.com \
    --cc=intel-gfx@lists.freedesktop.org \
    --cc=jani.nikula@intel.com \
    --cc=lucas.demarchi@intel.com \
    --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.