Hi Maxime, Thank you for the feedback. You're right - showing the driver usage is important to validate the API design before merging framework changes.
I'm preparing follow-up patches to demonstrate how this would be used in practice. Here's the plan: 1. DRM driver side: Show where to call drm_connector_hdmi_audio_crtc_notify() in the CRTC enable/disable paths (using i915 as an example) 2. Audio codec side: Show how an audio codec driver would implement the crtc_state_change callback (using HDA HDMI as an example) I'll send these as a small series (framework patch + driver usage examples) for your review. The examples will show: - How i915 would notify audio when a CRTC is disabled while the connector remains physically connected (e.g., user switches to "internal display only") - How the HDA HDMI codec would handle this notification to prevent silent audio breakage Would you prefer I send the full series now, or would you like to see the example patches first for API design review? Best regards, Wang Dicheng
