- 10 Mar, 2012 19 commits
-
-
Kirill A. Shutemov authored
Signed-off-by:
Kirill A. Shutemov <kirill.shutemov@linux.intel.com> Signed-off-by:
Alan Cox <alan@linux.intel.com> Signed-off-by:
Dave Airlie <airlied@redhat.com>
-
Kirill A. Shutemov authored
Signed-off-by:
-
Kirill A. Shutemov authored
Signed-off-by:
-
Kirill A. Shutemov authored
Signed-off-by:
-
Kirill A. Shutemov authored
Signed-off-by:
-
Kirill A. Shutemov authored
Signed-off-by:
-
Kirill A. Shutemov authored
It fixes W=1 warnings: drivers/gpu/drm/gma500/gem_glue.c:23:6: warning: no previous prototype for ‘drm_gem_object_release_wrap’ [-Wmissing-prototypes] drivers/gpu/drm/gma500/gem_glue.c:44:5: warning: no previous prototype for ‘gem_create_mmap_offset’ [-Wmissing-prototypes] Signed-off-by:
-
Kirill A. Shutemov authored
Signed-off-by:
-
Kirill A. Shutemov authored
Nobody uses 'config' parameter. Signed-off-by:
-
Kirill A. Shutemov authored
Signed-off-by:
-
Kirill A. Shutemov authored
We need to merge this ahead of some of the cleanup because a lot of needed cleanup spans both new and old chips. If we try and clean up and the merge we end up fighting ourselves. Signed-off-by:
-
Alan Cox authored
Rework registers handling to prepare for Medfield. Signed-off-by:
-
Kirill A. Shutemov authored
Signed-off-by:
-
Alan Cox authored
Noted by Kirill A Shutemov Signed-off-by:
-
Jesper Juhl authored
In psb_intel_lvds_init(), if we fail to allocate memory for 'psb_intel_connector' we free the memory we previously allocated for 'psb_intel_encoder', but we then proceed to use that free'd pointer when we do 'psb_intel_encoder->dev_priv = lvds_priv;'. We may also leak the memory we allocated for 'psb_intel_encoder' if we 'goto failed_connector;' and the variable goes out of scope. While I was there anyway, I also removed the pointless 'if (psb_intel_connector)' before freeing it at the 'failed_connector:' label - kfree() deals gracefully with NULL pointers, so it is not needed. Signed-off-by:
Jesper Juhl <jj@chaosbits.net> Signed-off-by:
-
Alan Cox authored
Update this to better reflect the status Signed-off-by:
-
Alan Cox authored
Signed-off-by:
-
Alan Cox authored
Some this is Medfield stuff that may reappear in some form later, other bits are just dead stuff Signed-off-by:
-
Alan Cox authored
Signed-off-by:
-
- 07 Mar, 2012 1 commit
-
-
Rob Clark authored
If there are not multiple instances of a platform device, the id should apparently be set to -1. Which results in a odd looking bus-id like "platform:foodrm:-1". Probably we should just treat this case as id 0. Signed-off-by:
Rob Clark <rob@ti.com> Signed-off-by:
-
- 05 Mar, 2012 1 commit
-
-
Dave Airlie authored
Talking to Al Viro on irc, we can see no possible reason for doing this, the upper mmap code does it. The code has been there since first import into drm tree I can find. Al tracked down this as a requirement pre 2.3.51 hasn't been needed since. Acked-by:
Al Viro <viro@zeniv.linux.org.uk> Signed-off-by:
-
- 29 Feb, 2012 15 commits
-
-
Felix Kuehling authored
This fixes page-flip-related flickering observed on Iconia Tab W500. The update_pending status returned by radeon_page_flip is very accurate on Avivo-based ASICs when vpos is negative. Experiments were conducted on several ASIC generations ranging from RS690 to Cayman where the page flip was artificially timed to occur at a specific vpos. With negative vpos, overriding update_pending always lead to flickering. The same experiment on RV380 and RV410 showed that update_pending is not accurate with negative vpos. In most cases update_pending == 1 is returned although the flip would complete before the start of the next frame. Therefore I left the behaviour unchanged for pre-AVIVO ASICs for performance reasons, although this may result in flickering in rare cases. This change also makes the logic a little easier to understand. Signed-off-by:
Felix Kuehling <Felix.Kuehling@amd.com> Reviewed-by:
Mario Kleiner <mario.kleiner@tuebingen.mpg.de> Signed-off-by:
-
Sascha Hauer authored
remove declared but unused functions from drmP.h, fix the comments where necessary. Also, remove drm_mem_info which is unused. Signed-off-by:
Sascha Hauer <s.hauer@pengutronix.de> Signed-off-by:
-
Alex Deucher authored
v2: fix typo. Signed-off-by:
Alex Deucher <alexander.deucher@amd.com> Reviewed-by: Christian König<christian.koenig@amd.com> Reviewed-by:
Michel Dänzer <michel.daenzer@amd.com> Reviewed-by:
Jerome Glisse <jglisse@redhat.com> Signed-off-by:
-
Alex Deucher authored
tidy up the radeon_asic struct. Signed-off-by:
-
Alex Deucher authored
tidy up radeon_asic struct. Signed-off-by:
-
Alex Deucher authored
tidy up the radeon_asic struct. Signed-off-by:
-
Alex Deucher authored
tidy up the radeon_asic struct. Signed-off-by:
-
Alex Deucher authored
Each ring type may need a different variant. Signed-off-by:
-
Alex Deucher authored
Signed-off-by:
-
Alex Deucher authored
tidy up the radeon_asic struct. Signed-off-by:
-
Alex Deucher authored
tidy up the radeon_asic struct, handle multiple rings better. Signed-off-by:
-
Christian König authored
Storing pointers to the IBs in a static var just leads to giving the same content back for all cards in the system. Signed-off-by:
Christian König <deathsimple@vodafone.de> Reviewed-by:
-
Christian König authored
Not all rings use PM4, so the cs_parser also needs to be per ring. Signed-off-by:
-
Christian König authored
So don't confuse devs by doing so. Signed-off-by:
Alex Deucher <alex.deucher@amd.com> Signed-off-by:
-
Christian König authored
The function radeon_bo_list_validate can cause a bo to move, resulting in a different sync_obj and a dependency to wait for this move to finish. Signed-off-by:
-
- 27 Feb, 2012 4 commits
-
-
Alex Deucher authored
tidy up the radeon_asic struct. Signed-off-by:
Christian König <christian.koenig@amd.com> Reviewed-by:
-
Alex Deucher authored
tidy up the radeon_asic struct. Signed-off-by:
-
Alex Deucher authored
tidy up the radeon_asic struct. Signed-off-by:
-
Alex Deucher authored
Required for future functionality. Signed-off-by:
-
