1450N/A * Copyright (c) 2012, 2013, Oracle and/or its affiliates. All rights reserved. 1450N/A * Copyright (c) 2006-2009 Red Hat Inc. 1450N/A * Copyright (c) 2006-2008, 2013, Intel Corporation 1450N/A * Copyright (c) 2007 Dave Airlie <airlied@linux.ie> 1450N/A * DRM framebuffer helper functions 1450N/A * Permission to use, copy, modify, distribute, and sell this software and its 1450N/A * documentation for any purpose is hereby granted without fee, provided that 1450N/A * the above copyright notice appear in all copies and that both that copyright 1450N/A * notice and this permission notice appear in supporting documentation, and 1450N/A * that the name of the copyright holders not be used in advertising or 1450N/A * publicity pertaining to distribution of the software without specific, 1450N/A * written prior permission. The copyright holders make no representations 1450N/A * about the suitability of this software for any purpose. It is provided "as 1450N/A * is" without express or implied warranty. 1450N/A * THE COPYRIGHT HOLDERS DISCLAIM ALL WARRANTIES WITH REGARD TO THIS SOFTWARE, 1450N/A * INCLUDING ALL IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS, IN NO 1450N/A * EVENT SHALL THE COPYRIGHT HOLDERS BE LIABLE FOR ANY SPECIAL, INDIRECT OR 1450N/A * CONSEQUENTIAL DAMAGES OR ANY DAMAGES WHATSOEVER RESULTING FROM LOSS OF USE, 1450N/A * DATA OR PROFITS, WHETHER IN AN ACTION OF CONTRACT, NEGLIGENCE OR OTHER 1450N/A * TORTIOUS ACTION, ARISING OUT OF OR IN CONNECTION WITH THE USE OR PERFORMANCE 1450N/A * Dave Airlie <airlied@linux.ie> 1450N/A * Jesse Barnes <jesse.barnes@intel.com> 1450N/A * The fb helper functions are useful to provide an fbdev on top of a drm kernel 1450N/A * mode setting driver. They can be used mostly independantely from the crtc 1450N/A * helper functions used by many drivers to implement the kernel mode setting 1450N/A * Initialization is done as a three-step process with drm_fb_helper_init(), 1450N/A * drm_fb_helper_single_add_all_connectors() and drm_fb_helper_initial_config(). 1450N/A * Drivers with fancier requirements than the default beheviour can override the 1450N/A * second step with their own code. Teardown is done with drm_fb_helper_fini(). 1450N/A * At runtime drivers should restore the fbdev console by calling 1450N/A * drm_fb_helper_restore_fbdev_mode() from their ->lastclose callback. They 1450N/A * should also notify the fb helper code from updates to the output 1450N/A * configuration by calling drm_fb_helper_hotplug_event(). For easier 1450N/A * code proves a ->output_poll_changed callback. 1450N/A * All other functions exported by the fb helper library can be used to 1450N/A * implement the fbdev driver interface by the driver. 1450N/A/* simple single crtc case helper function 1450N/A * drm_fb_helper_single_add_all_connectors() - add all connectors to fbdev 1450N/A * @fb_helper: fbdev initialized with drm_fb_helper_init 1450N/A * This functions adds all the available connectors for use with the given 1450N/A * fb_helper. This is a separate step to allow drivers to freely assign 1450N/A * connectors to the fbdev, e.g. if some are reserved for special purposes or 1450N/A * not adequate to be used for the fbcon. 1450N/A * Since this is part of the initial setup before the fbdev is published, no 1450N/A/* Find the real fb for a given fb helper CRTC */ 1450N/A/* maximum connectors per crtcs in the mode set */ 1450N/A /* if driver picks 8 or 16 by default use that 1450N/A /* hmm everyone went away - assume VGA cable just fell out 1450N/A and will come back later. */ 1450N/A /* push down into drivers */ 1450N/A * Set the fb pointer - usually drm_setup_crtcs does this for hotplug 1450N/A * events, but at init time drm_setup_crtcs needs to be called before 1450N/A * the fb is allocated (since we need to figure out the desired size of 1450N/A * the fb before we can allocate it ...). Hence we need to fix things up 1450N/A /* Switch back to kernel console on panic */ 1450N/A /* multi card linked list maybe */ 1450N/A /* LINTED E_FUNC_ARG_UNUSED */ 1450N/A /* attempt to find a matching mode in the list of modes 1450N/A * we have gotten so far, if not add a CVT mode that conforms 1450N/A /* only contemplate cloning in the single crtc case */ 1450N/A /* only contemplate cloning if more than one connector is enabled */ 1450N/A /* check the command line or if nothing common pick 1024x768 */ 1450N/A /* try and find a 1024x768 mode on each connector */ 1450N/A DRM_INFO(
"kms: can't enable cloning when we probably wanted to.\n");
1450N/A /* got for command line mode first */ 1450N/A /* No preferred modes, pick one off the list */ 1450N/A /* select a crtc for this connector and then attempt to configure 1450N/A /* ignore cloning unless only a single crtc */ 1450N/A /* need to set the modesets up here for use later */ 1450N/A /* fill out the connector<->crtc mappings into the modesets */ 1450N/A /* Clear out any old modes if there are no more connected outputs. */ 1450N/A * drm_helper_initial_config - setup a sane initial connector configuration 1450N/A * Scan the CRTCs and connectors and try to put together an initial setup. 1450N/A * At the moment, this is a cloned configuration across all heads with 1450N/A * a new framebuffer object as the backing store. 1450N/A * Note that this also registers the fbdev and so allows userspace to call into 1450N/A * the driver through the fbdev interfaces. 1450N/A * This function will call down into the ->fb_probe callback to let 1450N/A * the driver allocate and initialize the fbdev info structure and the drm 1450N/A * framebuffer used to back the fbdev. drm_fb_helper_fill_var() and 1450N/A * drm_fb_helper_fill_fix() are provided as helpers to setup simple default 1450N/A * values for the fbdev info structure. 1450N/A * Zero if everything went ok, nonzero otherwise. 1450N/A * we shouldn't end up with no modes here. 1450N/A * drm_fb_helper_hotplug_event - respond to a hotplug notification by 1450N/A * probing all the outputs attached to the fb. 1450N/A * @fb_helper: the drm_fb_helper 1450N/A * Scan the connectors attached to the fb_helper and try to put together a 1450N/A * setup after *notification of a change in output configuration. 1450N/A * modeset configuration. Must be run from process context (which usually means 1450N/A * either the output polling work or a work item launched from the driver's 1450N/A * Scan the connectors attached to the fb_helper and try to put together a 1450N/A * setup after *notification of a change in output configuration. 1450N/A * 0 on success and a non-zero error code otherwise.