From mboxrd@z Thu Jan 1 00:00:00 1970 From: Liam Girdwood Subject: Re: [PATCH] ASoC: dapm: Add speaker driver widget. Date: Tue, 07 Dec 2010 12:46:28 +0000 Message-ID: <1291725988.3275.22.camel@odin> References: <1889FA7136B567478A67D4B0F85B0CCEA4C52E7E@dlee06.ent.ti.com> <20101206224359.GB2862@opensource.wolfsonmicro.com> <1291676132.3281.116.camel@odin> <20101206230948.GH2862@opensource.wolfsonmicro.com> <1291678207.3281.152.camel@odin> <8C6859A9-36EF-4016-822B-DA67D7147E28@opensource.wolfsonmicro.com> <1291725285.3275.14.camel@odin> <20101207123600.GD4698@rakim.wolfsonmicro.main> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Return-path: Received: from mail-ww0-f51.google.com (mail-ww0-f51.google.com [74.125.82.51]) by alsa0.perex.cz (Postfix) with ESMTP id 55630103838 for ; Tue, 7 Dec 2010 13:46:31 +0100 (CET) Received: by wwe15 with SMTP id 15so903564wwe.20 for ; Tue, 07 Dec 2010 04:46:31 -0800 (PST) In-Reply-To: <20101207123600.GD4698@rakim.wolfsonmicro.main> List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: alsa-devel-bounces@alsa-project.org Errors-To: alsa-devel-bounces@alsa-project.org To: Mark Brown Cc: "Olaya, Margarita" , "alsa-devel@alsa-project.org" List-Id: alsa-devel@alsa-project.org On Tue, 2010-12-07 at 12:36 +0000, Mark Brown wrote: > On Tue, Dec 07, 2010 at 12:34:45PM +0000, Liam Girdwood wrote: > > On Mon, 2010-12-06 at 23:38 +0000, Mark Brown wrote: > > > > ...we don't need to change the ordering at all, we've already got a > > > sequence point for this sort of widget we can use. We should just make > > > the existing speaker and headphone widgets be in terms of one, I think. > > > The only minor problem here is that the current sequence point is name > > "snd_soc_dapm_spk" which would seem confusing to haptic/vibra driver > > users. Although, I can live with this.... > > I meant the number in the sequence - the patch had the new widget coming > up in the slot before the existing output driver widgets. Ok, but by sharing the number we take away some flexibility in the sequence ordering. Say something has to be done in the machine driver _after_ the spk/haptic/vibra driver is enabled in the CODEC driver ? I dont actually see any major issue of using a new number here unless you have it reserved for something else ? Liam -- Freelance Developer, SlimLogic Ltd ASoC and Voltage Regulator Maintainer. http://www.slimlogic.co.uk