Re: [PATCH v3 1/2] drm/file: Rehabilitate the firstopen hook for non-legacy drivers

2019-03-29 Thread Paul Kocialkowski
Hi Daniel, On Fri, 2019-03-29 at 09:35 +0100, Daniel Vetter wrote: > On Thu, Mar 28, 2019 at 05:13:05PM +0100, Paul Kocialkowski wrote: > > The firstopen DRM driver hook was initially used to perform hardware > > initialization, which is now considered legacy. Only a single user of > > firstopen r

Re: [PATCH v3 1/2] drm/file: Rehabilitate the firstopen hook for non-legacy drivers

2019-03-29 Thread Daniel Vetter
On Fri, Mar 29, 2019 at 09:35:34AM +0100, Daniel Vetter wrote: > On Thu, Mar 28, 2019 at 05:13:05PM +0100, Paul Kocialkowski wrote: > > The firstopen DRM driver hook was initially used to perform hardware > > initialization, which is now considered legacy. Only a single user of > > firstopen remain

Re: [PATCH v3 1/2] drm/file: Rehabilitate the firstopen hook for non-legacy drivers

2019-03-29 Thread Daniel Vetter
On Thu, Mar 28, 2019 at 05:13:05PM +0100, Paul Kocialkowski wrote: > The firstopen DRM driver hook was initially used to perform hardware > initialization, which is now considered legacy. Only a single user of > firstopen remains at this point (savage). > > In some specific cases, non-legacy drive

[PATCH v3 1/2] drm/file: Rehabilitate the firstopen hook for non-legacy drivers

2019-03-28 Thread Paul Kocialkowski
The firstopen DRM driver hook was initially used to perform hardware initialization, which is now considered legacy. Only a single user of firstopen remains at this point (savage). In some specific cases, non-legacy drivers may also need to implement these hooks. For instance on VC4, we need to al