Merge tag 'drm-intel-next-2022-05-06' of git://anongit.freedesktop.org/drm/drm-intel into drm-next

     struct mdev_driver {

	     int  (*probe)  (struct mdev_device *dev);

	     void (*remove) (struct mdev_device *dev);

	     struct attribute_group **supported_type_groups;

	     struct device_driver    driver;

     };

    extern void mdev_unregister_driver(struct mdev_driver *drv);

The mediated bus driver is responsible for adding mediated devices to the VFIO

group when devices are bound to the driver and removing mediated devices from

the VFIO when devices are unbound from the driver.

Physical Device Driver Interface

--------------------------------

The physical device driver interface provides the mdev_parent_ops[3] structure

to define the APIs to manage work in the mediated core driver that is related

to the physical device.

The structures in the mdev_parent_ops structure are as follows:

* dev_attr_groups: attributes of the parent device

* mdev_attr_groups: attributes of the mediated device

* supported_config: attributes to define supported configurations

* device_driver: device driver to bind for mediated device instances

The mdev_parent_ops also still has various functions pointers.  Theses exist

for historical reasons only and shall not be used for new drivers.

The mediated bus driver's probe function should create a vfio_device on top of

the mdev_device and connect it to an appropriate implementation of

vfio_device_ops.

When a driver wants to add the GUID creation sysfs to an existing device it has

probe'd to then it should call::

	extern int  mdev_register_device(struct device *dev,

	                                 const struct mdev_parent_ops *ops);

	                                 struct mdev_driver *mdev_driver);

This will provide the 'mdev_supported_types/XX/create' files which can then be

used to trigger the creation of a mdev_device. The created mdev_device will be

	INTEL_ADLP_IDS(&gen11_early_ops),

	INTEL_ADLN_IDS(&gen11_early_ops),

	INTEL_RPLS_IDS(&gen11_early_ops),

	INTEL_RPLP_IDS(&gen11_early_ops),

};

struct resource intel_graphics_stolen_res __ro_after_init = DEFINE_RES_MEM(0, 0);

	  If in doubt, say "Y".

config DRM_I915_GVT

	bool "Enable Intel GVT-g graphics virtualization host support"

	bool

config DRM_I915_GVT_KVMGT

	tristate "Enable KVM host support Intel GVT-g graphics virtualization"

	depends on DRM_I915

	depends on X86

	depends on 64BIT

	default n

	depends on KVM

	depends on VFIO_MDEV

	select DRM_I915_GVT

	select KVM_EXTERNAL_WRITE_TRACKING

	help

	  Choose this option if you want to enable Intel GVT-g graphics

	  virtualization technology host support with integrated graphics.

	  With GVT-g, it's possible to have one integrated graphics

	  device shared by multiple VMs under different hypervisors.

	  Note that at least one hypervisor like Xen or KVM is required for

	  this driver to work, and it only supports newer device from

	  Broadwell+. For further information and setup guide, you can

	  visit: http://01.org/igvt-g.

	  device shared by multiple VMs under KVM.

	  Now it's just a stub to support the modifications of i915 for

	  GVT device model. It requires at least one MPT modules for Xen/KVM

	  and other components of GVT device model to work. Use it under

	  you own risk.

	  Note that this driver only supports newer device from Broadwell on.

	  For further information and setup guide, you can visit:

	  http://01.org/igvt-g.

	  If in doubt, say "N".

config DRM_I915_GVT_KVMGT

	tristate "Enable KVM/VFIO support for Intel GVT-g"

	depends on DRM_I915_GVT

	depends on KVM

	depends on VFIO_MDEV

	select KVM_EXTERNAL_WRITE_TRACKING

	default n

	help

	  Choose this option if you want to enable KVMGT support for

	  Intel GVT-g.

config DRM_I915_PXP

	bool "Enable Intel PXP support"

	depends on DRM_I915

	display/intel_cursor.o \

	display/intel_display.o \

	display/intel_display_power.o \

	display/intel_display_power_map.o \

	display/intel_display_power_well.o \

	display/intel_dmc.o \

	display/intel_dpio_phy.o \

# virtual gpu code

i915-y += i915_vgpu.o

ifeq ($(CONFIG_DRM_I915_GVT),y)

i915-y += intel_gvt.o

i915-$(CONFIG_DRM_I915_GVT) += \

	intel_gvt.o \

	intel_gvt_mmio_table.o

include $(src)/gvt/Makefile

endif

obj-$(CONFIG_DRM_I915) += i915.o

obj-$(CONFIG_DRM_I915_GVT_KVMGT) += gvt/kvmgt.o

obj-$(CONFIG_DRM_I915_GVT_KVMGT) += kvmgt.o

# header test

#include "intel_connector.h"

#include "intel_crtc.h"

#include "intel_de.h"

#include "intel_display_power.h"

#include "intel_display_types.h"

#include "intel_dp.h"

#include "intel_dp_link_training.h"

	dig_port->max_lanes = 4;

	intel_encoder->type = INTEL_OUTPUT_DP;

	intel_encoder->power_domain = intel_port_to_power_domain(port);

	intel_encoder->power_domain = intel_display_power_ddi_lanes_domain(dev_priv, port);

	if (IS_CHERRYVIEW(dev_priv)) {

		if (port == PORT_D)

			intel_encoder->pipe_mask = BIT(PIPE_C);