Intel-XE Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Gustavo Sousa <gustavo.sousa@intel.com>
To: Kai Vehmanen <kai.vehmanen@linux.intel.com>
Cc: <intel-gfx@lists.freedesktop.org>,
	<intel-xe@lists.freedesktop.org>,
	"Kai Vehmanen" <kai.vehmanen@linux.intel.com>
Subject: Re: [PATCH] drm/i915/xe3lpd: Map POWER_DOMAIN_AUDIO_PLAYBACK to DC_off
Date: Mon, 10 Mar 2025 12:43:27 -0300	[thread overview]
Message-ID: <174162140709.3769.4631804581155473882@intel.com> (raw)
In-Reply-To: <alpine.DEB.2.22.394.2502281138120.14041@eliteleevi.tm.intel.com>

Quoting Kai Vehmanen (2025-02-28 06:40:51-03:00)
>Hi,
>
>On Thu, 27 Feb 2025, Gustavo Sousa wrote:
>
>> In Xe3_LPD, display audio has the core audio logic located in PG0 and
>> per-transcoder logic in the same power well that provides power for the
>> transcoder [1].
>[...]
>> Since intel_audio_component_get_power() uses
>> POWER_DOMAIN_AUDIO_PLAYBACK, make sure to map that power domain to
>> DC_off power well, so that we disable dynamic DC states (which includes
>> DC6) while the audio driver needs display audio power.
>[...]
>> +++ b/drivers/gpu/drm/i915/display/intel_display_power_map.c
>> @@ -1694,6 +1694,7 @@ I915_DECL_PW_DOMAINS(xe3lpd_pwdoms_dc_off,
>>          XE3LPD_PW_C_POWER_DOMAINS,
>>          XE3LPD_PW_D_POWER_DOMAINS,
>>          POWER_DOMAIN_AUDIO_MMIO,
>> +        POWER_DOMAIN_AUDIO_PLAYBACK,
>>          POWER_DOMAIN_INIT);
>
>ack, this looks good and covers audio expectations for 
>drm_audio_component.h usage:
>
>Reviewed-by: Kai Vehmanen <kai.vehmanen@linux.intel.com>

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

--
Gustavo Sousa

  reply	other threads:[~2025-03-10 15:44 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-02-27 19:14 [PATCH] drm/i915/xe3lpd: Map POWER_DOMAIN_AUDIO_PLAYBACK to DC_off Gustavo Sousa
2025-02-27 20:10 ` ✓ CI.Patch_applied: success for " Patchwork
2025-02-27 20:10 ` ✓ CI.checkpatch: " Patchwork
2025-02-27 20:12 ` ✓ CI.KUnit: " Patchwork
2025-02-27 20:31 ` ✓ CI.Build: " Patchwork
2025-02-27 20:34 ` ✓ CI.Hooks: " Patchwork
2025-02-27 20:35 ` ✓ CI.checksparse: " Patchwork
2025-02-27 20:53 ` ✓ Xe.CI.BAT: " Patchwork
2025-02-28  0:29 ` ✗ Xe.CI.Full: failure " Patchwork
2025-02-28  9:40 ` [PATCH] " Kai Vehmanen
2025-03-10 15:43   ` Gustavo Sousa [this message]
2025-03-05 22:50 ` ✓ CI.Patch_applied: success for drm/i915/xe3lpd: Map POWER_DOMAIN_AUDIO_PLAYBACK to DC_off (rev2) Patchwork
2025-03-05 22:51 ` ✓ CI.checkpatch: " Patchwork
2025-03-05 22:52 ` ✓ CI.KUnit: " Patchwork
2025-03-05 23:08 ` ✓ CI.Build: " Patchwork
2025-03-05 23:11 ` ✓ CI.Hooks: " Patchwork
2025-03-05 23:12 ` ✓ CI.checksparse: " Patchwork
2025-03-05 23:32 ` ✓ Xe.CI.BAT: " Patchwork
2025-03-06  3:50 ` ✗ Xe.CI.Full: failure " Patchwork
2025-03-10 13:29   ` Gustavo Sousa

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=174162140709.3769.4631804581155473882@intel.com \
    --to=gustavo.sousa@intel.com \
    --cc=intel-gfx@lists.freedesktop.org \
    --cc=intel-xe@lists.freedesktop.org \
    --cc=kai.vehmanen@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