DRM: i915: add mode setting support
This commit adds i915 driver support for the DRM mode setting APIs.
Currently, VGA, LVDS, SDVO DVI & VGA, TV and DVO LVDS outputs are
supported. HDMI, DisplayPort and additional SDVO output support will
follow.
Support for the mode setting code is controlled by the new 'modeset'
module option. A new config option, CONFIG_DRM_I915_KMS controls the
default behavior, and whether a PCI ID list is built into the module for
use by user level module utilities.
Note that if mode setting is enabled, user level drivers that access
display registers directly or that don't use the kernel graphics memory
manager will likely corrupt kernel graphics memory, disrupt output
configuration (possibly leading to hangs and/or blank displays), and
prevent panic/oops messages from appearing. So use caution when
enabling this code; be sure your user level code supports the new
interfaces.
A new SysRq key, 'g', provides emergency support for switching back to
the kernel's framebuffer console; which is useful for testing.
Co-authors: Dave Airlie <airlied@linux.ie>, Hong Liu <hong.liu@intel.com>
Signed-off-by: Jesse Barnes <jbarnes@virtuousgeek.org>
Signed-off-by: Eric Anholt <eric@anholt.net>
Signed-off-by: Dave Airlie <airlied@redhat.com>
2008-11-07 22:24:08 +00:00
|
|
|
/*
|
|
|
|
* Copyright © 2007 David Airlie
|
|
|
|
*
|
|
|
|
* Permission is hereby granted, free of charge, to any person obtaining a
|
|
|
|
* copy of this software and associated documentation files (the "Software"),
|
|
|
|
* to deal in the Software without restriction, including without limitation
|
|
|
|
* the rights to use, copy, modify, merge, publish, distribute, sublicense,
|
|
|
|
* and/or sell copies of the Software, and to permit persons to whom the
|
|
|
|
* Software is furnished to do so, subject to the following conditions:
|
|
|
|
*
|
|
|
|
* The above copyright notice and this permission notice (including the next
|
|
|
|
* paragraph) shall be included in all copies or substantial portions of the
|
|
|
|
* Software.
|
|
|
|
*
|
|
|
|
* THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
|
|
|
|
* IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
|
|
|
|
* FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL
|
|
|
|
* THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER
|
|
|
|
* LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING
|
|
|
|
* FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER
|
|
|
|
* DEALINGS IN THE SOFTWARE.
|
|
|
|
*
|
|
|
|
* Authors:
|
|
|
|
* David Airlie
|
|
|
|
*/
|
|
|
|
|
2014-05-28 21:39:03 +00:00
|
|
|
#include <linux/async.h>
|
DRM: i915: add mode setting support
This commit adds i915 driver support for the DRM mode setting APIs.
Currently, VGA, LVDS, SDVO DVI & VGA, TV and DVO LVDS outputs are
supported. HDMI, DisplayPort and additional SDVO output support will
follow.
Support for the mode setting code is controlled by the new 'modeset'
module option. A new config option, CONFIG_DRM_I915_KMS controls the
default behavior, and whether a PCI ID list is built into the module for
use by user level module utilities.
Note that if mode setting is enabled, user level drivers that access
display registers directly or that don't use the kernel graphics memory
manager will likely corrupt kernel graphics memory, disrupt output
configuration (possibly leading to hangs and/or blank displays), and
prevent panic/oops messages from appearing. So use caution when
enabling this code; be sure your user level code supports the new
interfaces.
A new SysRq key, 'g', provides emergency support for switching back to
the kernel's framebuffer console; which is useful for testing.
Co-authors: Dave Airlie <airlied@linux.ie>, Hong Liu <hong.liu@intel.com>
Signed-off-by: Jesse Barnes <jbarnes@virtuousgeek.org>
Signed-off-by: Eric Anholt <eric@anholt.net>
Signed-off-by: Dave Airlie <airlied@redhat.com>
2008-11-07 22:24:08 +00:00
|
|
|
#include <linux/module.h>
|
|
|
|
#include <linux/kernel.h>
|
2014-08-13 12:09:46 +00:00
|
|
|
#include <linux/console.h>
|
DRM: i915: add mode setting support
This commit adds i915 driver support for the DRM mode setting APIs.
Currently, VGA, LVDS, SDVO DVI & VGA, TV and DVO LVDS outputs are
supported. HDMI, DisplayPort and additional SDVO output support will
follow.
Support for the mode setting code is controlled by the new 'modeset'
module option. A new config option, CONFIG_DRM_I915_KMS controls the
default behavior, and whether a PCI ID list is built into the module for
use by user level module utilities.
Note that if mode setting is enabled, user level drivers that access
display registers directly or that don't use the kernel graphics memory
manager will likely corrupt kernel graphics memory, disrupt output
configuration (possibly leading to hangs and/or blank displays), and
prevent panic/oops messages from appearing. So use caution when
enabling this code; be sure your user level code supports the new
interfaces.
A new SysRq key, 'g', provides emergency support for switching back to
the kernel's framebuffer console; which is useful for testing.
Co-authors: Dave Airlie <airlied@linux.ie>, Hong Liu <hong.liu@intel.com>
Signed-off-by: Jesse Barnes <jbarnes@virtuousgeek.org>
Signed-off-by: Eric Anholt <eric@anholt.net>
Signed-off-by: Dave Airlie <airlied@redhat.com>
2008-11-07 22:24:08 +00:00
|
|
|
#include <linux/errno.h>
|
|
|
|
#include <linux/string.h>
|
|
|
|
#include <linux/mm.h>
|
|
|
|
#include <linux/tty.h>
|
|
|
|
#include <linux/sysrq.h>
|
|
|
|
#include <linux/delay.h>
|
|
|
|
#include <linux/fb.h>
|
|
|
|
#include <linux/init.h>
|
2010-02-01 05:38:10 +00:00
|
|
|
#include <linux/vga_switcheroo.h>
|
DRM: i915: add mode setting support
This commit adds i915 driver support for the DRM mode setting APIs.
Currently, VGA, LVDS, SDVO DVI & VGA, TV and DVO LVDS outputs are
supported. HDMI, DisplayPort and additional SDVO output support will
follow.
Support for the mode setting code is controlled by the new 'modeset'
module option. A new config option, CONFIG_DRM_I915_KMS controls the
default behavior, and whether a PCI ID list is built into the module for
use by user level module utilities.
Note that if mode setting is enabled, user level drivers that access
display registers directly or that don't use the kernel graphics memory
manager will likely corrupt kernel graphics memory, disrupt output
configuration (possibly leading to hangs and/or blank displays), and
prevent panic/oops messages from appearing. So use caution when
enabling this code; be sure your user level code supports the new
interfaces.
A new SysRq key, 'g', provides emergency support for switching back to
the kernel's framebuffer console; which is useful for testing.
Co-authors: Dave Airlie <airlied@linux.ie>, Hong Liu <hong.liu@intel.com>
Signed-off-by: Jesse Barnes <jbarnes@virtuousgeek.org>
Signed-off-by: Eric Anholt <eric@anholt.net>
Signed-off-by: Dave Airlie <airlied@redhat.com>
2008-11-07 22:24:08 +00:00
|
|
|
|
2012-10-02 17:01:07 +00:00
|
|
|
#include <drm/drmP.h>
|
|
|
|
#include <drm/drm_crtc.h>
|
|
|
|
#include <drm/drm_fb_helper.h>
|
DRM: i915: add mode setting support
This commit adds i915 driver support for the DRM mode setting APIs.
Currently, VGA, LVDS, SDVO DVI & VGA, TV and DVO LVDS outputs are
supported. HDMI, DisplayPort and additional SDVO output support will
follow.
Support for the mode setting code is controlled by the new 'modeset'
module option. A new config option, CONFIG_DRM_I915_KMS controls the
default behavior, and whether a PCI ID list is built into the module for
use by user level module utilities.
Note that if mode setting is enabled, user level drivers that access
display registers directly or that don't use the kernel graphics memory
manager will likely corrupt kernel graphics memory, disrupt output
configuration (possibly leading to hangs and/or blank displays), and
prevent panic/oops messages from appearing. So use caution when
enabling this code; be sure your user level code supports the new
interfaces.
A new SysRq key, 'g', provides emergency support for switching back to
the kernel's framebuffer console; which is useful for testing.
Co-authors: Dave Airlie <airlied@linux.ie>, Hong Liu <hong.liu@intel.com>
Signed-off-by: Jesse Barnes <jbarnes@virtuousgeek.org>
Signed-off-by: Eric Anholt <eric@anholt.net>
Signed-off-by: Dave Airlie <airlied@redhat.com>
2008-11-07 22:24:08 +00:00
|
|
|
#include "intel_drv.h"
|
2012-10-02 17:01:07 +00:00
|
|
|
#include <drm/i915_drm.h>
|
DRM: i915: add mode setting support
This commit adds i915 driver support for the DRM mode setting APIs.
Currently, VGA, LVDS, SDVO DVI & VGA, TV and DVO LVDS outputs are
supported. HDMI, DisplayPort and additional SDVO output support will
follow.
Support for the mode setting code is controlled by the new 'modeset'
module option. A new config option, CONFIG_DRM_I915_KMS controls the
default behavior, and whether a PCI ID list is built into the module for
use by user level module utilities.
Note that if mode setting is enabled, user level drivers that access
display registers directly or that don't use the kernel graphics memory
manager will likely corrupt kernel graphics memory, disrupt output
configuration (possibly leading to hangs and/or blank displays), and
prevent panic/oops messages from appearing. So use caution when
enabling this code; be sure your user level code supports the new
interfaces.
A new SysRq key, 'g', provides emergency support for switching back to
the kernel's framebuffer console; which is useful for testing.
Co-authors: Dave Airlie <airlied@linux.ie>, Hong Liu <hong.liu@intel.com>
Signed-off-by: Jesse Barnes <jbarnes@virtuousgeek.org>
Signed-off-by: Eric Anholt <eric@anholt.net>
Signed-off-by: Dave Airlie <airlied@redhat.com>
2008-11-07 22:24:08 +00:00
|
|
|
#include "i915_drv.h"
|
|
|
|
|
2014-06-18 13:05:19 +00:00
|
|
|
static int intel_fbdev_set_par(struct fb_info *info)
|
|
|
|
{
|
|
|
|
struct drm_fb_helper *fb_helper = info->par;
|
|
|
|
struct intel_fbdev *ifbdev =
|
|
|
|
container_of(fb_helper, struct intel_fbdev, helper);
|
|
|
|
int ret;
|
|
|
|
|
|
|
|
ret = drm_fb_helper_set_par(info);
|
|
|
|
|
|
|
|
if (ret == 0) {
|
|
|
|
mutex_lock(&fb_helper->dev->struct_mutex);
|
2015-07-09 16:56:41 +00:00
|
|
|
intel_fb_obj_invalidate(ifbdev->fb->obj, ORIGIN_GTT);
|
2014-06-18 13:05:19 +00:00
|
|
|
mutex_unlock(&fb_helper->dev->struct_mutex);
|
|
|
|
}
|
|
|
|
|
|
|
|
return ret;
|
|
|
|
}
|
|
|
|
|
2015-03-10 00:57:07 +00:00
|
|
|
static int intel_fbdev_blank(int blank, struct fb_info *info)
|
|
|
|
{
|
|
|
|
struct drm_fb_helper *fb_helper = info->par;
|
|
|
|
struct intel_fbdev *ifbdev =
|
|
|
|
container_of(fb_helper, struct intel_fbdev, helper);
|
|
|
|
int ret;
|
|
|
|
|
|
|
|
ret = drm_fb_helper_blank(blank, info);
|
|
|
|
|
|
|
|
if (ret == 0) {
|
|
|
|
mutex_lock(&fb_helper->dev->struct_mutex);
|
2015-06-18 18:43:24 +00:00
|
|
|
intel_fb_obj_invalidate(ifbdev->fb->obj, ORIGIN_GTT);
|
2015-03-10 00:57:07 +00:00
|
|
|
mutex_unlock(&fb_helper->dev->struct_mutex);
|
|
|
|
}
|
|
|
|
|
|
|
|
return ret;
|
|
|
|
}
|
|
|
|
|
2015-05-28 17:26:58 +00:00
|
|
|
static int intel_fbdev_pan_display(struct fb_var_screeninfo *var,
|
|
|
|
struct fb_info *info)
|
|
|
|
{
|
|
|
|
struct drm_fb_helper *fb_helper = info->par;
|
|
|
|
struct intel_fbdev *ifbdev =
|
|
|
|
container_of(fb_helper, struct intel_fbdev, helper);
|
|
|
|
|
|
|
|
int ret;
|
|
|
|
ret = drm_fb_helper_pan_display(var, info);
|
|
|
|
|
|
|
|
if (ret == 0) {
|
|
|
|
mutex_lock(&fb_helper->dev->struct_mutex);
|
2015-06-18 18:43:24 +00:00
|
|
|
intel_fb_obj_invalidate(ifbdev->fb->obj, ORIGIN_GTT);
|
2015-05-28 17:26:58 +00:00
|
|
|
mutex_unlock(&fb_helper->dev->struct_mutex);
|
|
|
|
}
|
|
|
|
|
|
|
|
return ret;
|
|
|
|
}
|
|
|
|
|
DRM: i915: add mode setting support
This commit adds i915 driver support for the DRM mode setting APIs.
Currently, VGA, LVDS, SDVO DVI & VGA, TV and DVO LVDS outputs are
supported. HDMI, DisplayPort and additional SDVO output support will
follow.
Support for the mode setting code is controlled by the new 'modeset'
module option. A new config option, CONFIG_DRM_I915_KMS controls the
default behavior, and whether a PCI ID list is built into the module for
use by user level module utilities.
Note that if mode setting is enabled, user level drivers that access
display registers directly or that don't use the kernel graphics memory
manager will likely corrupt kernel graphics memory, disrupt output
configuration (possibly leading to hangs and/or blank displays), and
prevent panic/oops messages from appearing. So use caution when
enabling this code; be sure your user level code supports the new
interfaces.
A new SysRq key, 'g', provides emergency support for switching back to
the kernel's framebuffer console; which is useful for testing.
Co-authors: Dave Airlie <airlied@linux.ie>, Hong Liu <hong.liu@intel.com>
Signed-off-by: Jesse Barnes <jbarnes@virtuousgeek.org>
Signed-off-by: Eric Anholt <eric@anholt.net>
Signed-off-by: Dave Airlie <airlied@redhat.com>
2008-11-07 22:24:08 +00:00
|
|
|
static struct fb_ops intelfb_ops = {
|
|
|
|
.owner = THIS_MODULE,
|
2009-08-28 05:46:53 +00:00
|
|
|
.fb_check_var = drm_fb_helper_check_var,
|
2014-06-18 13:05:19 +00:00
|
|
|
.fb_set_par = intel_fbdev_set_par,
|
2015-07-31 10:51:56 +00:00
|
|
|
.fb_fillrect = drm_fb_helper_cfb_fillrect,
|
|
|
|
.fb_copyarea = drm_fb_helper_cfb_copyarea,
|
|
|
|
.fb_imageblit = drm_fb_helper_cfb_imageblit,
|
2015-05-28 17:26:58 +00:00
|
|
|
.fb_pan_display = intel_fbdev_pan_display,
|
2015-03-10 00:57:07 +00:00
|
|
|
.fb_blank = intel_fbdev_blank,
|
2009-10-04 23:58:02 +00:00
|
|
|
.fb_setcmap = drm_fb_helper_setcmap,
|
2010-08-02 19:07:50 +00:00
|
|
|
.fb_debug_enter = drm_fb_helper_debug_enter,
|
|
|
|
.fb_debug_leave = drm_fb_helper_debug_leave,
|
DRM: i915: add mode setting support
This commit adds i915 driver support for the DRM mode setting APIs.
Currently, VGA, LVDS, SDVO DVI & VGA, TV and DVO LVDS outputs are
supported. HDMI, DisplayPort and additional SDVO output support will
follow.
Support for the mode setting code is controlled by the new 'modeset'
module option. A new config option, CONFIG_DRM_I915_KMS controls the
default behavior, and whether a PCI ID list is built into the module for
use by user level module utilities.
Note that if mode setting is enabled, user level drivers that access
display registers directly or that don't use the kernel graphics memory
manager will likely corrupt kernel graphics memory, disrupt output
configuration (possibly leading to hangs and/or blank displays), and
prevent panic/oops messages from appearing. So use caution when
enabling this code; be sure your user level code supports the new
interfaces.
A new SysRq key, 'g', provides emergency support for switching back to
the kernel's framebuffer console; which is useful for testing.
Co-authors: Dave Airlie <airlied@linux.ie>, Hong Liu <hong.liu@intel.com>
Signed-off-by: Jesse Barnes <jbarnes@virtuousgeek.org>
Signed-off-by: Eric Anholt <eric@anholt.net>
Signed-off-by: Dave Airlie <airlied@redhat.com>
2008-11-07 22:24:08 +00:00
|
|
|
};
|
|
|
|
|
2013-11-25 23:51:16 +00:00
|
|
|
static int intelfb_alloc(struct drm_fb_helper *helper,
|
|
|
|
struct drm_fb_helper_surface_size *sizes)
|
DRM: i915: add mode setting support
This commit adds i915 driver support for the DRM mode setting APIs.
Currently, VGA, LVDS, SDVO DVI & VGA, TV and DVO LVDS outputs are
supported. HDMI, DisplayPort and additional SDVO output support will
follow.
Support for the mode setting code is controlled by the new 'modeset'
module option. A new config option, CONFIG_DRM_I915_KMS controls the
default behavior, and whether a PCI ID list is built into the module for
use by user level module utilities.
Note that if mode setting is enabled, user level drivers that access
display registers directly or that don't use the kernel graphics memory
manager will likely corrupt kernel graphics memory, disrupt output
configuration (possibly leading to hangs and/or blank displays), and
prevent panic/oops messages from appearing. So use caution when
enabling this code; be sure your user level code supports the new
interfaces.
A new SysRq key, 'g', provides emergency support for switching back to
the kernel's framebuffer console; which is useful for testing.
Co-authors: Dave Airlie <airlied@linux.ie>, Hong Liu <hong.liu@intel.com>
Signed-off-by: Jesse Barnes <jbarnes@virtuousgeek.org>
Signed-off-by: Eric Anholt <eric@anholt.net>
Signed-off-by: Dave Airlie <airlied@redhat.com>
2008-11-07 22:24:08 +00:00
|
|
|
{
|
2013-05-31 17:07:05 +00:00
|
|
|
struct intel_fbdev *ifbdev =
|
|
|
|
container_of(helper, struct intel_fbdev, helper);
|
2015-12-19 14:40:39 +00:00
|
|
|
struct drm_framebuffer *fb;
|
2013-05-31 17:07:05 +00:00
|
|
|
struct drm_device *dev = helper->dev;
|
2015-09-23 15:52:23 +00:00
|
|
|
struct drm_i915_private *dev_priv = to_i915(dev);
|
2016-03-30 13:57:10 +00:00
|
|
|
struct i915_ggtt *ggtt = &dev_priv->ggtt;
|
2012-05-24 18:08:56 +00:00
|
|
|
struct drm_mode_fb_cmd2 mode_cmd = {};
|
2015-09-23 15:52:23 +00:00
|
|
|
struct drm_i915_gem_object *obj = NULL;
|
2010-12-20 19:10:39 +00:00
|
|
|
int size, ret;
|
DRM: i915: add mode setting support
This commit adds i915 driver support for the DRM mode setting APIs.
Currently, VGA, LVDS, SDVO DVI & VGA, TV and DVO LVDS outputs are
supported. HDMI, DisplayPort and additional SDVO output support will
follow.
Support for the mode setting code is controlled by the new 'modeset'
module option. A new config option, CONFIG_DRM_I915_KMS controls the
default behavior, and whether a PCI ID list is built into the module for
use by user level module utilities.
Note that if mode setting is enabled, user level drivers that access
display registers directly or that don't use the kernel graphics memory
manager will likely corrupt kernel graphics memory, disrupt output
configuration (possibly leading to hangs and/or blank displays), and
prevent panic/oops messages from appearing. So use caution when
enabling this code; be sure your user level code supports the new
interfaces.
A new SysRq key, 'g', provides emergency support for switching back to
the kernel's framebuffer console; which is useful for testing.
Co-authors: Dave Airlie <airlied@linux.ie>, Hong Liu <hong.liu@intel.com>
Signed-off-by: Jesse Barnes <jbarnes@virtuousgeek.org>
Signed-off-by: Eric Anholt <eric@anholt.net>
Signed-off-by: Dave Airlie <airlied@redhat.com>
2008-11-07 22:24:08 +00:00
|
|
|
|
2009-10-06 03:54:01 +00:00
|
|
|
/* we don't do packed 24bpp */
|
2010-03-30 05:34:13 +00:00
|
|
|
if (sizes->surface_bpp == 24)
|
|
|
|
sizes->surface_bpp = 32;
|
2009-10-06 03:54:01 +00:00
|
|
|
|
2010-03-30 05:34:13 +00:00
|
|
|
mode_cmd.width = sizes->surface_width;
|
|
|
|
mode_cmd.height = sizes->surface_height;
|
DRM: i915: add mode setting support
This commit adds i915 driver support for the DRM mode setting APIs.
Currently, VGA, LVDS, SDVO DVI & VGA, TV and DVO LVDS outputs are
supported. HDMI, DisplayPort and additional SDVO output support will
follow.
Support for the mode setting code is controlled by the new 'modeset'
module option. A new config option, CONFIG_DRM_I915_KMS controls the
default behavior, and whether a PCI ID list is built into the module for
use by user level module utilities.
Note that if mode setting is enabled, user level drivers that access
display registers directly or that don't use the kernel graphics memory
manager will likely corrupt kernel graphics memory, disrupt output
configuration (possibly leading to hangs and/or blank displays), and
prevent panic/oops messages from appearing. So use caution when
enabling this code; be sure your user level code supports the new
interfaces.
A new SysRq key, 'g', provides emergency support for switching back to
the kernel's framebuffer console; which is useful for testing.
Co-authors: Dave Airlie <airlied@linux.ie>, Hong Liu <hong.liu@intel.com>
Signed-off-by: Jesse Barnes <jbarnes@virtuousgeek.org>
Signed-off-by: Eric Anholt <eric@anholt.net>
Signed-off-by: Dave Airlie <airlied@redhat.com>
2008-11-07 22:24:08 +00:00
|
|
|
|
2013-10-18 21:48:24 +00:00
|
|
|
mode_cmd.pitches[0] = ALIGN(mode_cmd.width *
|
|
|
|
DIV_ROUND_UP(sizes->surface_bpp, 8), 64);
|
2011-11-14 22:51:28 +00:00
|
|
|
mode_cmd.pixel_format = drm_mode_legacy_fb_format(sizes->surface_bpp,
|
|
|
|
sizes->surface_depth);
|
DRM: i915: add mode setting support
This commit adds i915 driver support for the DRM mode setting APIs.
Currently, VGA, LVDS, SDVO DVI & VGA, TV and DVO LVDS outputs are
supported. HDMI, DisplayPort and additional SDVO output support will
follow.
Support for the mode setting code is controlled by the new 'modeset'
module option. A new config option, CONFIG_DRM_I915_KMS controls the
default behavior, and whether a PCI ID list is built into the module for
use by user level module utilities.
Note that if mode setting is enabled, user level drivers that access
display registers directly or that don't use the kernel graphics memory
manager will likely corrupt kernel graphics memory, disrupt output
configuration (possibly leading to hangs and/or blank displays), and
prevent panic/oops messages from appearing. So use caution when
enabling this code; be sure your user level code supports the new
interfaces.
A new SysRq key, 'g', provides emergency support for switching back to
the kernel's framebuffer console; which is useful for testing.
Co-authors: Dave Airlie <airlied@linux.ie>, Hong Liu <hong.liu@intel.com>
Signed-off-by: Jesse Barnes <jbarnes@virtuousgeek.org>
Signed-off-by: Eric Anholt <eric@anholt.net>
Signed-off-by: Dave Airlie <airlied@redhat.com>
2008-11-07 22:24:08 +00:00
|
|
|
|
2015-06-30 09:06:27 +00:00
|
|
|
mutex_lock(&dev->struct_mutex);
|
|
|
|
|
2011-11-14 22:51:28 +00:00
|
|
|
size = mode_cmd.pitches[0] * mode_cmd.height;
|
2014-07-01 18:39:41 +00:00
|
|
|
size = PAGE_ALIGN(size);
|
2015-09-23 15:52:23 +00:00
|
|
|
|
|
|
|
/* If the FB is too big, just don't use it since fbdev is not very
|
|
|
|
* important and we should probably use that space with FBC or other
|
|
|
|
* features. */
|
2016-03-30 13:57:10 +00:00
|
|
|
if (size * 2 < ggtt->stolen_usable_size)
|
2015-09-23 15:52:23 +00:00
|
|
|
obj = i915_gem_object_create_stolen(dev, size);
|
2012-11-15 11:32:27 +00:00
|
|
|
if (obj == NULL)
|
2016-04-22 18:14:32 +00:00
|
|
|
obj = i915_gem_object_create(dev, size);
|
2016-04-25 12:32:13 +00:00
|
|
|
if (IS_ERR(obj)) {
|
2009-06-28 22:42:17 +00:00
|
|
|
DRM_ERROR("failed to allocate framebuffer\n");
|
2016-04-25 12:32:13 +00:00
|
|
|
ret = PTR_ERR(obj);
|
DRM: i915: add mode setting support
This commit adds i915 driver support for the DRM mode setting APIs.
Currently, VGA, LVDS, SDVO DVI & VGA, TV and DVO LVDS outputs are
supported. HDMI, DisplayPort and additional SDVO output support will
follow.
Support for the mode setting code is controlled by the new 'modeset'
module option. A new config option, CONFIG_DRM_I915_KMS controls the
default behavior, and whether a PCI ID list is built into the module for
use by user level module utilities.
Note that if mode setting is enabled, user level drivers that access
display registers directly or that don't use the kernel graphics memory
manager will likely corrupt kernel graphics memory, disrupt output
configuration (possibly leading to hangs and/or blank displays), and
prevent panic/oops messages from appearing. So use caution when
enabling this code; be sure your user level code supports the new
interfaces.
A new SysRq key, 'g', provides emergency support for switching back to
the kernel's framebuffer console; which is useful for testing.
Co-authors: Dave Airlie <airlied@linux.ie>, Hong Liu <hong.liu@intel.com>
Signed-off-by: Jesse Barnes <jbarnes@virtuousgeek.org>
Signed-off-by: Eric Anholt <eric@anholt.net>
Signed-off-by: Dave Airlie <airlied@redhat.com>
2008-11-07 22:24:08 +00:00
|
|
|
goto out;
|
|
|
|
}
|
|
|
|
|
2014-02-10 17:00:39 +00:00
|
|
|
fb = __intel_framebuffer_create(dev, &mode_cmd, obj);
|
|
|
|
if (IS_ERR(fb)) {
|
2015-10-22 11:37:18 +00:00
|
|
|
drm_gem_object_unreference(&obj->base);
|
2014-02-10 17:00:39 +00:00
|
|
|
ret = PTR_ERR(fb);
|
2015-10-22 11:37:18 +00:00
|
|
|
goto out;
|
2014-10-30 16:39:38 +00:00
|
|
|
}
|
|
|
|
|
2015-06-30 09:06:27 +00:00
|
|
|
mutex_unlock(&dev->struct_mutex);
|
|
|
|
|
2014-02-10 17:00:39 +00:00
|
|
|
ifbdev->fb = to_intel_framebuffer(fb);
|
2013-11-25 23:51:16 +00:00
|
|
|
|
|
|
|
return 0;
|
|
|
|
|
|
|
|
out:
|
2015-06-30 09:06:27 +00:00
|
|
|
mutex_unlock(&dev->struct_mutex);
|
2013-11-25 23:51:16 +00:00
|
|
|
return ret;
|
|
|
|
}
|
|
|
|
|
|
|
|
static int intelfb_create(struct drm_fb_helper *helper,
|
|
|
|
struct drm_fb_helper_surface_size *sizes)
|
|
|
|
{
|
|
|
|
struct intel_fbdev *ifbdev =
|
|
|
|
container_of(helper, struct intel_fbdev, helper);
|
2014-02-07 20:10:38 +00:00
|
|
|
struct intel_framebuffer *intel_fb = ifbdev->fb;
|
2013-11-25 23:51:16 +00:00
|
|
|
struct drm_device *dev = helper->dev;
|
2016-03-30 13:57:10 +00:00
|
|
|
struct drm_i915_private *dev_priv = to_i915(dev);
|
|
|
|
struct i915_ggtt *ggtt = &dev_priv->ggtt;
|
2013-11-25 23:51:16 +00:00
|
|
|
struct fb_info *info;
|
|
|
|
struct drm_framebuffer *fb;
|
2016-04-28 08:56:39 +00:00
|
|
|
struct i915_vma *vma;
|
2013-11-25 23:51:16 +00:00
|
|
|
struct drm_i915_gem_object *obj;
|
2014-03-07 16:57:51 +00:00
|
|
|
bool prealloc = false;
|
2016-04-28 08:56:39 +00:00
|
|
|
void *vaddr;
|
|
|
|
int ret;
|
2013-11-25 23:51:16 +00:00
|
|
|
|
2014-04-23 07:54:31 +00:00
|
|
|
if (intel_fb &&
|
|
|
|
(sizes->fb_width > intel_fb->base.width ||
|
|
|
|
sizes->fb_height > intel_fb->base.height)) {
|
|
|
|
DRM_DEBUG_KMS("BIOS fb too small (%dx%d), we require (%dx%d),"
|
|
|
|
" releasing it\n",
|
|
|
|
intel_fb->base.width, intel_fb->base.height,
|
|
|
|
sizes->fb_width, sizes->fb_height);
|
|
|
|
drm_framebuffer_unreference(&intel_fb->base);
|
|
|
|
intel_fb = ifbdev->fb = NULL;
|
|
|
|
}
|
2014-02-07 20:10:38 +00:00
|
|
|
if (!intel_fb || WARN_ON(!intel_fb->obj)) {
|
2013-11-26 19:25:54 +00:00
|
|
|
DRM_DEBUG_KMS("no BIOS fb, allocating a new one\n");
|
2013-11-25 23:51:16 +00:00
|
|
|
ret = intelfb_alloc(helper, sizes);
|
|
|
|
if (ret)
|
2015-06-30 09:06:27 +00:00
|
|
|
return ret;
|
2014-02-07 20:10:38 +00:00
|
|
|
intel_fb = ifbdev->fb;
|
2013-11-25 23:51:16 +00:00
|
|
|
} else {
|
2013-11-26 19:25:54 +00:00
|
|
|
DRM_DEBUG_KMS("re-using BIOS fb\n");
|
2014-03-07 16:57:51 +00:00
|
|
|
prealloc = true;
|
2013-11-25 23:51:16 +00:00
|
|
|
sizes->fb_width = intel_fb->base.width;
|
|
|
|
sizes->fb_height = intel_fb->base.height;
|
|
|
|
}
|
|
|
|
|
|
|
|
obj = intel_fb->obj;
|
|
|
|
|
2015-06-30 09:06:27 +00:00
|
|
|
mutex_lock(&dev->struct_mutex);
|
|
|
|
|
2015-12-04 16:05:26 +00:00
|
|
|
/* Pin the GGTT vma for our access via info->screen_base.
|
|
|
|
* This also validates that any existing fb inherited from the
|
|
|
|
* BIOS is suitable for own access.
|
|
|
|
*/
|
2016-02-15 20:54:43 +00:00
|
|
|
ret = intel_pin_and_fence_fb_obj(&ifbdev->fb->base, BIT(DRM_ROTATE_0));
|
2015-12-04 16:05:26 +00:00
|
|
|
if (ret)
|
|
|
|
goto out_unlock;
|
|
|
|
|
2015-07-31 10:51:56 +00:00
|
|
|
info = drm_fb_helper_alloc_fbi(helper);
|
|
|
|
if (IS_ERR(info)) {
|
2015-11-18 15:29:51 +00:00
|
|
|
DRM_ERROR("Failed to allocate fb_info\n");
|
2015-07-31 10:51:56 +00:00
|
|
|
ret = PTR_ERR(info);
|
2009-02-11 14:26:36 +00:00
|
|
|
goto out_unpin;
|
DRM: i915: add mode setting support
This commit adds i915 driver support for the DRM mode setting APIs.
Currently, VGA, LVDS, SDVO DVI & VGA, TV and DVO LVDS outputs are
supported. HDMI, DisplayPort and additional SDVO output support will
follow.
Support for the mode setting code is controlled by the new 'modeset'
module option. A new config option, CONFIG_DRM_I915_KMS controls the
default behavior, and whether a PCI ID list is built into the module for
use by user level module utilities.
Note that if mode setting is enabled, user level drivers that access
display registers directly or that don't use the kernel graphics memory
manager will likely corrupt kernel graphics memory, disrupt output
configuration (possibly leading to hangs and/or blank displays), and
prevent panic/oops messages from appearing. So use caution when
enabling this code; be sure your user level code supports the new
interfaces.
A new SysRq key, 'g', provides emergency support for switching back to
the kernel's framebuffer console; which is useful for testing.
Co-authors: Dave Airlie <airlied@linux.ie>, Hong Liu <hong.liu@intel.com>
Signed-off-by: Jesse Barnes <jbarnes@virtuousgeek.org>
Signed-off-by: Eric Anholt <eric@anholt.net>
Signed-off-by: Dave Airlie <airlied@redhat.com>
2008-11-07 22:24:08 +00:00
|
|
|
}
|
|
|
|
|
2013-05-31 17:07:05 +00:00
|
|
|
info->par = helper;
|
DRM: i915: add mode setting support
This commit adds i915 driver support for the DRM mode setting APIs.
Currently, VGA, LVDS, SDVO DVI & VGA, TV and DVO LVDS outputs are
supported. HDMI, DisplayPort and additional SDVO output support will
follow.
Support for the mode setting code is controlled by the new 'modeset'
module option. A new config option, CONFIG_DRM_I915_KMS controls the
default behavior, and whether a PCI ID list is built into the module for
use by user level module utilities.
Note that if mode setting is enabled, user level drivers that access
display registers directly or that don't use the kernel graphics memory
manager will likely corrupt kernel graphics memory, disrupt output
configuration (possibly leading to hangs and/or blank displays), and
prevent panic/oops messages from appearing. So use caution when
enabling this code; be sure your user level code supports the new
interfaces.
A new SysRq key, 'g', provides emergency support for switching back to
the kernel's framebuffer console; which is useful for testing.
Co-authors: Dave Airlie <airlied@linux.ie>, Hong Liu <hong.liu@intel.com>
Signed-off-by: Jesse Barnes <jbarnes@virtuousgeek.org>
Signed-off-by: Eric Anholt <eric@anholt.net>
Signed-off-by: Dave Airlie <airlied@redhat.com>
2008-11-07 22:24:08 +00:00
|
|
|
|
2014-02-07 20:10:38 +00:00
|
|
|
fb = &ifbdev->fb->base;
|
DRM: i915: add mode setting support
This commit adds i915 driver support for the DRM mode setting APIs.
Currently, VGA, LVDS, SDVO DVI & VGA, TV and DVO LVDS outputs are
supported. HDMI, DisplayPort and additional SDVO output support will
follow.
Support for the mode setting code is controlled by the new 'modeset'
module option. A new config option, CONFIG_DRM_I915_KMS controls the
default behavior, and whether a PCI ID list is built into the module for
use by user level module utilities.
Note that if mode setting is enabled, user level drivers that access
display registers directly or that don't use the kernel graphics memory
manager will likely corrupt kernel graphics memory, disrupt output
configuration (possibly leading to hangs and/or blank displays), and
prevent panic/oops messages from appearing. So use caution when
enabling this code; be sure your user level code supports the new
interfaces.
A new SysRq key, 'g', provides emergency support for switching back to
the kernel's framebuffer console; which is useful for testing.
Co-authors: Dave Airlie <airlied@linux.ie>, Hong Liu <hong.liu@intel.com>
Signed-off-by: Jesse Barnes <jbarnes@virtuousgeek.org>
Signed-off-by: Eric Anholt <eric@anholt.net>
Signed-off-by: Dave Airlie <airlied@redhat.com>
2008-11-07 22:24:08 +00:00
|
|
|
|
2010-03-30 05:34:13 +00:00
|
|
|
ifbdev->helper.fb = fb;
|
2009-08-28 05:46:53 +00:00
|
|
|
|
DRM: i915: add mode setting support
This commit adds i915 driver support for the DRM mode setting APIs.
Currently, VGA, LVDS, SDVO DVI & VGA, TV and DVO LVDS outputs are
supported. HDMI, DisplayPort and additional SDVO output support will
follow.
Support for the mode setting code is controlled by the new 'modeset'
module option. A new config option, CONFIG_DRM_I915_KMS controls the
default behavior, and whether a PCI ID list is built into the module for
use by user level module utilities.
Note that if mode setting is enabled, user level drivers that access
display registers directly or that don't use the kernel graphics memory
manager will likely corrupt kernel graphics memory, disrupt output
configuration (possibly leading to hangs and/or blank displays), and
prevent panic/oops messages from appearing. So use caution when
enabling this code; be sure your user level code supports the new
interfaces.
A new SysRq key, 'g', provides emergency support for switching back to
the kernel's framebuffer console; which is useful for testing.
Co-authors: Dave Airlie <airlied@linux.ie>, Hong Liu <hong.liu@intel.com>
Signed-off-by: Jesse Barnes <jbarnes@virtuousgeek.org>
Signed-off-by: Eric Anholt <eric@anholt.net>
Signed-off-by: Dave Airlie <airlied@redhat.com>
2008-11-07 22:24:08 +00:00
|
|
|
strcpy(info->fix.id, "inteldrmfb");
|
|
|
|
|
2010-06-23 19:56:12 +00:00
|
|
|
info->flags = FBINFO_DEFAULT | FBINFO_CAN_FORCE_OUTPUT;
|
DRM: i915: add mode setting support
This commit adds i915 driver support for the DRM mode setting APIs.
Currently, VGA, LVDS, SDVO DVI & VGA, TV and DVO LVDS outputs are
supported. HDMI, DisplayPort and additional SDVO output support will
follow.
Support for the mode setting code is controlled by the new 'modeset'
module option. A new config option, CONFIG_DRM_I915_KMS controls the
default behavior, and whether a PCI ID list is built into the module for
use by user level module utilities.
Note that if mode setting is enabled, user level drivers that access
display registers directly or that don't use the kernel graphics memory
manager will likely corrupt kernel graphics memory, disrupt output
configuration (possibly leading to hangs and/or blank displays), and
prevent panic/oops messages from appearing. So use caution when
enabling this code; be sure your user level code supports the new
interfaces.
A new SysRq key, 'g', provides emergency support for switching back to
the kernel's framebuffer console; which is useful for testing.
Co-authors: Dave Airlie <airlied@linux.ie>, Hong Liu <hong.liu@intel.com>
Signed-off-by: Jesse Barnes <jbarnes@virtuousgeek.org>
Signed-off-by: Eric Anholt <eric@anholt.net>
Signed-off-by: Dave Airlie <airlied@redhat.com>
2008-11-07 22:24:08 +00:00
|
|
|
info->fbops = &intelfb_ops;
|
|
|
|
|
2016-04-28 08:56:39 +00:00
|
|
|
vma = i915_gem_obj_to_ggtt(obj);
|
|
|
|
|
2009-06-16 22:34:38 +00:00
|
|
|
/* setup aperture base/size for vesafb takeover */
|
2010-05-16 15:27:03 +00:00
|
|
|
info->apertures->ranges[0].base = dev->mode_config.fb_base;
|
2016-03-30 13:57:10 +00:00
|
|
|
info->apertures->ranges[0].size = ggtt->mappable_end;
|
2009-06-16 22:34:38 +00:00
|
|
|
|
2016-04-28 08:56:39 +00:00
|
|
|
info->fix.smem_start = dev->mode_config.fb_base + vma->node.start;
|
|
|
|
info->fix.smem_len = vma->node.size;
|
DRM: i915: add mode setting support
This commit adds i915 driver support for the DRM mode setting APIs.
Currently, VGA, LVDS, SDVO DVI & VGA, TV and DVO LVDS outputs are
supported. HDMI, DisplayPort and additional SDVO output support will
follow.
Support for the mode setting code is controlled by the new 'modeset'
module option. A new config option, CONFIG_DRM_I915_KMS controls the
default behavior, and whether a PCI ID list is built into the module for
use by user level module utilities.
Note that if mode setting is enabled, user level drivers that access
display registers directly or that don't use the kernel graphics memory
manager will likely corrupt kernel graphics memory, disrupt output
configuration (possibly leading to hangs and/or blank displays), and
prevent panic/oops messages from appearing. So use caution when
enabling this code; be sure your user level code supports the new
interfaces.
A new SysRq key, 'g', provides emergency support for switching back to
the kernel's framebuffer console; which is useful for testing.
Co-authors: Dave Airlie <airlied@linux.ie>, Hong Liu <hong.liu@intel.com>
Signed-off-by: Jesse Barnes <jbarnes@virtuousgeek.org>
Signed-off-by: Eric Anholt <eric@anholt.net>
Signed-off-by: Dave Airlie <airlied@redhat.com>
2008-11-07 22:24:08 +00:00
|
|
|
|
2016-04-28 08:56:39 +00:00
|
|
|
vaddr = i915_vma_pin_iomap(vma);
|
|
|
|
if (IS_ERR(vaddr)) {
|
2015-11-18 15:29:51 +00:00
|
|
|
DRM_ERROR("Failed to remap framebuffer into virtual memory\n");
|
2016-04-28 08:56:39 +00:00
|
|
|
ret = PTR_ERR(vaddr);
|
2015-07-31 10:51:56 +00:00
|
|
|
goto out_destroy_fbi;
|
DRM: i915: add mode setting support
This commit adds i915 driver support for the DRM mode setting APIs.
Currently, VGA, LVDS, SDVO DVI & VGA, TV and DVO LVDS outputs are
supported. HDMI, DisplayPort and additional SDVO output support will
follow.
Support for the mode setting code is controlled by the new 'modeset'
module option. A new config option, CONFIG_DRM_I915_KMS controls the
default behavior, and whether a PCI ID list is built into the module for
use by user level module utilities.
Note that if mode setting is enabled, user level drivers that access
display registers directly or that don't use the kernel graphics memory
manager will likely corrupt kernel graphics memory, disrupt output
configuration (possibly leading to hangs and/or blank displays), and
prevent panic/oops messages from appearing. So use caution when
enabling this code; be sure your user level code supports the new
interfaces.
A new SysRq key, 'g', provides emergency support for switching back to
the kernel's framebuffer console; which is useful for testing.
Co-authors: Dave Airlie <airlied@linux.ie>, Hong Liu <hong.liu@intel.com>
Signed-off-by: Jesse Barnes <jbarnes@virtuousgeek.org>
Signed-off-by: Eric Anholt <eric@anholt.net>
Signed-off-by: Dave Airlie <airlied@redhat.com>
2008-11-07 22:24:08 +00:00
|
|
|
}
|
2016-04-28 08:56:39 +00:00
|
|
|
info->screen_base = vaddr;
|
|
|
|
info->screen_size = vma->node.size;
|
DRM: i915: add mode setting support
This commit adds i915 driver support for the DRM mode setting APIs.
Currently, VGA, LVDS, SDVO DVI & VGA, TV and DVO LVDS outputs are
supported. HDMI, DisplayPort and additional SDVO output support will
follow.
Support for the mode setting code is controlled by the new 'modeset'
module option. A new config option, CONFIG_DRM_I915_KMS controls the
default behavior, and whether a PCI ID list is built into the module for
use by user level module utilities.
Note that if mode setting is enabled, user level drivers that access
display registers directly or that don't use the kernel graphics memory
manager will likely corrupt kernel graphics memory, disrupt output
configuration (possibly leading to hangs and/or blank displays), and
prevent panic/oops messages from appearing. So use caution when
enabling this code; be sure your user level code supports the new
interfaces.
A new SysRq key, 'g', provides emergency support for switching back to
the kernel's framebuffer console; which is useful for testing.
Co-authors: Dave Airlie <airlied@linux.ie>, Hong Liu <hong.liu@intel.com>
Signed-off-by: Jesse Barnes <jbarnes@virtuousgeek.org>
Signed-off-by: Eric Anholt <eric@anholt.net>
Signed-off-by: Dave Airlie <airlied@redhat.com>
2008-11-07 22:24:08 +00:00
|
|
|
|
2013-03-26 16:25:45 +00:00
|
|
|
/* This driver doesn't need a VT switch to restore the mode on resume */
|
|
|
|
info->skip_vt_switch = true;
|
|
|
|
|
2011-12-19 22:06:49 +00:00
|
|
|
drm_fb_helper_fill_fix(info, fb->pitches[0], fb->depth);
|
2010-03-30 05:34:13 +00:00
|
|
|
drm_fb_helper_fill_var(info, &ifbdev->helper, sizes->fb_width, sizes->fb_height);
|
DRM: i915: add mode setting support
This commit adds i915 driver support for the DRM mode setting APIs.
Currently, VGA, LVDS, SDVO DVI & VGA, TV and DVO LVDS outputs are
supported. HDMI, DisplayPort and additional SDVO output support will
follow.
Support for the mode setting code is controlled by the new 'modeset'
module option. A new config option, CONFIG_DRM_I915_KMS controls the
default behavior, and whether a PCI ID list is built into the module for
use by user level module utilities.
Note that if mode setting is enabled, user level drivers that access
display registers directly or that don't use the kernel graphics memory
manager will likely corrupt kernel graphics memory, disrupt output
configuration (possibly leading to hangs and/or blank displays), and
prevent panic/oops messages from appearing. So use caution when
enabling this code; be sure your user level code supports the new
interfaces.
A new SysRq key, 'g', provides emergency support for switching back to
the kernel's framebuffer console; which is useful for testing.
Co-authors: Dave Airlie <airlied@linux.ie>, Hong Liu <hong.liu@intel.com>
Signed-off-by: Jesse Barnes <jbarnes@virtuousgeek.org>
Signed-off-by: Eric Anholt <eric@anholt.net>
Signed-off-by: Dave Airlie <airlied@redhat.com>
2008-11-07 22:24:08 +00:00
|
|
|
|
2012-12-16 12:15:41 +00:00
|
|
|
/* If the object is shmemfs backed, it will have given us zeroed pages.
|
|
|
|
* If the object is stolen however, it will be full of whatever
|
|
|
|
* garbage was left in there.
|
|
|
|
*/
|
2014-03-07 16:57:51 +00:00
|
|
|
if (ifbdev->fb->obj->stolen && !prealloc)
|
2012-12-16 12:15:41 +00:00
|
|
|
memset_io(info->screen_base, 0, info->screen_size);
|
|
|
|
|
2012-02-06 09:58:19 +00:00
|
|
|
/* Use default scratch pixmap (info->pixmap.flags = FB_PIXMAP_SYSTEM) */
|
DRM: i915: add mode setting support
This commit adds i915 driver support for the DRM mode setting APIs.
Currently, VGA, LVDS, SDVO DVI & VGA, TV and DVO LVDS outputs are
supported. HDMI, DisplayPort and additional SDVO output support will
follow.
Support for the mode setting code is controlled by the new 'modeset'
module option. A new config option, CONFIG_DRM_I915_KMS controls the
default behavior, and whether a PCI ID list is built into the module for
use by user level module utilities.
Note that if mode setting is enabled, user level drivers that access
display registers directly or that don't use the kernel graphics memory
manager will likely corrupt kernel graphics memory, disrupt output
configuration (possibly leading to hangs and/or blank displays), and
prevent panic/oops messages from appearing. So use caution when
enabling this code; be sure your user level code supports the new
interfaces.
A new SysRq key, 'g', provides emergency support for switching back to
the kernel's framebuffer console; which is useful for testing.
Co-authors: Dave Airlie <airlied@linux.ie>, Hong Liu <hong.liu@intel.com>
Signed-off-by: Jesse Barnes <jbarnes@virtuousgeek.org>
Signed-off-by: Eric Anholt <eric@anholt.net>
Signed-off-by: Dave Airlie <airlied@redhat.com>
2008-11-07 22:24:08 +00:00
|
|
|
|
2015-08-07 16:40:17 +00:00
|
|
|
DRM_DEBUG_KMS("allocated %dx%d fb: 0x%08llx, bo %p\n",
|
2010-03-30 05:34:14 +00:00
|
|
|
fb->width, fb->height,
|
2013-07-05 21:41:04 +00:00
|
|
|
i915_gem_obj_ggtt_offset(obj), obj);
|
DRM: i915: add mode setting support
This commit adds i915 driver support for the DRM mode setting APIs.
Currently, VGA, LVDS, SDVO DVI & VGA, TV and DVO LVDS outputs are
supported. HDMI, DisplayPort and additional SDVO output support will
follow.
Support for the mode setting code is controlled by the new 'modeset'
module option. A new config option, CONFIG_DRM_I915_KMS controls the
default behavior, and whether a PCI ID list is built into the module for
use by user level module utilities.
Note that if mode setting is enabled, user level drivers that access
display registers directly or that don't use the kernel graphics memory
manager will likely corrupt kernel graphics memory, disrupt output
configuration (possibly leading to hangs and/or blank displays), and
prevent panic/oops messages from appearing. So use caution when
enabling this code; be sure your user level code supports the new
interfaces.
A new SysRq key, 'g', provides emergency support for switching back to
the kernel's framebuffer console; which is useful for testing.
Co-authors: Dave Airlie <airlied@linux.ie>, Hong Liu <hong.liu@intel.com>
Signed-off-by: Jesse Barnes <jbarnes@virtuousgeek.org>
Signed-off-by: Eric Anholt <eric@anholt.net>
Signed-off-by: Dave Airlie <airlied@redhat.com>
2008-11-07 22:24:08 +00:00
|
|
|
|
|
|
|
mutex_unlock(&dev->struct_mutex);
|
2010-02-01 05:38:10 +00:00
|
|
|
vga_switcheroo_client_fb_set(dev->pdev, info);
|
DRM: i915: add mode setting support
This commit adds i915 driver support for the DRM mode setting APIs.
Currently, VGA, LVDS, SDVO DVI & VGA, TV and DVO LVDS outputs are
supported. HDMI, DisplayPort and additional SDVO output support will
follow.
Support for the mode setting code is controlled by the new 'modeset'
module option. A new config option, CONFIG_DRM_I915_KMS controls the
default behavior, and whether a PCI ID list is built into the module for
use by user level module utilities.
Note that if mode setting is enabled, user level drivers that access
display registers directly or that don't use the kernel graphics memory
manager will likely corrupt kernel graphics memory, disrupt output
configuration (possibly leading to hangs and/or blank displays), and
prevent panic/oops messages from appearing. So use caution when
enabling this code; be sure your user level code supports the new
interfaces.
A new SysRq key, 'g', provides emergency support for switching back to
the kernel's framebuffer console; which is useful for testing.
Co-authors: Dave Airlie <airlied@linux.ie>, Hong Liu <hong.liu@intel.com>
Signed-off-by: Jesse Barnes <jbarnes@virtuousgeek.org>
Signed-off-by: Eric Anholt <eric@anholt.net>
Signed-off-by: Dave Airlie <airlied@redhat.com>
2008-11-07 22:24:08 +00:00
|
|
|
return 0;
|
|
|
|
|
2015-07-31 10:51:56 +00:00
|
|
|
out_destroy_fbi:
|
|
|
|
drm_fb_helper_release_fbi(helper);
|
2009-02-11 14:26:36 +00:00
|
|
|
out_unpin:
|
2016-04-28 08:56:35 +00:00
|
|
|
intel_unpin_fb_obj(&ifbdev->fb->base, BIT(DRM_ROTATE_0));
|
2015-12-04 16:05:26 +00:00
|
|
|
out_unlock:
|
DRM: i915: add mode setting support
This commit adds i915 driver support for the DRM mode setting APIs.
Currently, VGA, LVDS, SDVO DVI & VGA, TV and DVO LVDS outputs are
supported. HDMI, DisplayPort and additional SDVO output support will
follow.
Support for the mode setting code is controlled by the new 'modeset'
module option. A new config option, CONFIG_DRM_I915_KMS controls the
default behavior, and whether a PCI ID list is built into the module for
use by user level module utilities.
Note that if mode setting is enabled, user level drivers that access
display registers directly or that don't use the kernel graphics memory
manager will likely corrupt kernel graphics memory, disrupt output
configuration (possibly leading to hangs and/or blank displays), and
prevent panic/oops messages from appearing. So use caution when
enabling this code; be sure your user level code supports the new
interfaces.
A new SysRq key, 'g', provides emergency support for switching back to
the kernel's framebuffer console; which is useful for testing.
Co-authors: Dave Airlie <airlied@linux.ie>, Hong Liu <hong.liu@intel.com>
Signed-off-by: Jesse Barnes <jbarnes@virtuousgeek.org>
Signed-off-by: Eric Anholt <eric@anholt.net>
Signed-off-by: Dave Airlie <airlied@redhat.com>
2008-11-07 22:24:08 +00:00
|
|
|
mutex_unlock(&dev->struct_mutex);
|
|
|
|
return ret;
|
|
|
|
}
|
|
|
|
|
2013-09-24 16:52:56 +00:00
|
|
|
/** Sets the color ramps on behalf of RandR */
|
|
|
|
static void intel_crtc_fb_gamma_set(struct drm_crtc *crtc, u16 red, u16 green,
|
|
|
|
u16 blue, int regno)
|
|
|
|
{
|
|
|
|
struct intel_crtc *intel_crtc = to_intel_crtc(crtc);
|
|
|
|
|
|
|
|
intel_crtc->lut_r[regno] = red >> 8;
|
|
|
|
intel_crtc->lut_g[regno] = green >> 8;
|
|
|
|
intel_crtc->lut_b[regno] = blue >> 8;
|
|
|
|
}
|
|
|
|
|
|
|
|
static void intel_crtc_fb_gamma_get(struct drm_crtc *crtc, u16 *red, u16 *green,
|
|
|
|
u16 *blue, int regno)
|
|
|
|
{
|
|
|
|
struct intel_crtc *intel_crtc = to_intel_crtc(crtc);
|
|
|
|
|
|
|
|
*red = intel_crtc->lut_r[regno] << 8;
|
|
|
|
*green = intel_crtc->lut_g[regno] << 8;
|
|
|
|
*blue = intel_crtc->lut_b[regno] << 8;
|
|
|
|
}
|
|
|
|
|
2014-02-12 20:26:25 +00:00
|
|
|
static struct drm_fb_helper_crtc *
|
|
|
|
intel_fb_helper_crtc(struct drm_fb_helper *fb_helper, struct drm_crtc *crtc)
|
|
|
|
{
|
|
|
|
int i;
|
|
|
|
|
|
|
|
for (i = 0; i < fb_helper->crtc_count; i++)
|
|
|
|
if (fb_helper->crtc_info[i].mode_set.crtc == crtc)
|
|
|
|
return &fb_helper->crtc_info[i];
|
|
|
|
|
|
|
|
return NULL;
|
|
|
|
}
|
|
|
|
|
|
|
|
/*
|
|
|
|
* Try to read the BIOS display configuration and use it for the initial
|
|
|
|
* fb configuration.
|
|
|
|
*
|
|
|
|
* The BIOS or boot loader will generally create an initial display
|
|
|
|
* configuration for us that includes some set of active pipes and displays.
|
|
|
|
* This routine tries to figure out which pipes and connectors are active
|
|
|
|
* and stuffs them into the crtcs and modes array given to us by the
|
|
|
|
* drm_fb_helper code.
|
|
|
|
*
|
|
|
|
* The overall sequence is:
|
|
|
|
* intel_fbdev_init - from driver load
|
|
|
|
* intel_fbdev_init_bios - initialize the intel_fbdev using BIOS data
|
|
|
|
* drm_fb_helper_init - build fb helper structs
|
|
|
|
* drm_fb_helper_single_add_all_connectors - more fb helper structs
|
|
|
|
* intel_fbdev_initial_config - apply the config
|
|
|
|
* drm_fb_helper_initial_config - call ->probe then register_framebuffer()
|
|
|
|
* drm_setup_crtcs - build crtc config for fbdev
|
|
|
|
* intel_fb_initial_config - find active connectors etc
|
|
|
|
* drm_fb_helper_single_fb_probe - set up fbdev
|
|
|
|
* intelfb_create - re-use or alloc fb, build out fbdev structs
|
|
|
|
*
|
|
|
|
* Note that we don't make special consideration whether we could actually
|
|
|
|
* switch to the selected modes without a full modeset. E.g. when the display
|
|
|
|
* is in VGA mode we need to recalculate watermarks and set a new high-res
|
|
|
|
* framebuffer anyway.
|
|
|
|
*/
|
|
|
|
static bool intel_fb_initial_config(struct drm_fb_helper *fb_helper,
|
|
|
|
struct drm_fb_helper_crtc **crtcs,
|
|
|
|
struct drm_display_mode **modes,
|
2014-10-20 06:31:53 +00:00
|
|
|
struct drm_fb_offset *offsets,
|
2014-02-12 20:26:25 +00:00
|
|
|
bool *enabled, int width, int height)
|
|
|
|
{
|
2014-02-12 23:03:40 +00:00
|
|
|
struct drm_device *dev = fb_helper->dev;
|
2016-07-02 14:36:02 +00:00
|
|
|
unsigned long conn_configured, mask;
|
|
|
|
unsigned int count = min(fb_helper->connector_count, BITS_PER_LONG);
|
2014-02-12 20:26:25 +00:00
|
|
|
int i, j;
|
2014-02-12 23:03:40 +00:00
|
|
|
bool *save_enabled;
|
2014-03-04 20:08:41 +00:00
|
|
|
bool fallback = true;
|
2014-03-04 20:08:42 +00:00
|
|
|
int num_connectors_enabled = 0;
|
|
|
|
int num_connectors_detected = 0;
|
2014-10-20 06:31:53 +00:00
|
|
|
int pass = 0;
|
2014-02-12 23:03:40 +00:00
|
|
|
|
2016-07-02 14:36:02 +00:00
|
|
|
save_enabled = kcalloc(count, sizeof(bool), GFP_KERNEL);
|
2014-02-12 23:03:40 +00:00
|
|
|
if (!save_enabled)
|
|
|
|
return false;
|
|
|
|
|
2016-07-02 14:36:02 +00:00
|
|
|
memcpy(save_enabled, enabled, count);
|
|
|
|
mask = BIT(count) - 1;
|
|
|
|
conn_configured = 0;
|
2014-10-20 06:31:53 +00:00
|
|
|
retry:
|
2016-07-02 14:36:02 +00:00
|
|
|
for (i = 0; i < count; i++) {
|
2014-02-12 20:26:25 +00:00
|
|
|
struct drm_fb_helper_connector *fb_conn;
|
|
|
|
struct drm_connector *connector;
|
|
|
|
struct drm_encoder *encoder;
|
|
|
|
struct drm_fb_helper_crtc *new_crtc;
|
2016-03-16 10:57:16 +00:00
|
|
|
struct intel_crtc *intel_crtc;
|
2014-02-12 20:26:25 +00:00
|
|
|
|
|
|
|
fb_conn = fb_helper->connector_info[i];
|
|
|
|
connector = fb_conn->connector;
|
2014-03-04 20:08:42 +00:00
|
|
|
|
2016-07-02 14:36:02 +00:00
|
|
|
if (conn_configured & BIT(i))
|
2014-10-20 06:31:53 +00:00
|
|
|
continue;
|
|
|
|
|
|
|
|
if (pass == 0 && !connector->has_tile)
|
|
|
|
continue;
|
|
|
|
|
2014-03-04 20:08:42 +00:00
|
|
|
if (connector->status == connector_status_connected)
|
|
|
|
num_connectors_detected++;
|
|
|
|
|
2014-02-12 20:26:25 +00:00
|
|
|
if (!enabled[i]) {
|
2014-05-13 12:45:09 +00:00
|
|
|
DRM_DEBUG_KMS("connector %s not enabled, skipping\n",
|
2014-06-03 11:56:17 +00:00
|
|
|
connector->name);
|
2016-07-02 14:36:02 +00:00
|
|
|
conn_configured |= BIT(i);
|
2014-02-12 20:26:25 +00:00
|
|
|
continue;
|
|
|
|
}
|
|
|
|
|
2014-08-18 17:35:29 +00:00
|
|
|
if (connector->force == DRM_FORCE_OFF) {
|
|
|
|
DRM_DEBUG_KMS("connector %s is disabled by user, skipping\n",
|
|
|
|
connector->name);
|
|
|
|
enabled[i] = false;
|
|
|
|
continue;
|
|
|
|
}
|
|
|
|
|
2016-02-17 08:18:39 +00:00
|
|
|
encoder = connector->state->best_encoder;
|
|
|
|
if (!encoder || WARN_ON(!connector->state->crtc)) {
|
2014-08-18 17:35:29 +00:00
|
|
|
if (connector->force > DRM_FORCE_OFF)
|
|
|
|
goto bail;
|
|
|
|
|
2014-05-13 12:45:09 +00:00
|
|
|
DRM_DEBUG_KMS("connector %s has no encoder or crtc, skipping\n",
|
2014-06-03 11:56:17 +00:00
|
|
|
connector->name);
|
2014-02-12 20:26:25 +00:00
|
|
|
enabled[i] = false;
|
2016-07-02 14:36:02 +00:00
|
|
|
conn_configured |= BIT(i);
|
2014-02-12 20:26:25 +00:00
|
|
|
continue;
|
|
|
|
}
|
|
|
|
|
2014-03-04 20:08:42 +00:00
|
|
|
num_connectors_enabled++;
|
|
|
|
|
2016-03-16 10:57:16 +00:00
|
|
|
intel_crtc = to_intel_crtc(connector->state->crtc);
|
|
|
|
for (j = 0; j < 256; j++) {
|
|
|
|
intel_crtc->lut_r[j] = j;
|
|
|
|
intel_crtc->lut_g[j] = j;
|
|
|
|
intel_crtc->lut_b[j] = j;
|
|
|
|
}
|
|
|
|
|
2016-07-02 14:36:02 +00:00
|
|
|
new_crtc = intel_fb_helper_crtc(fb_helper,
|
|
|
|
connector->state->crtc);
|
2014-02-12 20:26:25 +00:00
|
|
|
|
|
|
|
/*
|
|
|
|
* Make sure we're not trying to drive multiple connectors
|
|
|
|
* with a single CRTC, since our cloning support may not
|
|
|
|
* match the BIOS.
|
|
|
|
*/
|
2016-07-02 14:36:02 +00:00
|
|
|
for (j = 0; j < count; j++) {
|
2014-02-12 23:03:40 +00:00
|
|
|
if (crtcs[j] == new_crtc) {
|
2014-03-04 20:08:42 +00:00
|
|
|
DRM_DEBUG_KMS("fallback: cloned configuration\n");
|
2014-08-18 17:35:29 +00:00
|
|
|
goto bail;
|
2014-02-12 23:03:40 +00:00
|
|
|
}
|
2014-02-12 20:26:25 +00:00
|
|
|
}
|
|
|
|
|
2014-05-13 12:45:09 +00:00
|
|
|
DRM_DEBUG_KMS("looking for cmdline mode on connector %s\n",
|
2014-06-03 11:56:17 +00:00
|
|
|
connector->name);
|
2014-02-12 20:26:25 +00:00
|
|
|
|
|
|
|
/* go for command line mode first */
|
|
|
|
modes[i] = drm_pick_cmdline_mode(fb_conn, width, height);
|
|
|
|
|
|
|
|
/* try for preferred next */
|
|
|
|
if (!modes[i]) {
|
2014-10-20 06:31:53 +00:00
|
|
|
DRM_DEBUG_KMS("looking for preferred mode on connector %s %d\n",
|
|
|
|
connector->name, connector->has_tile);
|
2014-02-12 20:26:25 +00:00
|
|
|
modes[i] = drm_has_preferred_mode(fb_conn, width,
|
|
|
|
height);
|
|
|
|
}
|
|
|
|
|
2014-05-13 15:07:37 +00:00
|
|
|
/* No preferred mode marked by the EDID? Are there any modes? */
|
|
|
|
if (!modes[i] && !list_empty(&connector->modes)) {
|
|
|
|
DRM_DEBUG_KMS("using first mode listed on connector %s\n",
|
2014-06-05 10:28:59 +00:00
|
|
|
connector->name);
|
2014-05-13 15:07:37 +00:00
|
|
|
modes[i] = list_first_entry(&connector->modes,
|
|
|
|
struct drm_display_mode,
|
|
|
|
head);
|
|
|
|
}
|
|
|
|
|
2014-02-12 20:26:25 +00:00
|
|
|
/* last resort: use current mode */
|
|
|
|
if (!modes[i]) {
|
|
|
|
/*
|
|
|
|
* IMPORTANT: We want to use the adjusted mode (i.e.
|
|
|
|
* after the panel fitter upscaling) as the initial
|
|
|
|
* config, not the input mode, which is what crtc->mode
|
2015-07-14 13:58:28 +00:00
|
|
|
* usually contains. But since our current
|
2014-02-12 20:26:25 +00:00
|
|
|
* code puts a mode derived from the post-pfit timings
|
2015-07-14 13:58:28 +00:00
|
|
|
* into crtc->mode this works out correctly.
|
2016-02-17 08:18:39 +00:00
|
|
|
*
|
|
|
|
* This is crtc->mode and not crtc->state->mode for the
|
|
|
|
* fastboot check to work correctly. crtc_state->mode has
|
|
|
|
* I915_MODE_FLAG_INHERITED, which we clear to force check
|
|
|
|
* state.
|
2014-02-12 20:26:25 +00:00
|
|
|
*/
|
2014-05-13 12:45:09 +00:00
|
|
|
DRM_DEBUG_KMS("looking for current mode on connector %s\n",
|
2014-06-03 11:56:17 +00:00
|
|
|
connector->name);
|
2016-02-17 08:18:39 +00:00
|
|
|
modes[i] = &connector->state->crtc->mode;
|
2014-02-12 20:26:25 +00:00
|
|
|
}
|
|
|
|
crtcs[i] = new_crtc;
|
|
|
|
|
2016-05-27 17:59:19 +00:00
|
|
|
DRM_DEBUG_KMS("connector %s on [CRTC:%d:%s]: %dx%d%s\n",
|
2014-06-03 11:56:17 +00:00
|
|
|
connector->name,
|
2016-02-17 08:18:39 +00:00
|
|
|
connector->state->crtc->base.id,
|
2016-05-27 17:59:19 +00:00
|
|
|
connector->state->crtc->name,
|
2014-05-13 12:45:09 +00:00
|
|
|
modes[i]->hdisplay, modes[i]->vdisplay,
|
|
|
|
modes[i]->flags & DRM_MODE_FLAG_INTERLACE ? "i" :"");
|
2014-02-12 23:03:40 +00:00
|
|
|
|
2014-03-04 20:08:41 +00:00
|
|
|
fallback = false;
|
2016-07-02 14:36:02 +00:00
|
|
|
conn_configured |= BIT(i);
|
2014-10-20 06:31:53 +00:00
|
|
|
}
|
|
|
|
|
|
|
|
if ((conn_configured & mask) != mask) {
|
|
|
|
pass++;
|
|
|
|
goto retry;
|
2014-02-12 23:03:40 +00:00
|
|
|
}
|
|
|
|
|
2014-03-04 20:08:42 +00:00
|
|
|
/*
|
|
|
|
* If the BIOS didn't enable everything it could, fall back to have the
|
|
|
|
* same user experiencing of lighting up as much as possible like the
|
|
|
|
* fbdev helper library.
|
|
|
|
*/
|
|
|
|
if (num_connectors_enabled != num_connectors_detected &&
|
|
|
|
num_connectors_enabled < INTEL_INFO(dev)->num_pipes) {
|
|
|
|
DRM_DEBUG_KMS("fallback: Not all outputs enabled\n");
|
|
|
|
DRM_DEBUG_KMS("Enabled: %i, detected: %i\n", num_connectors_enabled,
|
|
|
|
num_connectors_detected);
|
|
|
|
fallback = true;
|
|
|
|
}
|
|
|
|
|
2014-03-04 20:08:41 +00:00
|
|
|
if (fallback) {
|
2014-08-18 17:35:29 +00:00
|
|
|
bail:
|
2014-03-04 20:08:42 +00:00
|
|
|
DRM_DEBUG_KMS("Not using firmware configuration\n");
|
2016-07-02 14:36:02 +00:00
|
|
|
memcpy(enabled, save_enabled, count);
|
2014-02-12 23:03:40 +00:00
|
|
|
kfree(save_enabled);
|
|
|
|
return false;
|
2014-02-12 20:26:25 +00:00
|
|
|
}
|
|
|
|
|
2014-02-12 23:03:40 +00:00
|
|
|
kfree(save_enabled);
|
2014-02-12 20:26:25 +00:00
|
|
|
return true;
|
|
|
|
}
|
|
|
|
|
2014-06-27 15:19:23 +00:00
|
|
|
static const struct drm_fb_helper_funcs intel_fb_helper_funcs = {
|
2014-02-12 20:26:25 +00:00
|
|
|
.initial_config = intel_fb_initial_config,
|
2010-03-30 05:34:18 +00:00
|
|
|
.gamma_set = intel_crtc_fb_gamma_set,
|
|
|
|
.gamma_get = intel_crtc_fb_gamma_get,
|
2013-01-21 22:42:49 +00:00
|
|
|
.fb_probe = intelfb_create,
|
2010-03-30 05:34:18 +00:00
|
|
|
};
|
DRM: i915: add mode setting support
This commit adds i915 driver support for the DRM mode setting APIs.
Currently, VGA, LVDS, SDVO DVI & VGA, TV and DVO LVDS outputs are
supported. HDMI, DisplayPort and additional SDVO output support will
follow.
Support for the mode setting code is controlled by the new 'modeset'
module option. A new config option, CONFIG_DRM_I915_KMS controls the
default behavior, and whether a PCI ID list is built into the module for
use by user level module utilities.
Note that if mode setting is enabled, user level drivers that access
display registers directly or that don't use the kernel graphics memory
manager will likely corrupt kernel graphics memory, disrupt output
configuration (possibly leading to hangs and/or blank displays), and
prevent panic/oops messages from appearing. So use caution when
enabling this code; be sure your user level code supports the new
interfaces.
A new SysRq key, 'g', provides emergency support for switching back to
the kernel's framebuffer console; which is useful for testing.
Co-authors: Dave Airlie <airlied@linux.ie>, Hong Liu <hong.liu@intel.com>
Signed-off-by: Jesse Barnes <jbarnes@virtuousgeek.org>
Signed-off-by: Eric Anholt <eric@anholt.net>
Signed-off-by: Dave Airlie <airlied@redhat.com>
2008-11-07 22:24:08 +00:00
|
|
|
|
2016-06-21 08:16:54 +00:00
|
|
|
static void intel_fbdev_destroy(struct intel_fbdev *ifbdev)
|
DRM: i915: add mode setting support
This commit adds i915 driver support for the DRM mode setting APIs.
Currently, VGA, LVDS, SDVO DVI & VGA, TV and DVO LVDS outputs are
supported. HDMI, DisplayPort and additional SDVO output support will
follow.
Support for the mode setting code is controlled by the new 'modeset'
module option. A new config option, CONFIG_DRM_I915_KMS controls the
default behavior, and whether a PCI ID list is built into the module for
use by user level module utilities.
Note that if mode setting is enabled, user level drivers that access
display registers directly or that don't use the kernel graphics memory
manager will likely corrupt kernel graphics memory, disrupt output
configuration (possibly leading to hangs and/or blank displays), and
prevent panic/oops messages from appearing. So use caution when
enabling this code; be sure your user level code supports the new
interfaces.
A new SysRq key, 'g', provides emergency support for switching back to
the kernel's framebuffer console; which is useful for testing.
Co-authors: Dave Airlie <airlied@linux.ie>, Hong Liu <hong.liu@intel.com>
Signed-off-by: Jesse Barnes <jbarnes@virtuousgeek.org>
Signed-off-by: Eric Anholt <eric@anholt.net>
Signed-off-by: Dave Airlie <airlied@redhat.com>
2008-11-07 22:24:08 +00:00
|
|
|
{
|
2015-12-04 16:05:26 +00:00
|
|
|
/* We rely on the object-free to release the VMA pinning for
|
|
|
|
* the info->screen_base mmaping. Leaking the VMA is simpler than
|
|
|
|
* trying to rectify all the possible error paths leading here.
|
|
|
|
*/
|
2013-08-06 16:43:07 +00:00
|
|
|
|
2015-07-31 10:51:56 +00:00
|
|
|
drm_fb_helper_unregister_fbi(&ifbdev->helper);
|
|
|
|
drm_fb_helper_release_fbi(&ifbdev->helper);
|
DRM: i915: add mode setting support
This commit adds i915 driver support for the DRM mode setting APIs.
Currently, VGA, LVDS, SDVO DVI & VGA, TV and DVO LVDS outputs are
supported. HDMI, DisplayPort and additional SDVO output support will
follow.
Support for the mode setting code is controlled by the new 'modeset'
module option. A new config option, CONFIG_DRM_I915_KMS controls the
default behavior, and whether a PCI ID list is built into the module for
use by user level module utilities.
Note that if mode setting is enabled, user level drivers that access
display registers directly or that don't use the kernel graphics memory
manager will likely corrupt kernel graphics memory, disrupt output
configuration (possibly leading to hangs and/or blank displays), and
prevent panic/oops messages from appearing. So use caution when
enabling this code; be sure your user level code supports the new
interfaces.
A new SysRq key, 'g', provides emergency support for switching back to
the kernel's framebuffer console; which is useful for testing.
Co-authors: Dave Airlie <airlied@linux.ie>, Hong Liu <hong.liu@intel.com>
Signed-off-by: Jesse Barnes <jbarnes@virtuousgeek.org>
Signed-off-by: Eric Anholt <eric@anholt.net>
Signed-off-by: Dave Airlie <airlied@redhat.com>
2008-11-07 22:24:08 +00:00
|
|
|
|
2010-03-30 05:34:18 +00:00
|
|
|
drm_fb_helper_fini(&ifbdev->helper);
|
DRM: i915: add mode setting support
This commit adds i915 driver support for the DRM mode setting APIs.
Currently, VGA, LVDS, SDVO DVI & VGA, TV and DVO LVDS outputs are
supported. HDMI, DisplayPort and additional SDVO output support will
follow.
Support for the mode setting code is controlled by the new 'modeset'
module option. A new config option, CONFIG_DRM_I915_KMS controls the
default behavior, and whether a PCI ID list is built into the module for
use by user level module utilities.
Note that if mode setting is enabled, user level drivers that access
display registers directly or that don't use the kernel graphics memory
manager will likely corrupt kernel graphics memory, disrupt output
configuration (possibly leading to hangs and/or blank displays), and
prevent panic/oops messages from appearing. So use caution when
enabling this code; be sure your user level code supports the new
interfaces.
A new SysRq key, 'g', provides emergency support for switching back to
the kernel's framebuffer console; which is useful for testing.
Co-authors: Dave Airlie <airlied@linux.ie>, Hong Liu <hong.liu@intel.com>
Signed-off-by: Jesse Barnes <jbarnes@virtuousgeek.org>
Signed-off-by: Eric Anholt <eric@anholt.net>
Signed-off-by: Dave Airlie <airlied@redhat.com>
2008-11-07 22:24:08 +00:00
|
|
|
|
2015-11-18 12:43:20 +00:00
|
|
|
if (ifbdev->fb) {
|
2016-06-21 08:16:54 +00:00
|
|
|
mutex_lock(&ifbdev->helper.dev->struct_mutex);
|
2016-04-28 08:56:35 +00:00
|
|
|
intel_unpin_fb_obj(&ifbdev->fb->base, BIT(DRM_ROTATE_0));
|
2016-06-21 08:16:54 +00:00
|
|
|
mutex_unlock(&ifbdev->helper.dev->struct_mutex);
|
2016-04-28 08:56:35 +00:00
|
|
|
|
2015-11-18 12:43:20 +00:00
|
|
|
drm_framebuffer_remove(&ifbdev->fb->base);
|
|
|
|
}
|
2016-06-21 08:16:54 +00:00
|
|
|
|
|
|
|
kfree(ifbdev);
|
DRM: i915: add mode setting support
This commit adds i915 driver support for the DRM mode setting APIs.
Currently, VGA, LVDS, SDVO DVI & VGA, TV and DVO LVDS outputs are
supported. HDMI, DisplayPort and additional SDVO output support will
follow.
Support for the mode setting code is controlled by the new 'modeset'
module option. A new config option, CONFIG_DRM_I915_KMS controls the
default behavior, and whether a PCI ID list is built into the module for
use by user level module utilities.
Note that if mode setting is enabled, user level drivers that access
display registers directly or that don't use the kernel graphics memory
manager will likely corrupt kernel graphics memory, disrupt output
configuration (possibly leading to hangs and/or blank displays), and
prevent panic/oops messages from appearing. So use caution when
enabling this code; be sure your user level code supports the new
interfaces.
A new SysRq key, 'g', provides emergency support for switching back to
the kernel's framebuffer console; which is useful for testing.
Co-authors: Dave Airlie <airlied@linux.ie>, Hong Liu <hong.liu@intel.com>
Signed-off-by: Jesse Barnes <jbarnes@virtuousgeek.org>
Signed-off-by: Eric Anholt <eric@anholt.net>
Signed-off-by: Dave Airlie <airlied@redhat.com>
2008-11-07 22:24:08 +00:00
|
|
|
}
|
2010-03-30 05:34:13 +00:00
|
|
|
|
2014-03-07 16:57:51 +00:00
|
|
|
/*
|
|
|
|
* Build an intel_fbdev struct using a BIOS allocated framebuffer, if possible.
|
|
|
|
* The core display code will have read out the current plane configuration,
|
|
|
|
* so we use that to figure out if there's an object for us to use as the
|
|
|
|
* fb, and if so, we re-use it for the fbdev configuration.
|
|
|
|
*
|
|
|
|
* Note we only support a single fb shared across pipes for boot (mostly for
|
|
|
|
* fbcon), so we just find the biggest and use that.
|
|
|
|
*/
|
|
|
|
static bool intel_fbdev_init_bios(struct drm_device *dev,
|
|
|
|
struct intel_fbdev *ifbdev)
|
|
|
|
{
|
|
|
|
struct intel_framebuffer *fb = NULL;
|
|
|
|
struct drm_crtc *crtc;
|
|
|
|
struct intel_crtc *intel_crtc;
|
|
|
|
unsigned int max_size = 0;
|
|
|
|
|
|
|
|
/* Find the largest fb */
|
2014-05-13 22:32:24 +00:00
|
|
|
for_each_crtc(dev, crtc) {
|
2015-07-13 14:30:16 +00:00
|
|
|
struct drm_i915_gem_object *obj =
|
|
|
|
intel_fb_obj(crtc->primary->state->fb);
|
2014-03-07 16:57:51 +00:00
|
|
|
intel_crtc = to_intel_crtc(crtc);
|
|
|
|
|
2015-08-27 13:44:03 +00:00
|
|
|
if (!crtc->state->active || !obj) {
|
2014-03-07 16:57:51 +00:00
|
|
|
DRM_DEBUG_KMS("pipe %c not active or no fb, skipping\n",
|
|
|
|
pipe_name(intel_crtc->pipe));
|
|
|
|
continue;
|
|
|
|
}
|
|
|
|
|
2015-07-13 14:30:16 +00:00
|
|
|
if (obj->base.size > max_size) {
|
2014-03-07 16:57:51 +00:00
|
|
|
DRM_DEBUG_KMS("found possible fb from plane %c\n",
|
|
|
|
pipe_name(intel_crtc->pipe));
|
2015-07-13 14:30:16 +00:00
|
|
|
fb = to_intel_framebuffer(crtc->primary->state->fb);
|
|
|
|
max_size = obj->base.size;
|
2014-03-07 16:57:51 +00:00
|
|
|
}
|
|
|
|
}
|
|
|
|
|
|
|
|
if (!fb) {
|
|
|
|
DRM_DEBUG_KMS("no active fbs found, not using BIOS config\n");
|
|
|
|
goto out;
|
|
|
|
}
|
|
|
|
|
|
|
|
/* Now make sure all the pipes will fit into it */
|
2014-05-13 22:32:24 +00:00
|
|
|
for_each_crtc(dev, crtc) {
|
2014-03-07 16:57:51 +00:00
|
|
|
unsigned int cur_size;
|
|
|
|
|
|
|
|
intel_crtc = to_intel_crtc(crtc);
|
|
|
|
|
2015-08-27 13:44:03 +00:00
|
|
|
if (!crtc->state->active) {
|
2014-03-07 16:57:51 +00:00
|
|
|
DRM_DEBUG_KMS("pipe %c not active, skipping\n",
|
|
|
|
pipe_name(intel_crtc->pipe));
|
|
|
|
continue;
|
|
|
|
}
|
|
|
|
|
|
|
|
DRM_DEBUG_KMS("checking plane %c for BIOS fb\n",
|
|
|
|
pipe_name(intel_crtc->pipe));
|
|
|
|
|
|
|
|
/*
|
|
|
|
* See if the plane fb we found above will fit on this
|
2014-03-20 15:11:21 +00:00
|
|
|
* pipe. Note we need to use the selected fb's pitch and bpp
|
|
|
|
* rather than the current pipe's, since they differ.
|
2014-03-07 16:57:51 +00:00
|
|
|
*/
|
2015-01-15 12:55:25 +00:00
|
|
|
cur_size = intel_crtc->config->base.adjusted_mode.crtc_hdisplay;
|
2014-03-20 15:11:21 +00:00
|
|
|
cur_size = cur_size * fb->base.bits_per_pixel / 8;
|
|
|
|
if (fb->base.pitches[0] < cur_size) {
|
|
|
|
DRM_DEBUG_KMS("fb not wide enough for plane %c (%d vs %d)\n",
|
|
|
|
pipe_name(intel_crtc->pipe),
|
|
|
|
cur_size, fb->base.pitches[0]);
|
|
|
|
fb = NULL;
|
|
|
|
break;
|
|
|
|
}
|
|
|
|
|
2015-01-15 12:55:25 +00:00
|
|
|
cur_size = intel_crtc->config->base.adjusted_mode.crtc_vdisplay;
|
2015-01-20 12:51:45 +00:00
|
|
|
cur_size = intel_fb_align_height(dev, cur_size,
|
2015-02-10 17:16:10 +00:00
|
|
|
fb->base.pixel_format,
|
|
|
|
fb->base.modifier[0]);
|
2014-03-20 15:11:21 +00:00
|
|
|
cur_size *= fb->base.pitches[0];
|
|
|
|
DRM_DEBUG_KMS("pipe %c area: %dx%d, bpp: %d, size: %d\n",
|
|
|
|
pipe_name(intel_crtc->pipe),
|
2015-01-15 12:55:25 +00:00
|
|
|
intel_crtc->config->base.adjusted_mode.crtc_hdisplay,
|
|
|
|
intel_crtc->config->base.adjusted_mode.crtc_vdisplay,
|
2014-03-20 15:11:21 +00:00
|
|
|
fb->base.bits_per_pixel,
|
2014-03-07 16:57:51 +00:00
|
|
|
cur_size);
|
|
|
|
|
|
|
|
if (cur_size > max_size) {
|
|
|
|
DRM_DEBUG_KMS("fb not big enough for plane %c (%d vs %d)\n",
|
|
|
|
pipe_name(intel_crtc->pipe),
|
|
|
|
cur_size, max_size);
|
|
|
|
fb = NULL;
|
|
|
|
break;
|
|
|
|
}
|
|
|
|
|
|
|
|
DRM_DEBUG_KMS("fb big enough for plane %c (%d >= %d)\n",
|
|
|
|
pipe_name(intel_crtc->pipe),
|
|
|
|
max_size, cur_size);
|
|
|
|
}
|
|
|
|
|
|
|
|
if (!fb) {
|
|
|
|
DRM_DEBUG_KMS("BIOS fb not suitable for all pipes, not using\n");
|
|
|
|
goto out;
|
|
|
|
}
|
|
|
|
|
2014-03-07 16:57:55 +00:00
|
|
|
ifbdev->preferred_bpp = fb->base.bits_per_pixel;
|
2014-03-07 16:57:51 +00:00
|
|
|
ifbdev->fb = fb;
|
|
|
|
|
2014-03-07 16:57:55 +00:00
|
|
|
drm_framebuffer_reference(&ifbdev->fb->base);
|
2014-03-07 16:57:51 +00:00
|
|
|
|
|
|
|
/* Final pass to check if any active pipes don't have fbs */
|
2014-05-13 22:32:24 +00:00
|
|
|
for_each_crtc(dev, crtc) {
|
2014-03-07 16:57:51 +00:00
|
|
|
intel_crtc = to_intel_crtc(crtc);
|
|
|
|
|
2015-08-27 13:44:03 +00:00
|
|
|
if (!crtc->state->active)
|
2014-03-07 16:57:51 +00:00
|
|
|
continue;
|
|
|
|
|
2014-04-02 21:51:54 +00:00
|
|
|
WARN(!crtc->primary->fb,
|
2014-03-07 16:57:51 +00:00
|
|
|
"re-used BIOS config but lost an fb on crtc %d\n",
|
|
|
|
crtc->base.id);
|
|
|
|
}
|
|
|
|
|
|
|
|
|
|
|
|
DRM_DEBUG_KMS("using BIOS fb for initial console\n");
|
|
|
|
return true;
|
|
|
|
|
|
|
|
out:
|
|
|
|
|
|
|
|
return false;
|
|
|
|
}
|
|
|
|
|
2014-08-13 12:09:46 +00:00
|
|
|
static void intel_fbdev_suspend_worker(struct work_struct *work)
|
|
|
|
{
|
2016-07-05 09:40:23 +00:00
|
|
|
intel_fbdev_set_suspend(&container_of(work,
|
|
|
|
struct drm_i915_private,
|
|
|
|
fbdev_suspend_work)->drm,
|
2014-08-13 12:09:46 +00:00
|
|
|
FBINFO_STATE_RUNNING,
|
|
|
|
true);
|
|
|
|
}
|
|
|
|
|
2010-03-30 05:34:13 +00:00
|
|
|
int intel_fbdev_init(struct drm_device *dev)
|
|
|
|
{
|
2010-03-30 05:34:14 +00:00
|
|
|
struct intel_fbdev *ifbdev;
|
2016-07-04 10:34:36 +00:00
|
|
|
struct drm_i915_private *dev_priv = to_i915(dev);
|
2010-06-06 09:50:03 +00:00
|
|
|
int ret;
|
2010-03-30 05:34:14 +00:00
|
|
|
|
2014-03-07 16:57:51 +00:00
|
|
|
if (WARN_ON(INTEL_INFO(dev)->num_pipes == 0))
|
|
|
|
return -ENODEV;
|
|
|
|
|
|
|
|
ifbdev = kzalloc(sizeof(struct intel_fbdev), GFP_KERNEL);
|
|
|
|
if (ifbdev == NULL)
|
2010-03-30 05:34:14 +00:00
|
|
|
return -ENOMEM;
|
|
|
|
|
2014-06-27 15:19:24 +00:00
|
|
|
drm_fb_helper_prepare(dev, &ifbdev->helper, &intel_fb_helper_funcs);
|
|
|
|
|
2014-03-07 16:57:51 +00:00
|
|
|
if (!intel_fbdev_init_bios(dev, ifbdev))
|
|
|
|
ifbdev->preferred_bpp = 32;
|
2010-03-30 05:34:18 +00:00
|
|
|
|
2010-06-06 09:50:03 +00:00
|
|
|
ret = drm_fb_helper_init(dev, &ifbdev->helper,
|
2014-03-07 16:57:51 +00:00
|
|
|
INTEL_INFO(dev)->num_pipes, 4);
|
2010-06-06 09:50:03 +00:00
|
|
|
if (ret) {
|
|
|
|
kfree(ifbdev);
|
|
|
|
return ret;
|
|
|
|
}
|
2010-03-30 05:34:14 +00:00
|
|
|
|
2014-03-07 16:57:51 +00:00
|
|
|
dev_priv->fbdev = ifbdev;
|
2014-08-13 12:09:46 +00:00
|
|
|
INIT_WORK(&dev_priv->fbdev_suspend_work, intel_fbdev_suspend_worker);
|
|
|
|
|
2010-03-30 05:34:15 +00:00
|
|
|
drm_fb_helper_single_add_all_connectors(&ifbdev->helper);
|
2012-12-11 13:05:07 +00:00
|
|
|
|
DRM: i915: add mode setting support
This commit adds i915 driver support for the DRM mode setting APIs.
Currently, VGA, LVDS, SDVO DVI & VGA, TV and DVO LVDS outputs are
supported. HDMI, DisplayPort and additional SDVO output support will
follow.
Support for the mode setting code is controlled by the new 'modeset'
module option. A new config option, CONFIG_DRM_I915_KMS controls the
default behavior, and whether a PCI ID list is built into the module for
use by user level module utilities.
Note that if mode setting is enabled, user level drivers that access
display registers directly or that don't use the kernel graphics memory
manager will likely corrupt kernel graphics memory, disrupt output
configuration (possibly leading to hangs and/or blank displays), and
prevent panic/oops messages from appearing. So use caution when
enabling this code; be sure your user level code supports the new
interfaces.
A new SysRq key, 'g', provides emergency support for switching back to
the kernel's framebuffer console; which is useful for testing.
Co-authors: Dave Airlie <airlied@linux.ie>, Hong Liu <hong.liu@intel.com>
Signed-off-by: Jesse Barnes <jbarnes@virtuousgeek.org>
Signed-off-by: Eric Anholt <eric@anholt.net>
Signed-off-by: Dave Airlie <airlied@redhat.com>
2008-11-07 22:24:08 +00:00
|
|
|
return 0;
|
|
|
|
}
|
2010-03-30 05:34:13 +00:00
|
|
|
|
2015-11-06 13:08:33 +00:00
|
|
|
static void intel_fbdev_initial_config(void *data, async_cookie_t cookie)
|
2012-12-11 13:05:07 +00:00
|
|
|
{
|
2016-06-21 08:16:54 +00:00
|
|
|
struct intel_fbdev *ifbdev = data;
|
2012-12-11 13:05:07 +00:00
|
|
|
|
|
|
|
/* Due to peculiar init order wrt to hpd handling this is separate. */
|
2015-11-18 15:29:51 +00:00
|
|
|
if (drm_fb_helper_initial_config(&ifbdev->helper,
|
|
|
|
ifbdev->preferred_bpp))
|
2016-06-21 08:16:54 +00:00
|
|
|
intel_fbdev_fini(ifbdev->helper.dev);
|
2012-12-11 13:05:07 +00:00
|
|
|
}
|
|
|
|
|
2015-11-06 13:08:33 +00:00
|
|
|
void intel_fbdev_initial_config_async(struct drm_device *dev)
|
|
|
|
{
|
2016-06-21 08:16:54 +00:00
|
|
|
struct intel_fbdev *ifbdev = to_i915(dev)->fbdev;
|
|
|
|
|
|
|
|
ifbdev->cookie = async_schedule(intel_fbdev_initial_config, ifbdev);
|
|
|
|
}
|
|
|
|
|
|
|
|
static void intel_fbdev_sync(struct intel_fbdev *ifbdev)
|
|
|
|
{
|
|
|
|
if (!ifbdev->cookie)
|
|
|
|
return;
|
|
|
|
|
|
|
|
/* Only serialises with all preceding async calls, hence +1 */
|
|
|
|
async_synchronize_cookie(ifbdev->cookie + 1);
|
|
|
|
ifbdev->cookie = 0;
|
2015-11-06 13:08:33 +00:00
|
|
|
}
|
|
|
|
|
2010-03-30 05:34:13 +00:00
|
|
|
void intel_fbdev_fini(struct drm_device *dev)
|
|
|
|
{
|
2016-07-04 10:34:36 +00:00
|
|
|
struct drm_i915_private *dev_priv = to_i915(dev);
|
2016-06-21 08:16:54 +00:00
|
|
|
struct intel_fbdev *ifbdev = dev_priv->fbdev;
|
|
|
|
|
|
|
|
if (!ifbdev)
|
2010-03-30 05:34:14 +00:00
|
|
|
return;
|
|
|
|
|
2016-07-13 17:34:44 +00:00
|
|
|
cancel_work_sync(&dev_priv->fbdev_suspend_work);
|
2015-11-18 15:29:51 +00:00
|
|
|
if (!current_is_async())
|
2016-06-21 08:16:54 +00:00
|
|
|
intel_fbdev_sync(ifbdev);
|
|
|
|
|
|
|
|
intel_fbdev_destroy(ifbdev);
|
2010-03-30 05:34:13 +00:00
|
|
|
dev_priv->fbdev = NULL;
|
|
|
|
}
|
2012-03-28 09:48:49 +00:00
|
|
|
|
2014-08-13 12:09:46 +00:00
|
|
|
void intel_fbdev_set_suspend(struct drm_device *dev, int state, bool synchronous)
|
2012-03-28 09:48:49 +00:00
|
|
|
{
|
2016-07-04 10:34:36 +00:00
|
|
|
struct drm_i915_private *dev_priv = to_i915(dev);
|
2013-05-07 15:54:05 +00:00
|
|
|
struct intel_fbdev *ifbdev = dev_priv->fbdev;
|
|
|
|
struct fb_info *info;
|
|
|
|
|
|
|
|
if (!ifbdev)
|
2012-03-28 09:48:49 +00:00
|
|
|
return;
|
|
|
|
|
2013-05-07 15:54:05 +00:00
|
|
|
info = ifbdev->helper.fbdev;
|
|
|
|
|
2014-08-13 12:09:46 +00:00
|
|
|
if (synchronous) {
|
|
|
|
/* Flush any pending work to turn the console on, and then
|
|
|
|
* wait to turn it off. It must be synchronous as we are
|
|
|
|
* about to suspend or unload the driver.
|
|
|
|
*
|
|
|
|
* Note that from within the work-handler, we cannot flush
|
|
|
|
* ourselves, so only flush outstanding work upon suspend!
|
|
|
|
*/
|
|
|
|
if (state != FBINFO_STATE_RUNNING)
|
|
|
|
flush_work(&dev_priv->fbdev_suspend_work);
|
|
|
|
console_lock();
|
|
|
|
} else {
|
|
|
|
/*
|
|
|
|
* The console lock can be pretty contented on resume due
|
|
|
|
* to all the printk activity. Try to keep it out of the hot
|
|
|
|
* path of resume if possible.
|
|
|
|
*/
|
|
|
|
WARN_ON(state != FBINFO_STATE_RUNNING);
|
|
|
|
if (!console_trylock()) {
|
|
|
|
/* Don't block our own workqueue as this can
|
|
|
|
* be run in parallel with other i915.ko tasks.
|
|
|
|
*/
|
|
|
|
schedule_work(&dev_priv->fbdev_suspend_work);
|
|
|
|
return;
|
|
|
|
}
|
|
|
|
}
|
|
|
|
|
2013-05-07 15:54:05 +00:00
|
|
|
/* On resume from hibernation: If the object is shmemfs backed, it has
|
|
|
|
* been restored from swap. If the object is stolen however, it will be
|
|
|
|
* full of whatever garbage was left in there.
|
|
|
|
*/
|
2014-02-07 20:10:38 +00:00
|
|
|
if (state == FBINFO_STATE_RUNNING && ifbdev->fb->obj->stolen)
|
2013-05-07 15:54:05 +00:00
|
|
|
memset_io(info->screen_base, 0, info->screen_size);
|
|
|
|
|
2015-07-31 10:51:56 +00:00
|
|
|
drm_fb_helper_set_suspend(&ifbdev->helper, state);
|
2014-08-13 12:09:46 +00:00
|
|
|
console_unlock();
|
2012-03-28 09:48:49 +00:00
|
|
|
}
|
|
|
|
|
2013-10-08 15:44:49 +00:00
|
|
|
void intel_fbdev_output_poll_changed(struct drm_device *dev)
|
2010-05-07 06:42:51 +00:00
|
|
|
{
|
2016-07-04 10:34:36 +00:00
|
|
|
struct drm_i915_private *dev_priv = to_i915(dev);
|
2014-03-07 16:57:51 +00:00
|
|
|
if (dev_priv->fbdev)
|
|
|
|
drm_fb_helper_hotplug_event(&dev_priv->fbdev->helper);
|
2010-05-07 06:42:51 +00:00
|
|
|
}
|
2011-04-21 21:18:32 +00:00
|
|
|
|
2013-10-08 15:44:49 +00:00
|
|
|
void intel_fbdev_restore_mode(struct drm_device *dev)
|
2011-04-21 21:18:32 +00:00
|
|
|
{
|
|
|
|
int ret;
|
2016-07-04 10:34:36 +00:00
|
|
|
struct drm_i915_private *dev_priv = to_i915(dev);
|
2015-07-08 23:25:21 +00:00
|
|
|
struct intel_fbdev *ifbdev = dev_priv->fbdev;
|
|
|
|
struct drm_fb_helper *fb_helper;
|
2011-04-21 21:18:32 +00:00
|
|
|
|
2015-07-08 23:25:21 +00:00
|
|
|
if (!ifbdev)
|
2013-04-05 20:12:39 +00:00
|
|
|
return;
|
|
|
|
|
2016-06-21 08:16:55 +00:00
|
|
|
intel_fbdev_sync(ifbdev);
|
|
|
|
|
2015-07-08 23:25:21 +00:00
|
|
|
fb_helper = &ifbdev->helper;
|
|
|
|
|
|
|
|
ret = drm_fb_helper_restore_fbdev_mode_unlocked(fb_helper);
|
|
|
|
if (ret) {
|
2011-04-21 21:18:32 +00:00
|
|
|
DRM_DEBUG("failed to restore crtc mode\n");
|
2015-07-08 23:25:21 +00:00
|
|
|
} else {
|
|
|
|
mutex_lock(&fb_helper->dev->struct_mutex);
|
|
|
|
intel_fb_obj_invalidate(ifbdev->fb->obj, ORIGIN_GTT);
|
|
|
|
mutex_unlock(&fb_helper->dev->struct_mutex);
|
|
|
|
}
|
2011-04-21 21:18:32 +00:00
|
|
|
}
|