kernel/drivers/gpu/drm/radeon/evergreen_dma.c, branch linux-4.17.yHosts the 0x221E linux distro kernel.https://universe.0xinfinity.dev/distro/kernel/atom?h=linux-4.17.y2014-11-20T18:00:16Zdrm/radeon: split semaphore and sync object handling v22014-11-20T18:00:16ZChristian Königchristian.koenig@amd.com2014-11-19T13:01:22Zurn:sha1:975700d2cc84408efa9b2360e38b1ab95368556f
Previously we just allocated space for four hardware semaphores
in each software semaphore object. Make software semaphore objects
represent only one hardware semaphore address again by splitting
the sync code into it's own object.
v2: fix typo in comment
Signed-off-by: Christian König <christian.koenig@amd.com>
Signed-off-by: Alex Deucher <alexander.deucher@amd.com>
drm/radeon: cope with foreign fences inside the reservation object2014-10-03T13:19:16ZMaarten Lankhorstmaarten.lankhorst@canonical.com2014-09-25T10:39:38Zurn:sha1:392a250bd080e296f97ccc7e91b051a6b5da0ff1
Not the whole world is a radeon! :-)
Reviewed-by: Christian König <christian.koenig@amd.com>
Signed-off-by: Maarten Lankhorst <maarten.lankhorst@canonical.com>
Signed-off-by: Alex Deucher <alexander.deucher@amd.com>
drm/radeon: add the infrastructure for concurrent buffer access2014-09-11T14:46:01ZChristian Königchristian.koenig@amd.com2014-09-04T18:01:53Zurn:sha1:57d20a43c9b30663bdbacde8294a902edef35a84
This allows us to specify if we want to sync to
the shared fences of a reservation object or not.
Signed-off-by: Christian König <christian.koenig@amd.com>
Signed-off-by: Alex Deucher <alexander.deucher@amd.com>
drm/radeon: Only flush HDP cache for indirect buffers from userspace2014-08-18T21:09:44ZMichel Dänzermichel.daenzer@amd.com2014-08-18T08:34:55Zurn:sha1:1538a9e0e04f6a5b323cd3d65e9320512978fcec
It isn't necessary for command streams generated by the kernel (at least
not while we aren't storing ring or indirect buffers in VRAM).
Signed-off-by: Michel Dänzer <michel.daenzer@amd.com>
Signed-off-by: Alex Deucher <alexander.deucher@amd.com>
drm/radeon: drm/radeon: add missing radeon_semaphore_free to error path2014-05-06T10:18:41ZMaarten Lankhorstmaarten.lankhorst@canonical.com2014-04-24T11:29:14Zurn:sha1:aa4c8b36e5fcf70ba5ec7d175da19dac4a33c51a
It would appear this bug has been copy/pasted many times without being noticed.
Signed-off-by: Maarten Lankhorst <maarten.lankhorst@canonical.com>
Signed-off-by: Christian König <christian.koenig@amd.com>
Reviewed-by: Alex Deucher <alexander.deucher@amd.com>
drm/radeon: drop radeon_ring_force_activity2014-02-18T16:50:00ZChristian Königchristian.koenig@amd.com2014-02-18T11:37:50Zurn:sha1:2d2fe3f9b60fd3cc9a19dcc3ae892a23825da07f
The reason for the false positives was fixed quite some time ago and since
most engines can still execute NOPs while being locked up it leads to false
negatives.
Signed-off-by: Christian König <christian.koenig@amd.com>
Reviewed-by: Alex Deucher <alexander.deucher@amd.com>
drm/radeon: drop drivers copy of the rptr2014-02-18T16:49:19ZChristian Königchristian.koenig@amd.com2014-02-18T13:52:33Zurn:sha1:ff212f25feb44a915ce9c0144faef7fae27a6e61
In all cases where it really matters we are using the read functions anyway.
Signed-off-by: Christian König <christian.koenig@amd.com>
Reviewed-by: Alex Deucher <alexander.deucher@amd.com>
drm/radeon: allow semaphore emission to fail2013-11-15T20:56:09ZChristian Königchristian.koenig@amd.com2013-11-12T11:58:05Zurn:sha1:1654b817d8f5f1c27ebc98773fe0e517b0ba2f1e
To workaround bugs and/or certain limits it's sometimes
useful to fall back to waiting on fences.
Signed-off-by: Christian König <christian.koenig@amd.com>
Signed-off-by: Alex Deucher <alexander.deucher@amd.com>
Cc: stable@vger.kernel.org
drm/radeon: separate DMA code2013-08-30T20:30:42ZChristian Königchristian.koenig@amd.com2013-08-13T09:56:54Zurn:sha1:2483b4ea982efe8a544697d3f9642932e9af4dc1
Similar to separating the UVD code, just put the DMA
functions into separate files.
Signed-off-by: Christian König <christian.koenig@amd.com>
Signed-off-by: Alex Deucher <alexander.deucher@amd.com>