All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jaroslav Kysela <perex@perex.cz>
To: Oleksandr Dmytryshyn <oleksandr.dmytryshyn@globallogic.com>,
	xen-devel@lists.xen.org
Cc: Takashi Iwai <tiwai@suse.de>,
	Iurii Konovalenko <iurii.konovalenko@globallogic.com>
Subject: Re: [PATCH v2 1/2] xen-sndfront: add sound frontend driver
Date: Wed, 21 Jan 2015 16:39:06 +0100	[thread overview]
Message-ID: <54BFC81A.1000102@perex.cz> (raw)
In-Reply-To: <1421744640-22106-2-git-send-email-oleksandr.dmytryshyn@globallogic.com>

Dne 20.1.2015 v 10:03 Oleksandr Dmytryshyn napsal(a):
> This is Para-virtual sound driver.
> 
> Frontend driver registers an virtual sound card
> and sends an PCM streams to the backend driver.
> Backend driver is an user-space application and
> uses ALSA with dmix plugin to play audio.
> 
> Signed-off-by: Oleksandr Dmytryshyn <oleksandr.dmytryshyn@globallogic.com>
> Signed-off-by: Iurii Konovalenko <iurii.konovalenko@globallogic.com>

> +static struct snd_kcontrol_new snd_virtualcard_controls[] = {
> +VIRTUALCARD_VOLUME("Master Out Volume", 0, MIXER_ADDR_MASTER_OUT),
> +VIRTUALCARD_CAPSRC("Master Out Switch", 0, MIXER_ADDR_MASTER_OUT),
> +VIRTUALCARD_VOLUME("Master In Volume", 0, MIXER_ADDR_MASTER_IN),
> +VIRTUALCARD_CAPSRC("Master In Switch", 0, MIXER_ADDR_MASTER_IN),

Master In / Out ? Why ? I does not follow the standard naming.

I would prefer 'PCM' and 'PCM Input' or so...

					Jaroslav

-- 
Jaroslav Kysela <perex@perex.cz>
Linux Kernel Sound Maintainer
ALSA Project; Red Hat, Inc.

  reply	other threads:[~2015-01-21 15:39 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-01-20  9:03 [PATCH v2 0/2] Add sound frontend driver Oleksandr Dmytryshyn
2015-01-20  9:03 ` [PATCH v2 1/2] xen-sndfront: add " Oleksandr Dmytryshyn
2015-01-21 15:39   ` Jaroslav Kysela [this message]
2015-01-22 10:24     ` Oleksandr Dmytryshyn
2015-01-20  9:04 ` [PATCH v2 2/2] xen-sndfront: add capture support Oleksandr Dmytryshyn

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=54BFC81A.1000102@perex.cz \
    --to=perex@perex.cz \
    --cc=iurii.konovalenko@globallogic.com \
    --cc=oleksandr.dmytryshyn@globallogic.com \
    --cc=tiwai@suse.de \
    --cc=xen-devel@lists.xen.org \
    /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.