From: Pierre-Louis Bossart Subject: Re: [RFC PATCH] ucm: Add support for device positions Date: Tue, 3 Jan 2017 08:50:54 -0600 Message-ID: <1e49ebdc-38c3-0e51-6674-0fa1aebbb30a@linux.intel.com> References: <1483423758-8986-1-git-send-email-mengdong.lin@linux.intel.com> <20170103082143.GF3573@localhost> <586B7856.6090005@linux.intel.com> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii"; Format="flowed" Content-Transfer-Encoding: 7bit Return-path: Received: from mga03.intel.com (mga03.intel.com [134.134.136.65]) by alsa0.perex.cz (Postfix) with ESMTP id CFD6F266F05 for ; Tue, 3 Jan 2017 15:51:06 +0100 (CET) In-Reply-To: <586B7856.6090005@linux.intel.com> 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: Mengdong Lin , Vinod Koul Cc: alsa-devel@alsa-project.org, tiwai@suse.de, mengdong.lin@intel.com, liam.r.girdwood@linux.intel.com, broonie@kernel.org, pierre-louis.bossart@intel.com List-Id: alsa-devel@alsa-project.org On 01/03/2017 04:09 AM, Mengdong Lin wrote: > > > On 01/03/2017 04:21 PM, Vinod Koul wrote: >> On Tue, Jan 03, 2017 at 02:09:18PM +0800, >> mengdong.lin@linux.intel.com wrote: >>> From: Mengdong Lin >>> >>> Users can provide prosition info of audio devices as a device value. >>> This >>> will help the sound server to choose an audio devices from some >>> candidates >>> based on the their locations and the status of the machine. >> >> This is good thing to have but some bits are bit unclear to me atm. >> When you >> say device, do you mean sound card? > > No, the device here does not mean a sound card, but mean an I/O device > like speaker or dmic, defined by 'SectionDevice'. > >> For me, position makes sense for dmics and speakers. So can you help >> me out >> by understanding how we can describe these... >> > > For example, if there are two DMICs, one is in the front and one on > the back, we can define their positions as below: > > SectionDevice."MainMIC" { > > ... > > EnableSequence [ > ... > ] > > DisableSequence [ > ... > ] > > Value { > Position "Front" > } > } > > SectionDevice."SecondaryMIC" { > > ... > > EnableSequence [ > ... > ] > > DisableSequence [ > ... > ] > > Value { > Position "Back" > } > } What is the entity that will make use of the position information? For what purpose? This type of information needs to be known at a lower level (typically a DSP), I wonder what UCM would do with it? Also it can be tricky to define left and right for a tablet which works in all possible orientations, you'd need sensor information to refine the position. And last if you have a mic or speaker array you'd need to provide geometrical information?