All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jani Nikula <jani.nikula@linux.intel.com>
To: Dnyaneshwar Bhadane <dnyaneshwar.bhadane@intel.com>,
	intel-gfx@lists.freedesktop.org
Cc: Dnyaneshwar Bhadane <dnyaneshwar.bhadane@intel.com>
Subject: Re: [PATCH] drm/i915/dmc: Hardcode path to MTL DMC v2.23
Date: Wed, 28 Aug 2024 11:42:01 +0300	[thread overview]
Message-ID: <877cc1yr6u.fsf@intel.com> (raw)
In-Reply-To: <20240827140353.3022432-1-dnyaneshwar.bhadane@intel.com>

On Tue, 27 Aug 2024, Dnyaneshwar Bhadane <dnyaneshwar.bhadane@intel.com> wrote:
> NOT TO BE REVIEWED/MERGED
> Hardcode path to DMC firmware for CI purposes only.

This is why we have trybot, no?

BR,
Jani.

>
> Signed-off-by: Dnyaneshwar Bhadane <dnyaneshwar.bhadane@intel.com>
> ---
>  drivers/gpu/drm/i915/display/intel_dmc.c | 2 +-
>  1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/drivers/gpu/drm/i915/display/intel_dmc.c b/drivers/gpu/drm/i915/display/intel_dmc.c
> index 7c756d5ba2a2..723743cbe8e2 100644
> --- a/drivers/gpu/drm/i915/display/intel_dmc.c
> +++ b/drivers/gpu/drm/i915/display/intel_dmc.c
> @@ -119,7 +119,7 @@ MODULE_FIRMWARE(XE2LPD_DMC_PATH);
>  #define BMG_DMC_PATH			DMC_PATH(bmg)
>  MODULE_FIRMWARE(BMG_DMC_PATH);
>  
> -#define MTL_DMC_PATH			DMC_PATH(mtl)
> +#define MTL_DMC_PATH			"i915/mtl_dmc_ver2_23.bin"
>  MODULE_FIRMWARE(MTL_DMC_PATH);
>  
>  #define DG2_DMC_PATH			DMC_LEGACY_PATH(dg2, 2, 08)

-- 
Jani Nikula, Intel

  parent reply	other threads:[~2024-08-28  8:42 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-08-27 14:03 [PATCH] drm/i915/dmc: Hardcode path to MTL DMC v2.23 Dnyaneshwar Bhadane
2024-08-27 14:39 ` ✓ Fi.CI.BAT: success for " Patchwork
2024-08-28  8:42 ` Jani Nikula [this message]
2024-08-28 13:13   ` [PATCH] " Gustavo Sousa
2024-08-28 19:17 ` ✗ Fi.CI.IGT: failure for " Patchwork
2024-09-03 10:41 ` [PATCH] " Bhadane, Dnyaneshwar

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=877cc1yr6u.fsf@intel.com \
    --to=jani.nikula@linux.intel.com \
    --cc=dnyaneshwar.bhadane@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.