From: Takashi Iwai <tiwai@suse.de>
To: Oleksandr Andrushchenko <andr2000@gmail.com>
Cc: xen-devel@lists.xenproject.org, linux-kernel@vger.kernel.org,
alsa-devel@alsa-project.org, jgross@suse.com,
boris.ostrovsky@oracle.com, konrad.wilk@oracle.com,
perex@perex.cz,
Oleksandr Andrushchenko <oleksandr_andrushchenko@epam.com>
Subject: Re: [alsa-devel] [PATCH v3 0/6] ALSA: xen-front: Add Xen para-virtualized frontend driver
Date: Mon, 14 May 2018 17:52:41 +0200 [thread overview]
Message-ID: <s5hmux2s08m.wl-tiwai@suse.de> (raw)
In-Reply-To: <20180514062742.25879-1-andr2000@gmail.com>
On Mon, 14 May 2018 08:27:36 +0200,
Oleksandr Andrushchenko wrote:
>
> From: Oleksandr Andrushchenko <oleksandr_andrushchenko@epam.com>
>
> Please note: this patch series depends on [3].
>
> This patch series adds support for Xen [1] para-virtualized
> sound frontend driver. It implements the protocol from
> include/xen/interface/io/sndif.h with the following limitations:
> - mute/unmute is not supported
> - get/set volume is not supported
> Volume control is not supported for the reason that most of the
> use-cases (at the moment) are based on scenarious where
> unprivileged OS (e.g. Android, AGL etc) use software mixers.
>
> Both capture and playback are supported.
>
> Corresponding backend, implemented as a user-space application, can be
> found at [2].
Through a quick glance, all look OK for merge (assuming that they
really work on your systems :)
Of course, it'd be great if anyone else can review, test and give
reviewed-by or tested-by tags. So I'll keep this floating for a
couple of days and merge to for-next branch after that.
thanks,
Takashi
next prev parent reply other threads:[~2018-05-14 15:52 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-05-14 6:27 [PATCH v3 0/6] ALSA: xen-front: Add Xen para-virtualized frontend driver Oleksandr Andrushchenko
2018-05-14 6:27 ` [PATCH v3 1/6] ALSA: xen-front: Introduce Xen para-virtualized sound " Oleksandr Andrushchenko
2018-05-14 6:27 ` [PATCH v3 2/6] ALSA: xen-front: Read sound driver configuration from Xen store Oleksandr Andrushchenko
2018-05-14 6:27 ` [PATCH v3 3/6] ALSA: xen-front: Implement Xen event channel handling Oleksandr Andrushchenko
2018-05-14 6:27 ` [PATCH v3 4/6] ALSA: xen-front: Implement handling of shared buffers Oleksandr Andrushchenko
2018-05-14 20:28 ` Takashi Iwai
2018-05-15 5:46 ` Oleksandr Andrushchenko
2018-05-15 6:01 ` Takashi Iwai
2018-05-15 6:02 ` Oleksandr Andrushchenko
2018-05-17 6:26 ` Takashi Iwai
2018-05-17 6:33 ` Oleksandr Andrushchenko
2018-05-21 20:26 ` Takashi Iwai
2018-05-22 5:25 ` Oleksandr Andrushchenko
2018-05-14 6:27 ` [PATCH v3 5/6] ALSA: xen-front: Implement ALSA virtual sound driver Oleksandr Andrushchenko
2018-05-23 4:00 ` Takashi Sakamoto
2018-05-23 6:14 ` Oleksandr Andrushchenko
2018-05-14 6:27 ` [PATCH v3 6/6] MAINTAINERS: Add ALSA: xen-front: maintainer entry Oleksandr Andrushchenko
2018-05-14 15:52 ` Takashi Iwai [this message]
2018-05-14 16:08 ` [alsa-devel] [PATCH v3 0/6] ALSA: xen-front: Add Xen para-virtualized frontend driver Oleksandr Andrushchenko
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=s5hmux2s08m.wl-tiwai@suse.de \
--to=tiwai@suse.de \
--cc=alsa-devel@alsa-project.org \
--cc=andr2000@gmail.com \
--cc=boris.ostrovsky@oracle.com \
--cc=jgross@suse.com \
--cc=konrad.wilk@oracle.com \
--cc=linux-kernel@vger.kernel.org \
--cc=oleksandr_andrushchenko@epam.com \
--cc=perex@perex.cz \
--cc=xen-devel@lists.xenproject.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox