Re: [Intel-gfx] [PATCH 6/6] drm/i915: Migrate stolen objects before hibernation

2015-12-09 Thread Ville Syrjälä
On Wed, Dec 09, 2015 at 05:25:19PM +, Tvrtko Ursulin wrote: > > Hi, > > On 09/12/15 12:46, ankitprasad.r.sha...@intel.com wrote: > > From: Chris Wilson > > > > Ville reminded us that stolen memory is not preserved across > > hibernation, and a result of this was that context objects now bein

Re: [Intel-gfx] [PATCH 6/6] drm/i915: Migrate stolen objects before hibernation

2015-12-09 Thread Dave Gordon
On 09/12/15 12:46, ankitprasad.r.sha...@intel.com wrote: From: Chris Wilson Ville reminded us that stolen memory is not preserved across hibernation, and a result of this was that context objects now being allocated from stolen were being corrupted on S4 and promptly hanging the GPU on resume.

Re: [Intel-gfx] [PATCH 5/6] drm/i915: Support for pread/pwrite from/to non shmem backed objects

2015-12-09 Thread Dave Gordon
On 09/12/15 16:15, Tvrtko Ursulin wrote: Hi, On 09/12/15 12:46, ankitprasad.r.sha...@intel.com wrote: From: Ankitprasad Sharma This patch adds support for extending the pread/pwrite functionality for objects not backed by shmem. The access will be made through gtt interface. This will cover

Re: [Intel-gfx] [PATCH 1/5] drm/i915: Separate cherryview from valleyview

2015-12-09 Thread Boyer, Wayne
Thanks Ville. I'll send one more update with some of the changes. I'll leave the others for a different patch. Details below. Wayne On 12/9/15, 9:10 AM, "Ville Syrjälä" wrote: >On Tue, Dec 08, 2015 at 11:46:53AM -0800, Wayne Boyer wrote: >> The cherryview device shares many characteristics

[Intel-gfx] [PATCH 1/5] drm/i915: Separate cherryview from valleyview

2015-12-09 Thread Wayne Boyer
The cherryview device shares many characteristics with the valleyview device. When support was added to the driver for cherryview, the corresponding device info structure included .is_valleyview = 1. This is not correct and leads to some confusion. This patch changes .is_valleyview to .is_cherryv

Re: [Intel-gfx] [PATCH] drm/i915: Flush the RPS bottom-half when the GPU idles

2015-12-09 Thread Chris Wilson
On Wed, Dec 09, 2015 at 07:47:29PM +0200, Imre Deak wrote: > >  void gen6_rps_idle(struct drm_i915_private *dev_priv) > >  { > > - struct drm_device *dev = dev_priv->dev; > > + /* Flush our bottom-half so that it does not race with us > > +  * setting the idle frequency and so that it is boun

Re: [Intel-gfx] [PATCH] drm/i915/skl: SKL CDCLK change on modeset tracking VCO

2015-12-09 Thread Ville Syrjälä
On Tue, Dec 08, 2015 at 04:15:05PM -0800, clinton.a.tay...@intel.com wrote: > From: Clint Taylor > > Track VCO frequency of SKL instead of the boot CDCLK and allow modeset > to set cdclk based on the max required pixel clock based on VCO > selected. > > Signed-off-by: Clint Taylor > --- > driv

Re: [Intel-gfx] [PATCH 1/5] drm/i915: Separate cherryview from valleyview

2015-12-09 Thread Ville Syrjälä
On Wed, Dec 09, 2015 at 12:29:35PM -0800, Wayne Boyer wrote: > The cherryview device shares many characteristics with the valleyview > device. When support was added to the driver for cherryview, the > corresponding device info structure included .is_valleyview = 1. > This is not correct and leads

Re: [Intel-gfx] [PATCH] drm/i915: Flush the RPS bottom-half when the GPU idles

2015-12-09 Thread Imre Deak
On Wed, 2015-12-09 at 20:52 +, Chris Wilson wrote: > On Wed, Dec 09, 2015 at 07:47:29PM +0200, Imre Deak wrote: > > >  void gen6_rps_idle(struct drm_i915_private *dev_priv) > > >  { > > > - struct drm_device *dev = dev_priv->dev; > > > + /* Flush our bottom-half so that it does not race with >

Re: [Intel-gfx] [PATCH v2] PM / Runtime: Introduce pm_runtime_get_noidle

2015-12-09 Thread Rafael J. Wysocki
On Wednesday, December 09, 2015 06:22:19 PM Joonas Lahtinen wrote: > Introduce pm_runtime_get_noidle to for situations where it is not > desireable to touch an idling device. One use scenario is periodic > hangchecks performed by the drm/i915 driver which can be omitted > on a device in a runtime i

[Intel-gfx] [PATCH 1/2] drm/i915: Call encoder hotplug for init and resume cases

2015-12-09 Thread Sonika Jindal
Call the encoders, call the hot_plug if it is registered. This is required for connected boot and resume cases to generate fake hpd resulting in reading of edid. Removing the initial sdvo hot_plug call too so that it will be called just once from this loop. v2: Schedule a work function to call hot

[Intel-gfx] [PATCH 2/2] drm/i915: Add hot_plug hook for hdmi encoder

2015-12-09 Thread Sonika Jindal
This patch adds a separate probe function for HDMI EDID read over DDC channel. This function has been registered as a .hot_plug handler for HDMI encoder. The current implementation of hdmi_detect() function re-sets the cached HDMI edid (in connector->detect_edid) in every detect call.This function

[Intel-gfx] [PATCH] drm/i915: Add hot_plug hook for hdmi encoder

2015-12-09 Thread Sonika Jindal
From: Shashank Sharma This patch adds a separate probe function for HDMI EDID read over DDC channel. This function has been registered as a .hot_plug handler for HDMI encoder. The current implementation of hdmi_detect() function re-sets the cached HDMI edid (in connector->detect_edid) in every d

<    1   2