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
609 * pick up any changes and fire the hotplug event. But if in drm_helper_probe_single_connector_modes()
611 * check here, and if anything changed start the hotplug code. in drm_helper_probe_single_connector_modes()
620 * The hotplug event code might call into the fb in drm_helper_probe_single_connector_modes()
713 * drm_kms_helper_hotplug_event - fire off KMS hotplug events
717 * client hotplug function, which is most commonly used to inform the fbdev
720 * Drivers should call this from their hotplug handling code when a change is
739 * drm_kms_helper_connector_hotplug_event - fire off a KMS connector hotplug event
791 * want any hotplug detection at all for polling. */ in output_poll_execute()
816 * call after receiving a hotplug event due to this in output_poll_execute()
908 * @dev. Drivers which do not have reliable hotplug support in hardware can use
919 * Note that a connector can be both polled and probed from the hotplug handler,
920 * in case the hotplug interrupt is known to be unreliable.
1012 * drm_connector_helper_hpd_irq_event - hotplug processing
1018 * This helper function is useful for drivers which can track hotplug
1020 * hotplug event for all connectors or can't track hotplug interrupts
1026 * Note that a connector can be both polled and probed from the hotplug
1027 * handler, in case the hotplug interrupt is known to be unreliable.
1043 drm_dbg_kms(dev, "[CONNECTOR:%d:%s] Sent hotplug event\n", in drm_connector_helper_hpd_irq_event()
1053 * drm_helper_hpd_irq_event - hotplug processing
1061 * This helper function is useful for drivers which can't or don't track hotplug
1064 * Drivers which support hotplug interrupts for each connector individually and
1073 * Note that a connector can be both polled and probed from the hotplug handler,
1074 * in case the hotplug interrupt is known to be unreliable.