- 15 May, 2018 11 commits
-
-
Leo (Sunpeng) Li authored
Input transfer function creation is now done when the plane is created. This is done within the following change: Author: Anthony Koo <Anthony.Koo@amd.com> drm/amd/display: Have DC manage its own allocation of gamma Therefore, we no longer need to create it when filling in the plane attributes. Signed-off-by:Leo (Sunpeng) Li <sunpeng.li@amd.com> Reviewed-by:
Harry Wentland <harry.wentland@amd.com> Signed-off-by:
Alex Deucher <alexander.deucher@amd.com>
-
Leo (Sunpeng) Li authored
Before programming the input gamma, check that we're not using the identity correction. Signed-off-by:
Anthony Koo <Anthony.Koo@amd.com> Acked-by:
-
Anthony Koo authored
Creating plane will also allocate gamma and input TF Creating stream will also allocate outputTF Fix issue with gamma not applied OS may call SetGamma before surface committed, so need to store in target and apply later. Signed-off-by:
Aric Cyr <Aric.Cyr@amd.com> Acked-by:
-
Anthony Koo authored
Signed-off-by:
-
Anthony Koo authored
Signed-off-by:
-
Anthony Koo authored
Remove some unnecessary TF definitions from update structures Signed-off-by:
-
Anthony Koo authored
Signed-off-by:
-
Anthony Koo authored
Signed-off-by:
-
Anthony Koo authored
Signed-off-by:
-
Anthony Koo authored
Signed-off-by:
-
Anthony Koo authored
Updated HDR Static Metadata to directly take info packet raw Updating Infopacket does not require Passive Signed-off-by:
-
- 11 Apr, 2018 29 commits
-
-
Yongqiang Sun authored
Signed-off-by:
Yongqiang Sun <yongqiang.sun@amd.com> Reviewed-by:
-
Roman Li authored
Signed-off-by:
Roman Li <roman.li@amd.com> Reviewed-by:
Charlene Liu <Charlene.Liu@amd.com> Acked-by:
-
Anthony Koo authored
Signed-off-by:
-
Eric Bernstein authored
Signed-off-by:
Eric Bernstein <eric.bernstein@amd.com> Reviewed-by:
-
Dmytro Laktyushkin authored
Signed-off-by:
Dmytro Laktyushkin <Dmytro.Laktyushkin@amd.com> Reviewed-by:
Nikola Cornij <Nikola.Cornij@amd.com> Reviewed-by:
Wesley Chalmers <Wesley.Chalmers@amd.com> Acked-by:
-
Yongqiang Sun authored
Instead of user set brightness with range of percentage, HLK test set brightness level with range of normal, this will result in HLK test case set brightness from 0 to 255, DC set brightness with ramp is 0, and disabled ramp change which will fail the HLK test. Fix: In case of unblank stream and turn on edp, change brightness level in stream to 0xFFFFFFFF(actural maximum level is 0xFF), use that value as a flag to recogonize this the case of resume from S3. Signed-off-by:
Eric Yang <eric.yang2@amd.com> Acked-by:
-
Jun Lei authored
We would otherwise fallback to the timing, which would always give us identity. Signed-off-by:
Jun Lei <Jun.Lei@amd.com> Reviewed-by:
-
Eric Yang authored
Link bw required is reduced when we have chroma subsampling. Signed-off-by:
-
Jun Lei authored
Signed-off-by:
-
Eric Bernstein authored
Move DCN1 implementation of stream encoder to new file (instead of common dce_stream_encoder.c). Cleanup code related to different implementation due to register definition differences. Signed-off-by:
Tony Cheng <Tony.Cheng@amd.com> Acked-by:
-
Eric Yang authored
To prevent future optimization related bugs, just set all update flags when we have a full update, since we know we want to reprogram everything in that case. Signed-off-by:
-
Charlene Liu authored
As per eDP 1.4 spec, there must be at least 500ms delay between eDP power off and on. This change added time stamp when edp power off, which can be used to calculate duration time when edp power on. If duration less than 500ms, add a wait. Signed-off-by:
-
Harry Wentland authored
We use this to ensure we wait at least 500ms in between eDP disable/enable. Signed-off-by:
-
Anthony Koo authored
Signed-off-by:
-
Bhawanpreet Lakha authored
Created Macros for DC_LOG_XXX to pr_debug() & DRM_DEBUG_KMS. Signed-off-by:
Bhawanpreet Lakha <Bhawanpreet.Lakha@amd.com> Reviewed-by:
-
Harry Wentland authored
Signed-off-by:
-
Hersen Wu authored
Signed-off-by:
Hersen Wu <hersenxs.wu@amd.com> Reviewed-by:
-
Harry Wentland authored
Signed-off-by:
-
Anthony Koo authored
Signed-off-by:
-
Harry Wentland authored
Signed-off-by:
-
Harry Wentland authored
Signed-off-by:
-
Harry Wentland authored
We're an atomic driver and shouldn't access legacy properties. Doing so will only scare users with stack traces. Instead save the prop in the state and access it directly. Much simpler. Signed-off-by:
Andrey Grodzovsky <andrey.grodzovsky@amd.com> Signed-off-by:
-
James Zhu authored
Motion vector packet needs support in physical mode. Signed-off-by:
James Zhu <James.Zhu@amd.com> Acked-by:
Christian König <christian.koenig@amd.com> Signed-off-by:
-
Eric Anholt authored
These comments answer all the questions I had for myself when implementing a driver using the GPU scheduler. Signed-off-by:
Eric Anholt <eric@anholt.net> Reviewed-by:
-
Chunming Zhou authored
user cases: 1. KFD wraps amdgpu_bo_create, they have no fallback case which is different with amdgpu_gem_object_create. since upstream branch has no amdgpu_amdkfd_gpuvm.c, which need KFD guys add this flag to __alloc_memory_of_gpu: + flags |= AMDGPU_GEM_CREATE_NO_FALLBACK; 2. UMD can specify this flag for their allocation as well if they like. v2: squash in merge conflict fix (Chunming) Signed-off-by:
Chunming Zhou <david1.zhou@amd.com> Acked-by:
Felix Kuehling <Felix.Kuehling@amd.com> Cc: felix.kuehling@amd.com Signed-off-by:
-
Chunming Zhou authored
v2: add sanity checking v3: make code open v4: also handle visible to invisible fallback v5: Since two fallback cases, re-use goto retry v6: avoid bo is unref when retry, and only user BO can fallback Signed-off-by:
-
Nayan Deshmukh authored
Move it with the scheduler code. This is mostly a straight forward rename with no code change except for updating the TRACE_INCLUDE_PATH Signed-off-by:
Nayan Deshmukh <nayan26deshmukh@gmail.com> Suggested-by:
Lucas Stach <l.stach@pengutronix.de> Signed-off-by:
-
Nayan Deshmukh authored
There is no @kernel parameter anymore and document the @guilty parameter Signed-off-by:
-
Colin Ian King authored
Trivial fix to spelling mistake in DRM_ERROR error message text Reviewed-by:
Colin Ian King <colin.king@canonical.com> Signed-off-by:
-
