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
610 * pick up any changes and fire the hotplug event. But if in drm_helper_probe_single_connector_modes()
612 * check here, and if anything changed start the hotplug code. in drm_helper_probe_single_connector_modes()
621 * The hotplug event code might call into the fb in drm_helper_probe_single_connector_modes()
714 * drm_kms_helper_hotplug_event - fire off KMS hotplug events
718 * client hotplug function, which is most commonly used to inform the fbdev
721 * Drivers should call this from their hotplug handling code when a change is
740 * drm_kms_helper_connector_hotplug_event - fire off a KMS connector hotplug event
792 * want any hotplug detection at all for polling. */ in output_poll_execute()
817 * call after receiving a hotplug event due to this in output_poll_execute()
909 * @dev. Drivers which do not have reliable hotplug support in hardware can use
920 * Note that a connector can be both polled and probed from the hotplug handler,
921 * in case the hotplug interrupt is known to be unreliable.
1013 * drm_connector_helper_hpd_irq_event - hotplug processing
1019 * This helper function is useful for drivers which can track hotplug
1021 * hotplug event for all connectors or can't track hotplug interrupts
1027 * Note that a connector can be both polled and probed from the hotplug
1028 * handler, in case the hotplug interrupt is known to be unreliable.
1044 drm_dbg_kms(dev, "[CONNECTOR:%d:%s] Sent hotplug event\n", in drm_connector_helper_hpd_irq_event()
1054 * drm_helper_hpd_irq_event - hotplug processing
1062 * This helper function is useful for drivers which can't or don't track hotplug
1065 * Drivers which support hotplug interrupts for each connector individually and
1074 * Note that a connector can be both polled and probed from the hotplug handler,
1075 * in case the hotplug interrupt is known to be unreliable.