Lines Matching full:hotplug
56 * generic hotplug interrupt handling where the driver doesn't or cannot keep
60 * Drivers can also overwrite different parts e.g. use their own hotplug
472 * pick up any changes and fire the hotplug event. But if in drm_helper_probe_single_connector_modes()
474 * check here, and if anything changed start the hotplug code. in drm_helper_probe_single_connector_modes()
484 * The hotplug event code might call into the fb in drm_helper_probe_single_connector_modes()
592 * drm_kms_helper_hotplug_event - fire off KMS hotplug events
599 * Drivers should call this from their hotplug handling code when a change is
649 * want any hotplug detection at all for polling. */ in output_poll_execute()
673 * call after receiving a hotplug event due to this in output_poll_execute()
755 * @dev. Drivers which do not have reliable hotplug support in hardware can use
766 * Note that a connector can be both polled and probed from the hotplug handler,
767 * in case the hotplug interrupt is known to be unreliable.
793 * drm_helper_hpd_irq_event - hotplug processing
801 * This helper function is useful for drivers which can't or don't track hotplug
804 * Drivers which support hotplug interrupts for each connector individually and
812 * Note that a connector can be both polled and probed from the hotplug handler,
813 * in case the hotplug interrupt is known to be unreliable.
866 DRM_DEBUG_KMS("Sent hotplug event\n"); in drm_helper_hpd_irq_event()