Intel-GFX Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: "Pottumuttu, Sai Teja" <sai.teja.pottumuttu@intel.com>
To: Dnyaneshwar Bhadane <dnyaneshwar.bhadane@intel.com>,
	<intel-xe@lists.freedesktop.org>
Cc: <intel-gfx@lists.freedesktop.org>
Subject: Re: [PATCH v4 7/9] drm/i915/xe3lpd: Extend DMC path for display version 30.02
Date: Thu, 12 Jun 2025 11:57:12 +0530	[thread overview]
Message-ID: <b0c2d1fb-0dea-478a-88c9-e43eb4a3a16e@intel.com> (raw)
In-Reply-To: <20250611134431.2761487-8-dnyaneshwar.bhadane@intel.com>

On 11-06-2025 19:14, Dnyaneshwar Bhadane wrote:
> Display version 30.02 should be treated the same as other Xe3 IP.
> So exteding DMC load path the condition for it.
> 
> Signed-off-by: Dnyaneshwar Bhadane <dnyaneshwar.bhadane@intel.com>

Nit, should be 'extending DMC load path condition for it' in commit 
message, other than that

LGTM,
Reviewed-by: Sai Teja Pottumuttu <sai.teja.pottumuttu@intel.com>

> ---
>   drivers/gpu/drm/i915/display/intel_dmc.c | 3 ++-
>   1 file changed, 2 insertions(+), 1 deletion(-)
> 
> diff --git a/drivers/gpu/drm/i915/display/intel_dmc.c b/drivers/gpu/drm/i915/display/intel_dmc.c
> index a10e56e7cf31..1295d8245a2e 100644
> --- a/drivers/gpu/drm/i915/display/intel_dmc.c
> +++ b/drivers/gpu/drm/i915/display/intel_dmc.c
> @@ -179,7 +179,8 @@ static const char *dmc_firmware_default(struct intel_display *display, u32 *size
>   	const char *fw_path = NULL;
>   	u32 max_fw_size = 0;
>   
> -	if (DISPLAY_VERx100(display) == 3000) {
> +	if (DISPLAY_VERx100(display) == 3002 ||
> +	    DISPLAY_VERx100(display) == 3000) {
>   		fw_path = XE3LPD_DMC_PATH;
>   		max_fw_size = XE2LPD_DMC_MAX_FW_SIZE;
>   	} else if (DISPLAY_VERx100(display) == 2000) {

  reply	other threads:[~2025-06-12  6:27 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-06-11 13:44 [PATCH v4 0/9] Add WildCat Lake support Dnyaneshwar Bhadane
2025-06-11 13:44 ` [PATCH v4 1/9] drm/i915/xe3lpd: Add support for display version 30.02 Dnyaneshwar Bhadane
2025-06-11 13:44 ` [PATCH v4 2/9] drm/xe/xe3: Add support for graphics IP version 30.03 Dnyaneshwar Bhadane
2025-06-12  6:50   ` Pottumuttu, Sai Teja
2025-06-12 16:30     ` Matt Roper
2025-06-12 17:13       ` Bhadane, Dnyaneshwar
2025-06-11 13:44 ` [PATCH v4 3/9] drm/xe/xe3: Add support for media IP version 30.02 Dnyaneshwar Bhadane
2025-06-11 13:44 ` [PATCH v4 4/9] drm/i915/xe3lpd: Update bandwidth parameters for display " Dnyaneshwar Bhadane
2025-06-11 13:44 ` [PATCH v4 5/9] drm/i915: Set max cdclk for display 30.02 Dnyaneshwar Bhadane
2025-06-11 13:44 ` [PATCH v4 6/9] drm/xe: Add Wildcat Lake device IDs to PTL list Dnyaneshwar Bhadane
2025-06-11 13:44 ` [PATCH v4 7/9] drm/i915/xe3lpd: Extend DMC path for display version 30.02 Dnyaneshwar Bhadane
2025-06-12  6:27   ` Pottumuttu, Sai Teja [this message]
2025-06-11 13:44 ` [PATCH v4 8/9] drm/i915/wcl: C10 phy connected to port A and B Dnyaneshwar Bhadane
2025-06-11 13:44 ` [PATCH v4 9/9] drm/i915/xe3lpd: Extend WA 16023981245 for display 30.02 Dnyaneshwar Bhadane
2025-06-11 13:56 ` [PATCH v4 0/9] Add WildCat Lake support Jani Nikula
2025-06-11 16:44 ` ✗ Fi.CI.BUILD: failure for " Patchwork
2025-06-12 17:17   ` 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=b0c2d1fb-0dea-478a-88c9-e43eb4a3a16e@intel.com \
    --to=sai.teja.pottumuttu@intel.com \
    --cc=dnyaneshwar.bhadane@intel.com \
    --cc=intel-gfx@lists.freedesktop.org \
    --cc=intel-xe@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