All of lore.kernel.org
 help / color / mirror / Atom feed
From: Mark Brown <broonie@opensource.wolfsonmicro.com>
To: Liam Girdwood <lrg@slimlogic.co.uk>
Cc: "Olaya, Margarita" <magi.olaya@ti.com>,
	"alsa-devel@alsa-project.org" <alsa-devel@alsa-project.org>
Subject: Re: [PATCH] ASoC: dapm: Add speaker driver widget.
Date: Tue, 7 Dec 2010 13:09:15 +0000	[thread overview]
Message-ID: <20101207130914.GF4698@rakim.wolfsonmicro.main> (raw)
In-Reply-To: <1291725988.3275.22.camel@odin>

On Tue, Dec 07, 2010 at 12:46:28PM +0000, Liam Girdwood wrote:

> 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 ?

You can say that for pretty much all of the widgets, though, including
the existing speaker and headphone widgets.  I'd be a bit surprised if
you had anything afterwards in this case, a driver is generally the high
power stage wired directly to the transducer.

> I dont actually see any major issue of using a new number here unless
> you have it reserved for something else ?

Adding a new number and renumbering all the subsequent ones wouldn't be
so bad, the patch wasn't doing that.

  reply	other threads:[~2010-12-07 13:09 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-12-06 22:34 [PATCH] ASoC: dapm: Add speaker driver widget Olaya, Margarita
2010-12-06 22:43 ` Mark Brown
2010-12-06 22:55   ` Liam Girdwood
2010-12-06 23:09     ` Mark Brown
2010-12-06 23:30       ` Liam Girdwood
2010-12-06 23:38         ` Mark Brown
2010-12-07 12:34           ` Liam Girdwood
2010-12-07 12:36             ` Mark Brown
2010-12-07 12:46               ` Liam Girdwood
2010-12-07 13:09                 ` Mark Brown [this message]
2010-12-07 14:01                   ` Liam Girdwood
2010-12-07 14:13                     ` Mark Brown

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20101207130914.GF4698@rakim.wolfsonmicro.main \
    --to=broonie@opensource.wolfsonmicro.com \
    --cc=alsa-devel@alsa-project.org \
    --cc=lrg@slimlogic.co.uk \
    --cc=magi.olaya@ti.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.