1278f7de7fa5606ed513a5271f7fb63910ef1b8b |
|
15-Mar-2012 |
Yoichi Yuasa <yuasa@linux-mips.org> |
gma500: Fix mmap frambuffer It cannot map correctly if page fault begins from a intermediate address. [The driver prefaults the mapping, so we need to work from the correct base address not the faulting address otherwise the map appears offset by the fault offset] Signed-off-by: Yoichi Yuasa <yuasa@linux-mips.org> Signed-off-by: Alan Cox <alan@linux.intel.com> Cc: stable@kernel.org Signed-off-by: Dave Airlie <airlied@redhat.com>
|
bc7f2b0839fc0b867a9877d8640e07b9b9813875 |
|
08-Mar-2012 |
Kirill A. Shutemov <kirill.shutemov@linux.intel.com> |
gma500: mark psb_fbdev_destroy() and psb_fbdev_fini() as static 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>
|
4796001a7d5dfdae082919f93ef6104be0108012 |
|
08-Mar-2012 |
Kirill A. Shutemov <kirill.shutemov@linux.intel.com> |
gma500: drop unused psbfb_suspend()/psbfb_resume() 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>
|
6aa1ead1b855819b8b754d0f84f9da6942fe7589 |
|
08-Mar-2012 |
Kirill A. Shutemov <kirill.shutemov@linux.intel.com> |
gma500: psbfb_create(): move depth initialization out of loop 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>
|
4578240b48ed33f4377748701616a870fe5a1a94 |
|
08-Mar-2012 |
Alan Cox <alan@linux.intel.com> |
gma500: re-order calling on the fix setup so we set up after the DRM layer Noted by Kirill A Shutemov Signed-off-by: Alan Cox <alan@linux.intel.com> Signed-off-by: Dave Airlie <airlied@redhat.com>
|
3df546be6b74c1e2633498104ba8879507fb06fd |
|
08-Mar-2012 |
Alan Cox <alan@linux.intel.com> |
gma500: plug in more of the gamma functionality Signed-off-by: Alan Cox <alan@linux.intel.com> Signed-off-by: Dave Airlie <airlied@redhat.com>
|
055bf38d3d6069707e2d555cffdde629b8404ff2 |
|
05-Mar-2012 |
Alan Cox <alan@linux.intel.com> |
drm, gma500: Fix Cedarview boot failures in 3.3-rc Production GMA3600/3650 hardware turns out to be subtly different to the development platforms. This combined with a minor driver bug is causing the kernel to hang on these platforms. This patch does the following - turn down a couple of messages that were meant to be debug and are causing much confusion - ensure the hotplug interrupt is disabled on Cedartrail systems. - fix a bug where gtt roll mode called psbfb_sync, which tries to sync the 2D engine. On other devices it is harmless as the 2D engine is present but not in use when in gtt roll mode, on Cedartrail it causes a hang Without these changes 3.3-rc hangs on boot on Cedartrail based systems. Signed-off-by: Alan Cox <alan@linux.intel.com> Signed-off-by: Linus Torvalds <torvalds@linux-foundation.org>
|
91982b58d35720b75b894c60e1e3133daa455b53 |
|
03-Mar-2012 |
Alan Cox <alan@lxorguk.ukuu.org.uk> |
drm/gma500: Fix Cedarview boot failures in 3.3-rc Production GMA3600/3650 hardware turns out to be subtly different to the development platforms. This combined with a minor driver bug is causing the kernel to hang on these platforms. This patch does the following - turn down a couple of messages that were meant to be debug and are causing much confusion - ensure the hotplug interrupt is disabled on Cedartrail systems. - fix a bug where gtt roll mode called psbfb_sync, which tries to sync the 2D engine. On other devices it is harmless as the 2D engine is present but not in use when in gtt roll mode, on Cedartrail it causes a hang Signed-off-by: Alan Cox <alan@linux.intel.com> Signed-off-by: Dave Airlie <airlied@redhat.com>
|
fb2a99e15ff0d342de4ba58c84a791224a96a01a |
|
06-Feb-2012 |
Sascha Hauer <s.hauer@pengutronix.de> |
drm: do not set fb_info->pixmap fields The drm drivers set the fb_info->pixmap fields without setting fb_info->pixmap.addr. If this is not set the fb core will overwrite these all fb_info->pixmap fields anyway, so there is not much point in setting them in the first place. [airlied: dropped nvidiafb piece - not mine] Signed-off-by: Sascha Hauer <s.hauer@pengutronix.de> Signed-off-by: Dave Airlie <airlied@redhat.com>
|
d9bc3c02e36d844c2d980e65ddda5c7699e073f8 |
|
06-Feb-2012 |
Sascha Hauer <s.hauer@pengutronix.de> |
drm: add convenience function to create an range property Creating a range property is a common pattern, so create a convenience function for this and use it where appropriate. Signed-off-by: Sascha Hauer <s.hauer@pengutronix.de> Signed-off-by: Dave Airlie <airlied@redhat.com>
|
2d8357e66df9f7593cbe23b224b4ed06aff90e73 |
|
27-Jan-2012 |
Ryan Mallon <rmallon@gmail.com> |
gma500: Fix suspend/resume functions Both the suspend and resume functions incorrectly set psbfb = to_psb_fb(NULL) outside of the loop over all of the framebuffers. Fix this by moving the assignment of psbfb inside the loop and removing the initialisation of fb. Signed-off-by: Ryan Mallon <rmallon@gmail.com> Acked-by: Alan Cox <alan@linux.intel.com> Signed-off-by: Dave Airlie <airlied@redhat.com>
|
1730f89bfcff353484672cdcefbef13b2f374176 |
|
19-Dec-2011 |
Patrik Jakobsson <patrik.r.jakobsson@gmail.com> |
gma500: Fix encoder type checking for connectors Fix cases where we need to know what encoder type is behind a given connector. Signed-off-by: Patrik Jakobsson <patrik.r.jakobsson@gmail.com> Signed-off-by: Alan Cox <alan@linux.intel.com> Signed-off-by: Dave Airlie <airlied@redhat.com>
|
01f2c7730e188077026c5f766f85f329c7000c54 |
|
19-Dec-2011 |
Ville Syrjälä <ville.syrjala@linux.intel.com> |
drm: Replace pitch with pitches[] in drm_framebuffer Otherwise each driver would need to keep the information inside their own framebuffer object structure. Also add offsets[]. BOs on the other hand are driver specific, so those can be kept in driver specific structures. Signed-off-by: Ville Syrjälä <ville.syrjala@linux.intel.com> Signed-off-by: Dave Airlie <airlied@redhat.com>
|
1b223c9ebf11e9597820fac57b211709f8ffce26 |
|
29-Nov-2011 |
Alan Cox <alan@linux.intel.com> |
gma500: Be smarter about layout If we can't fit a page aligned display stride then it's not the end of the world for a normal font, so try half a page and work down sizes. Signed-off-by: Alan Cox <alan@linux.intel.com> Signed-off-by: Dave Airlie <airlied@redhat.com>
|
a6ba582d264f67074f669f76172e8a2afadff2a4 |
|
29-Nov-2011 |
Alan Cox <alan@linux.intel.com> |
gma500: gtt based hardware scrolling console Add support for GTT based scrolling. Instead of pushing bits around we simply use the GTT to change the mappings. This provides us with a very fast way to scroll the display providing we have enough memory to allocate on 4K line boundaries. In practice this seems to be the case except for very big displays such as HDMI, and the usual configurations are netbooks/tablets. Signed-off-by: Alan Cox <alan@linux.intel.com> Signed-off-by: Dave Airlie <airlied@redhat.com>
|
dffc9ceb55695f121adc57dd1fde7304c3afe81e |
|
29-Nov-2011 |
Alan Cox <alan@linux.intel.com> |
gma500: kill virtual mapping support This isn't actually usable - we simply don't have the vmap space on a 32bit system to do this stunt. Instead we will rely on the low level drivers limiting the console resolution as before. The real fix is for someone to write a page table aware version of the framebuffer console blit functions. Good university student project perhaps.. Signed-off-by: Alan Cox <alan@linux.intel.com> Signed-off-by: Dave Airlie <airlied@redhat.com>
|
248dbc2350501e2c7b9f5ceb60c75515d82f4134 |
|
29-Nov-2011 |
Dave Airlie <airlied@redhat.com> |
drm: move the fb bpp/depth helper into the core. This is used by nearly everyone including vmwgfx which doesn't generally use the fb helper. Signed-off-by: Dave Airlie <airlied@redhat.com>
|
a9a644ac9e8d6c8efdcc0581b120a0260d1f477d |
|
28-Nov-2011 |
Dave Airlie <airlied@redhat.com> |
drm/gma500: port framebuffer to new plane interface. This takes over the staging change into the mainline driver. Fixes -next part one. Signed-off-by: Dave Airlie <airlied@redhat.com>
|
4d8d096e9ae86621cc38b5417f4353305c5fd3a9 |
|
03-Nov-2011 |
Alan Cox <alan@linux.intel.com> |
gma500: introduce the framebuffer support code We support 2D acceleration on some devices but we try and do tricks with the GTT as a starting point as this is far faster. The GTT logic could be improved further but for most display sizes it already makes a pretty good decision. Signed-off-by: Alan Cox <alan@linux.intel.com> Signed-off-by: Dave Airlie <airlied@redhat.com>
|