linux-toradex.git/drivers/gpu/drm/drm_fb_helper.c, branch v3.2.68

drm: Validate requested virtual size against allocated fb size

2012-04-13T15:33:47+00:00

commit 62fb376e214d3c1bfdf6fbb77dac162f6da04d7e upstream.

mplayer -vo fbdev tries to create a screen that is twice as tall as the
allocated framebuffer for "doublebuffering". By default, and all in-tree
users, only sufficient memory is allocated and mapped to satisfy the
smallest framebuffer and the virtual size is no larger than the actual.
For these users, we should therefore reject any userspace request to
create a screen that requires a buffer larger than the framebuffer
originally allocated.

References: https://bugs.freedesktop.org/show_bug.cgi?id=38138
Signed-off-by: Chris Wilson 
Reviewed-by: Daniel Vetter 
Signed-off-by: Dave Airlie 
Signed-off-by: Greg Kroah-Hartman

gpu: add module.h to drivers/gpu files as required.

2011-10-31T23:32:03+00:00

So that we don't get build failures once the implicit module.h
presence is removed.

Signed-off-by: Paul Gortmaker

drm: Remove duplicate "return" statement

2011-09-09T08:11:44+00:00

Remove the duplicate "return" statement in drm_fb_helper_panic().

Signed-off-by: Lin Ming 
Signed-off-by: Dave Airlie

drm: Export the command-line mode parser

2011-04-28T04:56:23+00:00

In the absence of configuration data for providing the fixed mode for
a panel, I would like to be able to pass such modes along a separate
module paramenter. To do so, I then need to parse a modeline from a
string, which drm is already capable of. Export that capability to the
drivers.

Signed-off-by: Chris Wilson 
Signed-off-by: Dave Airlie

drm: Take lock around probes for drm_fb_helper_hotplug_event

2011-04-28T04:50:25+00:00

We need to hold the dev->mode_config.mutex whilst detecting the output
status. But we also need to drop it for the call into
drm_fb_helper_single_fb_probe(), which indirectly acquires the lock when
attaching the fbcon.

Failure to do so exposes a race with normal output probing. Detected by
adding some warnings that the mutex is held to the backend detect routines:

[   17.772456] WARNING: at drivers/gpu/drm/i915/intel_crt.c:471 intel_crt_detect+0x3e/0x373 [i915]()
[   17.772458] Hardware name: Latitude E6400
[   17.772460] Modules linked in: ....
[   17.772582] Pid: 11, comm: kworker/0:1 Tainted: G        W 2.6.38.4-custom.2 #8
[   17.772584] Call Trace:
[   17.772591]  [] ? warn_slowpath_common+0x78/0x8c
[   17.772603]  [] ? intel_crt_detect+0x3e/0x373 [i915]
[   17.772612]  [] ?  drm_helper_probe_single_connector_modes+0xbf/0x2af [drm_kms_helper]
[   17.772619]  [] ?  drm_fb_helper_probe_connector_modes+0x39/0x4d [drm_kms_helper]
[   17.772625]  [] ?  drm_fb_helper_hotplug_event+0xa5/0xc3 [drm_kms_helper]
[   17.772633]  [] ? output_poll_execute+0x146/0x17c [drm_kms_helper]
[   17.772638]  [] ? cfq_init_queue+0x247/0x345
[   17.772644]  [] ? output_poll_execute+0x0/0x17c [drm_kms_helper]
[   17.772648]  [] ? process_one_work+0x193/0x28e
[   17.772652]  [] ? worker_thread+0xef/0x172
[   17.772655]  [] ? worker_thread+0x0/0x172
[   17.772658]  [] ? worker_thread+0x0/0x172
[   17.772663]  [] ? kthread+0x7a/0x82
[   17.772668]  [] ? kernel_thread_helper+0x4/0x10
[   17.772671]  [] ? kthread+0x0/0x82
[   17.772674]  [] ? kernel_thread_helper+0x0/0x10

Reported-by:  Frederik Himpe 
References: https://bugs.freedesktop.org/show_bug.cgi?id=36394
Signed-off-by: Chris Wilson 
Signed-off-by: Dave Airlie

drm/i915: restore only the mode of this driver on lastclose (v2)

2011-04-27T07:51:59+00:00

i915 calls the panic handler function on last close to reset the modes,
however this is a really bad idea for multi-gpu machines, esp shareable
gpus machines. So add a new entry point for the driver to just restore
its own fbcon mode.

v2: move code into fb helper, fix panic code to block mode change on
powered off GPUs.

[airlied: this hits drm core and I wrote it and it was reviewed on intel-gfx
 so really I signed it off twice ;-).]
Signed-off-by: Chris Wilson 
Signed-off-by: Dave Airlie

Merge commit '5359533801e3dd3abca5b7d3d985b0b33fd9fe8b' into drm-core-next

2011-03-16T01:34:41+00:00

This commit changed an internal radeon structure, that meant a new driver
in -next had to be fixed up, merge in the commit and fix up the driver.

Also fixes a trivial nouveau merge.

Conflicts:
	drivers/gpu/drm/nouveau/nouveau_mem.c

drm: index i shadowed in 2nd loop

2011-03-07T22:28:33+00:00

Index i was already used in thhe first loop

Signed-off-by: Roel Kluin 
Signed-off-by: Dave Airlie

drm: psuedocolor support for ARGB modes

2011-02-23T01:09:13+00:00

If there is an alpha channel, need to mask in 1's in the alpha channel
to prevent the fb from being completely transparent.

Signed-off-by: Rob Clark 
Signed-off-by: Dave Airlie

kconfig: rename CONFIG_EMBEDDED to CONFIG_EXPERT

2011-01-21T01:02:05+00:00

The meaning of CONFIG_EMBEDDED has long since been obsoleted; the option
is used to configure any non-standard kernel with a much larger scope than
only small devices.

This patch renames the option to CONFIG_EXPERT in init/Kconfig and fixes
references to the option throughout the kernel.  A new CONFIG_EMBEDDED
option is added that automatically selects CONFIG_EXPERT when enabled and
can be used in the future to isolate options that should only be
considered for embedded systems (RISC architectures, SLOB, etc).

Calling the option "EXPERT" more accurately represents its intention: only
expert users who understand the impact of the configuration changes they
are making should enable it.

Reviewed-by: Ingo Molnar 
Acked-by: David Woodhouse 
Signed-off-by: David Rientjes 
Cc: Greg KH 
Cc: "David S. Miller" 
Cc: Jens Axboe 
Cc: Arnd Bergmann 
Cc: Robin Holt 
Cc: 
Signed-off-by: Andrew Morton 
Signed-off-by: Linus Torvalds