It seems like we can't have nice things, so let's just document the disappointing behaviour instead. The previous version assumed the kernel would perform the probing work when appropriate, however this is not the case today. Update the documentation to reflect reality. v2: - Improve commit message to explain why this change is made (Pekka) - Keep the bit about flickering (Daniel) - Explain when user-space should force-probe, and when it shouldn't (Daniel)
Showing the changes to include/uapi (1 of 1 file). Show all
Unified · Split
| @@ -414,15 +414,12 @@ enum drm_mode_subconnector { · 413 unmodified lines | ||
| 414 | 414 | * |
| 415 | 415 | * If the @count_modes field is set to zero, the kernel will perform a forced |
| 416 | 416 | * probe on the connector to refresh the connector status, modes and EDID. |
| 417 | − * A forced-probe can be slow and the ioctl will block. A force-probe can cause | |
| 418 | − * flickering and temporary freezes, so it should not be performed | |
| 419 | − * automatically. | |
| 417 | + * A forced-probe can be slow, might cause flickering and the ioctl will block. | |
| 420 | 418 | * |
| 421 | − * User-space shouldn't need to force-probe connectors in general: the kernel | |
| 422 | − * will automatically take care of probing connectors that don't support | |
| 423 | − * hot-plug detection when appropriate. However, user-space may force-probe | |
| 424 | − * connectors on user request (e.g. clicking a "Scan connectors" button, or | |
| 425 | − * opening a UI to manage screens). | |
| 419 | + * User-space needs to force-probe connectors to ensure their metadata is | |
| 420 | + * up-to-date at startup and after receiving a hot-plug event. User-space | |
| 421 | + * may perform a forced-probe when the user explicitly requests it. User-space | |
| 422 | + * shouldn't perform a forced-probe in other situations. | |
| 426 | 423 | */ |
| 427 | 424 | struct drm_mode_get_connector { |
| 428 | 425 | /** @encoders_ptr: Pointer to ``__u32`` array of object IDs. */ |