From: Lucas De Marchi <lucas.demarchi@intel.com>
To: intel-xe@lists.freedesktop.org, intel-gfx@lists.freedesktop.org
Cc: Lucas De Marchi <lucas.demarchi@intel.com>,
Jani Nikula <jani.nikula@linux.intel.com>,
Matt Roper <matthew.d.roper@intel.com>
Subject: [PATCH 0/2] drm/i915: DRAM type logging
Date: Mon, 24 Mar 2025 19:28:40 -0700 [thread overview]
Message-ID: <20250324-dram-type-v1-0-bf60ef33ac01@intel.com> (raw)
Improve DRAM type logging across platforms.
Signed-off-by: Lucas De Marchi <lucas.demarchi@intel.com>
---
Lucas De Marchi (2):
drm/i915/dram: Add missing INTEL_DRAM str conversions
drm/i915/dram: Consolidate logging of DRAM type
drivers/gpu/drm/i915/i915_drv.h | 1 +
drivers/gpu/drm/i915/soc/intel_dram.c | 17 ++++++++++++-----
drivers/gpu/drm/xe/xe_device_types.h | 1 +
3 files changed, 14 insertions(+), 5 deletions(-)
base-commit: 9a42bdcde0f77b2c1e947e283cc3b267b1ce2056
change-id: 20250324-dram-type-e7c74461c670
Lucas De Marchi
next reply other threads:[~2025-03-25 2:29 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-03-25 2:28 Lucas De Marchi [this message]
2025-03-25 2:28 ` [PATCH 1/2] drm/i915/dram: Add missing INTEL_DRAM str conversions Lucas De Marchi
2025-03-28 22:25 ` Matt Roper
2025-03-25 2:28 ` [PATCH 2/2] drm/i915/dram: Consolidate logging of DRAM type Lucas De Marchi
2025-03-28 22:29 ` Matt Roper
2025-03-25 2:34 ` ✓ CI.Patch_applied: success for drm/i915: DRAM type logging Patchwork
2025-03-25 2:34 ` ✓ CI.checkpatch: " Patchwork
2025-03-25 2:36 ` ✓ CI.KUnit: " Patchwork
2025-03-25 2:52 ` ✓ CI.Build: " Patchwork
2025-03-25 2:54 ` ✓ CI.Hooks: " Patchwork
2025-03-25 2:56 ` ✗ CI.checksparse: warning " Patchwork
2025-03-25 3:16 ` ✓ Xe.CI.BAT: success " Patchwork
2025-03-31 15:18 ` [PATCH 0/2] " Lucas De Marchi
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=20250324-dram-type-v1-0-bf60ef33ac01@intel.com \
--to=lucas.demarchi@intel.com \
--cc=intel-gfx@lists.freedesktop.org \
--cc=intel-xe@lists.freedesktop.org \
--cc=jani.nikula@linux.intel.com \
--cc=matthew.d.roper@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox