From: "Ville Syrjälä" <ville.syrjala@linux.intel.com>
To: Jani Nikula <jani.nikula@intel.com>
Cc: intel-gfx@lists.freedesktop.org, intel-xe@lists.freedesktop.org
Subject: Re: [PATCH v2 5/5] drm/i915: use graphics version instead of PCH split in error capture
Date: Fri, 11 Apr 2025 16:39:10 +0300 [thread overview]
Message-ID: <Z_kbfnZ1yKrbmKkO@intel.com> (raw)
In-Reply-To: <786195f92466317f521404be744629b0a077c491.1744208554.git.jani.nikula@intel.com>
On Wed, Apr 09, 2025 at 05:23:47PM +0300, Jani Nikula wrote:
> Avoid using PCH checks in core i915 code, in preparation for moving PCH
> handling to display.
>
> Signed-off-by: Jani Nikula <jani.nikula@intel.com>
> ---
> drivers/gpu/drm/i915/i915_gpu_error.c | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/drivers/gpu/drm/i915/i915_gpu_error.c b/drivers/gpu/drm/i915/i915_gpu_error.c
> index 62e4a293ed9b..aa2cad910902 100644
> --- a/drivers/gpu/drm/i915/i915_gpu_error.c
> +++ b/drivers/gpu/drm/i915/i915_gpu_error.c
> @@ -1792,7 +1792,7 @@ static void gt_record_global_nonguc_regs(struct intel_gt_coredump *gt)
> gt->gtier[i] =
> intel_uncore_read(uncore, GEN8_GT_IER(i));
> gt->ngtier = 4;
> - } else if (HAS_PCH_SPLIT(i915)) {
> + } else if (GRAPHICS_VER(i915) >= 5) {
This would now cover VLV correctly as well, so you could drop the
vlv special case at the top of the if ladder completely.
Either way
Reviewed-by: Ville Syrjälä <ville.syrjala@linux.intel.com>
> gt->gtier[0] = intel_uncore_read(uncore, GTIER);
> gt->ngtier = 1;
> } else {
> --
> 2.39.5
--
Ville Syrjälä
Intel
next prev parent reply other threads:[~2025-04-11 13:39 UTC|newest]
Thread overview: 35+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-04-09 14:23 [PATCH v2 0/5] drm/i915: error capture cleanups and refactor Jani Nikula
2025-04-09 14:23 ` [PATCH v2 1/5] drm/i915: use 32-bit access for gen2 irq registers Jani Nikula
2025-04-10 16:13 ` Ville Syrjälä
2025-04-09 14:23 ` [PATCH v2 2/5] drm/i915: record GEN2_IER in gtier[0] for pre-ilk error capture Jani Nikula
2025-04-10 16:15 ` Ville Syrjälä
2025-04-09 14:23 ` [PATCH v2 3/5] drm/i915: stop recording IER in " Jani Nikula
2025-04-10 16:16 ` Ville Syrjälä
2025-04-09 14:23 ` [PATCH v2 4/5] drm/i915: use display snapshot mechanism for display irq regs Jani Nikula
2025-04-10 16:26 ` Ville Syrjälä
2025-04-11 7:09 ` [PATCH v3] " Jani Nikula
2025-04-09 14:23 ` [PATCH v2 5/5] drm/i915: use graphics version instead of PCH split in error capture Jani Nikula
2025-04-11 9:45 ` Jani Nikula
2025-04-11 13:39 ` Ville Syrjälä [this message]
2025-04-09 14:39 ` ✓ CI.Patch_applied: success for drm/i915: error capture cleanups and refactor Patchwork
2025-04-09 14:40 ` ✗ CI.checkpatch: warning " Patchwork
2025-04-09 14:41 ` ✓ CI.KUnit: success " Patchwork
2025-04-09 14:57 ` ✗ CI.Build: failure " Patchwork
2025-04-10 8:20 ` ✓ CI.Patch_applied: success " Patchwork
2025-04-10 8:20 ` ✗ CI.checkpatch: warning " Patchwork
2025-04-10 8:21 ` ✓ CI.KUnit: success " Patchwork
2025-04-10 8:30 ` ✓ CI.Build: " Patchwork
2025-04-10 8:32 ` ✓ CI.Hooks: " Patchwork
2025-04-10 8:34 ` ✗ CI.checksparse: warning " Patchwork
2025-04-10 8:53 ` ✓ Xe.CI.BAT: success " Patchwork
2025-04-10 10:57 ` ✗ Xe.CI.Full: failure " Patchwork
2025-04-11 7:08 ` [PATCH] drm/i915: don't capture DERRMR for VLV/CHV Jani Nikula
2025-04-11 7:15 ` Ville Syrjälä
2025-04-11 7:15 ` ✓ CI.Patch_applied: success for drm/i915: don't capture DERRMR for VLV/CHV (rev2) Patchwork
2025-04-11 7:15 ` ✗ CI.checkpatch: warning " Patchwork
2025-04-11 7:16 ` ✓ CI.KUnit: success " Patchwork
2025-04-11 7:24 ` ✓ CI.Build: " Patchwork
2025-04-11 7:27 ` ✓ CI.Hooks: " Patchwork
2025-04-11 7:28 ` ✗ CI.checksparse: warning " Patchwork
2025-04-11 7:47 ` ✓ Xe.CI.BAT: success " Patchwork
2025-04-11 9:47 ` ✗ Xe.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=Z_kbfnZ1yKrbmKkO@intel.com \
--to=ville.syrjala@linux.intel.com \
--cc=intel-gfx@lists.freedesktop.org \
--cc=intel-xe@lists.freedesktop.org \
--cc=jani.nikula@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;
as well as URLs for NNTP newsgroup(s).