linux-toradex.git/drivers/gpu/drm, branch v3.9-rc3

Merge branch 'drm-nouveau-fixes-3.9' of git://anongit.freedesktop.org/git/nouveau/linux-2.6 into drm-next

2013-03-11T03:53:58+00:00

Regression fixes and oops fixes for nouveau.

* 'drm-nouveau-fixes-3.9' of git://anongit.freedesktop.org/git/nouveau/linux-2.6:
  drm/nv50: use correct tiling methods for m2mf buffer moves
  drm/nouveau: idle channel before releasing notify object
  drm/nouveau: fix regression in vblanking
  drm/nv50: encoder creation failure doesn't mean full init failure

drm/nv50: use correct tiling methods for m2mf buffer moves

2013-03-10T22:43:09+00:00

Currently used only on original nv50, nvaa and nvac.

Signed-off-by: Marcin Slusarz 
Signed-off-by: Ben Skeggs

drm/nouveau: idle channel before releasing notify object

2013-03-10T22:43:05+00:00

Unmapping it while it's still in use (e.g. by M2MF) can lead to page faults
and a lot of TRAP_M2MF spam in dmesg.

Signed-off-by: Marcin Slusarz 
Signed-off-by: Ben Skeggs

drm/nouveau: fix regression in vblanking

2013-03-10T22:43:00+00:00

nv50_vblank_enable/disable got switched from NV50_PDISPLAY_INTR_EN_1_VBLANK_CRTC_0 (4) << head to 1 << head, which is wrong.

4 << head is the correct value.

Fixes regression with vblanking since 1d7c71a3e2f77 "drm/nouveau/disp: port vblank handling to event interface"

Signed-off-by: Maarten Lankhorst 
Signed-off-by: Ben Skeggs

drm/nv50: encoder creation failure doesn't mean full init failure

2013-03-10T22:42:52+00:00

It's meant as a notification only, not a fatal error.

Signed-off-by: Ben Skeggs

drm/tegra: drop "select DRM_HDMI"

2013-03-07T22:36:01+00:00

Commit ac24c2204a76e5b42aa103bf963ae0eda1b827f3 ("drm/tegra: Use generic
HDMI infoframe helpers") added "select DRM_HDMI" to the DRM_TEGRA
Kconfig entry. But there is no Kconfig symbol named DRM_HDMI. The select
statement for that symbol is a nop. Drop it.

What was needed to use HDMI functionality was to select HDMI (which this
entry already did through depending on DRM) and to include linux/hdmi.h
(which this commit also did).

Signed-off-by: Paul Bolle 
Acked-by: Thierry Reding 
Signed-off-by: Dave Airlie

drm/mgag200: Bug fix: Renesas board now selects native resolution.

2013-03-07T22:31:49+00:00

Renesas boards were consistently defaulting to the 1024x768 resolution,
regardless of the native resolution of the monitor plugged in.  It was
determined that the EDID of the monitor was not being read.  Since the
DAC is a shared line, in order to read from or write to it we must take
control of the DAC clock.  This can be done by setting the proper
register to one.

This bug fix sets the register MGA1064_GEN_IO_CTL2 to one.  The DAC
control line can be used to determine whether or not a new monitor has
been plugged in.  But since the hotplug feature is not one we will
support, it has been decided to simply leave the register set to one.

Signed-off-by: Julia Lemire 
Signed-off-by: Dave Airlie

drm/mgag200: Reject modes that are too big for VRAM

2013-03-07T22:31:31+00:00

A monitor or a user could request a resolution greater than the
available VRAM for the backing framebuffer. This change checks the
required framebuffer size against the max VRAM size and rejects modes
if they are too big. This change can also remove a mode request passed
in via the video= parameter.

Signed-off-by: Christopher Harvey 
Signed-off-by: Dave Airlie

drm/mgag200: 'fbdev_list' in 'struct mga_fbdev' is not used

2013-03-07T22:30:54+00:00

Signed-off-by: Christopher Harvey 
Signed-off-by: Dave Airlie

drm/radeon: don't check mipmap alignment if MIP_ADDRESS is FMASK

2013-03-07T17:58:59+00:00

The MIP_ADDRESS state has 2 meanings. If the texture has one sample
per pixel, it's a pointer to the mipmap chain. If the texture has
multiple samples per pixel, it's a pointer to FMASK, a metadata buffer
needed for reading compressed MSAA textures. The mipmap
alignment rules do not apply to FMASK.

Signed-off-by: Marek Olšák 
Signed-off-by: Alex Deucher