[PATCH v3 1/3] drm/radeon: take exclusive_lock in read mode during, ring tests, v3

2014-08-20 Thread Maarten Lankhorst
Hey, I found another bug related to gpu reset, one that seems to trigger more reliable with the delayed work changes. Op 19-08-14 om 15:06 schreef Christian K?nig: > Am 19.08.2014 um 14:22 schrieb Maarten Lankhorst: >> This is needed for the next commit, because the lockup detection >> will need

[PATCH v3 1/3] drm/radeon: take exclusive_lock in read mode during, ring tests, v3

2014-08-19 Thread Maarten Lankhorst
Op 19-08-14 om 15:06 schreef Christian K?nig: > Am 19.08.2014 um 14:22 schrieb Maarten Lankhorst: >> This is needed for the next commit, because the lockup detection >> will need the read lock to run. >> >> Signed-off-by: Maarten Lankhorst >> --- >> radeon_pm_compute_clocks already checks if dpm i

[PATCH v3 1/3] drm/radeon: take exclusive_lock in read mode during, ring tests, v3

2014-08-19 Thread Christian König
Am 19.08.2014 um 14:22 schrieb Maarten Lankhorst: > This is needed for the next commit, because the lockup detection > will need the read lock to run. > > Signed-off-by: Maarten Lankhorst > --- > radeon_pm_compute_clocks already checks if dpm is enabled, so no need to > check a second time. > > B

[PATCH v3 1/3] drm/radeon: take exclusive_lock in read mode during, ring tests, v3

2014-08-19 Thread Maarten Lankhorst
This is needed for the next commit, because the lockup detection will need the read lock to run. Signed-off-by: Maarten Lankhorst --- radeon_pm_compute_clocks already checks if dpm is enabled, so no need to check a second time. Because of locking and waiting stuff the radeon_pm_compute_clocks a