From: Takashi Iwai Subject: Re: Use of snd_atomic_write_t for dshare and friends Date: Tue, 08 Nov 2016 15:40:10 +0100 Message-ID: References: <58209DD9.8060905@IEE.org> Mime-Version: 1.0 (generated by SEMI 1.14.6 - "Maruoka") Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Return-path: Received: from mx2.suse.de (mx2.suse.de [195.135.220.15]) by alsa0.perex.cz (Postfix) with ESMTP id 9DB1A265119 for ; Tue, 8 Nov 2016 15:40:11 +0100 (CET) In-Reply-To: <58209DD9.8060905@IEE.org> List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: alsa-devel-bounces@alsa-project.org Sender: alsa-devel-bounces@alsa-project.org To: Alan Young Cc: alsa-devel@alsa-project.org List-Id: alsa-devel@alsa-project.org On Mon, 07 Nov 2016 16:29:29 +0100, Alan Young wrote: > > Would it make sense for dshare, and other d-* plugins, to use a shared > snd_atomic_write_t in the shared memory segment and associated > snd_atomic_write_xxx() & snd_atomic_read_xxx() calls? It's not recommended and not expected to work well always with DMA buffer. And above all, these calls were dropped in the recent alsa-lib. Takashi