[alsa-devel] move snd-aloop to the alsa-kernel tree?

[Takashi Iwai]

At Mon, 9 Aug 2010 15:10:13 +0200 (CEST),
Jaroslav Kysela wrote:
> 
> On Mon, 9 Aug 2010, Takashi Iwai wrote:
> 
> > At Mon, 9 Aug 2010 13:50:37 +0200 (CEST),
> > Jaroslav Kysela wrote:
> >>
> >> On Mon, 9 Aug 2010, Takashi Iwai wrote:
> >>
> >>> At Mon, 9 Aug 2010 09:17:10 +0200 (CEST),
> >>> Jaroslav Kysela wrote:
> >>>>
> >>>> Hi all,
> >>>>
> >>>>  	does anyone have any objection to move the loop module (snd-aloop)
> >>>> from the alsa-driver tree to the alsa-kernel tree (Linux 2.6 tree)?
> >>>>  	I worked on these things last days:
> >>>>
> >>>> - fixed timing issues (we cannot use the identical period
> >>>>    timing for both playback/capture - it also means that the capture and
> >>>>    playback buffer setup might be different)
> >>>> - added proper buffer silencing when the playback is in the draining phase
> >>>> - added stream parameters change notification (stop the capture stream
> >>>>    when the playback stream parameters were changed)
> >>>> - added controls to propagate the playback stream parameters to the
> >>>>    user space with the notification of changes
> >>>> - added simple time shift functionality to compensate the time drift for
> >>>>    another clock source
> >>>
> >>> Sounds good.  But, let's merge it into 2.6.37.
> >>
> >> I don't see any reason to wait with merging of this pretty generic driver
> >> while 2.6.36-rc1 is not released, but I'm not in a hurry :-)
> >
> > As a generic rule, all new features to be merged should have appeared
> > in linux-next (i.e. also mm tree) before the merge window opened.
> 
> OK, I put the snd-aloop driver to my devel git tree and removed the code 
> from the alsa-driver git tree (with the new pm_qos_request updates).

Thanks.  I'll pull it and keep in the master branch.  After the merge
window is closed, it'll be again merged to linux-next for the next
kernel.


Takashi