All of lore.kernel.org
 help / color / mirror / Atom feed
From: pl bossart <bossart.nospam@gmail.com>
To: Liam Girdwood <lrg@slimlogic.co.uk>
Cc: ALSA development <alsa-devel@alsa-project.org>,
	Mark Brown <broonie@opensource.wolfsonmicro.com>
Subject: Re: UCM questions
Date: Tue, 25 Jan 2011 13:58:19 -0800	[thread overview]
Message-ID: <AANLkTim8=jOV8toPMbeFTC+JMEKYXJ7TJEq1RxC24GMx@mail.gmail.com> (raw)
In-Reply-To: <1295957605.3322.89.camel@odin>

>> Most of my questions are not really on the abstraction but really on
>> how to handle devices that can be plugged or may not be active at all
>> times. USB, HDMI, Wireless/remote displays fall in this category. So
>> on top of the traditional local headset/speakers, I can either have a
>> variety of devices that can be used for the same use case. It's still
>> not clear to me if I would need to create a set of new verbs
>> (hifi_usb, hifi_hdmi) or if I can stick to the existing verbs and add
>> a modifier?
>
> You should stick to the existing verb and use a new device in most cases
> above where your use case is the same but the output device is
> different.

ok, thanks for clarifying.

      reply	other threads:[~2011-01-25 21:58 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-01-20 22:06 UCM questions pl bossart
2011-01-21 11:37 ` Mark Brown
2011-01-21 15:12   ` pl bossart
2011-01-21 16:43     ` Mark Brown
2011-01-21 20:53       ` pl bossart
2011-01-21 23:37         ` Liam Girdwood
2011-01-22  5:22           ` Raymond Yau
2011-01-23  0:41         ` Mark Brown
2011-01-23 13:49         ` Jaroslav Kysela
2011-01-21 15:24   ` Liam Girdwood
2011-01-21 21:03     ` pl bossart
2011-01-21 23:37       ` Liam Girdwood
2011-01-23 13:39       ` Jaroslav Kysela
2011-01-24 22:31         ` pl bossart
2011-01-25 12:13           ` Liam Girdwood
2011-01-25 21:58             ` pl bossart [this message]

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='AANLkTim8=jOV8toPMbeFTC+JMEKYXJ7TJEq1RxC24GMx@mail.gmail.com' \
    --to=bossart.nospam@gmail.com \
    --cc=alsa-devel@alsa-project.org \
    --cc=broonie@opensource.wolfsonmicro.com \
    --cc=lrg@slimlogic.co.uk \
    /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.