From: Jani Nikula <jani.nikula@intel.com>
To: imre.deak@intel.com
Cc: intel-gfx@lists.freedesktop.org, intel-xe@lists.freedesktop.org
Subject: Re: [PATCH v2 4/6] drm/i915/display: convert power domain code internally to struct intel_display
Date: Fri, 29 Nov 2024 16:46:47 +0200 [thread overview]
Message-ID: <877c8m6qso.fsf@intel.com> (raw)
In-Reply-To: <Z0nNBKLObDJbnQdt@ideak-desk.fi.intel.com>
On Fri, 29 Nov 2024, Imre Deak <imre.deak@intel.com> wrote:
> On Thu, Nov 28, 2024 at 05:38:22PM +0200, Jani Nikula wrote:
>> Going forward, struct intel_display is the main device data structure
>> for display. Convert intel_display_power.c internally first, leaving
>> external interfaces for follow-up.
>>
>> v2: Rebase, checkpatch fixes
>>
>> Cc: Imre Deak <imre.deak@intel.com>
>> Signed-off-by: Jani Nikula <jani.nikula@intel.com>
>> ---
>> .../drm/i915/display/intel_display_power.c | 806 +++++++++---------
>> 1 file changed, 414 insertions(+), 392 deletions(-)
>>
>> diff --git a/drivers/gpu/drm/i915/display/intel_display_power.c b/drivers/gpu/drm/i915/display/intel_display_power.c
>> index ade7192c0461..4043d6971c3e 100644
>> --- a/drivers/gpu/drm/i915/display/intel_display_power.c
>> +++ b/drivers/gpu/drm/i915/display/intel_display_power.c
>>
>> [...]
>>
>> -static void hsw_disable_pc8(struct drm_i915_private *dev_priv)
>> +static void hsw_disable_pc8(struct intel_display *display)
>> {
>> - drm_dbg_kms(&dev_priv->drm, "Disabling package C8+\n");
>> + struct drm_i915_private *dev_priv = to_i915(display->drm);
>> +
>> + drm_dbg_kms(display->drm, "Disabling package C8+\n");
>>
>> - hsw_restore_lcpll(dev_priv);
>> + hsw_restore_lcpll(display);
>> intel_init_pch_refclk(dev_priv);
>>
>> /* Many display registers don't survive PC8+ */
>> +#ifdef I915 /* FIXME */
>> intel_clock_gating_init(dev_priv);
>> +#endif
>
> So before the call of hsw_disable_pc8() was optimized out, but now it's
> not. For now ok, but imo this could've been in a separate patch.
Yeah, stuck it in to fix the build, but forgot about it.
>
>> }
>>
--
Jani Nikula, Intel
next prev parent reply other threads:[~2024-11-29 14:46 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-11-28 15:38 [PATCH v2 0/6] drm/i915/display: power conversion to struct intel_display Jani Nikula
2024-11-28 15:38 ` [PATCH v2 1/6] drm/i915/display: convert for_each_power_well() " Jani Nikula
2024-11-28 15:38 ` [PATCH v2 2/6] drm/i915/display: convert for_each_power_domain_well() " Jani Nikula
2024-11-28 15:38 ` [PATCH v2 3/6] drm/i915/display: convert power wells " Jani Nikula
2024-11-28 15:38 ` [PATCH v2 4/6] drm/i915/display: convert power domain code internally " Jani Nikula
2024-11-29 14:17 ` Imre Deak
2024-11-29 14:46 ` Jani Nikula [this message]
2024-11-28 15:38 ` [PATCH v2 5/6] drm/i915/display: convert high level power interfaces " Jani Nikula
2024-11-28 15:38 ` [PATCH v2 6/6] drm/i915/display: convert power map " Jani Nikula
2024-11-28 16:39 ` ✓ CI.Patch_applied: success for drm/i915/display: power conversion to struct intel_display (rev2) Patchwork
2024-11-28 16:39 ` ✗ CI.checkpatch: warning " Patchwork
2024-11-28 16:40 ` ✓ CI.KUnit: success " Patchwork
2024-11-28 16:58 ` ✓ CI.Build: " Patchwork
2024-11-28 17:00 ` ✓ CI.Hooks: " Patchwork
2024-11-28 17:02 ` ✗ CI.checksparse: warning " Patchwork
2024-11-28 17:20 ` ✓ Xe.CI.BAT: success " Patchwork
2024-11-28 18:13 ` ✗ Fi.CI.CHECKPATCH: warning " Patchwork
2024-11-28 18:13 ` ✗ Fi.CI.SPARSE: " Patchwork
2024-11-28 18:22 ` ✗ i915.CI.BAT: failure " Patchwork
2024-11-29 8:19 ` Jani Nikula
2024-11-29 16:08 ` Illipilli, TejasreeX
2024-11-29 1:40 ` ✗ Xe.CI.Full: " Patchwork
2024-11-29 14:00 ` ✓ i915.CI.BAT: success " Patchwork
2024-11-29 14:18 ` [PATCH v2 0/6] drm/i915/display: power conversion to struct intel_display Imre Deak
2024-11-29 19:12 ` ✗ i915.CI.Full: failure for drm/i915/display: power conversion to struct intel_display (rev2) 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=877c8m6qso.fsf@intel.com \
--to=jani.nikula@intel.com \
--cc=imre.deak@intel.com \
--cc=intel-gfx@lists.freedesktop.org \
--cc=intel-xe@lists.freedesktop.org \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.