1. 18 May, 2012 1 commit
  2. 17 May, 2012 23 commits
  3. 16 May, 2012 1 commit
  4. 13 May, 2012 10 commits
  5. 11 May, 2012 5 commits
    • Dave Airlie's avatar
      Merge tag 'drm-intel-next-2012-05-06-merged' of... · 218c872b
      Dave Airlie authored
      Merge tag 'drm-intel-next-2012-05-06-merged' of git://people.freedesktop.org/~danvet/drm-intel into drm-core-next
      
      Daniel says
      
      Highlights:
      - sparse fixes from Ben.
      - tons of little cleanups from Chris all over: tiling_changed
       clarification, deferred_free list removal, ...
      - fix up irq handler on gen2 & gen3 + related cleanups from Chris
      - prep work for wait_rendering_timeout from Ben with some nice
       refactorings
      - first set of infoframe fixes from Paulo for doubleclocked CEA modes
      - improve pch pll handling from Jesse and Chris
      - gpu hangman, this also contains the reset fix for gen4
      - rps sanity check from Chris - this papers over issues when the gpu fails
       to clock up on snb/ivb, and it is shockingly easy to hit. The code
       prints a big WARN backtrace and restores the hw to a sane state. The
       real fix is still in the works.
      
      Atm I'm aware of 2 regressions in -next:
      - One of the gmbus patches (not gmbus itself) regressed lvds detection on
       a MacbookPro. I've analyzed the bug already and I think I know what's
       going on, patch is awaiting test feedback.
      - Just today QA reported that DP on ilk regressed. That bug is fresh of
       the press and still awaiting detailed logfiles and the bisect result.
       The only thing that's clear atm is that -fixes works and -next doesn't.
      218c872b
    • Rob Clark's avatar
      drm: pass dev to drm_vm_{open,close}_locked() · b06d66be
      Rob Clark authored
      Previously these functions would assume that vma->vm_file was the
      drm_file.  Although if in some cases if the drm driver needs to use
      something else for the backing file (such as the tmpfs filp) then this
      assumption is no longer true.  But vma->vm_private_data is still the
      GEM object.
      
      With this change, now the drm_device comes from the GEM object rather
      than the drm_file so the driver is more free to play with vma->vm_file.
      
      The scenario where this comes up is for mmap'ing of cached dmabuf's
      for non-coherent systems, where the driver needs to use fault handling
      and PTE shootdown to simulate coherency.  We can't use the vma->vm_file
      of the dmabuf, which is using anon_inode's address_space.  The most
      straightforward thing to do is to use the GEM object's obj->filp for
      vma->vm_file in all cases, for which we need this patch.
      Signed-off-by: default avatarRob Clark <rob@ti.com>
      Signed-off-by: default avatarDave Airlie <airlied@redhat.com>
      b06d66be
    • Alan Cox's avatar
      gma500: Turn on the IRQ for everything · 62363a48
      Alan Cox authored
      Keep this as a patch of its own in case of bug reports.
      Signed-off-by: default avatarAlan Cox <alan@linux.intel.com>
      Signed-off-by: default avatarDave Airlie <airlied@redhat.com>
      62363a48
    • Alan Cox's avatar
      gma500: clean up some more checks · 9c0b6fcd
      Alan Cox authored
      We don't need to check these - they are always going to be the
      same for any PVR based device.
      Signed-off-by: default avatarAlan Cox <alan@linux.intel.com>
      Signed-off-by: default avatarDave Airlie <airlied@redhat.com>
      9c0b6fcd
    • Alan Cox's avatar
      cdv: Add all cedarview pci ids · 9aa65a2b
      Alan Cox authored
      Cover all D2xxx/N2xxx chips.
      Signed-off-by: default avatarZhenyu Wang <zhenyuw@linux.intel.com>
      [Hand applied to upstream driver]
      Signed-off-by: default avatarAlan Cox <alan@linux.intel.com>
      Signed-off-by: default avatarDave Airlie <airlied@redhat.com>
      9aa65a2b