- 06 Apr, 2016 40 commits
-
-
Alex Deucher authored
BugLink: http://bugs.launchpad.net/bugs/1546572 So they can be used by powerplay. Reviewed-by:
Eric Huang <JinHuiEric.Huang@amd.com> Signed-off-by:
Alex Deucher <alexander.deucher@amd.com> (cherry picked from commit e3b04bc7) Signed-off-by:
Alberto Milone <alberto.milone@canonical.com> Signed-off-by:
Tim Gardner <tim.gardner@canonical.com>
-
Alex Deucher authored
BugLink: http://bugs.launchpad.net/bugs/1546572 Leftover from radeon. Reviewed-by:
-
Alex Deucher authored
BugLink: http://bugs.launchpad.net/bugs/1546572 Needed to pass the cg and pg info to powerplay. Reviewed-by:
-
Alex Deucher authored
BugLink: http://bugs.launchpad.net/bugs/1546572 Not working reliably yet. Reviewed-by:
-
Alex Deucher authored
BugLink: http://bugs.launchpad.net/bugs/1546572 Not working reliably yet. Reviewed-by:
-
Alex Deucher authored
BugLink: http://bugs.launchpad.net/bugs/1546572 Not working reliably yet. Reviewed-by:
-
Alex Deucher authored
BugLink: http://bugs.launchpad.net/bugs/1546572 Not working reliably yet. Reviewed-by:
-
Alex Deucher authored
BugLink: http://bugs.launchpad.net/bugs/1546572 Don't do anything if the uvd cg flags are not set. Reviewed-by:
-
Alex Deucher authored
BugLink: http://bugs.launchpad.net/bugs/1546572 It was already disabled elsewhere, make it offical. Reviewed-by:
-
Alex Deucher authored
BugLink: http://bugs.launchpad.net/bugs/1546572 Don't attempt to start/stop the vce block if pg is disabled. Reviewed-by:
-
Alex Deucher authored
BugLink: http://bugs.launchpad.net/bugs/1546572 Don't attempt to start/stop the uvd block if pg is disabled. Reviewed-by:
-
Alex Deucher authored
BugLink: http://bugs.launchpad.net/bugs/1546572 We already query this at driver init, so use that info. Also handles virtualization cases. Reviewed-by:
monk liu <monk.liu@amd.com> Signed-off-by:
-
Alex Deucher authored
BugLink: http://bugs.launchpad.net/bugs/1546572 Pcie registers may not be available in a virtualized environment. Reviewed-by:
-
Alex Deucher authored
BugLink: http://bugs.launchpad.net/bugs/1546572 Allows the user to force the supported pcie gen and lane config on both the asic and the chipset. Useful for debugging pcie problems and for virtualization where we may not be able to query the pcie bridge caps. Default to: gen: chipset 1/2, asic 1/2/3 lanes: 1/2/4/8/16 v2: fix bare metal case Reviewed-by:
-
Alex Deucher authored
BugLink: http://bugs.launchpad.net/bugs/1546572 Doesn't work properly yet. Reviewed-by:
Christian König <christian.koenig@amd.com> Reviewed-by:
Sonny Jiang <sonny.jiang@amd.com> Signed-off-by:
-
Alex Deucher authored
BugLink: http://bugs.launchpad.net/bugs/1546572 The smc doesn't handle it. Reviewed-by:
Ken Wang <Qingqing.Wang@amd.com> Reviewed-by:
-
Alex Deucher authored
BugLink: http://bugs.launchpad.net/bugs/1546572 Enable CP register/instruction error interrupts. Useful for debugging command stream problems. Reviewed-by:
-
Alex Deucher authored
BugLink: http://bugs.launchpad.net/bugs/1546572 Enable CP register/instruction error interrupts. Useful for debugging command stream problems. Reviewed-by:
-
Oded Gabbay authored
BugLink: http://bugs.launchpad.net/bugs/1546572Reviewed-by:
Michel Dänzer <michel.daenzer@amd.com> Signed-off-by:
Oded Gabbay <oded.gabbay@gmail.com> Signed-off-by:
-
Nicolai Hähnle authored
BugLink: http://bugs.launchpad.net/bugs/1546572 This fixes a race condition in the error case: since the pt bos have not necessarily been reserved in case of an error, we could move a pt bo that is currently in the middle of being evicted/moved by another process, which then resulted in a BUG_ON in ttm_bo_add_to_lru. Reviewed-by:
Nicolai Hähnle <nicolai.haehnle@amd.com> Reviewed-by:
-
Amitoj Kaur Chawla authored
BugLink: http://bugs.launchpad.net/bugs/1546572 Remove an unnecassary cast in the argument to kfree. Found using Coccinelle. The semantic patch used to find this is as follows: //<smpl> @@ type T; expression *f; @@ - kfree((T *)(f)); + kfree(f); //</smpl> Signed-off-by:
Amitoj Kaur Chawla <amitoj1606@gmail.com> Signed-off-by:
-
Colin Ian King authored
BugLink: http://bugs.launchpad.net/bugs/1546572 amdgpu_amdkfd_gfx_7_get_functions and amdgpu_amdkfd_gfx_8_0_get_functions have no parameters, so use the normal void parameter convention to make them match their prototypes in the header file drivers/gpu/drm/amd/amdgpu/amdgpu_amdkfd.h Signed-off-by:
Colin Ian King <colin.king@canonical.com> Signed-off-by:
-
Rex Zhu authored
BugLink: http://bugs.launchpad.net/bugs/1546572 Fix firmware init on Stoney when powerplay is enabled. Signed-off-by:
Rex Zhu <Rex.Zhu@amd.com> Reviewed-by:
-
Alex Deucher authored
BugLink: http://bugs.launchpad.net/bugs/1546572 Don't init fbdev if we don't have connectors. E.g., if you have a PX laptop with the displays attached to an IGP with no driver support, you may end up with a blank screen rather than falling back to vesa, etc. Based on a similar radeon patch from Rob Clark. Signed-off-by:
-
Rob Clark authored
BugLink: http://bugs.launchpad.net/bugs/1546572 This fixes an issue that was noticed on an optimus/prime laptop with a kernel that was old enough to not support the integrated intel gfx (which was driving all the outputs), but did have support for the discrete radeon gpu. The end result was not falling back to VESA and leaving the user with a black screen. (Plus it is kind of silly to create an framebuffer device if there are no outputs hooked up to the gpu.) Signed-off-by:
Rob Clark <robdclark@gmail.com> Signed-off-by:
-
Matthew Dawson authored
BugLink: http://bugs.launchpad.net/bugs/1546572 Found with lockdep while testing gpu reset. Reviewed-by:
Matthew Dawson <matthew@mjdsystems.ca> Signed-off-by:
-
Christian König authored
BugLink: http://bugs.launchpad.net/bugs/1546572 That somehow got lost. Signed-off-by:
Chunming Zhou <david1.zhou@amd.com> Acked-by:
-
Alex Deucher authored
BugLink: http://bugs.launchpad.net/bugs/1546572 Makes it clear to the user which power management path is in use. v2: make consistent with dpm Reviewed-by:
Tom St Denis <tom.stdenis@amd.com> Signed-off-by:
-
Eric Huang authored
BugLink: http://bugs.launchpad.net/bugs/1546572 The two macros returns are values which probably are used in the expression of calculation. Without the brackets the result of the expression may be wrong. v2: agd: squash both patches together Reviewed-by:
-
John Keeping authored
BugLink: http://bugs.launchpad.net/bugs/1546572 The Rockchip driver cannot use drm_atomic_helper_wait_for_vblanks() because it has hardware counters for neither vblanks nor scanlines. In order to simplify re-implementing the functionality for this driver, export the framebuffer_changed() helper so it can be reused. Signed-off-by:
John Keeping <john@metanate.com> Reviewed-by:
Daniel Vetter <daniel.vetter@ffwll.ch> (cherry picked from commit c240906d) Signed-off-by:
-
Jordan Lazare authored
BugLink: http://bugs.launchpad.net/bugs/1546572 Avoid setting pp_enabled if there is no powerplay implementation. Signed-off-by:
Jordan Lazare <Jordan.Lazare@amd.com> Reviewed-by:
-
Alex Deucher authored
BugLink: http://bugs.launchpad.net/bugs/1546572 Hopefully we can enable this by default once we get more upstream feedback on stability, etc. Signed-off-by:
-
Michel Dänzer authored
BugLink: http://bugs.launchpad.net/bugs/1546572 It can be big, depending on the VM address space size, which is tunable via the vm_size module parameter. Bugzilla: https://bugs.freedesktop.org/show_bug.cgi?id=93721Reviewed-by:
-
Borislav Petkov authored
BugLink: http://bugs.launchpad.net/bugs/1546572 8f1d57c1 ("amdkfd: don't open-code memdup_user()") mistakenly uses an uninitialized local pointer, gcc complains: drivers/gpu/drm/amd/amdkfd/kfd_chardev.c: In function ‘kfd_ioctl_dbg_address_watch’: drivers/gpu/drm/amd/amdkfd/kfd_chardev.c:562:12: warning: ‘args_buff’ may be used uninitialized in this function [-Wmaybe-uninitialized] args_buff = memdup_user(args_buff, ^ Fix it. Signed-off-by:
Borislav Petkov <bp@suse.de> Cc: Al Viro <viro@zeniv.linux.org.uk> Signed-off-by:
Al Viro <viro@zeniv.linux.org.uk> (cherry picked from commit 39c01bf9) Signed-off-by:
-
Al Viro authored
BugLink: http://bugs.launchpad.net/bugs/1546572Signed-off-by:
-
Alex Deucher authored
BugLink: http://bugs.launchpad.net/bugs/1546572Reviewed-by:
Junwei Zhang <Jerry.Zhang@amd.com> Reviewed-by:
-
Maxime Ripard authored
BugLink: http://bugs.launchpad.net/bugs/1546572 The drm_fbdev_cma_init function always calls the drm_helper_disable_unused_functions. Since it's part of the usual probe process, all the drivers using that helper will end up having their encoder and CRTC disable functions called at probe if their device has not been reported as enabled. This could be fixed by reading out from the registers the current state of the device if it is enabled, but even that will not handle the case where the device is actually disabled. Moreover, the drivers using the atomic modesetting expect that their enable and disable callback to be called when the device is already enabled or disabled (respectively). We can however fix this issue by moving the call to drm_helper_disable_unused_functions out of drm_fbdev_cma_init and make the drivers needing it (all the drivers calling drm_fbdev_cma_init and not using the atomic modesetting) explicitly call it. Signed-off-by:
Maxime Ripard <maxime.ripard@free-electrons.com> Link: http://patchwork.freedesktop.org/patch/msgid/1452785109-6172-14-git-send-email-maxime.ripard@free-electrons.comAcked-by:
Laurent Pinchart <laurent.pinchart@ideasonboard.com> Signed-off-by:
-
Dave Airlie authored
BugLink: http://bugs.launchpad.net/bugs/1546572 this fixes the build on arm. Signed-off-by:
Dave Airlie <airlied@redhat.com> (cherry picked from commit e9c5e740) Signed-off-by:
-
Christian König authored
BugLink: http://bugs.launchpad.net/bugs/1546572 Most VM BOs end up in the duplicates list, validate it first make -ENOMEM less likely. Signed-off-by:
-
Christian König authored
BugLink: http://bugs.launchpad.net/bugs/1546572 This makes it less likely to run into an ENOMEM because VM page tables are evicted last. v2: move the BOs in the LRU tail after validation Signed-off-by:
-
