At Tue, 9 Dec 2014 11:19:34 +0100, Daniel Vetter wrote: > > On Tue, Dec 09, 2014 at 11:41:18AM +0200, Imre Deak wrote: > > Register a component master to be used to interface with the i915 > > driver. This is meant to replace the current interface which is based on > > module symbol lookups. > > > > Note that currently we keep the existing behavior and pin the i915 > > module while the hda driver is loaded. Using the component interface > > allows us to remove this dependency once support for dynamically > > enabling / disabling the HDMI functionality is added to the driver. > > > > v2: > > - change roles between the hda and i915 components (Daniel) > > > > Signed-off-by: Imre Deak <imre.deak@xxxxxxxxx> > > Ok, I think this is a good foundation to build on and later on add more > pieces to fix suspend/resume and similar. > > But we also need to discuss how to merge this. My proposal is that I do a > special topic branch with just the patches in this series and then pull > that into drm-intel-next and send a pull request for it to Takashi for > sound-next, too. That way we don't have any depencies between drm and > sound for the 3.20 merge window. > > Testing by intel QA is also solved this way since sound-next is already > pulled into drm-intel-nightly. And both gfx and sound QA use that branch. > > Takashi/Dave, does this sound good? Yes, this sounds good. Maybe it'd be good to base the branch on 3.19-rc1 so that all changes are covered? Takashi _______________________________________________ Intel-gfx mailing list Intel-gfx@xxxxxxxxxxxxxxxxxxxxx http://lists.freedesktop.org/mailman/listinfo/intel-gfx
