From: Matt Roper <matthew.d.roper@intel.com>
To: intel-gfx@lists.freedesktop.org
Subject: [Intel-gfx] [PATCH 0/3] AUX power well fixes
Date: Thu, 12 Dec 2019 14:37:32 -0800 [thread overview]
Message-ID: <20191212223735.666014-1-matthew.d.roper@intel.com> (raw)
A few fixes related to AUX power wells for various platforms:
* EHL shouldn't use TC power well handling on C/D since all of its
outputs are combo.
* TGL shouldn't be applying Display WA #1178; doing so causes failures
to enable power wells in some cases.
There's some ambiguity as to whether WA#1178 is even still relevant to
ICL or not; we're checking with the hardware architects on that, but
this series leaves it in place for ICL for now.
Matt Roper (3):
drm/i915/ehl: Define EHL powerwells independently of ICL
drm/i915/tgl: Drop Wa#1178
drm/i915/icl: Cleanup combo PHY aux power well handlers
.../drm/i915/display/intel_display_power.c | 193 +++++++++++++++---
1 file changed, 166 insertions(+), 27 deletions(-)
--
2.23.0
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/intel-gfx
next reply other threads:[~2019-12-12 22:37 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-12-12 22:37 Matt Roper [this message]
2019-12-12 22:37 ` [Intel-gfx] [PATCH 1/3] drm/i915/ehl: Define EHL powerwells independently of ICL Matt Roper
2019-12-12 22:37 ` [Intel-gfx] [PATCH 2/3] drm/i915/tgl: Drop Wa#1178 Matt Roper
2019-12-12 23:52 ` Lucas De Marchi
2019-12-12 22:37 ` [Intel-gfx] [PATCH 3/3] drm/i915/icl: Cleanup combo PHY aux power well handlers Matt Roper
2019-12-12 23:04 ` Lucas De Marchi
2019-12-12 23:51 ` [Intel-gfx] [PATCH v2 " Matt Roper
2019-12-12 23:56 ` Lucas De Marchi
2019-12-13 0:03 ` Matt Roper
2019-12-19 0:43 ` [Intel-gfx] [PATCH " kbuild test robot
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=20191212223735.666014-1-matthew.d.roper@intel.com \
--to=matthew.d.roper@intel.com \
--cc=intel-gfx@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.