Intel-XE Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Gustavo Sousa <gustavo.sousa@intel.com>
To: Luca Coelho <luca@coelho.fi>, <intel-gfx@lists.freedesktop.org>,
	<intel-xe@lists.freedesktop.org>
Cc: Luca Coelho <luciano.coelho@intel.com>
Subject: Re: [PATCH] drm/i915/dmc_wl: Track INITIATE_PM_DMD_REQ for DC5
Date: Tue, 4 Feb 2025 09:50:41 -0300	[thread overview]
Message-ID: <173867344150.1635.2419403316434821729@intel.com> (raw)
In-Reply-To: <1b46838458692079e07251286f0b6ff388e2070d.camel@coelho.fi>

Quoting Luca Coelho (2025-02-04 05:46:38-03:00)
>On Mon, 2025-02-03 at 17:58 -0300, Gustavo Sousa wrote:
>> The Bspec has been updated to include INITIATE_PM_DMD_REQ in the set of
>> register offsets that require the DMC wakelock for access during DC5.
>> Update our table accordingly.
>> 
>> Bspec: 71583
>> Signed-off-by: Gustavo Sousa <gustavo.sousa@intel.com>
>> ---
>>  drivers/gpu/drm/i915/display/intel_dmc_wl.c | 1 +
>>  1 file changed, 1 insertion(+)
>> 
>> diff --git a/drivers/gpu/drm/i915/display/intel_dmc_wl.c b/drivers/gpu/drm/i915/display/intel_dmc_wl.c
>> index 43884740f8ea..86ba159b683c 100644
>> --- a/drivers/gpu/drm/i915/display/intel_dmc_wl.c
>> +++ b/drivers/gpu/drm/i915/display/intel_dmc_wl.c
>> @@ -102,6 +102,7 @@ static const struct intel_dmc_wl_range xe3lpd_dc5_dc6_dmc_ranges[] = {
>>          { .start = 0x42088 }, /* CHICKEN_MISC_3 */
>>          { .start = 0x46160 }, /* CMTG_CLK_SEL */
>>          { .start = 0x8f000, .end = 0x8ffff }, /* Main DMC registers */
>> +        { .start = 0x45230 }, /* INITIATE_PM_DMD_REQ */
>>  
>>          {},
>>  };
>
>Matches the bspec.
>
>Reviewed-by: Luca Coelho <luciano.coelho@intel.com>

Thanks for the review! Pushed to drm-intel-next.

--
Gustavo Sousa

      reply	other threads:[~2025-02-04 12:50 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-02-03 20:58 [PATCH] drm/i915/dmc_wl: Track INITIATE_PM_DMD_REQ for DC5 Gustavo Sousa
2025-02-03 21:25 ` ✓ CI.Patch_applied: success for " Patchwork
2025-02-03 21:26 ` ✓ CI.checkpatch: " Patchwork
2025-02-03 21:27 ` ✓ CI.KUnit: " Patchwork
2025-02-03 21:43 ` ✓ CI.Build: " Patchwork
2025-02-03 21:45 ` ✓ CI.Hooks: " Patchwork
2025-02-03 21:47 ` ✓ CI.checksparse: " Patchwork
2025-02-03 22:06 ` ✓ Xe.CI.BAT: " Patchwork
2025-02-04  0:22 ` ✗ Xe.CI.Full: failure " Patchwork
2025-02-04 11:38   ` Gustavo Sousa
2025-02-04  8:46 ` [PATCH] " Luca Coelho
2025-02-04 12:50   ` Gustavo Sousa [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=173867344150.1635.2419403316434821729@intel.com \
    --to=gustavo.sousa@intel.com \
    --cc=intel-gfx@lists.freedesktop.org \
    --cc=intel-xe@lists.freedesktop.org \
    --cc=luca@coelho.fi \
    --cc=luciano.coelho@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