- Aug 13, 2015
-
-
Thierry Reding authored
Support low-active hotplug detect signals by storing the GPIO flags parsed from device tree. Signed-off-by:
Thierry Reding <treding@nvidia.com>
-
Thierry Reding authored
Use this macro to reduce some of the boilerplate. Signed-off-by:
Thierry Reding <treding@nvidia.com>
-
Thierry Reding authored
Signed-off-by:
Thierry Reding <treding@nvidia.com>
-
- Jul 03, 2015
-
-
Shixin Zeng authored
The length of each EDID block is EDID_LENGTH, and number of blocks is (1 + edid->extensions) - we need to multiply not add them. This causes wrong EDID to be passed on, and is a regression introduced by d2ed3436 (drm: Introduce helper for replacing blob properties) Signed-off-by:
Shixin Zeng <zeng.shixin@gmail.com> Cc: Daniel Stone <daniels@collabora.com> Cc: Maarten Lankhorst <maarten.lankhorst@linux.intel.com> Reviewed-by:
Daniel Stone <daniels@collabora.com> [danvet: Add Cc: and fix commit summary.] Signed-off-by:
Daniel Vetter <daniel.vetter@ffwll.ch>
-
- Jul 01, 2015
-
-
Pekka Enberg authored
Use kvfree() instead of open-coding it. Signed-off-by:
Pekka Enberg <penberg@kernel.org> Cc: David Airlie <airlied@linux.ie> Signed-off-by:
Andrew Morton <akpm@linux-foundation.org> Signed-off-by:
Linus Torvalds <torvalds@linux-foundation.org>
-
- Jun 30, 2015
-
-
Ander Conselvan de Oliveira authored
Similarly to what is done for SKL, clear the dpll_hw_state of the pipe config in hsw_dp_set_ddi_pll_sel(), since it main contain stale values. That can happen if a crtc that was previously driving an HDMI connector switches to a DP connector. In that case, the wrpll field was left with its old value, leading to warnings like the one below: [drm:check_crtc_state [i915]] *ERROR* mismatch in dpll_hw_state.wrpll (expected 0xb035061f, found 0x00000000) ------------[ cut here ]------------ WARNING: CPU: 1 PID: 767 at drivers/gpu/drm/i915/intel_display.c:12324 check_crtc_state+0x975/0x10b0 [i915]() pipe state doesn't match! This regression was indroduced in commit dd3cd74a Author: Ander Conselvan de Oliveira <ander.conselvan.de.oliveira@intel.com> Date: Fri May 15 13:34:29 2015 +0300 drm/i915: Don't overwrite (e)DP PLL selection on SKL Reported-by:
Linus Torvalds <torvalds@linux-foundation.org> Signed-off-by:
Ander Conselvan de Oliveira <ander.conselvan.de.oliveira@intel.com> Tested-by:
Jani Nikula <jani.nikula@intel.com> Reviewed-by:
Daniel Vetter <daniel.vetter@ffwll.ch> Signed-off-by:
Jani Nikula <jani.nikula@intel.com>
-
Alex Deucher authored
Avoids a crash on pre-DP asics that support HDMI. Signed-off-by:
Alex Deucher <alexander.deucher@amd.com> Cc: stable@vger.kernel.org
-
- Jun 29, 2015
-
-
Christian König authored
Signed-off-by:
Christian König <christian.koenig@amd.com> Reviewed-by:
Alex Deucher <alexander.deucher@amd.com>
-
Christian König authored
v2: remove unrelated whitespace change, fix C comment Signed-off-by:
Christian König <christian.koenig@amd.com> Reviewed-by:
Alex Deucher <alexander.deucher@amd.com>
-
Christian König authored
And use common fence infrastructure for the wait. Signed-off-by:
Christian König <christian.koenig@amd.com> Reviewed-by:
Alex Deucher <alexander.deucher@amd.com> Reviewed-by:
Chunming Zhou <david1.zhou@amd.com>
-
Alexander Kuleshov authored
If the CONFIG_DEBUG_FS is not selected, compilation of the drivers/gpu/drm/amd/amdgpu/amdgpu_device.c provides two warnings that amdgpu_debugfs_regs_init and amdgpu_debugfs_regs_cleanup are used but never defined. And as result: ERROR: "amdgpu_debugfs_regs_cleanup" [drivers/gpu/drm/amd/amdgpu/amdgpu.ko] undefined! ERROR: "amdgpu_debugfs_regs_init" [drivers/gpu/drm/amd/amdgpu/amdgpu.ko] undefined! ^ Reviewed-by:
Christian König <christian.koenig@amd.com> Signed-off-by:
Alexander Kuleshov <kuleshovmail@gmail.com> Signed-off-by:
Alex Deucher <alexander.deucher@amd.com>
-
Alex Deucher authored
This reverts commit b9729b17. This seems to break the cursor on resume for lots of systems. Cc: stable@vger.kernel.org
-
Sonny Jiang authored
Fixes a hang on resume. Signed-off-by:
Sonny Jiang <sonny.jiang@amd.com> Reviewed-by:
Alex Deucher <alexander.deucher@amd.com>
-
Sonny Jiang authored
Signed-off-by:
Sonny Jiang <sonny.jiang@amd.com> Reviewed-by:
Alex Deucher <alexander.deucher@amd.com>
-
Alex Deucher authored
Remove duplication across asic families and make it symmetric with the freeing of the code in amdgpu_device.c Reviewed-by:
Christian König <christian.koenig@amd.com> Signed-off-by:
Alex Deucher <alexander.deucher@amd.com>
-
Maninder Singh authored
kfree(NULL) is safe and this check is probably not required Signed-off-by:
Maninder Singh <maninder1.s@samsung.com> Reviewed-by:
Vaneet Narang <v.narang@samsung.com> Reviewed-by:
Christian Konig <christian.koenig@amd.com> Signed-off-by:
Alex Deucher <alexander.deucher@amd.com>
-
Maninder Singh authored
Use kzalloc rather than kcalloc(1.. for allocating one thing. Signed-off-by:
Maninder Singh <maninder1.s@samsung.com> Reviewed-by:
Vaneet Narang <v.narang@samsung.com> Reviewed-by:
Christian Konig <christian.koenig@amd.com> Signed-off-by:
Alex Deucher <alexander.deucher@amd.com>
-
Christian König authored
We only should do so when the BO_VA was actually mapped. Otherwise we get a nice error message on the next CS. v2: It actually doesn't matter if it was invalidated or not, if it was mapped we need to clear the area where it was mapped. Signed-off-by:
Christian König <christian.koenig@amd.com> Tested-by: Michel Dänzer <michel.daenzer@amd.com> (v1) Signed-off-by:
Alex Deucher <alexander.deucher@amd.com>
-
Christian König authored
Signed-off-by:
Christian König <christian.koenig@amd.com> Reviewed-by:
Alex Deucher <alexander.deucher@amd.com>
-
Christian König authored
Signed-off-by:
Christian König <christian.koenig@amd.com> Reviewed-by:
Alex Deucher <alexander.deucher@amd.com>
-
Sonny Jiang authored
This patch is to resolve compute hang at resume time. v2: (agd5f) squash in second fix Signed-off-by:
Sonny Jiang <sonny.jiang@amd.com> Reviewed-by:
Christian König <christian.koenig@amd.com>
-
Christian König authored
Signed-off-by:
Christian König <christian.koenig@amd.com> Reviewed-by:
Leo Liu <leo.liu@amd.com>
-
Christian König authored
Port of radeon commit 29c63fe2. Signed-off-by:
Christian König <christian.koenig@amd.com> Reviewed-by:
Leo Liu <leo.liu@amd.com>
-
Christian König authored
port of radeon commit 2fc5703a. Signed-off-by:
Christian König <christian.koenig@amd.com> Reviewed-by:
Leo Liu <leo.liu@amd.com>
-
Christian König authored
Signed-off-by:
Christian König <christian.koenig@amd.com> Reviewed-by:
Leo Liu <leo.liu@amd.com>
-
monk.liu authored
Signed-off-by:
monk.liu <monk.liu@amd.com> Reviewed-by:
Christian König <christian.koenig@amd.com>
-
Christian König authored
Signed-off-by:
Christian König <christian.koenig@amd.com> Acked-by:
Alex Deucher <aleander.deucher@amd.com>
-
Christian König authored
Signed-off-by:
Christian König <christian.koenig@amd.com> Acked-by:
Alex Deucher <aleander.deucher@amd.com>
-
Christian König authored
Signed-off-by:
Christian König <christian.koenig@amd.com> Acked-by:
Alex Deucher <aleander.deucher@amd.com>
-
Christian König authored
Signed-off-by:
Christian König <christian.koenig@amd.com> Reviewed-by:
Alex Deucher <aleander.deucher@amd.com>
-
Jérôme Glisse authored
In order for hibernation to reliably work we need to properly turn off the SDMA block, sadly after numerous attemps i haven't not found proper sequence for clean and full shutdown. So simply reset both SDMA block, this makes hibernation works reliably on sea island GPU family (CI) Hibernation and suspend to ram were tested (several times) on : Bonaire Hawaii Mullins Kaveri Kabini Cc: stable@vger.kernel.org Signed-off-by:
Jérôme Glisse <jglisse@redhat.com> Reviewed-by:
Christian König <christian.koenig@amd.com> Signed-off-by:
Alex Deucher <alexander.deucher@amd.com>
-
Jérôme Glisse authored
In order for hibernation to reliably work we need to cleanup more thoroughly the compute ring. Hibernation is different from suspend resume as when we resume from hibernation the hardware is first fully initialize by regular kernel then freeze callback happens (which correspond to a suspend inside the radeon kernel driver) and turn off each of the block. It turns out we were not cleanly shutting down the compute ring. This patch fix that. Hibernation and suspend to ram were tested (several times) on : Bonaire Hawaii Mullins Kaveri Kabini Changed since v1: - Factor the ring stop logic into a function taking ring as arg. Cc: stable@vger.kernel.org Signed-off-by:
Jérôme Glisse <jglisse@redhat.com> Reviewed-by:
Christian König <christian.koenig@amd.com> Signed-off-by:
Alex Deucher <alexander.deucher@amd.com>
-
Ben Goz authored
Signed-off-by:
Ben Goz <ben.goz@amd.com> Acked-by:
Oded Gabbay <oded.gabbay@amd.com> Signed-off-by:
Alex Deucher <alexander.deucher@amd.com>
-
Ben Goz authored
v2: add missing MTYPE_NONCACHED enum Signed-off-by:
Ben Goz <ben.goz@amd.com> Acked-by:
Oded Gabbay <oded.gabbay@amd.com> Reviewed-by:
Alex Deucher <alexander.deucher@amd.com> Signed-off-by:
Alex Deucher <alexander.deucher@amd.com>
-
Maninder Singh authored
Use kzalloc for allocating one thing rather than kcalloc(1... The semantic patch that makes this change is as follows: // <smpl> @@ @@ - kcalloc(1, + kzalloc( ...) // </smpl> Signed-off-by:
Maninder Singh <maninder1.s@samsung.com> Reviewed-by:
Vaneet Narang <v.narang@samsung.com> Reviewed-by:
Christian König <christian.koenig@amd.com> Signed-off-by:
Alex Deucher <alexander.deucher@amd.com>
-
Alex Deucher authored
Spotted by Dan Carpenter. This is a slight variant of his fix. Signed-off-by:
Alex Deucher <alexander.deucher@amd.com>
-
Jani Nikula authored
Some 855gm models (at least ThinkPad X40) regressed because of commit b0cd324f Author: Jani Nikula <jani.nikula@intel.com> Date: Wed Nov 12 16:25:43 2014 +0200 drm/i915: don't save/restore backlight hist ctl registers which tried to make our driver more robust by not blindly saving and restoring registers, but it failed to take into account commit 0eb96d6e Author: Jesse Barnes <jbarnes@virtuousgeek.org> Date: Wed Oct 14 12:33:41 2009 -0700 drm/i915: save/restore BLC histogram control reg across suspend/resume Fix the regression by enabling hist ctl on gen2. v2: Improved the comment. v3: Improved the comment, again. Reported-and-tested-by:
Philipp Gesang <phg@phi-gamma.net> References: http://mid.gmane.org/20150623222648.GD12335@acheron Fixes: b0cd324f ("drm/i915: don't save/restore backlight hist ctl registers") Cc: Ville Syrjälä <ville.syrjala@linux.intel.com> Cc: stable@vger.kernel.org Acked-by:
Chris Wilson <chris@chris-wilson.co.uk> Signed-off-by:
Jani Nikula <jani.nikula@intel.com>
-
- Jun 26, 2015
-
-
Michel Thierry authored
If for some reason [1], the page directory/table does not exist, clear_range would end up in an infinite while loop. Introduced by commit 06fda602 ("drm/i915: Create page table allocators"). [1] This is already being addressed in one of Mika's patches: http://mid.gmane.org/1432314314-23530-17-git-send-email-mika.kuoppala@intel.com Cc: Mika Kuoppala <mika.kuoppala@linux.intel.com> Cc: stable@vger.kernel.org Reported-by:
John Harrison <john.c.harrison@intel.com> Signed-off-by:
Michel Thierry <michel.thierry@intel.com> Reviewed-by:
Mika Kuoppala <mika.kuoppala@intel.com> Signed-off-by:
Jani Nikula <jani.nikula@intel.com>
-
Rodrigo Vivi authored
We cannot let IPS enabled with no plane on the pipe: BSpec: "IPS cannot be enabled until after at least one plane has been enabled for at least one vertical blank." and "IPS must be disabled while there is still at least one plane enabled on the same pipe as IPS." This restriction apply to HSW and BDW. However a shortcut path on update primary plane function to make primary plane invisible by setting DSPCTRL to 0 was leting IPS enabled while there was no other plane enabled on the pipe causing flickerings that we were believing that it was caused by that other restriction where ips cannot be used when pixel rate is greater than 95% of cdclok. v2: Don't mess with Atomic path as pointed out by Ville. Reference: https://bugs.freedesktop.org/show_bug.cgi?id=85583 Cc: Ville Syrjälä <ville.syrjala@linux.intel.com> Cc: Paulo Zanoni <paulo.r.zanoni@intel.com> Cc: stable@vger.kernel.org Signed-off-by:
Rodrigo Vivi <rodrigo.vivi@intel.com> Reviewed-by:
Ville Syrjälä <ville.syrjala@linux.intel.com> Signed-off-by:
Jani Nikula <jani.nikula@intel.com>
-
Lukas Wunner authored
On the MacBook Pro, power of the gpu is cut by a gmux chip. Sometimes the gpu gets stuck in powersaving mode and refuses to wake up ("Refused to change power state, currently in D3"). Inserting a delay between setting the gpu to D3hot and cutting the power seems to help (most of the time). This issue and its (partial) remediation by the patch was observed with an Nvidia GT650M (NVE7 / GK107). Signed-off-by:
Lukas Wunner <lukas@wunner.de> Signed-off-by:
Dave Airlie <airlied@redhat.com>
-