From: "Nilawar, Badal" <badal.nilawar@intel.com>
To: Rodrigo Vivi <rodrigo.vivi@intel.com>
Cc: intel-gfx@lists.freedesktop.org, dri-devel@lists.freedesktop.org
Subject: Re: [Intel-gfx] [PATCH 1/1] drm/i915/mtl: Enable Idle Messaging for GSC CS
Date: Thu, 17 Nov 2022 12:15:20 +0530 [thread overview]
Message-ID: <ec84875d-b1b0-407c-dd71-c7b628095fa7@intel.com> (raw)
In-Reply-To: <Y3Ov2jrHAqnIDGUs@intel.com>
Hi Rodrigo,
On 15-11-2022 20:57, Rodrigo Vivi wrote:
> On Tue, Nov 15, 2022 at 07:14:40PM +0530, Badal Nilawar wrote:
>> From: Vinay Belgaumkar <vinay.belgaumkar@intel.com>
>>
>> By defaut idle mesaging is disabled for GSC CS so to unblock RC6
>> entry on media tile idle messaging need to be enabled.
>>
>> v2:
>> - Fix review comments (Vinay)
>> - Set GSC idle hysterisis to 5 us (Badal)
>
> btw, no need for the cover letter in single/standalone patches.
> This history here is enough.
Sure, next revision I will take care of this.
>
>>
>> Bspec: 71496
>>
>> Cc: Daniele Ceraolo Spurio <daniele.ceraolospurio@intel.com>
>> Signed-off-by: Vinay Belgaumkar <vinay.belgaumkar@intel.com>
>> Signed-off-by: Badal Nilawar <badal.nilawar@intel.com>
>> ---
>> drivers/gpu/drm/i915/gt/intel_engine_pm.c | 18 ++++++++++++++++++
>> drivers/gpu/drm/i915/gt/intel_gt_regs.h | 4 ++++
>> 2 files changed, 22 insertions(+)
>>
>> diff --git a/drivers/gpu/drm/i915/gt/intel_engine_pm.c b/drivers/gpu/drm/i915/gt/intel_engine_pm.c
>> index b0a4a2dbe3ee..5522885b2db0 100644
>> --- a/drivers/gpu/drm/i915/gt/intel_engine_pm.c
>> +++ b/drivers/gpu/drm/i915/gt/intel_engine_pm.c
>> @@ -15,6 +15,22 @@
>> #include "intel_rc6.h"
>> #include "intel_ring.h"
>> #include "shmem_utils.h"
>> +#include "intel_gt_regs.h"
>> +
>> +static void intel_gsc_idle_msg_enable(struct intel_engine_cs *engine)
>> +{
>> + struct drm_i915_private *i915 = engine->i915;
>> +
>> + if (IS_METEORLAKE(i915) && engine->id == GSC0) {
>> + intel_uncore_write(engine->gt->uncore,
>> + RC_PSMI_CTRL_GSCCS,
>> + _MASKED_BIT_DISABLE(IDLE_MSG_DISABLE));
>> + /* 5 us hysterisis */
>
> typo
>
>> + intel_uncore_write(engine->gt->uncore,
>> + PWRCTX_MAXCNT_GSCCS,
>> + 0xA);
>
> you said 5 above, but used 10 here, why?
Bspec:71496 specifies 0xA = 5us.
>
>> + }
>> +}
>>
>> static void dbg_poison_ce(struct intel_context *ce)
>> {
>> @@ -275,6 +291,8 @@ void intel_engine_init__pm(struct intel_engine_cs *engine)
>>
>> intel_wakeref_init(&engine->wakeref, rpm, &wf_ops);
>> intel_engine_init_heartbeat(engine);
>> +
>> + intel_gsc_idle_msg_enable(engine);
>> }
>>
>> /**
>> diff --git a/drivers/gpu/drm/i915/gt/intel_gt_regs.h b/drivers/gpu/drm/i915/gt/intel_gt_regs.h
>> index 07031e03f80c..20472eb15364 100644
>> --- a/drivers/gpu/drm/i915/gt/intel_gt_regs.h
>> +++ b/drivers/gpu/drm/i915/gt/intel_gt_regs.h
>> @@ -913,6 +913,10 @@
>> #define MSG_IDLE_FW_MASK REG_GENMASK(13, 9)
>> #define MSG_IDLE_FW_SHIFT 9
>>
>> +#define RC_PSMI_CTRL_GSCCS _MMIO(0x11a050)
>> +#define IDLE_MSG_DISABLE BIT(0)
>
> REG_BIT should be preferred.
I will take care of this and above comments in next revision.
Regards,
Badal
>
>> +#define PWRCTX_MAXCNT_GSCCS _MMIO(0x11a054)
>> +
>> #define FORCEWAKE_MEDIA_GEN9 _MMIO(0xa270)
>> #define FORCEWAKE_RENDER_GEN9 _MMIO(0xa278)
>>
>> --
>> 2.25.1
>>
next prev parent reply other threads:[~2022-11-17 6:45 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-15 13:44 [Intel-gfx] [PATCH 0/1] i915/mtl: Enable idle messaging for GSC CS Badal Nilawar
2022-11-15 13:44 ` [Intel-gfx] [PATCH 1/1] drm/i915/mtl: Enable Idle Messaging " Badal Nilawar
2022-11-15 15:27 ` Rodrigo Vivi
2022-11-17 6:45 ` Nilawar, Badal [this message]
2022-11-16 18:05 ` Belgaumkar, Vinay
2022-11-17 22:14 ` Rodrigo Vivi
2022-11-18 4:05 ` Nilawar, Badal
2022-11-18 14:32 ` Rodrigo Vivi
2022-11-18 14:43 ` Rodrigo Vivi
2022-11-15 23:13 ` [Intel-gfx] ✓ Fi.CI.BAT: success for i915/mtl: Enable idle messaging for GSC CS (rev2) Patchwork
2022-11-16 6:50 ` [Intel-gfx] ✗ Fi.CI.IGT: 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=ec84875d-b1b0-407c-dd71-c7b628095fa7@intel.com \
--to=badal.nilawar@intel.com \
--cc=dri-devel@lists.freedesktop.org \
--cc=intel-gfx@lists.freedesktop.org \
--cc=rodrigo.vivi@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