From: Suraj Kandpal <suraj.kandpal@intel.com>
To: intel-xe@lists.freedesktop.org, intel-gfx@lists.freedesktop.org
Cc: ankit.k.nautiyal@intel.com, arun.r.murthy@intel.com,
jani.nikula@intel.com, Suraj Kandpal <suraj.kandpal@intel.com>
Subject: [PATCH 0/2] drm/i915/backlight: Sanitize BIOS-enabled PCH PWM in full-AUX VESA path
Date: Thu, 14 May 2026 11:28:46 +0530 [thread overview]
Message-ID: <20260514055848.871938-1-suraj.kandpal@intel.com> (raw)
In full-AUX VESA mode (aux_enable && aux_set) the driver never touches the
native PCH PWM. If BIOS left the PWM CTL register enabled, the PCH PWM keeps
the system alive during s2idle and blocks S0ix. This series sanitizes that
stale BIOS state on first enable so S0ix is no longer blocked, while keeping
runtime behaviour otherwise unchanged.
Patch 1 is a minor debug-message rename cleanup.
Signed-off-by: Suraj Kandpal <suraj.kandpal@intel.com>
Suraj Kandpal (2):
drm/i915/backlight: Rename debug message in the setup() callback
drm/i915/backlight: Sanitize BIOS-enabled PCH PWM in full-AUX VESA
path
.../gpu/drm/i915/display/intel_backlight.c | 14 ++++----
.../drm/i915/display/intel_dp_aux_backlight.c | 32 +++++++++++++------
2 files changed, 30 insertions(+), 16 deletions(-)
--
2.34.1
next reply other threads:[~2026-05-14 5:58 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-05-14 5:58 Suraj Kandpal [this message]
2026-05-14 5:58 ` [PATCH 1/2] drm/i915/backlight: Rename debug message in the setup() callback Suraj Kandpal
2026-05-14 5:58 ` [PATCH 2/2] drm/i915/backlight: Sanitize BIOS-enabled PCH PWM in full-AUX VESA path Suraj Kandpal
2026-05-14 6:05 ` ✓ CI.KUnit: success for drm/i915/backlight: Sanitize BIOS-enabled PCH PWM in full-AUX VESA path (rev2) Patchwork
2026-05-14 7:06 ` ✓ Xe.CI.BAT: " Patchwork
2026-05-14 10:12 ` [PATCH 0/2] drm/i915/backlight: Sanitize BIOS-enabled PCH PWM in full-AUX VESA path Brandt, Todd E
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=20260514055848.871938-1-suraj.kandpal@intel.com \
--to=suraj.kandpal@intel.com \
--cc=ankit.k.nautiyal@intel.com \
--cc=arun.r.murthy@intel.com \
--cc=intel-gfx@lists.freedesktop.org \
--cc=intel-xe@lists.freedesktop.org \
--cc=jani.nikula@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