On Thu, Oct 11, 2012 at 3:19 PM, Rob Clark <robdclark@xxxxxxxxx> wrote: >> Should the documenation be updated to mark those functions as deprecated for >> new drivers and explain how to handle IRQ (un)registration manually ? They're not deprecated, since for most drivers they're good enough. Maybe just make it clear that they're optional (and whoever's the first might need to do some refactoring to make things simpler for fancy irq handling). > It might be nice to provide the driver an option to give it's own > install/uninstall irq fxn ptrs.. this way we can keep > drm_irq_install/uninstall(). In particular, the uninstall fxn still > does some useful cleanup like wake up anyone waiting for vblank events > which would still be needed by drivers registering irq in their own > special way. And the irq pre/post-install stuff is still a bit nice > to keep. If a driver needs its own irq setup/teardown magic, I'd prefer if we simply extract the useful parts of the common code into a little helper that drivers can call, and don't add new&fancy callbacks and interface. At least not without really good reasons. /me has seen enough midlayer awesomeness in drm land already Cheers, Daniel -- Daniel Vetter Software Engineer, Intel Corporation +41 (0) 79 365 57 48 - http://blog.ffwll.ch _______________________________________________ dri-devel mailing list dri-devel@xxxxxxxxxxxxxxxxxxxxx http://lists.freedesktop.org/mailman/listinfo/dri-devel
