From: Mika Kahola <mika.kahola@intel.com>
To: intel-gfx@lists.freedesktop.org, intel-xe@lists.freedesktop.org
Cc: imre.deak@intel.com, Mika Kahola <mika.kahola@intel.com>
Subject: [PATCH 0/2] drm/i915/display: Allow display PHYs to reset power state
Date: Wed, 29 Jan 2025 15:01:03 +0200 [thread overview]
Message-ID: <20250129130105.198817-1-mika.kahola@intel.com> (raw)
The dedicated display PHYs reset to a power state that blocks S0ix,
increasing idle system power. After a system reset (cold boot,
S3/4/5, warm reset) if a dedicated PHY is not being brought up
shortly, use these steps to move the PHY to the lowest power state
to save power.
1. Follow the PLL Enable Sequence, using any valid frequency such as DP 1.62 GHz.
This brings lanes out of reset and enables the PLL to allow powerdown to be moved
to the Disable state.
2. Follow PLL Disable Sequence. This moves powerdown to the Disable state and disables the PLL.
Before doing this, let's refactor the pll enabling in such a way that
the crtc_state structure is no longer needed.
Mika Kahola (2):
drm/i915/display: Drop crtc_state from C10/C20 pll programming
drm/i915/display: Allow display PHYs to reset power state
drivers/gpu/drm/i915/display/intel_cx0_phy.c | 144 ++++++++++++------
drivers/gpu/drm/i915/display/intel_cx0_phy.h | 1 +
.../drm/i915/display/intel_display_reset.c | 2 +
drivers/gpu/drm/i915/display/intel_dpll_mgr.c | 2 +
4 files changed, 104 insertions(+), 45 deletions(-)
--
2.43.0
next reply other threads:[~2025-01-29 13:11 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-01-29 13:01 Mika Kahola [this message]
2025-01-29 13:01 ` [PATCH 1/2] drm/i915/display: Drop crtc_state from C10/C20 pll programming Mika Kahola
2025-01-29 14:40 ` Jani Nikula
2025-01-30 9:26 ` Kahola, Mika
2025-01-30 13:26 ` Imre Deak
2025-01-29 13:01 ` [PATCH 2/2] drm/i915/display: Allow display PHYs to reset power state Mika Kahola
2025-01-29 14:44 ` Jani Nikula
2025-01-30 9:52 ` Kahola, Mika
2025-01-29 14:46 ` ✓ CI.Patch_applied: success for " Patchwork
2025-01-29 14:47 ` ✗ CI.checkpatch: warning " Patchwork
2025-01-29 14:48 ` ✓ CI.KUnit: success " Patchwork
2025-01-29 15:05 ` ✓ CI.Build: " Patchwork
2025-01-29 15:07 ` ✗ CI.Hooks: failure " Patchwork
2025-01-29 15:08 ` ✓ CI.checksparse: success " Patchwork
2025-01-29 15:35 ` ✓ Xe.CI.BAT: " Patchwork
2025-01-29 23:00 ` ✗ Xe.CI.Full: 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=20250129130105.198817-1-mika.kahola@intel.com \
--to=mika.kahola@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox