aboutsummaryrefslogtreecommitdiff
path: root/scripts/gdb/linux/config.py
diff options
context:
space:
mode:
authorAnthony Koo <[email protected]>2019-01-20 01:08:02 -0500
committerAlex Deucher <[email protected]>2019-02-06 13:30:44 -0500
commit68f1a00c23d443c9d940fbd512a195e9e6c08b11 (patch)
treedafcbc81858c8faa6c77d5c1c61beec8e620d551 /scripts/gdb/linux/config.py
parentc00800c46e832ca27f4db489b8c28a56603f8d2c (diff)
drm/amd/display: interface to check if timing can be seamless
[Why] Need to figure out whether a timing we want to commit matches something that GOP already programmed, in which case we can decide to some optimizations [How] 1. Add way to check for DIG FE 2. Add way to check for matching OTG timing 3. Add way to check for matching pixel clock (if possible) - Currently only support DP for pixel clock, since it is easy to calc Signed-off-by: Anthony Koo <[email protected]> Reviewed-by: Aric Cyr <[email protected]> Acked-by: Bhawanpreet Lakha <[email protected]> Signed-off-by: Alex Deucher <[email protected]>
Diffstat (limited to 'scripts/gdb/linux/config.py')
0 files changed, 0 insertions, 0 deletions