[Intel-gfx] [PATCH v3] drm/i915: New offset for reading frequencies on CHV.

2015-01-16 Thread deepak . s
From: Deepak S Use new Sideband offset to read max/min/gaur freq based on the SKU it is running on. Based on the Number of EU, we read different bits to identify the max frequencies at which system can run. v2: reuse mask definitions & INTEL_INFO() to get device info (Ville) v3: add break in sw

Re: [Intel-gfx] [PATCH v2 3/3] drm/i915: New offset for reading frequencies on CHV.

2015-01-16 Thread Deepak S
On Friday 16 January 2015 10:39 PM, Ville Syrjälä wrote: On Fri, Jan 16, 2015 at 08:42:18PM +0530, deepa...@linux.intel.com wrote: From: Deepak S Use new Sideband offset to read max/min/gaur freq based on the SKU it is running on. Based on the Number of EU, we read different bits to identify

Re: [Intel-gfx] [PATCH] drm/i915: Don't cleanup plane state in intel_plane_destroy()

2015-01-16 Thread shuang . he
Tested-By: PRC QA PRTS (Patch Regression Test System Contact: shuang...@intel.com) Task id: 5594 -Summary- Platform Delta drm-intel-nightly Series Applied PNV -1 353/353

Re: [Intel-gfx] [PATCH 2/2] intel: Use I915_EXEC_NO_RELOC when available

2015-01-16 Thread Daniel Vetter
On Fri, Jan 16, 2015 at 05:46:00PM -0800, Kristian Høgsberg wrote: > The I915_EXEC_NO_RELOC flag lets us tell the kernel that the offset we > provide in the validate list entry is what we've used in all relocations > to the bo in question. If the bo hasn't moved, the kernel can skip > relocations

Re: [Intel-gfx] [PATCH] drm/i915/skl: Enabling PSR on Skylake

2015-01-16 Thread Daniel Vetter
On Fri, Jan 16, 2015 at 02:07:26PM +0530, Sonika Jindal wrote: > Mainly taking care of some register offsets, otherwise things are similar to > hsw. Also, programming ddi aux to use hardcoded values for psr data select. > > v2: introduce EDP_PSR_AUX_BASE macro (Chris) > v3: Moving to HW tracking f

Re: [Intel-gfx] [PATCH] drm/i915: Do not invalidate obj->pages under mempressure

2015-01-16 Thread Daniel Vetter
On Thu, Jan 15, 2015 at 08:44:00PM +, Chris Wilson wrote: > On Thu, Jan 15, 2015 at 08:36:15PM +0100, Daniel Vetter wrote: > > On Wed, Jan 14, 2015 at 9:34 PM, Chris Wilson > > wrote: > > > This (partially) reverts > > > > > > commit 5537252b6b6d71fb1a8ed7395a8e5babf91953fd > > > Author: Chri

Re: [Intel-gfx] [PATCH] drm/i915: Changes required to enable DSI Video Mode on CHT

2015-01-16 Thread Daniel Vetter
On Thu, Jan 15, 2015 at 01:25:02PM +0200, Jani Nikula wrote: > On Wed, 14 Jan 2015, "Singh, Gaurav K" wrote: > > On 12/12/2014 1:03 PM, Singh, Gaurav K wrote: > >> > >> On 12/10/2014 7:38 PM, Gaurav K Singh wrote: > >>> For CHT changes are required for calculating the correct m,n & p with > >>> mi

Re: [Intel-gfx] [PATCH] Revert "drm/i915: Fix mutex->owner inspection race under DEBUG_MUTEXES"

2015-01-16 Thread Daniel Vetter
On Thu, Jan 15, 2015 at 09:13:02AM +0200, Jani Nikula wrote: > On Wed, 14 Jan 2015, Chris Wilson wrote: > > The core fix was applied in > > > > commit a63b03e2d2477586440741677ecac45bcf28d7b1 > > Author: Chris Wilson > > Date: Tue Jan 6 10:29:35 2015 + > > > > mutex: Always clear owner

[Intel-gfx] [PATCH 1/2] intel: Use I915_EXEC_HANDLE_LUT when available

2015-01-16 Thread Kristian Høgsberg
In userspace we can track which buffer a relocation refers to in constant time. However, the kernel has to look up the per-fd gem handle for each relocation. Using the I915_EXEC_HANDLE_LUT flag lets us use the the bos validation list index instead of the gem handle in the relocation entries. Thi

[Intel-gfx] [PATCH 2/2] intel: Use I915_EXEC_NO_RELOC when available

2015-01-16 Thread Kristian Høgsberg
The I915_EXEC_NO_RELOC flag lets us tell the kernel that the offset we provide in the validate list entry is what we've used in all relocations to the bo in question. If the bo hasn't moved, the kernel can skip relocations completely. Signed-off-by: Kristian Høgsberg --- intel/intel_bufmgr_gem.

Re: [Intel-gfx] [PATCH 6/7] drm/i915: Improve how the memory for crtc state is allocated

2015-01-16 Thread Matt Roper
On Thu, Jan 15, 2015 at 02:55:26PM +0200, Ander Conselvan de Oliveira wrote: > The previous patch changed the config field in intel_crtc to a pointer, > but to keep the mechanical changes (done with spatch) separate from the > new code, the pointer was made to point to a new _config field with type

Re: [Intel-gfx] [PATCH 9/9] drm/i915: Rename i915_gen6_forcewake_count_info

2015-01-16 Thread shuang . he
Tested-By: PRC QA PRTS (Patch Regression Test System Contact: shuang...@intel.com) Task id: 5592 -Summary- Platform Delta drm-intel-nightly Series Applied PNV -1 353/353

Re: [Intel-gfx] [PATCH i-g-t v2] tools/intel_gpu_frequency: remove use of getsubopt

2015-01-16 Thread Ben Widawsky
On Fri, Jan 16, 2015 at 09:12:15AM +, tim.g...@intel.com wrote: > From: Tim Gore > > getsubopt is not available in android. The "get" option > doesn't really need sub-options, just display all the > current frequency settings (as per discussion with > Ben Widawsky) > > Signed-off-by: Tim Gor

[Intel-gfx] [PATCH 0/4] SKL turbo part 1

2015-01-16 Thread Damien Lespiau
The turbo work is not quite complete with those patches, but it's a big step forward. The missing bit is that the granularity of frequency the GPU supports has changed. For this reason, I left in the code disabling gen6_rps_irq_handler() for gen9+ in until we have a proper implementation. -- Dam

[Intel-gfx] [PATCH 2/4] drm/i915/skl: Retrieve the frequency limits

2015-01-16 Thread Damien Lespiau
v2: Use the new function, gen6_init_rps_frequencies() (Damien) Reviewed-by: Mika Kuoppala (v1) Signed-off-by: Damien Lespiau --- drivers/gpu/drm/i915/intel_pm.c | 2 ++ 1 file changed, 2 insertions(+) diff --git a/drivers/gpu/drm/i915/intel_pm.c b/drivers/gpu/drm/i915/intel_pm.c index 3a0aec0.

[Intel-gfx] [PATCH 4/4] drm/i915/skl: Updated the RC6/Forcewake related debugfs interface for Gen9

2015-01-16 Thread Damien Lespiau
From: Akash Goel Updated the i915_drpc_info & i915_gen6_forcewake_count debugfs interface v2: Change all IS_GEN9() by gen >= 9 (Damien) Change-Id: Ibed2fb71b233a369e69278bc96298df82d032a47 Signed-off-by: Akash Goel Signed-off-by: Damien Lespiau --- drivers/gpu/drm/i915/i915_debugfs.c | 44 ++

[Intel-gfx] [PATCH 3/4] drm/i915/skl: Gen9 coarse power gating

2015-01-16 Thread Damien Lespiau
From: Zhe Wang Enable coarse power gating for Gen9. This feature allows render and media engine to enter RC6 independently. Policies are configured together with RC6. This feature will only be enabled when RC6 is enabled. Signed-off-by: Zhe Wang Signed-off-by: Damien Lespiau --- drivers/gpu/d

[Intel-gfx] [PATCH 1/4] drm/i915/skl: add turbo support

2015-01-16 Thread Damien Lespiau
From: Jesse Barnes Per latest PM programming guide. v2: the wrong flavour of the function updating the ring frequency was called, leading to dead locks (Tvrtko) v3: Add GEN6_RP_MEDIA_IS_GFX to RP_CONTROL (Imre, done by Damien) Signed-off-by: Jesse Barnes Signed-off-by: Damien Lespiau ---

Re: [Intel-gfx] [PATCH v2 1/3] drm/i915/chv: Populate total EU count on Cherryview

2015-01-16 Thread Ville Syrjälä
On Fri, Jan 16, 2015 at 08:42:16PM +0530, deepa...@linux.intel.com wrote: > From: Deepak S > > Starting with Cherryview, devices may have a varying number of EU for > a given ID due to creative fusing. Punit support different frequency for > different fuse data. We use this patch to help get tota

Re: [Intel-gfx] [PATCH v2 2/3] drm/i915: Increase the range of sideband address.

2015-01-16 Thread Ville Syrjälä
On Fri, Jan 16, 2015 at 08:42:17PM +0530, deepa...@linux.intel.com wrote: > From: Deepak S > > Looks like latest BSW/CHV production system has sideband address > 128. > Use u32 data types to cover new offset/address range :) > > Signed-off-by: Deepak S Reviewed-by: Ville Syrjälä > --- > dri

Re: [Intel-gfx] [PATCH v2 3/3] drm/i915: New offset for reading frequencies on CHV.

2015-01-16 Thread Ville Syrjälä
On Fri, Jan 16, 2015 at 08:42:18PM +0530, deepa...@linux.intel.com wrote: > From: Deepak S > > Use new Sideband offset to read max/min/gaur freq based on the SKU it > is running on. Based on the Number of EU, we read different bits to > identify the max frequencies at which system can run. > > v

Re: [Intel-gfx] [PATCH] drm/i915: Don't cleanup plane state in intel_plane_destroy()

2015-01-16 Thread Jani Nikula
On Fri, 16 Jan 2015, Matt Roper wrote: > When we transitioned to the atomic plane helpers in commit: > > commit ea2c67bb4affa84080c616920f3899f123786e56 > Author: Matt Roper > Date: Tue Dec 23 10:41:52 2014 -0800 > > drm/i915: Move to atomic plane helpers (v9

[Intel-gfx] [PATCH 0/2] Power well support for SKL

2015-01-16 Thread Damien Lespiau
Those two patches implement power support for SKL. Patch 1 is already reviewed. For the moment we don't do anything fancy with the AUX power domain, so the series has no real impact on current hardware to ease its inclusion in 3.20. -- Damien Satheeshakrishna M (2): drm/i915/skl: Adding power

[Intel-gfx] [PATCH 1/2] drm/i915/skl: Adding power domains for AUX controllers

2015-01-16 Thread Damien Lespiau
From: Satheeshakrishna M Adding new power doamins for AUX controllers v2: Added new power domains in power_domain_str per Imre's comment v3: Added AUX power domains to older platforms v4: Rebase on top of POWER_DOMAIN_PLLS. v5: Modified to address review comments from Imre Reviewed-by: Imre

[Intel-gfx] [PATCH 2/2] drm/i915/skl: Implementation of SKL display power well support

2015-01-16 Thread Damien Lespiau
From: Satheeshakrishna M This patch implements core logic of SKL display power well. v2: Addressed Imre's comments - Added respective DDIs under power well #1 and #2 - Simplified repetitive code in power well programming v3: Implemented Imre's comments - Further simplifi

Re: [Intel-gfx] [PATCH v2 1/3] drm/i915/chv: Populate total EU count on Cherryview

2015-01-16 Thread Jeff McGee
On Fri, Jan 16, 2015 at 08:42:16PM +0530, deepa...@linux.intel.com wrote: > From: Deepak S > > Starting with Cherryview, devices may have a varying number of EU for > a given ID due to creative fusing. Punit support different frequency for > different fuse data. We use this patch to help get tota

[Intel-gfx] [PATCH] drm/i915: Don't cleanup plane state in intel_plane_destroy()

2015-01-16 Thread Matt Roper
When we transitioned to the atomic plane helpers in commit: commit ea2c67bb4affa84080c616920f3899f123786e56 Author: Matt Roper Date: Tue Dec 23 10:41:52 2014 -0800 drm/i915: Move to atomic plane helpers (v9) one of the changes was to call intel_plane_destro

[Intel-gfx] [PATCH v2 2/3] drm/i915: Increase the range of sideband address.

2015-01-16 Thread deepak . s
From: Deepak S Looks like latest BSW/CHV production system has sideband address > 128. Use u32 data types to cover new offset/address range :) Signed-off-by: Deepak S --- drivers/gpu/drm/i915/i915_drv.h | 4 ++-- drivers/gpu/drm/i915/intel_sideband.c | 4 ++-- 2 files changed, 4 insertio

[Intel-gfx] [PATCH v2 3/3] drm/i915: New offset for reading frequencies on CHV.

2015-01-16 Thread deepak . s
From: Deepak S Use new Sideband offset to read max/min/gaur freq based on the SKU it is running on. Based on the Number of EU, we read different bits to identify the max frequencies at which system can run. v2: reuse mask definitions & INTEL_INFO() to get device info (Ville) Signed-off-by: Deep

[Intel-gfx] [PATCH v2 1/3] drm/i915/chv: Populate total EU count on Cherryview

2015-01-16 Thread deepak . s
From: Deepak S Starting with Cherryview, devices may have a varying number of EU for a given ID due to creative fusing. Punit support different frequency for different fuse data. We use this patch to help get total eu enabled and read the right offset to get RP0 Based upon a patch from Jeff, but

[Intel-gfx] [PATCH v2 0/3] Use new turbo offset for chv production system

2015-01-16 Thread deepak . s
From: Deepak S CHV/BSW production system has new turbo offset to read different freq. This series adds the support. Deepak S (3): drm/i915/chv: Populate total EU count on Cherryview drm/i915: Increase the range of sideband address. drm/i915: New offset for reading frequencies on CHV. dri

Re: [Intel-gfx] [PATCH] drm/i915/skl: Enabling PSR on Skylake

2015-01-16 Thread shuang . he
Tested-By: PRC QA PRTS (Patch Regression Test System Contact: shuang...@intel.com) Task id: 5591 -Summary- Platform Delta drm-intel-nightly Series Applied PNV -1 353/353

[Intel-gfx] [RFC PATCH 11/12] drm/i915/dsi: move dpi_send_cmd() to intel_dsi.c and make it static

2015-01-16 Thread Jani Nikula
No functional changes. Signed-off-by: Jani Nikula --- drivers/gpu/drm/i915/intel_dsi.c | 39 ++-- drivers/gpu/drm/i915/intel_dsi_cmd.c | 34 --- drivers/gpu/drm/i915/intel_dsi_cmd.h | 5 - 3 files changed, 37 insertions(+), 41

[Intel-gfx] [RFC PATCH 12/12] drm/i915/dsi: remove intel_dsi_cmd.c and the unused functions therein

2015-01-16 Thread Jani Nikula
The removed functions can be resurrected in intel_dsi.c as need arises. Signed-off-by: Jani Nikula --- drivers/gpu/drm/i915/Makefile | 1 - drivers/gpu/drm/i915/intel_dsi.c | 1 - drivers/gpu/drm/i915/intel_dsi_cmd.c | 117 - drivers/g

[Intel-gfx] [RFC PATCH 09/12] drm/i915/dsi: make the vbt panel driver use mipi_dsi_device for transfers

2015-01-16 Thread Jani Nikula
Use the drm core interfaces in preparation of removing our homebrew. Signed-off-by: Jani Nikula --- drivers/gpu/drm/i915/intel_dsi_panel_vbt.c | 52 +++--- 1 file changed, 34 insertions(+), 18 deletions(-) diff --git a/drivers/gpu/drm/i915/intel_dsi_panel_vbt.c b/driver

[Intel-gfx] [RFC PATCH 08/12] drm/i915/dsi: add drm mipi dsi host support

2015-01-16 Thread Jani Nikula
Add basic support for using the drm mipi dsi framework for DSI. We don't use device tree which is pretty much required by mipi_dsi_host_register and friends, and we don't have the kind of device model the functions expect either. So we cheat and use it as a library to abstract what we need: a nice,

[Intel-gfx] [RFC PATCH 05/12] drm/i915/dsi: remove unnecessary dsi device callbacks

2015-01-16 Thread Jani Nikula
Remove all the trivial and/or dummy callbacks from intel dsi device ops. Merge send_otp_cmds into panel_reset as they're called back to back. This will be helpful for switching to use drm_panel for the callbacks. If we ever need the additional callbacks, we should add them to drm_panel funcs. Sig

[Intel-gfx] [RFC PATCH 07/12] drm/i915/dsi: switch to drm_panel interface

2015-01-16 Thread Jani Nikula
Replace intel_dsi_device and intel_dsi_dev_ops with drm_panel and drm_panel_funcs. They are adequate for what we have now, and if we end up needing more than this we should improve drm_panel. This will keep us better aligned with the drm core infrastructure. The panel driver initialization changes

[Intel-gfx] [RFC PATCH 10/12] drm/i915/dsi: remove old read/write functions in favor of new stuff

2015-01-16 Thread Jani Nikula
All of these are replaced by the drm core mipi dsi functions. Signed-off-by: Jani Nikula --- drivers/gpu/drm/i915/intel_dsi_cmd.c | 259 --- drivers/gpu/drm/i915/intel_dsi_cmd.h | 72 -- 2 files changed, 331 deletions(-) diff --git a/drivers/gpu/drm/i915

[Intel-gfx] [RFC PATCH 06/12] drm/i915/dsi: add some constness to vbt panel driver

2015-01-16 Thread Jani Nikula
Const is good for you. No functional changes. Signed-off-by: Jani Nikula --- drivers/gpu/drm/i915/intel_dsi_panel_vbt.c | 17 + 1 file changed, 9 insertions(+), 8 deletions(-) diff --git a/drivers/gpu/drm/i915/intel_dsi_panel_vbt.c b/drivers/gpu/drm/i915/intel_dsi_panel_vbt.c i

[Intel-gfx] [RFC PATCH 02/12] drm/i915/dsi: set max return packet size for each dsi port

2015-01-16 Thread Jani Nikula
This seems like the right thing to do. This also gets rid of a call to intel_dsi_pipe_to_port() which we want to remove eventually. Signed-off-by: Jani Nikula --- drivers/gpu/drm/i915/intel_dsi.c | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/drivers/gpu/drm/i915/intel

[Intel-gfx] [RFC PATCH 03/12] drm/i915/dsi: move wait_for_dsi_fifo_empty to intel_dsi.c

2015-01-16 Thread Jani Nikula
wait_for_dsi_fifo_empty can be static in intel_dsi.c. No functional changes. Signed-off-by: Jani Nikula --- drivers/gpu/drm/i915/intel_dsi.c | 16 drivers/gpu/drm/i915/intel_dsi_cmd.c | 16 drivers/gpu/drm/i915/intel_dsi_cmd.h | 1 - 3 files changed, 16 ins

[Intel-gfx] [RFC PATCH 04/12] drm/i915/dsi: call wait_for_dsi_fifo_empty() for each dsi port

2015-01-16 Thread Jani Nikula
Add port parameter to wait_for_dsi_fifo_empty, and call it for each dsi port. We can now remove the transitional intel_dsi_pipe_to_port() function. Signed-off-by: Jani Nikula --- drivers/gpu/drm/i915/intel_dsi.c | 17 ++--- drivers/gpu/drm/i915/intel_dsi.h | 12 2 files

[Intel-gfx] [RFC PATCH 01/12] drm/i915/dsi: call dpi_send_cmd() for each dsi port at a higher level

2015-01-16 Thread Jani Nikula
Instead of having the for each dsi port loop within dpi_send_cmd(), add a port parameter to the function and call it for each port instead. This is a rewrite of commit 4510cd779e5897eeb8691aecbd639bb62ec27d55 Author: Gaurav K Singh Date: Thu Dec 4 10:58:51 2014 +0530 drm/i915: Dual link n

[Intel-gfx] [RFC PATCH 00/12] drm/i915: port dsi over to drm panel/dsi frameworks

2015-01-16 Thread Jani Nikula
This series ports our DSI code over to the drm_panel and mipi_dsi_host/mipi_dsi_device. There are some rough edges towards the end of the series, see commit message for patch 8 for details. Patches 1-6 are prep work, fairly independent Patch 7 ports the driver over to drm_panel Patches 8-10 port

Re: [Intel-gfx] [RFC v2 1/4] drm: Add support to find drm_panel by name

2015-01-16 Thread Thierry Reding
On Tue, Jan 13, 2015 at 12:08:11AM +0100, Daniel Vetter wrote: > On Fri, Jan 9, 2015 at 1:50 PM, Jani Nikula wrote: > > I have a slightly uneasy feeling about handing out drm_panel pointers > > (both from here and of_drm_find_panel) without refcounting. If the panel > > driver gets removed, whoeve

Re: [Intel-gfx] [PATCH v2 3/3] drm/i915: Ensure the HiZ RAW Stall Optimization is on for Cherryview.

2015-01-16 Thread Ville Syrjälä
On Tue, Jan 13, 2015 at 12:46:53PM -0800, Kenneth Graunke wrote: > This is an important optimization for avoiding read-after-write (RAW) > stalls in the HiZ buffer. Certain workloads would run very slowly with > HiZ enabled, but run much faster with the "hiz=false" driconf option. > With this patc

Re: [Intel-gfx] [PATCH 4/7] drm/i915: Don't pretend SDVO hotplug works on 915

2015-01-16 Thread Ville Syrjälä
On Tue, Jan 13, 2015 at 12:48:47AM +0100, Daniel Vetter wrote: > On Fri, Jan 09, 2015 at 02:21:15PM +0200, ville.syrj...@linux.intel.com wrote: > > From: Ville Syrjälä > > > > 915 doens't support hotplug at all, so we shouldn't try to pretend > > otherwise in the SDVO code. > > It actually has a

Re: [Intel-gfx] [PATCH] i915: reuse %ph to dump small buffers

2015-01-16 Thread shuang . he
Tested-By: PRC QA PRTS (Patch Regression Test System Contact: shuang...@intel.com) Task id: 5588 -Summary- Platform Delta drm-intel-nightly Series Applied PNV 353/353

Re: [Intel-gfx] [PATCH 0/4] drm/i915: Untangle execlist tracking

2015-01-16 Thread Daniel, Thomas
> -Original Message- > From: Intel-gfx [mailto:intel-gfx-boun...@lists.freedesktop.org] On Behalf > Of Nick Hoath > Sent: Thursday, January 15, 2015 1:11 PM > To: intel-gfx@lists.freedesktop.org > Cc: daniel.vet...@ffwll.ch > Subject: [Intel-gfx] [PATCH 0/4] drm/i915: Untangle execlist trac

[Intel-gfx] [PATCH 4/9] drm/i915: Reduce duplicated forcewake logic

2015-01-16 Thread Mika Kuoppala
From: Chris Wilson Introduce a structure to track the individual forcewake domains and use that to eliminate duplicate logic. v2: - Rebase on latest dinq (Mika) - for_each_fw_domain macro (Mika) - Handle reset atomically, keeping the timer running (Mika) - for_each_fw_domain paramete

[Intel-gfx] [PATCH 2/9] drm/i915: Assert that runtime pm is active on user fw access

2015-01-16 Thread Mika Kuoppala
From: Chris Wilson On user forcewake access, assert that runtime pm reference is held. Fix and cleanup the callsites accordingly. v2: Remove intel_runtime_pm_get() rebasehap (Deepak) v3: use drivers own runtime state tracking as pm_runtime_active() will return wrong results when we are in r

[Intel-gfx] [PATCH 6/9] drm/i915: Make vlv and chv forcewake put generic.

2015-01-16 Thread Mika Kuoppala
From: Mika Kuoppala These two were using a fw dance logic where posting read was done after both domain bit were set. When in other gens, the posting read is done immediately after setting the forcewake bit for each domain. Now bring these in line with other gens. Signed-off-by: Mika Kuoppala

[Intel-gfx] [PATCH 7/9] drm/i915: Rename the forcewake get/put functions

2015-01-16 Thread Mika Kuoppala
From: Mika Kuoppala We have multiple forcewake domains now on recent gens. Change the function naming to reflect this. v2: More verbose names (Chris) v3: Rebase v4: Rebase v5: Add documentation for forcewake_get/put Signed-off-by: Mika Kuoppala Reviewed-by: Deepak S (v2) --- drivers/gpu/drm/

[Intel-gfx] [PATCH 9/9] drm/i915: Rename i915_gen6_forcewake_count_info

2015-01-16 Thread Mika Kuoppala
From: Mika Kuoppala There are multiple forcewake domains in newer architectures. Rename 'i915_gen6_forcewake_count_info' debugfs entry to 'i915_forcewake_domains' to reflect this. Signed-off-by: Mika Kuoppala --- drivers/gpu/drm/i915/i915_debugfs.c | 6 +++--- 1 file changed, 3 insertions(+),

[Intel-gfx] [PATCH 3/9] drm/i915: Skip uncore lock on earlier gens

2015-01-16 Thread Mika Kuoppala
From: Chris Wilson With gen < 6 we don't need to take uncore lock as we don't have anything to protect from concurrent access. v2: rebase and account for gen9 changes Signed-off-by: Chris Wilson (v1) Signed-off-by: Mika Kuoppala Reviewed-by: Deepak S --- drivers/gpu/drm/i915/intel_uncore.c

[Intel-gfx] [PATCH 8/9] drm/i915: Enum forcewake domains and domain identifiers

2015-01-16 Thread Mika Kuoppala
From: Mika Kuoppala Make the domains and domain identifiers enums. To emphasize the difference in order to avoid mistakes. v2: s/fw_domain/forcewake_domain (Jani) v3: rebase Suggested-by: Daniel Vetter Signed-off-by: Mika Kuoppala Reviewed-by: Deepak S (v1) --- drivers/gpu/drm/i915/i915_drv

[Intel-gfx] [PATCH 5/9] drm/i915: Consolidate forcewake code

2015-01-16 Thread Mika Kuoppala
From: Mika Kuoppala As we now have forcewake domains, take advantage of it by putting the differences in gen fw handling in data rather than in code. In past we have opencoded this quite extensively as the fw handling is in the fast path. There has also been a lot of cargo-culted copy'n'pasting

[Intel-gfx] [PATCH 1/9] drm/i915: Rebalance runtime pm vs forcewake

2015-01-16 Thread Mika Kuoppala
From: Chris Wilson Calling intel_runtime_pm_put() is illegal from a soft-irq context, so revert the crude hack commit aa0b3b5bb8768c1a6a6788869d9c7015eae7e80c Author: Paulo Zanoni Date: Tue Apr 1 14:55:07 2014 -0300 drm/i915: don't schedule force_wake_timer at gen6_read and apply the si

[Intel-gfx] [PATCH i-g-t v2] tools/intel_gpu_frequency: remove use of getsubopt

2015-01-16 Thread tim . gore
From: Tim Gore getsubopt is not available in android. The "get" option doesn't really need sub-options, just display all the current frequency settings (as per discussion with Ben Widawsky) Signed-off-by: Tim Gore --- man/intel_gpu_frequency.man | 6 +++--- tools/intel_gpu_frequency.c | 29 ++

Re: [Intel-gfx] [PATCH 6/7] drm/i915: Improve how the memory for crtc state is allocated

2015-01-16 Thread Ander Conselvan de Oliveira
On 01/15/2015 08:50 PM, Matt Roper wrote: On Thu, Jan 15, 2015 at 02:55:26PM +0200, Ander Conselvan de Oliveira wrote: The previous patch changed the config field in intel_crtc to a pointer, but to keep the mechanical changes (done with spatch) separate from the new code, the pointer was made to

[Intel-gfx] [PATCH] drm/i915/skl: Enabling PSR on Skylake

2015-01-16 Thread Sonika Jindal
Mainly taking care of some register offsets, otherwise things are similar to hsw. Also, programming ddi aux to use hardcoded values for psr data select. v2: introduce EDP_PSR_AUX_BASE macro (Chris) v3: Moving to HW tracking for SKL+ platforms, so activating source psr during psr_enabling and then