From: Eugeni Dodonov <eugeni.dodonov@intel.com>
To: intel-gfx@lists.freedesktop.org
Cc: Eugeni Dodonov <eugeni.dodonov@intel.com>
Subject: [PATCH 00/29] Haswell round 3
Date: Fri, 13 Apr 2012 17:08:36 -0300 [thread overview]
Message-ID: <1334347745-11743-1-git-send-email-eugeni.dodonov@intel.com> (raw)
Hi forks,
Just in time for everyone's weekend, here comes the 3rd round of patches on
Haswell.
As major highlights, it also adds support for HDMI/DVI outputs and multi-head
modes (I tried with VGA and HDMI).
Other than that, it is the same patches with comments from the past round
addressed (SBI locking support, proper WM calculation, better PCH items
detection, and so on).
Daniel, I think that the bits definitions, power wells, clocks programming, and
modesetting for both FDI and HDMI modes should be good to go unless someone
spots additional issues with them - so please, all of you who have something to
say about them, say it now and bikeshed as you please :).
Note that the DP and eDP modesetting support is not there yet - it will still
require a considerable amount of patches.
Also, there is one patch which fixes null pointer exceptions in gmbus code I
was having with some of the drm-intel-next-queued iterations, but I don't think
it is necessary at the moment now that gmbus stuff was disabled again (patch
5). I am not even sure if we'll hit those code paths with invalid values in
real life, so I simple added some checks for cases when we don't have a valid
adapter as it was looking too error-prone otherwise. Perhaps we could add a
WARN into them as well.
Eugeni Dodonov (29):
drm/i915: add definition of LPT FDI port width registers
drm/i915: add WRPLL divider programming bits
drm/i915: add Haswell DIP controls registers
drm/i915: support infoframes on Haswell
drm/i915: prevent NULL pointer exception when using gmbus
drm/i915: add support for SBI ops
drm/i915: calculate same watermarks on Haswell as on Ivy Bridge
drm/i915: share forcewaking code between IVB and HSW
drm/i915: haswell has 3 pipes as well
drm/i915: reuse Ivybridge interrupts code for Haswell
drm/i915: share pipe count handling with Ivybridge
drm/i915: share IVB cursor routine with Haswell
drm/i915: show unknown sdvox registers on hdmi init
drm/i915: do not use fdi_normal_train on haswell
drm/i915: do not enable PCH PLL on pre-haswell
drm/i915: detect PCH encoders on Haswell
drm/i915: enable power wells on haswell init
drm/i915: disable rc6 on haswell for now
drm/i915: program WM_LINETIME on Haswell
drm/i915: do not use old code paths on Haswell
drm/i915: initialize DDI buffer translations
drm/i915: perform Haswell DDI link training in FDI mode
drm/i915: disable pipe DDI function when disabling pipe
drm/i915: program iCLKIP on Lynx Point
drm/i915: detect digital outputs on Haswell
drm/i915: add support for DDI-controlled digital outputs
drm/i915: add WR PLL programming table
drm/i915: prepare HDMI link for Haswell
drm/i915: hook Haswell devices in place
drivers/char/agp/intel-agp.c | 4 +
drivers/gpu/drm/i915/i915_dma.c | 2 +-
drivers/gpu/drm/i915/i915_drv.c | 7 +
drivers/gpu/drm/i915/i915_irq.c | 6 +-
drivers/gpu/drm/i915/i915_reg.h | 23 +
drivers/gpu/drm/i915/intel_display.c | 763 ++++++++++++++++++++++++++++++++--
drivers/gpu/drm/i915/intel_drv.h | 1 +
drivers/gpu/drm/i915/intel_hdmi.c | 602 ++++++++++++++++++++++++++-
8 files changed, 1357 insertions(+), 51 deletions(-)
--
1.7.10
next reply other threads:[~2012-04-13 20:08 UTC|newest]
Thread overview: 63+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-04-13 20:08 Eugeni Dodonov [this message]
2012-04-13 20:08 ` [PATCH 01/29] drm/i915: add definition of LPT FDI port width registers Eugeni Dodonov
2012-04-13 20:08 ` [PATCH 02/29] drm/i915: add WRPLL divider programming bits Eugeni Dodonov
2012-04-13 20:08 ` [PATCH 03/29] drm/i915: add Haswell DIP controls registers Eugeni Dodonov
2012-04-17 10:12 ` Daniel Vetter
2012-04-17 12:02 ` Eugeni Dodonov
2012-04-13 20:08 ` [PATCH 04/29] drm/i915: support infoframes on Haswell Eugeni Dodonov
2012-04-13 20:08 ` [PATCH 05/29] drm/i915: prevent NULL pointer exception when using gmbus Eugeni Dodonov
2012-04-13 20:18 ` Chris Wilson
2012-04-14 0:26 ` Eugeni Dodonov
2012-04-14 15:58 ` Daniel Vetter
2012-04-14 16:01 ` Chris Wilson
2012-04-13 20:08 ` [PATCH 06/29] drm/i915: add support for SBI ops Eugeni Dodonov
2012-04-13 20:26 ` Chris Wilson
2012-04-14 0:28 ` Eugeni Dodonov
2012-04-13 20:08 ` [PATCH 07/29] drm/i915: calculate same watermarks on Haswell as on Ivy Bridge Eugeni Dodonov
2012-04-13 20:27 ` Chris Wilson
2012-04-13 20:08 ` [PATCH 08/29] drm/i915: share forcewaking code between IVB and HSW Eugeni Dodonov
2012-04-13 20:08 ` [PATCH 09/29] drm/i915: haswell has 3 pipes as well Eugeni Dodonov
2012-04-13 20:08 ` [PATCH 10/29] drm/i915: reuse Ivybridge interrupts code for Haswell Eugeni Dodonov
2012-04-15 23:29 ` Daniel Vetter
2012-04-13 20:08 ` [PATCH 11/29] drm/i915: share pipe count handling with Ivybridge Eugeni Dodonov
2012-04-17 10:19 ` Daniel Vetter
2012-04-17 10:36 ` Chris Wilson
2012-04-17 11:26 ` Daniel Vetter
2012-04-17 11:38 ` Chris Wilson
2012-04-13 20:08 ` [PATCH 12/29] drm/i915: share IVB cursor routine with Haswell Eugeni Dodonov
2012-04-13 20:08 ` [PATCH 13/29] drm/i915: show unknown sdvox registers on hdmi init Eugeni Dodonov
2012-04-17 10:20 ` Daniel Vetter
2012-04-13 20:08 ` [PATCH 14/29] drm/i915: do not use fdi_normal_train on haswell Eugeni Dodonov
2012-04-13 20:08 ` [PATCH 15/29] drm/i915: do not enable PCH PLL on pre-haswell Eugeni Dodonov
2012-04-13 20:55 ` Chris Wilson
2012-04-14 0:31 ` Eugeni Dodonov
2012-04-15 23:52 ` Daniel Vetter
2012-04-13 20:08 ` [PATCH 16/29] drm/i915: detect PCH encoders on Haswell Eugeni Dodonov
2012-04-17 10:21 ` Daniel Vetter
2012-04-13 20:08 ` [PATCH 17/29] drm/i915: enable power wells on haswell init Eugeni Dodonov
2012-04-13 21:03 ` Chris Wilson
2012-04-14 1:26 ` Eugeni Dodonov
2012-04-13 20:08 ` [PATCH 18/29] drm/i915: disable rc6 on haswell for now Eugeni Dodonov
2012-04-13 20:08 ` [PATCH 19/29] drm/i915: program WM_LINETIME on Haswell Eugeni Dodonov
2012-04-13 20:08 ` [PATCH 20/29] drm/i915: do not use old code paths " Eugeni Dodonov
2012-04-13 20:08 ` [PATCH 21/29] drm/i915: initialize DDI buffer translations Eugeni Dodonov
2012-04-13 21:05 ` Chris Wilson
2012-04-13 21:11 ` Chris Wilson
2012-04-14 1:32 ` Eugeni Dodonov
2012-04-13 20:08 ` [PATCH 22/29] drm/i915: perform Haswell DDI link training in FDI mode Eugeni Dodonov
2012-04-13 20:08 ` [PATCH 23/29] drm/i915: disable pipe DDI function when disabling pipe Eugeni Dodonov
2012-04-13 20:09 ` [PATCH 24/29] drm/i915: program iCLKIP on Lynx Point Eugeni Dodonov
2012-04-15 23:49 ` Daniel Vetter
2012-04-16 0:44 ` Eugeni Dodonov
2012-04-16 8:26 ` Chris Wilson
2012-04-16 8:56 ` Daniel Vetter
2012-04-13 20:09 ` [PATCH 25/29] drm/i915: detect digital outputs on Haswell Eugeni Dodonov
2012-04-13 21:17 ` Chris Wilson
2012-04-14 0:37 ` Eugeni Dodonov
2012-04-15 23:36 ` Daniel Vetter
2012-04-13 20:09 ` [PATCH 26/29] drm/i915: add support for DDI-controlled digital outputs Eugeni Dodonov
2012-04-13 20:09 ` [PATCH 27/29] drm/i915: add WR PLL programming table Eugeni Dodonov
2012-04-13 20:09 ` [PATCH 28/29] drm/i915: prepare HDMI link for Haswell Eugeni Dodonov
2012-04-13 20:09 ` [PATCH 29/29] drm/i915: hook Haswell devices in place Eugeni Dodonov
2012-04-17 10:49 ` [PATCH 00/29] Haswell round 3 Daniel Vetter
2012-04-17 11:58 ` Eugeni Dodonov
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=1334347745-11743-1-git-send-email-eugeni.dodonov@intel.com \
--to=eugeni.dodonov@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.