Re: Updated -next

Re: Updated -next

[Daniel Vetter]

Hi Dave,

QA beat on the -next tree in my absence and filed 3 new issue. Afaict
they're all new sightings of old issues (hooray for improved test-suites)
safe for a very funky sporadic failure on ilk - investigation is still
going on this one.

Otherwise the missed irq on snb poped up again, but Ben confirmed that the
full ivb voodoo works. You likely get a one-liner to enable that on snb,
too. And imo the swizzling regression has been fixed as well as possible
given the ugly situation - the patch to fix lying kernels prior to 3.2 is
submitted to stable (needed for correctness with updated mesa git/8.0)
and the mesa patch to correctly detile the stencil buffer is on track to
get into the next 8.0 release (the only affected mesa release branch).

Highlights of this pull request:
- gmbus fixes and reenabling gmbus by default (one-liner to switch back).
  Note that this also contains a i2c core change and a i2c patch for
  nouveau.
- random smaller fixes and some quirks
- the finish_gpu patch, despite the lack of a clear testcase and and
  obviously correct theory how exactly this fixes anything. But this does
  paper too well over various issues (among them the hibernate desaster,
  at least to some extent), so I've grumpily included it.
i.e. winding down for 3.4.

PSA to everyone else: I expect the next -next to go into 3.5 already, so
if I've picked up patches that you think should go into 3.4, please annoy
Keith about them.

As usual, qa report below the pull request.

Cheers, Daniel

The following changes since commit ff5f4b0585620e5c158ecaad84d91c5bf3c5d0a1:

  Merge remote-tracking branch 'airlied/drm-next' into for-airlied (2012-02-23 14:56:11 +0100)

are available in the git repository at:


  git://people.freedesktop.org/~danvet/drm-intel tags/drm-intel-next-2012-03-01

for you to fetch changes up to c501ae7f332cdaf42e31af30b72b4b66cbbb1604:

  drm/i915: Only clear the GPU domains upon a successful finish (2012-03-01 21:36:13 +0100)

----------------------------------------------------------------
Benson Leung (1):
      drm/i915: Fix single msg gmbus_xfers writes

Chris Wilson (5):
      drm/i915/bios: Downgrade the "signature missing" DRM_ERROR to debug
      drm/i915: Only bump refcnt on objects scheduled for eviction
      drm/i915: No need to search again after retiring requests
      drm/i915: Silence the error message from i915_wait_request()
      drm/i915: Only clear the GPU domains upon a successful finish

Daniel Vetter (9):
      drm/i915: use the new hdmi_force_audio enum more
      drm/i915: error_buffer->ring should be signed
      drm/i915: add dev_priv to intel_gmbus
      drm/nouveau: do a better job at hiding the NIH i2c bit-banging algo
      i2c: export bit-banging algo functions
      drm/i915: merge struct intel_gpio into struct intel_gmbus
      drm/i915: merge gmbus and gpio i2c adpater into one
      drm/i915: i2c: unconditionally set up gpio fallback
      drm/i915: reenable gmbus on gen3+ again

Marc Gariepy (1):
      drm/i915: Ignore LVDS on hp t5745 and hp st5747 thin client

Philipp Grete (1):
      drm/i915: Fixes distorted external screen image on HP 2730p

 drivers/gpu/drm/i915/i915_drv.h       |   19 +++-
 drivers/gpu/drm/i915/i915_gem.c       |   12 +--
 drivers/gpu/drm/i915/i915_gem_evict.c |   19 +---
 drivers/gpu/drm/i915/intel_bios.c     |    2 +-
 drivers/gpu/drm/i915/intel_display.c  |    2 -
 drivers/gpu/drm/i915/intel_dp.c       |   10 +-
 drivers/gpu/drm/i915/intel_i2c.c      |  190 +++++++++++++-------------------
 drivers/gpu/drm/i915/intel_lvds.c     |   16 +++
 drivers/gpu/drm/i915/intel_sdvo.c     |   10 +-
 drivers/gpu/drm/nouveau/nouveau_i2c.c |    8 +-
 drivers/i2c/algos/i2c-algo-bit.c      |    3 +-
 include/linux/i2c-algo-bit.h          |    1 +
 12 files changed, 130 insertions(+), 162 deletions(-)
On Thu, Mar 08, 2012 at 08:10:47AM +0000, Sun, Yi wrote:
> New round Kernel testing is finished. This time we covered the platform IVB, SNB, ILK, G45, PNV.
> The kernel commit is:
> Kernel: (drm-intel-testing) 9c5a1897768918a941aebbeaefd9f698358c7cf9
> Merge: c501ae7 108b0d3
> Author: Daniel Vetter <daniel.vetter@ffwll.ch>
> Date:   Thu Mar 1 21:47:53 2012 +0100
>     Merge remote-tracking branch 'airlied/drm-fixes' into drm-intel-testing
> 
>     Conflicts:
>         drivers/gpu/drm/i915/intel_ringbuffer.c
> 
> New filed bugs:
> Bug 47034 - [G45]testdisplay can't show all modes with VGA interface and black screen (https://bugs.freedesktop.org/show_bug.cgi?id=47034)
> Bug 47082 - [G33]GPU hung while running gem_cs_prefetch of intel-gpu-tools (https://bugs.freedesktop.org/show_bug.cgi?id=47082)
> Bug 47085 - [ILK]I-G-T/gem_pipe_control_store_loop fail unstablely (https://bugs.freedesktop.org/show_bug.cgi?id=47085)
> Note that, the bug 47082 and 47085 are unstable issue. If run the test cases separately, both two cases would pass. But if run the whole i-g-t suite with make test, the two cases which involved in the bug report would fail sometimes.
> 
> It's first time that we found some Piglit cases failure caused by Kernel regression. And the bug is filed:
> Bug 46863 - [ivb/snb regression] Piglit case fbo-stencil fail (https://bugs.freedesktop.org/show_bug.cgi?id=46863)
> 
> Fixed bugs:
> Bug 44250 - [IVB]"[drm:intel_dsm_platform_mux_info] *ERROR* MUX INFO call failed" while booting with monitor (https://bugs.freedesktop.org/show_bug.cgi?id=44250)
> 
> Old bugs Still occurs:
> Bug 41976 - [IVB] screen turn to be black while switching between console and x-window with 3-pipe active. (https://bugs.freedesktop.org/show_bug.cgi?id=41976)
> Bug 42194 - [IVB/SNB]plug in a monitor while running testdisplay fail to make the screen come up. (https://bugs.freedesktop.org/show_bug.cgi?id=42194)
> Bug 44309 - [IVB eDP] 3 pipe doesn't work with eDP monitor.  (https://bugs.freedesktop.org/show_bug.cgi?id=44309)
> Bug 45867 - [IVB 3pipe] 3 Pipe Doesn't Work with Eaglemont Card. (https://bugs.freedesktop.org/show_bug.cgi?id=45867)
> 
> So till now, in the i-g-t test suite, only 3 failures happen with -testing branch. Two are unstable which mentioned above(gem_cs_prefetch and gem_pipe_control_store_loop), and the other one is gem_ringfill which is also filed.
> 
> Thanks
>    --Yi,Sun
> 
> 
> > -----Original Message-----
> > From: Daniel Vetter [mailto:daniel.vetter@ffwll.ch] On Behalf Of Daniel Vetter
> > Sent: Friday, March 02, 2012 4:59 AM
> > To: Intel Graphics Development; Sun, Yi
> > Subject: Updated -next
> > 
> > Hi all,
> > 
> > I've just pushed out update -next and -testing trees. Highlights:
> > - gmbus fixes, gmbus is now again enabled by default.
> > - random smaller fixes.
> > 
> > ... so not too much this time around. For the 3.4 I think we should now slowly
> > wind down, of the big outstanding patch series I think only the pwrite series
> > might still get in. But it has blown up so often in 'final'
> > review already that I am sceptical.
> > 
> > In other news I'll be at osts next week and on vacation the following week, so
> > expect slow response times from me and an extended -next cycle.
> > 
> > Happy testing!
> > 
> > Cheers, Daniel
> > --
> > Daniel Vetter
> > Mail: daniel@ffwll.ch
> > Mobile: +41 (0)79 365 57 48

-- 
Daniel Vetter
Mail: daniel@ffwll.ch
Mobile: +41 (0)79 365 57 48

Re: Updated -next

[Daniel Vetter]

Hi Dave,

A new drm-intel-next pull. Highlights:
- More gmbus patches from Daniel Kurtz, I think gmbus is now ready, all
  known issues fixed.
- Fencing cleanup and pipelined fencing removal from Chris.
- rc6 residency interface from Ben, useful for powertop.
- Cleanups and code reorg around the ringbuffer code (Ben&me).
- Use hw semaphores in the pageflip code from Ben.
- More vlv stuff from Jesse, unfortunately his vlv cpu is doa, so less
  merged than I've hoped for - we still have the unused function warning :(
- More hsw patches from Eugeni, again, not yet enabled fully.
- intel_pm.c refactoring from Eugeni.
- Ironlake sprite support from Chris.
- And various smaller improvements/fixes all over the place.

Note that this pull request also contains a backmerge of -rc3 to sort out
a few things in -next. I've also had to frob the shortlog a bit to exclude
anything that -rc3 brings in with this pull.

Regression wise we have a few strange bugs going on, but for all of them
closer inspection revealed that they've been pre-existing, just now
slightly more likely to be hit. And for most of them we have a patch
already. Otherwise QA has not reported any regressions, and I'm also not
aware of anything bad happening in 3.4.

For 3.4 Ken discovered that one of the snb workarounds in -next is
required to fix hangs in google maps and tons of other apps, so expect
another -fixes pull.

Cheers, Daniel


The following changes since commit effbc4fd8e37e41d6f2bb6bcc611c14b4fbdcf9b:

  Merge branch 'drm-intel-next' of git://people.freedesktop.org/~danvet/drm-intel into drm-core-next (2012-04-12 10:27:01 +0100)

are available in the git repository at:


  git://people.freedesktop.org/~danvet/drm-intel tags/drm-intel-next-2012-04-23

for you to fetch changes up to a85d4bcb8a0cd5b3c754f98ff91ef2b9b3a73bc5:

  drm/i915: rc6 residency (fix the fix) (2012-04-23 09:30:14 +0200)

----------------------------------------------------------------
Armin Reese (1):
      drm/i915: Mask reserved bits in display/sprite address registers

Ben Widawsky (10):
      drm/i915: add rc6 residency times to debugfs
      drm/i915: use semaphores for the display plane
      drm/i915: rc6 in sysfs
      drm/i915: i915_gem_object_sync must handle NULL
      drm/i915: fix for when semaphore updates fail
      drm/i915: hide (seqno-1) in ringbuffer code
      drm/i915: [sparse] trivial sparse fixes
      drm/i915: [sparse] don't use variable size arrays
      drm/i915: [GEN7] Use HW scheduler for fixed function shaders
      drm/i915: rc6 residency (fix the fix)

Chris Wilson (25):
      drm/i915: Reorganise rules for get_fence/put_fence
      drm/i915: Ironlake shares the same video sprite controls as Sandybridge
      drm/i915: Allow concurrent read access between CPU and GPU domain
      drm/i915: Trigger hangcheck if we detect more a repeating missed IRQ
      drm/i915: Refactor the deferred PM_IIR handling into a single function
      drm/i915: Export the generic, not arch specific, intel_update_watermarks()
      drm/i915/sprite: Always enable the scaler on IronLake
      drm/i915/dp: Flush any outstanding work to turn the VDD off
      drm/i915: Always flush tiling changes before accessing through the GTT
      drm/i915: Replace open coded MI_BATCH_GTT
      drm/i915: Unpin the flip target if we fail to queue the flip
      drm/i915: intel_update_fbc() requires struct_mutex, so no longer atomic
      drm/i915: Don't set a MBZ bit in gen2/3 MI_FLUSH
      drm/i915: Wait for all pending operations to the fb before disabling the pipe
      drm/i915: Remove the pipelined parameter from get_fence()
      drm/i915: Remove fence pipelining
      drm/i915: Remove unused ring->setup_seqno
      drm/i915: Discard the unused obj->last_fenced_ring
      drm/i915: Simplify fence finding
      drm/i915: Remove the unsightly "optimisation" from flush_fence()
      drm/i915: Prepare to consolidate fence writing
      drm/i915: Refactor put_fence() to use the common fence writing routine
      drm/i915: Refactor fence clearing to use the common fence writing routine
      drm/i915: Refactor get_fence() to use the common fence writing routine
      drm/i915: Silence the change of LVDS sync polarity

Daniel Kurtz (9):
      drm/i915/intel_i2c: handle zero-length writes
      drm/i915/intel_i2c: use double-buffered writes
      drm/i915/intel_i2c: always wait for IDLE before clearing NAK
      drm/i915/intel_i2c: use WAIT cycle, not STOP
      drm/i915/intel_i2c: use INDEX cycles for i2c read transactions
      drm/i915/intel_i2c: reuse GMBUS2 value read in polling loop
      drm/i915/intel_i2c: remove POSTING_READ() from gmbus transfers
      drm/i915/intel_i2c: handle zero-length reads
      drm/i915/intel_i2c: reduce verbosity of some messages

Daniel Vetter (24):
      drm/i915: simplify ppgtt setup
      drm/i915: re-init modeset hw state after gpu reset
      drm/i915: rip out ring->irq_mask
      drm/i915: set ring->size in common ring setup code
      drm/i915: dynamically set up the render ring functions and params
      drm/i915: dynamically set up bsd ring functions and params
      drm/i915: dynamically set up blt ring functions and parameters
      drm/i915: don't set up rings on gen6+ for non-kms
      drm/i915: consolidate ring->sync-to functions
      drm/i915: abstract away ring-specific irq_get/put
      drm/i915: split out the gen5 ring irq get/put functions
      drm/i915: don't enable the gen6 bsd ring tail write enable on gen7
      drm/i915: split up ring->dispatch_execbuffer functions
      drm/i915: consolidate ring->add_request a bit
      drm/i915: don't set up gem ring functions on gen5 for !kms
      drm/i915: inline enable/disable_irq into ring->get/put_irq
      drm/i915: don't pwrite tiled objects through the gtt
      Merge tag 'v3.4-rc3' into drm-intel-next-queued
      drm/i915: implement a media hang w/a
      drm/i915: set w/a bit for snb pagefaults
      drm/i915: properly set ppgtt cacheability on snb
      drm/i915: implement w/a for incorrect guarband clipping
      drm/i915: set stc evict disable lra evict w/a
      drm/i915: invalidate render cache on gen2

Dave Airlie (1):
      drm/i915/tv: fix open-coded ARRAY_SIZE.

Eugeni Dodonov (13):
      drm/i915: add definition of LPT FDI port width registers
      drm/i915: add WRPLL divider programming bits
      drm/i915: share forcewaking code between IVB and HSW
      drm/i915: haswell has 3 pipes as well
      drm/i915: share IVB cursor routine with Haswell
      drm/i915: disable rc6 on haswell for now
      drm/i915: move fbc-related functionality into intel_pm module
      drm/i915: move watermarks settings into intel_pm module
      drm/i915: fix line breaks in intel_pm
      drm/i915: move drps, rps and rc6-related functions to intel_pm
      drm/i915: move emon functionality into intel_pm module
      drm/i915: move clock gating functionality into intel_pm module
      drm/i915: add generic power management initialization

Jesse Barnes (6):
      drm/i915: use register name when disabling VGA
      drm/i915: make DP configuration vars less confusing in ironlake_crtc_mode_se
      drm/i915: check PPS regs for sanity when using eDP
      drm/i915: disable turbo on ValleyView for now
      drm/i915: allow PCH PWM override on IVB
      drm/i915: IBX+ doesn't have separate vsync/hsync controls on the VGA DAC

-- 
Daniel Vetter
Mail: daniel@ffwll.ch
Mobile: +41 (0)79 365 57 48

Re: Updated -next

[Daniel Vetter]

On Fri, Apr 27, 2012 at 01:45:42PM +0200, Daniel Vetter wrote:
> Hi Dave,
> 
> A new drm-intel-next pull. Highlights:
> - More gmbus patches from Daniel Kurtz, I think gmbus is now ready, all
>   known issues fixed.
> - Fencing cleanup and pipelined fencing removal from Chris.
> - rc6 residency interface from Ben, useful for powertop.
> - Cleanups and code reorg around the ringbuffer code (Ben&me).
> - Use hw semaphores in the pageflip code from Ben.
> - More vlv stuff from Jesse, unfortunately his vlv cpu is doa, so less
>   merged than I've hoped for - we still have the unused function warning :(
> - More hsw patches from Eugeni, again, not yet enabled fully.
> - intel_pm.c refactoring from Eugeni.
> - Ironlake sprite support from Chris.
> - And various smaller improvements/fixes all over the place.
> 
> Note that this pull request also contains a backmerge of -rc3 to sort out
> a few things in -next. I've also had to frob the shortlog a bit to exclude
> anything that -rc3 brings in with this pull.
> 
> Regression wise we have a few strange bugs going on, but for all of them
> closer inspection revealed that they've been pre-existing, just now
> slightly more likely to be hit. And for most of them we have a patch
> already. Otherwise QA has not reported any regressions, and I'm also not
> aware of anything bad happening in 3.4.
> 
> For 3.4 Ken discovered that one of the snb workarounds in -next is
> required to fix hangs in google maps and tons of other apps, so expect
> another -fixes pull.
> 
> Cheers, Daniel
> 
> 
> The following changes since commit effbc4fd8e37e41d6f2bb6bcc611c14b4fbdcf9b:
> 
>   Merge branch 'drm-intel-next' of git://people.freedesktop.org/~danvet/drm-intel into drm-core-next (2012-04-12 10:27:01 +0100)
> 
> are available in the git repository at:
> 
> 
>   git://people.freedesktop.org/~danvet/drm-intel tags/drm-intel-next-2012-04-23

I've forgot to mention that this branch has a very funky conflict with
Linus' tree. Essentially it's just a few patches touching the same file
(not even the same functions), but the git diff algo gets completely
confused and thinks that the drm-intel-next branch completely rewrote
large parts of intel_display.c. In truth we've just moved a few functions
out of intel_display.c into intel_pm.c. But because the part in
intel_display.c where git is all confused about is also changed in the 3.4
tree, and we have a merge conflict where none should be.

drm-intel-testing has the merge resolution, in case anyone needs it.
-Daniel
-- 
Daniel Vetter
Mail: daniel@ffwll.ch
Mobile: +41 (0)79 365 57 48