[PATCH] drm: don't call ->firstopen for KMS drivers

2013-07-22 Thread Laurent Pinchart
Hi Daniel, Thank you for the patch. On Saturday 13 July 2013 16:45:10 Daniel Vetter wrote: > It has way too much potential for driver writers to do stupid things > like delayed hw setup because the load sequence is somehow racy (e.g. > the imx driver in staging). So don't call it for modesetting

Re: [PATCH] drm: don't call ->firstopen for KMS drivers

2013-07-22 Thread Laurent Pinchart
Hi Daniel, Thank you for the patch. On Saturday 13 July 2013 16:45:10 Daniel Vetter wrote: > It has way too much potential for driver writers to do stupid things > like delayed hw setup because the load sequence is somehow racy (e.g. > the imx driver in staging). So don't call it for modesetting

[PATCH] drm: don't call ->firstopen for KMS drivers

2013-07-13 Thread Daniel Vetter
It has way too much potential for driver writers to do stupid things like delayed hw setup because the load sequence is somehow racy (e.g. the imx driver in staging). So don't call it for modesetting drivers, which reduces the complexity of the drm core -> driver interface a notch. v2: Don't forge

[PATCH] drm: don't call ->firstopen for KMS drivers

2013-07-13 Thread Daniel Vetter
It has way too much potential for driver writers to do stupid things like delayed hw setup because the load sequence is somehow racy (e.g. the imx driver in staging). So don't call it for modesetting drivers, which reduces the complexity of the drm core -> driver interface a notch. v2: Don't forge

[PATCH] drm: don't call ->firstopen for KMS drivers

2013-07-11 Thread Daniel Vetter
On Thu, Jul 11, 2013 at 9:54 AM, Laurent Pinchart wrote: > Hi Daniel, > > On Wednesday 10 July 2013 20:17:44 Daniel Vetter wrote: >> It has way too much potential for driver writers to do stupid things >> like delayed hw setup because the load sequence is somehow racy (e.g. >> the imx driver in st

[PATCH] drm: don't call ->firstopen for KMS drivers

2013-07-11 Thread Laurent Pinchart
Hi Daniel, On Wednesday 10 July 2013 20:17:44 Daniel Vetter wrote: > It has way too much potential for driver writers to do stupid things > like delayed hw setup because the load sequence is somehow racy (e.g. > the imx driver in staging). So don't call it for modesetting drivers, > which reduces

Re: [PATCH] drm: don't call ->firstopen for KMS drivers

2013-07-11 Thread Daniel Vetter
On Thu, Jul 11, 2013 at 9:54 AM, Laurent Pinchart wrote: > Hi Daniel, > > On Wednesday 10 July 2013 20:17:44 Daniel Vetter wrote: >> It has way too much potential for driver writers to do stupid things >> like delayed hw setup because the load sequence is somehow racy (e.g. >> the imx driver in st

Re: [PATCH] drm: don't call ->firstopen for KMS drivers

2013-07-11 Thread Laurent Pinchart
Hi Daniel, On Wednesday 10 July 2013 20:17:44 Daniel Vetter wrote: > It has way too much potential for driver writers to do stupid things > like delayed hw setup because the load sequence is somehow racy (e.g. > the imx driver in staging). So don't call it for modesetting drivers, > which reduces

[PATCH] drm: don't call ->firstopen for KMS drivers

2013-07-10 Thread Daniel Vetter
It has way too much potential for driver writers to do stupid things like delayed hw setup because the load sequence is somehow racy (e.g. the imx driver in staging). So don't call it for modesetting drivers, which reduces the complexity of the drm core -> driver interface a notch. v2: Don't forge

[PATCH] drm: don't call ->firstopen for KMS drivers

2013-07-10 Thread Daniel Vetter
It has way too much potential for driver writers to do stupid things like delayed hw setup because the load sequence is somehow racy (e.g. the imx driver in staging). So don't call it for modesetting drivers, which reduces the complexity of the drm core -> driver interface a notch. v2: Don't forge