On Wed, Mar 08, 2017 at 09:15:24AM +0100, Romain Perier wrote: > - dw_hdmi_update_power() will be called. As hdmi->force will be equal to > DRM_FORCE_UNSPECIFIED the function will rely on hdmi->rxsense. This > field has not been updated by the irq handler, so it will be false and > DRM_FORCE_ON won't be put to hdmi->force. Right, and wrong. Your initial part is correct, but the latter sentence is incorrect - we only ever update hdmi->force according to the user's force requests, never as a result of the current state of the driver. hdmi->force exists to allow the user to say "I want to force this connector to always report disconnected or connected" to work around stupid monitors that pulse everything from HPD to RXSENSE when in standby mode. > This commit fixes the issue by removing the check for "!hdmi->disabled". > As already explained, even if the PHY is partially disabled, information > coming from HDMI Transmitter about HPD should be saved for a later use. Your fix looks fine to me, as both dw_hdmi_update_power() and dw_hdmi_update_phy_mask() effectively ignore attempts to update the state while hdmi->disabled is true. -- RMK's Patch system: http://www.armlinux.org.uk/developer/patches/ FTTC broadband for 0.8mile line: currently at 9.6Mbps down 400kbps up according to speedtest.net. _______________________________________________ dri-devel mailing list dri-devel@xxxxxxxxxxxxxxxxxxxxx https://lists.freedesktop.org/mailman/listinfo/dri-devel
