Attachment 17819 Details for Bug 16799 – Add suspend/resume hooks to radeon DRM driver

[patch] Add suspend/resume hooks to radeon DRM driver

libdrm-radeon-add-suspend-resume-hooks.patch (text/plain), 1.40 KB, created by Stefan Becker on 2008-07-22 03:09:45 UTC

(hide)

Description:

Filename:

MIME Type:

Creator: Stefan Becker

Created: 2008-07-22 03:09:45 UTC

Size: 1.40 KB

patch

obsolete

>diff -up libdrm-20080722/linux-core/radeon_drv.c.orig libdrm-20080722/linux-core/radeon_drv.c
>--- libdrm-20080722/linux-core/radeon_drv.c.orig	2008-07-22 01:06:52.000000000 +0300
>+++ libdrm-20080722/linux-core/radeon_drv.c	2008-07-22 12:50:36.000000000 +0300
>@@ -52,6 +52,28 @@ static int dri_library_name(struct drm_d
> 		"r300"));
> }
> 
>+static int radeon_suspend(struct drm_device *dev, pm_message_t state)
>+{
>+	drm_radeon_private_t *dev_priv = dev->dev_private;
>+
>+	/* Disable *all* interrupts */
>+	if ((dev_priv->flags & RADEON_FAMILY_MASK) >= CHIP_RS690)
>+		RADEON_WRITE(R500_DxMODE_INT_MASK, 0);
>+	RADEON_WRITE(RADEON_GEN_INT_CNTL, 0);
>+	return 0;
>+}
>+
>+static int radeon_resume(struct drm_device *dev)
>+{
>+	drm_radeon_private_t *dev_priv = dev->dev_private;
>+
>+	/* Restore interrupt registers */
>+	if ((dev_priv->flags & RADEON_FAMILY_MASK) >= CHIP_RS690)
>+		RADEON_WRITE(R500_DxMODE_INT_MASK, dev_priv->r500_disp_irq_reg);
>+	RADEON_WRITE(RADEON_GEN_INT_CNTL, dev_priv->irq_enable_reg);
>+	return 0;
>+}
>+
> static struct pci_device_id pciidlist[] = {
> 	radeon_PCI_IDS
> };
>@@ -69,6 +91,8 @@ static struct drm_driver driver = {
> 	.postclose = radeon_driver_postclose,
> 	.lastclose = radeon_driver_lastclose,
> 	.unload = radeon_driver_unload,
>+	.suspend = radeon_suspend,
>+	.resume = radeon_resume,
> 	.get_vblank_counter = radeon_get_vblank_counter,
> 	.enable_vblank = radeon_enable_vblank,
> 	.disable_vblank = radeon_disable_vblank,

Actions: View | Splinter Review

Attachments on bug 16799: 17814 | 17819

Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.