linux-stable.git/drivers/gpu/drm/shmobile, branch linux-3.14.y

drm/shmob: call drm_put_dev directly from ->remove hook

2013-12-18T01:05:46+00:00

We need to chase one pointer here.

Cc: Laurent Pinchart 
Signed-off-by: Daniel Vetter 
Acked-by: Laurent Pinchart 
Signed-off-by: Dave Airlie

drm: shmob_drm: Check clk_prepare_enable() return value

2013-12-18T01:04:40+00:00

The clk_prepare_enable() call can fail. Check it's return value. We
can't propagate it all the way to the user as the KMS operations in
which the clock is enabled return a void.

Signed-off-by: Laurent Pinchart 
Reviewed-by: Thierry Reding 
Signed-off-by: Dave Airlie

drm: shmob_drm: Convert to clk_prepare/unprepare

2013-11-10T08:48:38+00:00

Turn clk_enable() and clk_disable() calls into clk_prepare_enable() and
clk_disable_unprepare() to get ready for the migration to the common
clock framework.

Cc: David Airlie 
Cc: dri-devel@lists.freedesktop.org
Signed-off-by: Laurent Pinchart 
Signed-off-by: Dave Airlie

drm: shmobile: Add dependency on BACKLIGHT_CLASS_DEVICE

2013-11-06T02:00:08+00:00

The driver registers a backlight device and thus requires
BACKLIGHT_CLASS_DEVICE to be selected to avoid compilation breakages.

Cc: stable@vger.kernel.org
Reported-by: Russell King 
Signed-off-by: Laurent Pinchart 
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: Pass page flip ioctl flags to driver

2013-08-29T23:24:54+00:00

This lets drivers see the flags requested by the application

[airlied: fixup for rcar/imx/msm]

Signed-off-by: Keith Packard 
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/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/shmobile: Use the GEM PRIME helpers

2013-07-17T13:43:55+00:00

The GEM CMA PRIME import/export helpers have been removed in favor of
generic GEM PRIME helpers with GEM CMA low-level operations. Fix the
driver accordingly.

Reported-by: Mark Brown 
Signed-off-by: Laurent Pinchart 
Tested-by: Mark Brown

drm/shmobile: Enable compilation on all ARM platforms

2013-06-20T08:07:14+00:00

This is required to support multi-arch kernels.

Signed-off-by: Laurent Pinchart