f35257a3fe267c4280bb2f69453ca1dd3bf48956 |
|
11-Mar-2014 |
Patrik Jakobsson <patrik.r.jakobsson@gmail.com> |
drm/gma500: Unify _get_core_freq for cdv and psb Signed-off-by: Patrik Jakobsson <patrik.r.jakobsson@gmail.com>
|
cf8efd3afeff02fed2e2937ab3006618919bf65a |
|
16-Sep-2013 |
Patrik Jakobsson <patrik.r.jakobsson@gmail.com> |
drm/gma500: Add chip specific sdvo masks Signed-off-by: Patrik Jakobsson <patrik.r.jakobsson@gmail.com>
|
7f67c06721641df12ed68249218d1c2118517f78 |
|
02-Jul-2013 |
Patrik Jakobsson <patrik.r.jakobsson@gmail.com> |
drm/gma500/psb: Make use of generic clock code Add chip specific callbacks for the generic and non-generic clock calculation code. Also remove as much dupilicated code as possible. Signed-off-by: Patrik Jakobsson <patrik.r.jakobsson@gmail.com>
|
0a819515fc346b4e79d6e3fc01d837a660452c74 |
|
02-Dec-2012 |
Daniel Vetter <daniel.vetter@ffwll.ch> |
drm/gma500: use drm_modeset_lock_all Only two places: - suspend/resume - Some really strange mode validation tool with too much funny-lucking hand-rolled conversion code. - The recently-added lastclose fbdev restore code. Better safe than sorry, so convert both places to keep the locking semantics as much as possible. Signed-off-by: Daniel Vetter <daniel.vetter@ffwll.ch>
|
760285e7e7ab282c25b5e90816f7c47000557f4f |
|
02-Oct-2012 |
David Howells <dhowells@redhat.com> |
UAPI: (Scripted) Convert #include "..." to #include <path/...> in drivers/gpu/ Convert #include "..." to #include <path/...> in drivers/gpu/. Signed-off-by: David Howells <dhowells@redhat.com> Acked-by: Dave Airlie <airlied@redhat.com> Acked-by: Arnd Bergmann <arnd@arndb.de> Acked-by: Thomas Gleixner <tglx@linutronix.de> Acked-by: Paul E. McKenney <paulmck@linux.vnet.ibm.com> Acked-by: Dave Jones <davej@redhat.com>
|
6f314ebbaa2667d67a7206ba78f28e46cf47eda5 |
|
13-Jul-2012 |
Alan Cox <alan@linux.intel.com> |
gma500: Fix frequency detection If we have a 266MHz part we set core_freq to 0 in several spots Signed-off-by: Alan Cox <alan@linux.intel.com> Signed-off-by: Dave Airlie <airlied@gmail.com>
|
f507598b06ab00fb46495ccdeeb3ef9c1dc43dee |
|
16-Jul-2012 |
Alan Cox <alan@linux.intel.com> |
gma500: Fix lid related crash We now set up the lid timer before we set up the backlight. On some devices that causes a crash as we do a backlight change before or during the setup. As this fixes a crash on boot regression on some setups it ought to go in ASAP, especially as all the user gets is a blank screen. Signed-off-by: Alan Cox <alan@linux.intel.com> Tested-by: Mattia Dongili <malattia@linux.it> Signed-off-by: Linus Torvalds <torvalds@linux-foundation.org>
|
7beff62ee39d3ccf088bb77f61a63037f714d235 |
|
21-May-2012 |
Alan Cox <alan@linux.intel.com> |
gma500: Fix Poulsbo suspend/resume crash on devices with SDVO ports Reported-by: Guillaume Clément <guillaume@baobob.org> Signed-off-by: Alan Cox <alan@linux.intel.com> Cc: stable@vger.kernel.org Signed-off-by: Dave Airlie <airlied@redhat.com>
|
bc794829141f28e14fe7d0e07e35870bd9aee78c |
|
21-May-2012 |
Patrik Jakobsson <patrik.r.jakobsson@gmail.com> |
gma500: handle poulsbo cursor restriction Poulsbo needs a physical address in the cursor base register. We allocate a stolen memory buffer and copy the cursor image provided by userspace into it. When/If we get our own userspace driver we can map this stolen memory directly. The patch also adds a mark in chip ops so we can identify devices that has this requirement. Signed-off-by: Patrik Jakobsson <patrik.r.jakobsson@gmail.com> Signed-off-by: Dave Airlie <airlied@redhat.com>
|
0333592ff9e936c6e5ae143e7418468a3198b54d |
|
17-May-2012 |
Dave Airlie <airlied@redhat.com> |
gma500: fix build warning CC [M] drivers/gpu/drm/i915/i915_gem_evict.o /ssd/git/drm-core-next/drivers/gpu/drm/gma500/psb_device.c: In function ‘psb_chip_errata’: /ssd/git/drm-core-next/drivers/gpu/drm/gma500/psb_device.c:360:1: warning: no return statement in function returning non-void [-Wreturn-type] /ssd/git/drm-core-next/drivers/gpu/drm/gma500/psb_device.c: At top level: /ssd/git/drm-core-next/drivers/gpu/drm/gma500/psb_device.c:379:2: warning: initialization from incompatible pointer type [enabled by default] /ssd/git/drm-core-next/drivers/gpu/drm/gma500/psb_device.c:379:2: warning: (near initialization for ‘psb_chip_ops.errata’) [enabled by default] Signed-off-by: Dave Airlie <airlied@redhat.com>
|
6607e024014e4920e8d3e43bcfeec0436d43d980 |
|
14-May-2012 |
Alan Cox <alan@linux.intel.com> |
gma500: Fix crash on D2700MUD and various other boards The recent changes led to the lid timer code being run on various devices. It does no harm on most but isn't needed. It also calls unconditionally into the Poulsbo backlight code which goes bang on Cedartrail. Signed-off-by: Alan Cox <alan@linux.intel.com> Signed-off-by: Dave Airlie <airlied@redhat.com>
|
8512e0748729a49d9af6693f920c1b432796fa8d |
|
11-May-2012 |
Alan Cox <alan@linux.intel.com> |
gma500: introduce some register maps All the conditional ugly register selection really wants to be cleaned up. Use a struct describing each pipe and its registers. This will also let us hide some of the oddments between platforms for any future merging of bits together. In particular the way the DPLL and FP registers randomly wander around. Signed-off-by: Alan Cox <alan@linux.intel.com> Signed-off-by: Dave Airlie <airlied@redhat.com>
|
d839ede47a56ff5f316c88391818488f8e5913af |
|
03-May-2012 |
Alan Cox <alan@linux.intel.com> |
gma500: opregion and ACPI Add the opregion support and bring us in line with the opregion functionality in the reference driver code. We can't share this with i915 currently because there are hardcoded assumptions about dev_priv etc in both versions. [airlied: include opregion.h fix] Signed-off-by: Alan Cox <alan@linux.intel.com> Signed-off-by: Dave Airlie <airlied@redhat.com>
|
d235e64a4367ad3ff204309490c4325b4f89b25b |
|
25-Apr-2012 |
Alan Cox <alan@linux.intel.com> |
cdv: continue synching up with updated reference code In particular clean up the errata handling and correct the crtc masks. We do this a bit differently using our device abstraction for neatness. This doesn't address the ACPI opregion and hotplug plumbing, nor the IRQ related changes that will need. It touches on backlight init but the full backlight support is not in this change set. Signed-off-by: Alan Cox <alan@linux.intel.com> Signed-off-by: Dave Airlie <airlied@redhat.com>
|
c6265ff593467d472814aa9f16f89f6c1dc90a5d |
|
08-Mar-2012 |
Alan Cox <alan@linux.intel.com> |
gma500: rework register stuff sanely Rework registers handling to prepare for Medfield. Signed-off-by: Alan Cox <alan@linux.intel.com> [split out from a single big patch] Signed-off-by: Kirill A. Shutemov <kirill.shutemov@linux.intel.com> Signed-off-by: Dave Airlie <airlied@redhat.com>
|
648a8e342c5a754bdc62f003d3af90507c1abfde |
|
08-Mar-2012 |
Alan Cox <alan@linux.intel.com> |
gma500: now move the Oaktrail save state into its own structure Signed-off-by: Alan Cox <alan@linux.intel.com> Signed-off-by: Dave Airlie <airlied@redhat.com>
|
5c0c1d50d7ba7a678b7d6e2c4f2ff31edafb1067 |
|
19-Dec-2011 |
Patrik Jakobsson <patrik.r.jakobsson@gmail.com> |
gma500: Add support for Intel GMBUS Before we integrate the new SDVO code we need GMBUS support 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>
|
2357f7e61f4ca5789ce2ecbe44367acfe078a841 |
|
29-Nov-2011 |
Alan Cox <alan@linux.intel.com> |
gma500: kill bogus code During the power split ups and work a chunk of code escaped into the Poulsbo code path which it isn't for. On some devices such as the Dell mini-10 this causes problems. Signed-off-by: Alan Cox <alan@linux.intel.com> Signed-off-by: Dave Airlie <airlied@redhat.com>
|
838fa588a29331da012876623c3bc170d7d647c2 |
|
16-Nov-2011 |
Alan Cox <alan@linux.intel.com> |
gma500: Move the API Finally move the API where it can be seen Signed-off-by: Alan Cox <alan@linux.intel.com> Signed-off-by: Dave Airlie <airlied@redhat.com>
|
89c78134cc54dff016c83367912eb055637fa50c |
|
03-Nov-2011 |
Alan Cox <alan@linux.intel.com> |
gma500: Add Poulsbo support This provides the specific code for Poulsbo, some of which is also used for the later chipsets. We support the GTT, the 2D engine (for console), and the display setup/management. We do not support 3D or the video overlays. In theory enough public info is available to do the video overlay work but that represents a large task. Framebuffer X will run nicely with this but do *NOT* use the VESA X server at the same time as KMS. With a Dell mini 10 things like Xfce4 are nice and usable even when compositing as the CPU has a good path to the memory. Signed-off-by: Alan Cox <alan@linux.intel.com> Signed-off-by: Dave Airlie <airlied@redhat.com>
|