From: Jani Nikula <jani.nikula@linux.intel.com>
To: "Ville Syrjälä" <ville.syrjala@linux.intel.com>
Cc: intel-gfx@lists.freedesktop.org, intel-xe@lists.freedesktop.org
Subject: Re: [PATCH 5/8] drm/i915/dram: Move 16Gb DIMM detection fully to the skl/icl codepaths
Date: Tue, 02 Sep 2025 17:21:34 +0300 [thread overview]
Message-ID: <b7de8deb14a992b486a0a8060d66295bc008e9a3@intel.com> (raw)
In-Reply-To: <aLb8z_qvltv07_wp@intel.com>
On Tue, 02 Sep 2025, Ville Syrjälä <ville.syrjala@linux.intel.com> wrote:
> Currently we don't seem to allocate dram_info at all for dg2. So we
> need some protection there to avoid oopsing. But I think I'll be
> changing that to explictily check for the skl/icl platforms instead
> since those are the only ones that need the w/a.
Right, forgot about that!
BR,
Jani.
--
Jani Nikula, Intel
next prev parent reply other threads:[~2025-09-02 14:21 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-09-02 13:31 [PATCH 0/8] drm/i915/dram: DRAM detection stuff Ville Syrjala
2025-09-02 13:31 ` [PATCH 1/8] drm/i915/dram: Populate PNV memory type accurately Ville Syrjala
2025-09-02 13:45 ` Jani Nikula
2025-09-02 13:31 ` [PATCH 2/8] drm/i915/dram: Use intel_dram_type_str() for pnv Ville Syrjala
2025-09-02 13:46 ` Jani Nikula
2025-09-02 13:31 ` [PATCH 3/8] drm/i915/dram: Pack dram_info better Ville Syrjala
2025-09-02 13:46 ` Jani Nikula
2025-09-02 13:31 ` [PATCH 4/8] drm/i915/dram: s/wm_lv0.../has_16gb_dimms/ Ville Syrjala
2025-09-05 9:56 ` Jani Nikula
2025-09-02 13:31 ` [PATCH 5/8] drm/i915/dram: Move 16Gb DIMM detection fully to the skl/icl codepaths Ville Syrjala
2025-09-02 13:56 ` Jani Nikula
2025-09-02 14:18 ` Ville Syrjälä
2025-09-02 14:21 ` Jani Nikula [this message]
2025-09-02 13:31 ` [PATCH 6/8] drm/i915/dram: Fix some spelling aroynd the 16Gb DIMM w/a Ville Syrjala
2025-09-02 13:58 ` Jani Nikula
2025-09-02 14:03 ` Jani Nikula
2025-09-02 13:31 ` [PATCH 7/8] drm/i915/dram: Don't call skl_get_dram_info()/skl_get_dram_type() on icl Ville Syrjala
2025-09-02 14:02 ` Jani Nikula
2025-09-02 13:31 ` [PATCH 8/8] drm/i915/dram: Print memory details even if something went wrong Ville Syrjala
2025-09-02 14:03 ` Jani Nikula
2025-09-02 16:02 ` ✓ CI.KUnit: success for drm/i915/dram: DRAM detection stuff Patchwork
2025-09-02 16:18 ` ✗ CI.checksparse: warning " Patchwork
2025-09-02 16:38 ` ✓ Xe.CI.BAT: success " Patchwork
2025-09-02 17:15 ` ✓ i915.CI.BAT: " Patchwork
2025-09-02 22:06 ` ✓ Xe.CI.Full: " Patchwork
2025-09-03 1:34 ` ✗ i915.CI.Full: failure " 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=b7de8deb14a992b486a0a8060d66295bc008e9a3@intel.com \
--to=jani.nikula@linux.intel.com \
--cc=intel-gfx@lists.freedesktop.org \
--cc=intel-xe@lists.freedesktop.org \
--cc=ville.syrjala@linux.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.