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 16:04:43 +0100 Message-ID: <20160804150443.GW1041@n2100.armlinux.org.uk> References: <1bbffb944fb9ce0363f5544db31baf2a911c1c55.1470306826.git.joabreu@synopsys.com> <20160804104738.GR1041@n2100.armlinux.org.uk> <57A349E8.5040400@synopsys.com> <20160804143102.GU1041@n2100.armlinux.org.uk> <57A357D1.1070900@synopsys.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Return-path: Content-Disposition: inline In-Reply-To: <57A357D1.1070900@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 03:57:21PM +0100, Jose Abreu wrote: > Hmm, I am not debugging it right now but I remember that > drm_fb_helper_probe_connector_modes() was not being called at the > time I set the new EDID but only after I stopped sending video (I > was using modetest). Please investigate - I'd prefer that your patch does not get applied until we really know what's going on here. Hmm, if you're using modetest, then userspace is setting a mode, and userspace is in control of the DRM device - that's probably the reason why you're not seeing anything happening - modetest probably doesn't know anything about hotplug events, and so doesn't read the modes. Have you tried with the framebuffer console and DRM fbdev emulation enabled, without using modetest? -- 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.