drm/i915: Rename "_load"/"_unload" to match PCI entry points
Current names of i915_driver_load/unload() functions originate in legacy DRM stubs. Reduce nomenclature ambiguity by renaming them to match their current use as helpers called from PCI entry points. Suggested by: Chris Wilson <chris@chris-wilson.co.uk> Signed-off-by: Janusz Krzysztofik <janusz.krzysztofik@linux.intel.com> Reviewed-by: Chris Wilson <chris@chris-wilson.co.uk> Reviewed-by: Joonas Lahtinen <joonas.lahtinen@linux.intel.com> Signed-off-by: Chris Wilson <chris@chris-wilson.co.uk> Link: https://patchwork.freedesktop.org/patch/msgid/20190712112429.740-3-janusz.krzysztofik@linux.intel.com
This commit is contained in:

committed by
Chris Wilson

parent
b5893ffc27
commit
b01558e56f
@@ -1876,17 +1876,17 @@ static void i915_driver_destroy(struct drm_i915_private *i915)
|
||||
}
|
||||
|
||||
/**
|
||||
* i915_driver_load - setup chip and create an initial config
|
||||
* i915_driver_probe - setup chip and create an initial config
|
||||
* @pdev: PCI device
|
||||
* @ent: matching PCI ID entry
|
||||
*
|
||||
* The driver load routine has to do several things:
|
||||
* The driver probe routine has to do several things:
|
||||
* - drive output discovery via intel_modeset_init()
|
||||
* - initialize the memory manager
|
||||
* - allocate initial config memory
|
||||
* - setup the DRM framebuffer with the allocated memory
|
||||
*/
|
||||
int i915_driver_load(struct pci_dev *pdev, const struct pci_device_id *ent)
|
||||
int i915_driver_probe(struct pci_dev *pdev, const struct pci_device_id *ent)
|
||||
{
|
||||
const struct intel_device_info *match_info =
|
||||
(struct intel_device_info *)ent->driver_data;
|
||||
@@ -1952,7 +1952,7 @@ out_fini:
|
||||
return ret;
|
||||
}
|
||||
|
||||
void i915_driver_unload(struct drm_device *dev)
|
||||
void i915_driver_remove(struct drm_device *dev)
|
||||
{
|
||||
struct drm_i915_private *dev_priv = to_i915(dev);
|
||||
struct pci_dev *pdev = dev_priv->drm.pdev;
|
||||
|
Reference in New Issue
Block a user