Re: [PATCH 03/25] drm/imx: kill firstopen callback

2013-08-12 Thread Greg Kroah-Hartman
On Thu, Aug 08, 2013 at 03:41:13PM +0200, Daniel Vetter wrote: > 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

[PATCH 03/25] drm/imx: kill firstopen callback

2013-08-12 Thread Greg Kroah-Hartman
On Thu, Aug 08, 2013 at 03:41:13PM +0200, Daniel Vetter wrote: > 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

[PATCH 03/25] drm/imx: kill firstopen callback

2013-08-08 Thread Daniel Vetter
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 a

[PATCH 03/25] drm/imx: kill firstopen callback

2013-08-08 Thread Daniel Vetter
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 a