/*1* Copyright 1999 Precision Insight, Inc., Cedar Park, Texas.2* Copyright 2000 VA Linux Systems, Inc., Sunnyvale, California.3* Copyright (c) 2009-2010, Code Aurora Forum.4* Copyright 2016 Intel Corp.5*6* Permission is hereby granted, free of charge, to any person obtaining a7* copy of this software and associated documentation files (the "Software"),8* to deal in the Software without restriction, including without limitation9* the rights to use, copy, modify, merge, publish, distribute, sublicense,10* and/or sell copies of the Software, and to permit persons to whom the11* Software is furnished to do so, subject to the following conditions:12*13* The above copyright notice and this permission notice (including the next14* paragraph) shall be included in all copies or substantial portions of the15* Software.16*17* THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR18* IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,19* FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL20* VA LINUX SYSTEMS AND/OR ITS SUPPLIERS BE LIABLE FOR ANY CLAIM, DAMAGES OR21* OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE,22* ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR23* OTHER DEALINGS IN THE SOFTWARE.24*/2526#ifndef _DRM_DRV_H_27#define _DRM_DRV_H_2829#include <linux/list.h>30#include <linux/irqreturn.h>3132#include <video/nomodeset.h>3334#include <drm/drm_device.h>3536struct dmem_cgroup_region;37struct drm_fb_helper;38struct drm_fb_helper_surface_size;39struct drm_file;40struct drm_gem_object;41struct drm_master;42struct drm_minor;43struct dma_buf;44struct dma_buf_attachment;45struct drm_display_mode;46struct drm_mode_create_dumb;47struct drm_printer;48struct sg_table;4950/**51* enum drm_driver_feature - feature flags52*53* See &drm_driver.driver_features, drm_device.driver_features and54* drm_core_check_feature().55*/56enum drm_driver_feature {57/**58* @DRIVER_GEM:59*60* Driver use the GEM memory manager. This should be set for all modern61* drivers.62*/63DRIVER_GEM = BIT(0),64/**65* @DRIVER_MODESET:66*67* Driver supports mode setting interfaces (KMS).68*/69DRIVER_MODESET = BIT(1),70/**71* @DRIVER_RENDER:72*73* Driver supports dedicated render nodes. See also the :ref:`section on74* render nodes <drm_render_node>` for details.75*/76DRIVER_RENDER = BIT(3),77/**78* @DRIVER_ATOMIC:79*80* Driver supports the full atomic modesetting userspace API. Drivers81* which only use atomic internally, but do not support the full82* userspace API (e.g. not all properties converted to atomic, or83* multi-plane updates are not guaranteed to be tear-free) should not84* set this flag.85*/86DRIVER_ATOMIC = BIT(4),87/**88* @DRIVER_SYNCOBJ:89*90* Driver supports &drm_syncobj for explicit synchronization of command91* submission.92*/93DRIVER_SYNCOBJ = BIT(5),94/**95* @DRIVER_SYNCOBJ_TIMELINE:96*97* Driver supports the timeline flavor of &drm_syncobj for explicit98* synchronization of command submission.99*/100DRIVER_SYNCOBJ_TIMELINE = BIT(6),101/**102* @DRIVER_COMPUTE_ACCEL:103*104* Driver supports compute acceleration devices. This flag is mutually exclusive with105* @DRIVER_RENDER and @DRIVER_MODESET. Devices that support both graphics and compute106* acceleration should be handled by two drivers that are connected using auxiliary bus.107*/108DRIVER_COMPUTE_ACCEL = BIT(7),109/**110* @DRIVER_GEM_GPUVA:111*112* Driver supports user defined GPU VA bindings for GEM objects.113*/114DRIVER_GEM_GPUVA = BIT(8),115/**116* @DRIVER_CURSOR_HOTSPOT:117*118* Driver supports and requires cursor hotspot information in the119* cursor plane (e.g. cursor plane has to actually track the mouse120* cursor and the clients are required to set hotspot in order for121* the cursor planes to work correctly).122*/123DRIVER_CURSOR_HOTSPOT = BIT(9),124125/* IMPORTANT: Below are all the legacy flags, add new ones above. */126127/**128* @DRIVER_USE_AGP:129*130* Set up DRM AGP support, see drm_agp_init(), the DRM core will manage131* AGP resources. New drivers don't need this.132*/133DRIVER_USE_AGP = BIT(25),134/**135* @DRIVER_LEGACY:136*137* Denote a legacy driver using shadow attach. Do not use.138*/139DRIVER_LEGACY = BIT(26),140/**141* @DRIVER_PCI_DMA:142*143* Driver is capable of PCI DMA, mapping of PCI DMA buffers to userspace144* will be enabled. Only for legacy drivers. Do not use.145*/146DRIVER_PCI_DMA = BIT(27),147/**148* @DRIVER_SG:149*150* Driver can perform scatter/gather DMA, allocation and mapping of151* scatter/gather buffers will be enabled. Only for legacy drivers. Do152* not use.153*/154DRIVER_SG = BIT(28),155156/**157* @DRIVER_HAVE_DMA:158*159* Driver supports DMA, the userspace DMA API will be supported. Only160* for legacy drivers. Do not use.161*/162DRIVER_HAVE_DMA = BIT(29),163/**164* @DRIVER_HAVE_IRQ:165*166* Legacy irq support. Only for legacy drivers. Do not use.167*/168DRIVER_HAVE_IRQ = BIT(30),169};170171/**172* struct drm_driver - DRM driver structure173*174* This structure represent the common code for a family of cards. There will be175* one &struct drm_device for each card present in this family. It contains lots176* of vfunc entries, and a pile of those probably should be moved to more177* appropriate places like &drm_mode_config_funcs or into a new operations178* structure for GEM drivers.179*/180struct drm_driver {181/**182* @load:183*184* Backward-compatible driver callback to complete initialization steps185* after the driver is registered. For this reason, may suffer from186* race conditions and its use is deprecated for new drivers. It is187* therefore only supported for existing drivers not yet converted to188* the new scheme. See devm_drm_dev_alloc() and drm_dev_register() for189* proper and race-free way to set up a &struct drm_device.190*191* This is deprecated, do not use!192*193* Returns:194*195* Zero on success, non-zero value on failure.196*/197int (*load) (struct drm_device *, unsigned long flags);198199/**200* @open:201*202* Driver callback when a new &struct drm_file is opened. Useful for203* setting up driver-private data structures like buffer allocators,204* execution contexts or similar things. Such driver-private resources205* must be released again in @postclose.206*207* Since the display/modeset side of DRM can only be owned by exactly208* one &struct drm_file (see &drm_file.is_master and &drm_device.master)209* there should never be a need to set up any modeset related resources210* in this callback. Doing so would be a driver design bug.211*212* Returns:213*214* 0 on success, a negative error code on failure, which will be215* promoted to userspace as the result of the open() system call.216*/217int (*open) (struct drm_device *, struct drm_file *);218219/**220* @postclose:221*222* One of the driver callbacks when a new &struct drm_file is closed.223* Useful for tearing down driver-private data structures allocated in224* @open like buffer allocators, execution contexts or similar things.225*226* Since the display/modeset side of DRM can only be owned by exactly227* one &struct drm_file (see &drm_file.is_master and &drm_device.master)228* there should never be a need to tear down any modeset related229* resources in this callback. Doing so would be a driver design bug.230*/231void (*postclose) (struct drm_device *, struct drm_file *);232233/**234* @unload:235*236* Reverse the effects of the driver load callback. Ideally,237* the clean up performed by the driver should happen in the238* reverse order of the initialization. Similarly to the load239* hook, this handler is deprecated and its usage should be240* dropped in favor of an open-coded teardown function at the241* driver layer. See drm_dev_unregister() and drm_dev_put()242* for the proper way to remove a &struct drm_device.243*244* The unload() hook is called right after unregistering245* the device.246*247*/248void (*unload) (struct drm_device *);249250/**251* @release:252*253* Optional callback for destroying device data after the final254* reference is released, i.e. the device is being destroyed.255*256* This is deprecated, clean up all memory allocations associated with a257* &drm_device using drmm_add_action(), drmm_kmalloc() and related258* managed resources functions.259*/260void (*release) (struct drm_device *);261262/**263* @master_set:264*265* Called whenever the minor master is set. Only used by vmwgfx.266*/267void (*master_set)(struct drm_device *dev, struct drm_file *file_priv,268bool from_open);269/**270* @master_drop:271*272* Called whenever the minor master is dropped. Only used by vmwgfx.273*/274void (*master_drop)(struct drm_device *dev, struct drm_file *file_priv);275276/**277* @debugfs_init:278*279* Allows drivers to create driver-specific debugfs files.280*/281void (*debugfs_init)(struct drm_minor *minor);282283/**284* @gem_create_object: constructor for gem objects285*286* Hook for allocating the GEM object struct, for use by the CMA287* and SHMEM GEM helpers. Returns a GEM object on success, or an288* ERR_PTR()-encoded error code otherwise.289*/290struct drm_gem_object *(*gem_create_object)(struct drm_device *dev,291size_t size);292293/**294* @prime_handle_to_fd:295*296* PRIME export function. Only used by vmwgfx.297*/298int (*prime_handle_to_fd)(struct drm_device *dev, struct drm_file *file_priv,299uint32_t handle, uint32_t flags, int *prime_fd);300/**301* @prime_fd_to_handle:302*303* PRIME import function. Only used by vmwgfx.304*/305int (*prime_fd_to_handle)(struct drm_device *dev, struct drm_file *file_priv,306int prime_fd, uint32_t *handle);307308/**309* @gem_prime_import:310*311* Import hook for GEM drivers.312*313* This defaults to drm_gem_prime_import() if not set.314*/315struct drm_gem_object * (*gem_prime_import)(struct drm_device *dev,316struct dma_buf *dma_buf);317/**318* @gem_prime_import_sg_table:319*320* Optional hook used by the PRIME helper functions321* drm_gem_prime_import() respectively drm_gem_prime_import_dev().322*/323struct drm_gem_object *(*gem_prime_import_sg_table)(324struct drm_device *dev,325struct dma_buf_attachment *attach,326struct sg_table *sgt);327328/**329* @dumb_create:330*331* This creates a new dumb buffer in the driver's backing storage manager (GEM,332* TTM or something else entirely) and returns the resulting buffer handle. This333* handle can then be wrapped up into a framebuffer modeset object.334*335* Note that userspace is not allowed to use such objects for render336* acceleration - drivers must create their own private ioctls for such a use337* case.338*339* Width, height and depth are specified in the &drm_mode_create_dumb340* argument. The callback needs to fill the handle, pitch and size for341* the created buffer.342*343* Called by the user via ioctl.344*345* Returns:346*347* Zero on success, negative errno on failure.348*/349int (*dumb_create)(struct drm_file *file_priv,350struct drm_device *dev,351struct drm_mode_create_dumb *args);352/**353* @dumb_map_offset:354*355* Allocate an offset in the drm device node's address space to be able to356* memory map a dumb buffer.357*358* The default implementation is drm_gem_create_mmap_offset(). GEM based359* drivers must not overwrite this.360*361* Called by the user via ioctl.362*363* Returns:364*365* Zero on success, negative errno on failure.366*/367int (*dumb_map_offset)(struct drm_file *file_priv,368struct drm_device *dev, uint32_t handle,369uint64_t *offset);370371/**372* @fbdev_probe:373*374* Allocates and initialize the fb_info structure for fbdev emulation.375* Furthermore it also needs to allocate the DRM framebuffer used to376* back the fbdev.377*378* This callback is mandatory for fbdev support.379*380* Returns:381*382* 0 on success ot a negative error code otherwise.383*/384int (*fbdev_probe)(struct drm_fb_helper *fbdev_helper,385struct drm_fb_helper_surface_size *sizes);386387/**388* @show_fdinfo:389*390* Print device specific fdinfo. See Documentation/gpu/drm-usage-stats.rst.391*/392void (*show_fdinfo)(struct drm_printer *p, struct drm_file *f);393394/** @major: driver major number */395int major;396/** @minor: driver minor number */397int minor;398/** @patchlevel: driver patch level */399int patchlevel;400/** @name: driver name */401char *name;402/** @desc: driver description */403char *desc;404405/**406* @driver_features:407* Driver features, see &enum drm_driver_feature. Drivers can disable408* some features on a per-instance basis using409* &drm_device.driver_features.410*/411u32 driver_features;412413/**414* @ioctls:415*416* Array of driver-private IOCTL description entries. See the chapter on417* :ref:`IOCTL support in the userland interfaces418* chapter<drm_driver_ioctl>` for the full details.419*/420421const struct drm_ioctl_desc *ioctls;422/** @num_ioctls: Number of entries in @ioctls. */423int num_ioctls;424425/**426* @fops:427*428* File operations for the DRM device node. See the discussion in429* :ref:`file operations<drm_driver_fops>` for in-depth coverage and430* some examples.431*/432const struct file_operations *fops;433};434435void *__devm_drm_dev_alloc(struct device *parent,436const struct drm_driver *driver,437size_t size, size_t offset);438439struct dmem_cgroup_region *440drmm_cgroup_register_region(struct drm_device *dev,441const char *region_name, u64 size);442443/**444* devm_drm_dev_alloc - Resource managed allocation of a &drm_device instance445* @parent: Parent device object446* @driver: DRM driver447* @type: the type of the struct which contains struct &drm_device448* @member: the name of the &drm_device within @type.449*450* This allocates and initialize a new DRM device. No device registration is done.451* Call drm_dev_register() to advertice the device to user space and register it452* with other core subsystems. This should be done last in the device453* initialization sequence to make sure userspace can't access an inconsistent454* state.455*456* The initial ref-count of the object is 1. Use drm_dev_get() and457* drm_dev_put() to take and drop further ref-counts.458*459* It is recommended that drivers embed &struct drm_device into their own device460* structure.461*462* Note that this manages the lifetime of the resulting &drm_device463* automatically using devres. The DRM device initialized with this function is464* automatically put on driver detach using drm_dev_put().465*466* RETURNS:467* Pointer to new DRM device, or ERR_PTR on failure.468*/469#define devm_drm_dev_alloc(parent, driver, type, member) \470((type *) __devm_drm_dev_alloc(parent, driver, sizeof(type), \471offsetof(type, member)))472473struct drm_device *drm_dev_alloc(const struct drm_driver *driver,474struct device *parent);475476void *__drm_dev_alloc(struct device *parent,477const struct drm_driver *driver,478size_t size, size_t offset);479480int drm_dev_register(struct drm_device *dev, unsigned long flags);481void drm_dev_unregister(struct drm_device *dev);482483void drm_dev_get(struct drm_device *dev);484void drm_dev_put(struct drm_device *dev);485void drm_put_dev(struct drm_device *dev);486bool drm_dev_enter(struct drm_device *dev, int *idx);487void drm_dev_exit(int idx);488void drm_dev_unplug(struct drm_device *dev);489int drm_dev_wedged_event(struct drm_device *dev, unsigned long method,490struct drm_wedge_task_info *info);491492/**493* drm_dev_is_unplugged - is a DRM device unplugged494* @dev: DRM device495*496* This function can be called to check whether a hotpluggable is unplugged.497* Unplugging itself is singalled through drm_dev_unplug(). If a device is498* unplugged, these two functions guarantee that any store before calling499* drm_dev_unplug() is visible to callers of this function after it completes500*501* WARNING: This function fundamentally races against drm_dev_unplug(). It is502* recommended that drivers instead use the underlying drm_dev_enter() and503* drm_dev_exit() function pairs.504*/505static inline bool drm_dev_is_unplugged(struct drm_device *dev)506{507int idx;508509if (drm_dev_enter(dev, &idx)) {510drm_dev_exit(idx);511return false;512}513514return true;515}516517/**518* drm_core_check_all_features - check driver feature flags mask519* @dev: DRM device to check520* @features: feature flag(s) mask521*522* This checks @dev for driver features, see &drm_driver.driver_features,523* &drm_device.driver_features, and the various &enum drm_driver_feature flags.524*525* Returns true if all features in the @features mask are supported, false526* otherwise.527*/528static inline bool drm_core_check_all_features(const struct drm_device *dev,529u32 features)530{531u32 supported = dev->driver->driver_features & dev->driver_features;532533return features && (supported & features) == features;534}535536/**537* drm_core_check_feature - check driver feature flags538* @dev: DRM device to check539* @feature: feature flag540*541* This checks @dev for driver features, see &drm_driver.driver_features,542* &drm_device.driver_features, and the various &enum drm_driver_feature flags.543*544* Returns true if the @feature is supported, false otherwise.545*/546static inline bool drm_core_check_feature(const struct drm_device *dev,547enum drm_driver_feature feature)548{549return drm_core_check_all_features(dev, feature);550}551552/**553* drm_drv_uses_atomic_modeset - check if the driver implements554* atomic_commit()555* @dev: DRM device556*557* This check is useful if drivers do not have DRIVER_ATOMIC set but558* have atomic modesetting internally implemented.559*/560static inline bool drm_drv_uses_atomic_modeset(struct drm_device *dev)561{562return drm_core_check_feature(dev, DRIVER_ATOMIC) ||563(dev->mode_config.funcs && dev->mode_config.funcs->atomic_commit != NULL);564}565566567/* TODO: Inline drm_firmware_drivers_only() in all its callers. */568static inline bool drm_firmware_drivers_only(void)569{570return video_firmware_drivers_only();571}572573#if defined(CONFIG_DEBUG_FS)574void drm_debugfs_dev_init(struct drm_device *dev);575void drm_debugfs_init_root(void);576void drm_debugfs_remove_root(void);577void drm_debugfs_bridge_params(void);578#else579static inline void drm_debugfs_dev_init(struct drm_device *dev)580{581}582583static inline void drm_debugfs_init_root(void)584{585}586587static inline void drm_debugfs_remove_root(void)588{589}590591static inline void drm_debugfs_bridge_params(void)592{593}594#endif595596#endif597598599