From: Jani Nikula <jani.nikula@linux.intel.com>
To: Lucas De Marchi <lucas.demarchi@intel.com>,
Matt Roper <matthew.d.roper@intel.com>
Cc: intel-xe@lists.freedesktop.org, intel-gfx@lists.freedesktop.org,
Vivek Kasireddy <vivek.kasireddy@intel.com>,
stable@vger.kernel.org
Subject: Re: [PATCH v2] drm/i915/xe2hpd: Identify the memory type for SKUs with GDDR + ECC
Date: Tue, 25 Mar 2025 11:03:13 +0200 [thread overview]
Message-ID: <87bjtpa3e6.fsf@intel.com> (raw)
In-Reply-To: <32lakxysapix2hgoh5e7n2b6zlv544nh6vcvmg6zllzjnlikmd@7k37w7pqy4p2>
On Mon, 24 Mar 2025, Lucas De Marchi <lucas.demarchi@intel.com> wrote:
> On Mon, Mar 24, 2025 at 01:02:07PM -0700, Matt Roper wrote:
>>On Mon, Mar 24, 2025 at 10:22:33AM -0700, Lucas De Marchi wrote:
>>> From: Vivek Kasireddy <vivek.kasireddy@intel.com>
>>>
>>> Some SKUs of Xe2_HPD platforms (such as BMG) have GDDR memory type
>>> with ECC enabled. We need to identify this scenario and add a new
>>> case in xelpdp_get_dram_info() to handle it. In addition, the
>>> derating value needs to be adjusted accordingly to compensate for
>>> the limited bandwidth.
>>>
>>> Bspec: 64602
>>> Cc: Matt Roper <matthew.d.roper@intel.com>
>>> Fixes: 3adcf970dc7e ("drm/xe/bmg: Drop force_probe requirement")
>>> Cc: stable@vger.kernel.org
FYI, this does not cherry-pick cleanly to drm-intel-next-fixes, and
needs a backport.
There are dependencies on at least
4051c59e2a6a ("drm/i915/xe3lpd: Update bandwidth parameters")
9377c00cfdb5 ("drm/i915/display: Convert intel_bw.c internally to intel_display")
d706998b6da6 ("drm/i915/display: Convert intel_bw.c externally to intel_display")
but I don't think we want to backport those.
BR,
Jani.
>>> Signed-off-by: Vivek Kasireddy <vivek.kasireddy@intel.com>
>>> Signed-off-by: Lucas De Marchi <lucas.demarchi@intel.com>
>>
>>Reviewed-by: Matt Roper <matthew.d.roper@intel.com>
>
> Thanks. Patch pushed to drm-intel-next.
>
> Lucas De Marchi
--
Jani Nikula, Intel
next prev parent reply other threads:[~2025-03-25 9:03 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-03-24 17:22 [PATCH v2] drm/i915/xe2hpd: Identify the memory type for SKUs with GDDR + ECC Lucas De Marchi
2025-03-24 17:46 ` ✓ CI.Patch_applied: success for drm/i915/xe2hpd: Identify the memory type for SKUs with GDDR + ECC (rev3) Patchwork
2025-03-24 17:47 ` ✓ CI.checkpatch: " Patchwork
2025-03-24 17:48 ` ✓ CI.KUnit: " Patchwork
2025-03-24 18:04 ` ✓ CI.Build: " Patchwork
2025-03-24 18:07 ` ✓ CI.Hooks: " Patchwork
2025-03-24 18:08 ` ✓ CI.checksparse: " Patchwork
2025-03-24 18:15 ` ✗ Fi.CI.SPARSE: warning for drm/i915/xe2hpd: Identify the memory type for SKUs with GDDR + ECC (rev2) Patchwork
2025-03-24 18:30 ` ✓ Xe.CI.BAT: success for drm/i915/xe2hpd: Identify the memory type for SKUs with GDDR + ECC (rev3) Patchwork
2025-03-24 18:38 ` ✓ i915.CI.BAT: success for drm/i915/xe2hpd: Identify the memory type for SKUs with GDDR + ECC (rev2) Patchwork
2025-03-24 20:02 ` [PATCH v2] drm/i915/xe2hpd: Identify the memory type for SKUs with GDDR + ECC Matt Roper
2025-03-25 1:17 ` Lucas De Marchi
2025-03-25 9:03 ` Jani Nikula [this message]
2025-03-25 14:52 ` Lucas De Marchi
2025-04-09 12:42 ` Jani Nikula
2025-03-24 21:07 ` ✓ Xe.CI.Full: success for drm/i915/xe2hpd: Identify the memory type for SKUs with GDDR + ECC (rev3) Patchwork
2025-03-24 21:53 ` ✗ i915.CI.Full: failure for drm/i915/xe2hpd: Identify the memory type for SKUs with GDDR + ECC (rev2) 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=87bjtpa3e6.fsf@intel.com \
--to=jani.nikula@linux.intel.com \
--cc=intel-gfx@lists.freedesktop.org \
--cc=intel-xe@lists.freedesktop.org \
--cc=lucas.demarchi@intel.com \
--cc=matthew.d.roper@intel.com \
--cc=stable@vger.kernel.org \
--cc=vivek.kasireddy@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.