- 29 Jul, 2016 38 commits
-
-
Christian König authored
This fixes turning power and clock on when it is actually needed. Signed-off-by:
Christian König <christian.koenig@amd.com> Reviewed-by:
Edward O'Callaghan <funfunctor@folklore1984.net> Signed-off-by:
Alex Deucher <alexander.deucher@amd.com>
-
Christian König authored
This fixes turning power and clock on when it is actually needed. Signed-off-by:
-
Christian König authored
For manual UVD/VCE power and clock gating. Signed-off-by:
-
Christian König authored
Was never used as far as I can see. Signed-off-by:
Chunming Zhou <david1.zhou@amd.com> Reviewed-by:
-
Christian König authored
Signed-off-by:
-
Rex Zhu authored
Signed-off-by:
Rex Zhu <Rex.Zhu@amd.com> Reviewed-by:
Eric Huang <JinhuiEric.Huang@amd.com> Signed-off-by:
-
Rex Zhu authored
Signed-off-by:
-
Rex Zhu authored
This reverts commit <2ded8c7f04825bc5cde2624f6aa83f1ff62672c0> As we enabled bypass mode for uvd on polaris10 when clockgating. so no need to set uvd clock manually. Signed-off-by:
-
Rex Zhu authored
Signed-off-by:
-
jimqu authored
Signed-off-by:
JimQu <Jim.Qu@amd.com> Reviewed-by:
Michel Dänzer <michel.daenzer@amd.com> Signed-off-by:
-
Christian König authored
We need to check on Polaris if UVD session context is allowed or not. Signed-off-by:
-
Christian König authored
Starting with Stoney we support running UVD in VM mode as well. v2: rebased, only enable on Polaris for now. Signed-off-by:
-
Nils Wallménius authored
Signed-off-by:
Nils Wallménius <nils.wallmenius@gmail.com> Signed-off-by:
-
Nils Wallménius authored
This introduces some warnings due to unused functions, that are deleted in the following commit. Signed-off-by:
-
Bhaktipriya Shridhar authored
alloc_workqueue replaces deprecated create_singlethread_workqueue(). Each hardware CRTC has a single flip work queue. When a radeon_flip_work_func item is queued, it needs to be executed ASAP because even a slight delay may cause the flip to be delayed by one refresh cycle. Hence, a dedicated workqueue with WQ_HIGHPRI set, has been used here since a delay can cause the outcome to miss the refresh cycle. Since there are only a fixed number of work items, explicit concurrency limit is unnecessary here. Reviewed-by:
Tejun Heo <tj@kernel.org> Signed-off-by:
Bhaktipriya Shridhar <bhaktipriya96@gmail.com> Signed-off-by:
-
SF Markus Elfring authored
The variable "result" will be set to an appropriate value a bit later. Thus omit the explicit initialisation at the beginning. Reviewed-by:
Markus Elfring <elfring@users.sourceforge.net> Signed-off-by:
-
Markus Elfring authored
The variable "temp_storage" was eventually reassigned with a pointer. Thus omit the explicit initialisation at the beginning. v2: agd: fix coding style Reviewed-by:
-
Markus Elfring authored
Indicate successful function execution only at the end. Thus omit initialisation for the variable "result" at the beginning. Reviewed-by:
-
Markus Elfring authored
The variable "argument" will be set to an appropriate value a bit later. Thus omit the explicit initialisation at the beginning. Reviewed-by:
-
Markus Elfring authored
The local variable "func_no" was assigned a value at two places. But it was not read within this function. Thus delete it. Reviewed-by:
-
Markus Elfring authored
The kfree() function was called in one case by the amdgpu_cgs_acpi_eval_object() function during error handling even if the passed variable "obj" contained a null pointer. * Adjust jump targets according to the Linux coding style convention. * Delete unnecessary initialisations for the variables "obj" and "params" then. Reviewed-by:
-
Markus Elfring authored
The drm_gem_object_unreference_unlocked() function tests whether its argument is NULL and then returns immediately. Thus the test around the call is not needed. This issue was detected by using the Coccinelle software. Reviewed-by:
-
Markus Elfring authored
The drm_gem_object_unreference_unlocked() function tests whether its argument is NULL and then returns immediately. Thus the test around the call is not needed. This issue was detected by using the Coccinelle software. Signed-off-by:
-
Edward O'Callaghan authored
Found-by: Coccinelle Signed-off-by:
Tom St Denis <tom.stdenis@amd.com> Reviewed-by:
-
Edward O'Callaghan authored
V.2: Fixup by hand to remove a few instances of redundant '()' left over. Found-by: Coccinelle Signed-off-by:
-
Edward O'Callaghan authored
Found-by: Coccinelle Signed-off-by:
-
Edward O'Callaghan authored
Found-by: Coccinelle Signed-off-by:
-
Edward O'Callaghan authored
Found-by: Coccinelle Signed-off-by:
-
Edward O'Callaghan authored
Found-by: Coccinelle Signed-off-by:
-
Edward O'Callaghan authored
Found-by: Coccinelle Signed-off-by:
-
Rex Zhu authored
DIDT is a power saving feature which helps limit power consumption in order to hit a target power allocation. v1: delete temp file added accidentally. Signed-off-by:
-
Rex Zhu authored
Signed-off-by:
-
Alex Deucher authored
This fixes a warning on big endian. Bitfields need to be handled properly. Cc: Arnd Bergmann <arnd@arndb.de> Acked-by:
Arnd Bergmann <arnd@arndb.de> Signed-off-by:
-
Alex Deucher authored
The message is harmless and confusing. On PX systems, there is one ATIF method, but potentially multiple GPUs leading to an error on the GPU with no backlight control. Bug: https://bugzilla.kernel.org/show_bug.cgi?id=115011Signed-off-by:
-
Nicholas Mc Guire authored
commit d967be9b ("drm/radeon/ci: disable needless sclk changes") introduces an unreachable if(C != C) conditional code section flagged by coccinelle script bad_conditional.cocci: Add a comment to make it clear that this is intentional. Fixes: d967be9b ("drm/radeon/ci: disable needless sclk changes") Signed-off-by:
Nicholas Mc Guire <hofrat@osadl.org> Signed-off-by:
-
Lyude authored
Just about all of amdgpu's connector probing functions try to acquire runtime PM refs. If we try to do this in the context of amdgpu_resume_kms by calling drm_helper_hpd_irq_event(), we end up deadlocking the system. Since we're guaranteed to be holding the spinlock for RPM in amdgpu_resume_kms, and we already know the GPU is in working order, we need to prevent the RPM helpers from trying to run during the initial connector reprobe on resume. There's a couple of solutions I've explored for fixing this, but this one by far seems to be the simplest and most reliable (plus I'm pretty sure that's what disable_depth is there for anyway). Reproduction recipe: - Get any laptop dual GPUs using PRIME - Make sure runtime PM is enabled for amdgpu - Boot the machine - If the machine managed to boot without hanging, switch out of X to another VT. This should definitely cause X to hang infinitely. Changes since v1: - add appropriate #ifdef checks for CONFIG_PM. This is not very useful, but it appears some kernel test suites test compiling amdgpu with CONFIG_PM disabled, which results in this patch breaking the builds if we don't include this #ifdef Cc: stable@vger.kernel.org Cc: Alex Deucher <alexdeucher@gmail.com> Reviewed-by:Lyude <cpaul@redhat.com> Signed-off-by:
-
Alex Deucher authored
If we do it at enable time, it's too late for the feature checks. v2: drop .init setting as per Peter's comments bug: https://bugzilla.kernel.org/show_bug.cgi?id=115321Reviewed-by:
Peter Wu <peter@lekensteyn.nl> Signed-off-by:
-
Alex Deucher authored
If we do it at enable time, it's too late for the feature checks. v2: drop .init setting as per Peter's comments Reviewed-by:
-
- 28 Jul, 2016 2 commits
-
-
Alex Deucher authored
Some of the checks didn't handle frev 2 tables properly. amdgpu doesn't support any tables pre-frev 2, so drop the checks. Signed-off-by: -
Alex Deucher authored
Some of the checks didn't handle frev 2 tables properly. Signed-off-by:
-
