Hi Greg, On Wed, Aug 28, 2013 at 12:11 AM, Greg KH <[email protected]> wrote: > On Tue, Aug 27, 2013 at 11:32:43PM -0300, Fabio Estevam wrote: >> From: Fabio Estevam <[email protected]> >> >> Since commit b5dc0d10 (drm/imx: kill firstopen callback) the following probe >> failure is seen: > > I don't have that commit in any tree I control, so I can't apply this > patch. What tree is this commit in?
Ok, understood. Just realized that this commit reached linux-next via Dave Airlie's tree: commit b5dc0d108cd3c0b50ddcb6f6c54be1 bea4c39e01 Author: Daniel Vetter <[email protected]> Date: Thu Aug 8 15:41:13 2013 +0200 drm/imx: kill firstopen callback This thing seems to do some kind of delayed setup. Really, real kms drivers shouldn't do that at all. Either stuff needs to be dynamically hotplugged or the driver setup sequence needs to be fixed. This patch here just moves the setup at the very end of the driver load callback, with the locking adjusted accordingly. v2: Also move the corresponding put from ->lastclose to ->unload. Cc: Sascha Hauer <[email protected]> Cc: Greg Kroah-Hartman <[email protected]> Signed-off-by: Daniel Vetter <[email protected]> Acked-by: Greg Kroah-Hartman <[email protected]> Signed-off-by: Dave Airlie <[email protected]> Will resend it to Dave then. Thanks, Fabio Estevam -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [email protected] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
