linux-toradex.git/drivers/gpu/drm/udl, branch v3.13.11

udl: fix issue with imported prime buffers

2013-12-04T23:23:38+00:00

5dc9e1e8 was a bit over-ambitious, and accidentially removed handling
for imported prime buffers.

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

drm: Add separate Kconfig option for fbdev helpers

2013-10-11T21:36:58+00:00

For drivers which might want to disable fbdev legacy support.

Select the new option in all drivers for now, so this shouldn't result
in any change. Drivers need some work anyway to make fbdev support
optional (if they have it implemented, that is), so the recommended
way to expose this is by adding per-driver options. At least as long
as most drivers don't support disabling the fbdev support.

v2: Update for new drm drivers msm and rcar-du. Note that Rob's msm
driver can already take advantage of this, which allows us to build
msm without any fbdev depencies in the kernel!

v3: Move the MODULE_* stuff from the fbdev helper file to
drm_crtc_helper.c.

Cc: David Herrmann 
Cc: Rob Clark 
Reviewed-by: Rob Clark 
Acked-by: Dave Airlie 
Reviewed-by: Chon Ming Lee 
Signed-off-by: Daniel Vetter

drm: kill ->gem_init_object() and friends

2013-10-09T04:38:02+00:00

All drivers embed gem-objects into their own buffer objects. There is no
reason to keep drm_gem_object_alloc(), gem->driver_private and
->gem_init_object() anymore.

New drivers are highly encouraged to do the same. There is no benefit in
allocating gem-objects separately.

Cc: Dave Airlie 
Cc: Alex Deucher 
Cc: Daniel Vetter 
Cc: Jerome Glisse 
Cc: Rob Clark 
Cc: Inki Dae 
Cc: Ben Skeggs 
Cc: Patrik Jakobsson 
Signed-off-by: David Herrmann 
Acked-by: Alex Deucher 
Signed-off-by: Dave Airlie

drm/udl: rip out set_need_resched

2013-09-15T22:35:04+00:00

This very much looks like copypasta from drm/i915's fault handler.
It was used there to duct-tape over issues around gpu reset handling.

Since that can't ever happen for udl and there's seemingly no other
reason for this just drop it.

Reported-by: Peter Zijlstra 
Acked-by: Peter Zijlstra 
Signed-off-by: Daniel Vetter 
Signed-off-by: Dave Airlie

drm/udl: use gem get/put page helpers

2013-08-19T00:36:12+00:00

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

drm: remove FASYNC support

2013-08-19T00:05:17+00:00

So I've stumbled over drm_fasync and wondered what it does. Digging
that up is quite a story.

First I've had to read up on what this does and ended up being rather
bewildered why peopled loved signals so much back in the days that
they've created SIGIO just for that ...

Then I wondered how this ever works, and what that strange "No-op."
comment right above it should mean. After all calling the core fasync
helper is pretty obviously not a noop. After reading through the
kernels FASYNC implementation I've noticed that signals are only sent
out to the processes attached with FASYNC by calling kill_fasync.

No merged drm driver has ever done that.

After more digging I've found out that the only driver that ever used
this is the so called GAMMA driver. I've frankly never heard of such a
gpu brand ever before. Now FASYNC seems to not have been the only bad
thing with that driver, since Dave Airlie removed it from the drm
driver with prejudice:

commit 1430163b4bbf7b00367ea1066c1c5fe85dbeefed
Author: Dave Airlie 
Date:   Sun Aug 29 12:04:35 2004 +0000

    Drop GAMMA DRM from a great height ...

Long story short, the drm fasync support seems to be doing absolutely
nothing. And the only user of it was never merged into the upstream
kernel. And we don't need any fops->fasync callback since the fcntl
implementation in the kernel already implements the noop case
correctly.

So stop this particular cargo-cult and rip it all out.

v2: Kill drm_fasync assignments in rcar (newly added) and imx drivers
(somehow I've missed that one in staging). Also drop the reference in
the drm DocBook. ARM compile-fail reported by Rob Clark.

v3: Move the removal of dev->buf_asnyc assignment in drm_setup to this
patch here.

v4: Actually git add ... tsk.

Cc: Dave Airlie 
Cc: Laurent Pinchart 
Cc: Rob Clark 
Acked-by: Laurent Pinchart 
Signed-off-by: Daniel Vetter 
Reviewed-by: David Herrmann 
Signed-off-by: Dave Airlie

drm: don't push static constants on stack for %*ph

2013-08-07T00:10:58+00:00

There is no need to pass constants via stack. The width may be explicitly
specified in the format.

Signed-off-by: Andy Shevchenko 
Reviewed-by: David Herrmann 
Signed-off-by: Dave Airlie

drm/gem: create drm_gem_dumb_destroy

2013-08-06T23:59:24+00:00

All the gem based kms drivers really want the same function to
destroy a dumb framebuffer backing storage object.

So give it to them and roll it out in all drivers.

This still leaves the option open for kms drivers which don't use GEM
for backing storage, but it does decently simplify matters for gem
drivers.

Acked-by: Inki Dae 
Acked-by: Laurent Pinchart 
Cc: Intel Graphics Development 
Cc: Ben Skeggs 
Reviwed-by: Rob Clark 
Cc: Alex Deucher 
Acked-by: Patrik Jakobsson 
Signed-off-by: Daniel Vetter 
Signed-off-by: Dave Airlie

drm/gem: convert to new unified vma manager

2013-07-25T10:47:06+00:00

Use the new vma manager instead of the old hashtable. Also convert all
drivers to use the new convenience helpers. This drops all the
(map_list.hash.key << PAGE_SHIFT) non-sense.

Locking and access-management is exactly the same as before with an
additional lock inside of the vma-manager, which strictly wouldn't be
needed for gem.

v2:
 - rebase on drm-next
 - init nodes via drm_vma_node_reset() in drm_gem.c
v3:
 - fix tegra
v4:
 - remove duplicate if (drm_vma_node_has_offset()) checks
 - inline now trivial drm_vma_node_offset_addr() calls
v5:
 - skip node-reset on gem-init due to kzalloc()
 - do not allow mapping gem-objects with offsets (backwards compat)
 - remove unneccessary casts

Cc: Inki Dae 
Cc: Rob Clark 
Cc: Dave Airlie 
Cc: Thierry Reding 
Signed-off-by: David Herrmann 
Acked-by: Patrik Jakobsson 
Reviewed-by: Daniel Vetter 
Signed-off-by: Dave Airlie

drm: Drop all the stub gamma_get, gamma_set, load_lut functions from drivers

2013-06-17T09:42:47+00:00

Many of the drivers didn't implement palette/gamma handling, but were forced
to provide stubs for the hooks to avoid drm_fb_helper from oopsing. Now that
the hooks are optional, we can eliminate all the stubs.

Signed-off-by: Ville Syrjälä 
Reviewed-by: Daniel Vetter 
Signed-off-by: Dave Airlie