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
444 * pick up any changes and fire the hotplug event. But if in drm_helper_probe_single_connector_modes()
446 * check here, and if anything changed start the hotplug code. in drm_helper_probe_single_connector_modes()
456 * The hotplug event code might call into the fb in drm_helper_probe_single_connector_modes()
550 * drm_kms_helper_hotplug_event - fire off KMS hotplug events
557 * Drivers should call this from their hotplug handling code when a change is
607 * want any hotplug detection at all for polling. */ in output_poll_execute()
631 * call after receiving a hotplug event due to this in output_poll_execute()
713 * @dev. Drivers which do not have reliable hotplug support in hardware can use
724 * Note that a connector can be both polled and probed from the hotplug handler,
725 * in case the hotplug interrupt is known to be unreliable.
751 * drm_helper_hpd_irq_event - hotplug processing
759 * This helper function is useful for drivers which can't or don't track hotplug
762 * Drivers which support hotplug interrupts for each connector individually and
770 * Note that a connector can be both polled and probed from the hotplug handler,
771 * in case the hotplug interrupt is known to be unreliable.