Lines Matching full:hotplug

55  * generic hotplug interrupt handling where the driver doesn't or cannot keep
59  * Drivers can also overwrite different parts e.g. use their own hotplug
598 	 * pick up any changes and fire the hotplug event. But if  in drm_helper_probe_single_connector_modes()
600 	 * check here, and if anything changed start the hotplug code.  in drm_helper_probe_single_connector_modes()
610 		 * The hotplug event code might call into the fb  in drm_helper_probe_single_connector_modes()
697  * drm_kms_helper_hotplug_event - fire off KMS hotplug events
704  * Drivers should call this from their hotplug handling code when a change is
727  * drm_kms_helper_connector_hotplug_event - fire off a KMS connector hotplug event
781 		 * want any hotplug detection at all for polling. */  in output_poll_execute()
806 			 * call after receiving a hotplug event due to this  in output_poll_execute()
894  * @dev. Drivers which do not have reliable hotplug support in hardware can use
905  * Note that a connector can be both polled and probed from the hotplug handler,
906  * in case the hotplug interrupt is known to be unreliable.
972  * drm_connector_helper_hpd_irq_event - hotplug processing
978  * This helper function is useful for drivers which can track hotplug
980  * hotplug event for all connectors or can't track hotplug interrupts
986  * Note that a connector can be both polled and probed from the hotplug
987  * handler, in case the hotplug interrupt is known to be unreliable.
1003 		drm_dbg_kms(dev, "[CONNECTOR:%d:%s] Sent hotplug event\n",  in drm_connector_helper_hpd_irq_event()
1013  * drm_helper_hpd_irq_event - hotplug processing
1021  * This helper function is useful for drivers which can't or don't track hotplug
1024  * Drivers which support hotplug interrupts for each connector individually and
1033  * Note that a connector can be both polled and probed from the hotplug handler,
1034  * in case the hotplug interrupt is known to be unreliable.