From mboxrd@z Thu Jan 1 00:00:00 1970 From: =?windows-1252?Q?Michel_D=E4nzer?= Subject: Re: [PATCH 7/8] drm/irq: Implement a generic vblank_wait function Date: Wed, 30 Jul 2014 17:32:28 +0900 Message-ID: <53D8AD9C.7000006@daenzer.net> References: <1406669543-31213-1-git-send-email-daniel.vetter@ffwll.ch> <1406669543-31213-8-git-send-email-daniel.vetter@ffwll.ch> <53D85F95.3050502@daenzer.net> <20140730082212.GH4747@phenom.ffwll.local> Mime-Version: 1.0 Content-Type: text/plain; charset="windows-1252" Content-Transfer-Encoding: quoted-printable Return-path: In-Reply-To: <20140730082212.GH4747@phenom.ffwll.local> List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: intel-gfx-bounces@lists.freedesktop.org Sender: "Intel-gfx" To: Daniel Vetter Cc: Daniel Vetter , Intel Graphics Development , DRI Development List-Id: intel-gfx@lists.freedesktop.org On 30.07.2014 17:22, Daniel Vetter wrote: > On Wed, Jul 30, 2014 at 11:59:33AM +0900, Michel D=E4nzer wrote: >> On 30.07.2014 06:32, Daniel Vetter wrote: >>> + * due to lack of driver support or because the crtc is off. >>> + */ >>> +void drm_crtc_vblank_wait(struct drm_crtc *crtc) >>> +{ >>> + drm_vblank_wait(crtc->dev, drm_crtc_index(crtc)); >>> +} >>> +EXPORT_SYMBOL(drm_crtc_vblank_wait); >>> + >>> +/** >> >> Maybe the function names should be *_vblank_wait_next() or something to >> clarify the purpose and reduce potential confusion versus drm_wait_vblan= k(). > = > Yeah that name is just transferred from the i915 driver. What about > drm_wait_one_vblank()/drm_crtc_wait_one_vblank()? I don't care that much :), go ahead. -- = Earthling Michel D=E4nzer | http://www.amd.com Libre software enthusiast | Mesa and X developer