From mboxrd@z Thu Jan 1 00:00:00 1970 From: Jaroslav Kysela Subject: Re: [RFC] Channel mapping API Date: Tue, 21 Aug 2012 14:31:55 +0200 Message-ID: <50337FBB.4020709@perex.cz> References: <50337316.4080208@ladisch.de> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Return-path: Received: from mail1.perex.cz (mail1.perex.cz [77.48.224.245]) by alsa0.perex.cz (Postfix) with ESMTP id 0BE4C265F42 for ; Tue, 21 Aug 2012 14:29:25 +0200 (CEST) In-Reply-To: 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: alsa-devel@alsa-project.org Cc: Takashi Iwai List-Id: alsa-devel@alsa-project.org Date 21.8.2012 14:15, Takashi Iwai wrote: > For getting the channel map, the driver could send a notification once > when routing is changed. This leads to this question: Why you define the map controls volatile? I think that the channel map changes can be tracked nicely using the standard control event notifications without any hidden changes. Perhaps, the value change event may be invoked each time after prepare and when the user space set the new values and also in above situation, when the channel map is changed on an external request. Jaroslav -- Jaroslav Kysela Linux Kernel Sound Maintainer ALSA Project; Red Hat, Inc.