linux-toradex.git/include/linux/fb.h, branch v2.6.36-rc5

vt/console: try harder to print output when panicing

2010-08-10T20:47:40+00:00

Jesse's initial patch commit said:

"At panic time (i.e.  when oops_in_progress is set) we should try a bit
harder to update the screen and make sure output gets to the VT, since
some drivers are capable of flipping back to it.

So make sure we try to unblank and update the display if called from a
panic context."

I've enhanced this to add a flag to the vc that console layer can set to
indicate they want this behaviour to occur.  This also adds support to
fbcon for that flag and adds an fb flag for drivers to indicate they want
to use the support.  It enables this for KMS drivers.

Signed-off-by: Dave Airlie 
Signed-off-by: Jesse Barnes 
Acked-by: James Simmons 
Cc: Alan Cox 
Signed-off-by: Andrew Morton 
Signed-off-by: Greg Kroah-Hartman

fb: add hooks to handle KDB enter/exit

2010-08-05T14:22:31+00:00

Add fb ops to handle enter/exit of the kernel debugger.  If present, the
fb core will register them with KGDB and they'll be called when the
debugger is entered and exited.  The new functions are responsible for
switching to an appropriate debug framebuffer and restoring the
interrupted state at exit time.

Signed-off-by: Jesse Barnes 
Signed-off-by: Jason Wessel

fb: handle allocation failure in alloc_apertures()

2010-07-20T05:24:09+00:00

If the kzalloc() fails we should return NULL.  All the places that call
alloc_apertures() check for this already.

Signed-off-by: Dan Carpenter 
Acked-by: James Simmons 
Acked-by: Marcin Slusarz 
Signed-off-by: Dave Airlie

fb: fix colliding defines for fb flags.

2010-07-01T01:59:34+00:00

When I added the flags I must have been using a 25 line terminal and missed the following flags.

The collided with flag has one user in staging despite being in-tree for 5 years.

I'm happy to push this via my drm tree unless someone really wants to do it.

Signed-off-by: Dave Airlie 
Cc: stable@kernel.org

drop unused dentry argument to ->fsync

2010-05-28T02:05:02+00:00

Signed-off-by: Christoph Hellwig 
Signed-off-by: Al Viro

fbdev: move FBIO_WAITFORVSYNC to linux/fb.h

2010-05-25T15:07:09+00:00

FBIO_WAITFORVSYNC is currently implemented by matroxfb, atyfb, intelfb and
more.  All of them keep redefining the same FBIO_WAITFORVSYNC macro over
and over again, so move it to linux/fb.h and clean up those duplicate
defines.

Signed-off-by: Grazvydas Ignotas 
Cc: Ville Syrjala 
Cc: Grant Likely 
Cc: Maik Broemme 
Cc: Petr Vandrovec 
Cc: Benjamin Herrenschmidt 
Cc: Krzysztof Helt 
Cc: "Hiremath, Vaibhav" 
Signed-off-by: Andrew Morton 
Signed-off-by: Linus Torvalds

vga16fb, drm: vga16fb->drm handoff

2010-05-18T06:19:30+00:00

let vga16fb claim 0xA0000+0x10000 region as its aperture;
drm drivers don't use it, so we have to detect it and kick
vga16fb manually - but only if drm is driving the primary card

Signed-off-by: Marcin Slusarz 
Cc: James Simmons 
Cc: Dave Airlie 
Cc: Ben Skeggs 
Signed-off-by: Dave Airlie

fbmem, drm/nouveau: kick firmware framebuffers as soon as possible

2010-05-18T06:19:28+00:00

Currently vesafb/efifb/... is kicked when hardware driver is registering
framebuffer. To do it hardware must be fully functional, so there's a short
window between start of initialisation and framebuffer registration when
two drivers touch the hardware. Unfortunately sometimes it breaks nouveau
initialisation.

Fix it by kicking firmware driver(s) before we start touching the hardware.

Reported-by: Didier Spaier 
Tested-by: Didier Spaier 
Signed-off-by: Marcin Slusarz 
Cc: Ben Skeggs 
Cc: Peter Jones 
Cc: Andrew Morton 
Signed-off-by: Dave Airlie

fbdev: allow passing more than one aperture for handoff

2010-05-18T06:19:27+00:00

It removes a hack from nouveau code which had to detect which
region to pass to kick vesafb/efifb.

Signed-off-by: Marcin Slusarz 
Cc: Eric Anholt 
Cc: Ben Skeggs 
Cc: Thomas Hellstrom 
Cc: Dave Airlie 
Cc: Peter Jones 
Cc: Benjamin Herrenschmidt 
Signed-off-by: Dave Airlie

vga_switcheroo: initial implementation (v15)

2010-03-01T06:20:37+00:00

Many new laptops now come with 2 gpus, one to be used for low power
modes and one for gaming/on-ac applications. These GPUs are typically
wired to the laptop panel and VGA ports via a multiplexer unit which
is controlled via ACPI methods.

4 combinations of systems typically exist - with 2 ACPI methods.
Intel/ATI - Lenovo W500/T500 - use ATPX ACPI method
ATI/ATI - some ASUS - use ATPX ACPI Method
Intel/Nvidia - - use _DSM ACPI method
Nvidia/Nvidia -  - use _DSM ACPI method.

TODO:
This patch adds support for the ATPX method and initial bits
for the _DSM methods that need to written by someone with
access to the hardware.
Add a proper non-debugfs interface - need to get some proper
testing first.

v2: add power up/down support for both devices
on W500 puts i915/radeon into D3 and cuts power to radeon.

v3: redo probing methods, no DMI list, drm devices call to
register with switcheroo, it tries to find an ATPX method on
any device and once there is two devices + ATPX it inits the
switcher.

v4: ATPX msg handling using buffers - should work on more machines

v5: rearchitect after more mjg59 discussion - move ATPX handling to
    radeon driver.

v6: add file headers + initial nouveau bits (to be filled out).

v7: merge delayed switcher code.

v8: avoid suspend/resume of gpu that is off

v9: rearchitect - mjg59 is always right. - move all ATPX code to
radeon, should allow simpler DSM also proper ATRM handling

v10: add ATRM support for radeon BIOS, add mutex to lock vgasr_priv

v11: fix bug in resuming Intel for 2nd time.

v12: start fixing up nvidia code blindly.

v13: blindly guess at finishing nvidia code

v14: remove radeon audio hacks - fix up intel resume more like upstream

v15: clean up printks + remove unnecessary igd/dis pointers

mount debugfs

/sys/kernel/debug/vgaswitcheroo/switch - should exist if ATPX detected
 + 2 cards.

DIS - immediate change to discrete
IGD - immediate change to IGD
DDIS - delayed change to discrete
DIGD - delayed change to IGD
ON - turn on not in use
OFF - turn off not in use

Tested on W500 (Intel/ATI) and T500 (Intel/ATI)

Signed-off-by: Dave Airlie