From mboxrd@z Thu Jan 1 00:00:00 1970 From: Russell King - ARM Linux Subject: Re: [PATCH 3/3 v3] drm: bridge/dw-hdmi: Move edid reading to .detect() callback Date: Thu, 4 Aug 2016 11:47:38 +0100 Message-ID: <20160804104738.GR1041@n2100.armlinux.org.uk> References: <1bbffb944fb9ce0363f5544db31baf2a911c1c55.1470306826.git.joabreu@synopsys.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Return-path: Content-Disposition: inline In-Reply-To: <1bbffb944fb9ce0363f5544db31baf2a911c1c55.1470306826.git.joabreu@synopsys.com> Sender: linux-kernel-owner@vger.kernel.org To: Jose Abreu Cc: dri-devel@lists.freedesktop.org, Carlos Palminha , Archit Taneja , David Airlie , Fabio Estevam , Daniel Vetter , Takashi Iwai , Vladimir Zapolskiy , Thierry Reding , linux-kernel@vger.kernel.org List-Id: dri-devel@lists.freedesktop.org On Thu, Aug 04, 2016 at 11:44:51AM +0100, Jose Abreu wrote: > When running HDMI compliance tests we noticed that sometimes > the edid changes but the get_modes() function is not called > so the edid is not updated. Moving the edid reading to the > detect() callback ensures that the edid is correctly updated > after an hotplug. Wouldn't this be a bug in the higher levels of DRM? -- 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.