linux-toradex.git/drivers/gpu/drm/drm_crtc.c, branch tegra-9.12.14

drm: Delete the DRM_DEBUG_KMS in drm_mode_cursor_ioctl

2009-10-05T00:00:57+00:00

We can get the corresponding info by adding the boot option of "drm.debug=
0x07". But On some boxes it will print the following message many times in
course of moving mouse. In such case the useful DRM debug info will be flushed.
   >[drm:drm_mode_cursor_ioctl],

Avoid using the DRM_DEBUG_KMS in drm_mode_cursor_ioctl.

Signed-off-by: Zhao Yakui 
Signed-off-by: Dave Airlie

drm/kms: start adding command line interface using fb.

2009-09-25T03:08:20+00:00

[note this requires an fb patch posted to linux-fbdev-devel already]

This uses the normal video= command line option to control the kms
output setup at boot time. It is used to override the autodetection
done by kms.

video= normally takes a framebuffer as the first parameter, in kms
it will take a connector name, DVI-I-1, or LVDS-1 etc. If no output
connector is specified the mode string will apply to all connectors.

The mode specification used will match down the probed modes, and if
no mode is found it will add a CVT mode that matches.

video=1024x768 - all connectors match a 1024x768 mode or add a CVT on
video=VGA-1:1024x768, VGA-1 connector gets mode only.

The same strings as used in current fb modedb.c are used, except I've
added three more letters, e, D, d, e = enable, D = enable Digital,
d = disable, which allow a connector to be forced into a certain state.

Signed-off-by: Dave Airlie

drm: split crtc/fb helpers into a separate module

2009-09-07T05:45:33+00:00

I really don't want to have core drm module rely on CONFIG_FB,
so this is the easiest answer.

Signed-off-by: Dave Airlie

Merge Linus master to drm-next

2009-08-20T03:38:04+00:00

linux-next conflict reported needed resolution.

Conflicts:
	drivers/gpu/drm/drm_crtc.c
	drivers/gpu/drm/drm_edid.c
	drivers/gpu/drm/i915/intel_sdvo.c
	drivers/gpu/drm/radeon/radeon_ttm.c
	drivers/gpu/drm/ttm/ttm_bo.c

drm: clarify scaling property names

2009-08-19T06:06:40+00:00

Now that we're using the scaling property in the Intel driver I noticed
that the names were a bit confusing.  I've corrected them according to
our discussion on IRC and the mailing list, though I've left out
potential new additions for a new scaling property with an integer (or
two) for the scaling factor.  None of the drivers implement that today,
but if someone wants to do it, I think it could be done with the
addition of a single new type and a new property to describe the
scaling factor in the X and Y directions.

Signed-off-by: Jesse Barnes 
Acked-by: Alex Deucher 
Signed-off-by: Dave Airlie

drm/kms: teardown crtc correctly when fb is destroyed.

2009-08-19T04:11:34+00:00

If userspace destroys a framebuffer that is in use on a crtc,
don't just null it out, tear down the crtc properly so the
hw gets turned off.

Signed-off-by: Dave Airlie

drm: Add more standard TV properties.

2009-08-13T00:33:48+00:00

Overscan, saturation, hue. Used in the nouveau driver for GPUs with
integrated TV encoders.

Signed-off-by: Francisco Jerez 
Signed-off-by: Dave Airlie

drm: Define some new standard TV properties.

2009-08-04T04:14:46+00:00

Namely "brightness", "contrast" and "flicker reduction".

Signed-off-by: Francisco Jerez 
Signed-off-by: Dave Airlie

drm: Define DRM_MODE_SUBCONNECTOR_SCART

2009-08-04T04:11:00+00:00

Signed-off-by: Francisco Jerez 
Signed-off-by: Dave Airlie

drm: Define DRM_MODE_CONNECTOR_TV

2009-08-04T04:10:56+00:00

The existing TV connector types are often unsuitable either because
there is no way to probe them until they're actually plugged in or
because they can change during run time (e.g. 7-pin DIN connectors
that behave as S-Video, Component, Composite or SCART depending on the
adaptor plugged in).

Signed-off-by: Francisco Jerez 
Signed-off-by: Dave Airlie