On Mon, 2018-03-19 at 22:24 +0200, Tanu Kaskinen wrote:
> On Fri, 2018-03-16 at 20:04 +0100, Georg Chini wrote:
> > On 16.03.2018 19:26, Tanu Kaskinen wrote:
> > > On Fri, 2018-03-16 at 11:15 +0100, Georg Chini wrote:
> > > > On 13.03.2018 18:40, Tanu Kaskinen wrote:
> > > > > The suspend cause isn
On Fri, 2018-03-16 at 20:04 +0100, Georg Chini wrote:
> On 16.03.2018 19:26, Tanu Kaskinen wrote:
> > On Fri, 2018-03-16 at 11:15 +0100, Georg Chini wrote:
> > > On 13.03.2018 18:40, Tanu Kaskinen wrote:
> > > > The suspend cause isn't yet used by any of the callbacks. The alsa sink
> > > > and sou
On 16.03.2018 19:26, Tanu Kaskinen wrote:
On Fri, 2018-03-16 at 11:15 +0100, Georg Chini wrote:
On 13.03.2018 18:40, Tanu Kaskinen wrote:
The suspend cause isn't yet used by any of the callbacks. The alsa sink
and source will use it to sync the mixer when the SESSION suspend cause
is removed. C
On Fri, 2018-03-16 at 11:15 +0100, Georg Chini wrote:
> On 13.03.2018 18:40, Tanu Kaskinen wrote:
> > The suspend cause isn't yet used by any of the callbacks. The alsa sink
> > and source will use it to sync the mixer when the SESSION suspend cause
> > is removed. Currently the syncing is done in
On 13.03.2018 18:40, Tanu Kaskinen wrote:
The suspend cause isn't yet used by any of the callbacks. The alsa sink
and source will use it to sync the mixer when the SESSION suspend cause
is removed. Currently the syncing is done in pa_sink/source_suspend(),
and I want to change that, because pa_si
The suspend cause isn't yet used by any of the callbacks. The alsa sink
and source will use it to sync the mixer when the SESSION suspend cause
is removed. Currently the syncing is done in pa_sink/source_suspend(),
and I want to change that, because pa_sink/source_suspend() shouldn't
have any alsa
