From: Jani Nikula <jani.nikula@linux.intel.com>
To: Ville Syrjala <ville.syrjala@linux.intel.com>,
intel-gfx@lists.freedesktop.org
Subject: Re: [Intel-gfx] [PATCH 1/2] drm/i915: Include stepping informaiton in device info dump
Date: Tue, 31 Jan 2023 09:12:29 +0200 [thread overview]
Message-ID: <87wn532n4y.fsf@intel.com> (raw)
In-Reply-To: <87zg9z2n6b.fsf@intel.com>
On Tue, 31 Jan 2023, Jani Nikula <jani.nikula@linux.intel.com> wrote:
> On Mon, 30 Jan 2023, Ville Syrjala <ville.syrjala@linux.intel.com> wrote:
>> From: Ville Syrjälä <ville.syrjala@linux.intel.com>
>>
>> Dump the stepping information alongside all the other device
>> info. Might avoid some guesswork when reading logs.
>>
>> Signed-off-by: Ville Syrjälä <ville.syrjala@linux.intel.com>
>
> Reviewed-by: Jani Nikula <jani.nikula@intel.com>
*information
in the subject line, can be fixed while applying.
>
>> ---
>> drivers/gpu/drm/i915/intel_device_info.c | 5 +++++
>> 1 file changed, 5 insertions(+)
>>
>> diff --git a/drivers/gpu/drm/i915/intel_device_info.c b/drivers/gpu/drm/i915/intel_device_info.c
>> index 98769e5f2c3d..599c6d399de4 100644
>> --- a/drivers/gpu/drm/i915/intel_device_info.c
>> +++ b/drivers/gpu/drm/i915/intel_device_info.c
>> @@ -119,6 +119,11 @@ void intel_device_info_print(const struct intel_device_info *info,
>> drm_printf(p, "display version: %u\n",
>> runtime->display.ip.ver);
>>
>> + drm_printf(p, "graphics stepping: %s\n", intel_step_name(runtime->step.graphics_step));
>> + drm_printf(p, "media stepping: %s\n", intel_step_name(runtime->step.media_step));
>> + drm_printf(p, "display stepping: %s\n", intel_step_name(runtime->step.display_step));
>> + drm_printf(p, "base die stepping: %s\n", intel_step_name(runtime->step.basedie_step));
>> +
>> drm_printf(p, "gt: %d\n", info->gt);
>> drm_printf(p, "memory-regions: %x\n", runtime->memory_regions);
>> drm_printf(p, "page-sizes: %x\n", runtime->page_sizes);
--
Jani Nikula, Intel Open Source Graphics Center
prev parent reply other threads:[~2023-01-31 7:12 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-01-30 18:17 [Intel-gfx] [PATCH 1/2] drm/i915: Include stepping informaiton in device info dump Ville Syrjala
2023-01-30 18:17 ` [Intel-gfx] [PATCH 2/2] drm/i915: Prefix hex numbers with 0x Ville Syrjala
2023-01-31 7:12 ` Jani Nikula
2023-01-30 21:04 ` [Intel-gfx] ✗ Fi.CI.BAT: failure for series starting with [1/2] drm/i915: Include stepping informaiton in device info dump Patchwork
2023-01-30 23:51 ` [Intel-gfx] ✓ Fi.CI.BAT: success for series starting with [1/2] drm/i915: Include stepping informaiton in device info dump (rev2) Patchwork
2023-01-31 5:54 ` [Intel-gfx] ✗ Fi.CI.IGT: failure " Patchwork
2023-01-31 7:11 ` [Intel-gfx] [PATCH 1/2] drm/i915: Include stepping informaiton in device info dump Jani Nikula
2023-01-31 7:12 ` Jani Nikula [this message]
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=87wn532n4y.fsf@intel.com \
--to=jani.nikula@linux.intel.com \
--cc=intel-gfx@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox