From: Oleksandr Andrushchenko <andr2000@gmail.com>
To: Juergen Gross <jgross@suse.com>,
xen-devel@lists.xenproject.org, linux-kernel@vger.kernel.org,
alsa-devel@alsa-project.org, boris.ostrovsky@oracle.com,
konrad.wilk@oracle.com, perex@perex.cz, tiwai@suse.com
Cc: Oleksandr Andrushchenko <oleksandr_andrushchenko@epam.com>
Subject: Re: [PATCH v2 1/5] ALSA: xen-front: Introduce Xen para-virtualized sound frontend driver
Date: Tue, 17 Apr 2018 11:24:56 +0300 [thread overview]
Message-ID: <ea707fd4-fb72-aa8a-f5ac-dd9ff89dea9b@gmail.com> (raw)
In-Reply-To: <c473b7b3-6125-7f2f-d3c2-bff58dc61d48@suse.com>
On 04/16/2018 03:25 PM, Juergen Gross wrote:
> On 16/04/18 08:24, Oleksandr Andrushchenko wrote:
>> From: Oleksandr Andrushchenko <oleksandr_andrushchenko@epam.com>
>>
>> Introduce skeleton of the para-virtualized Xen sound
>> frontend driver.
>>
>> Initial handling for Xen bus states: implement
>> Xen bus state machine for the frontend driver according to
>> the state diagram and recovery flow from sound para-virtualized
>> protocol: xen/interface/io/sndif.h.
>>
>> Signed-off-by: Oleksandr Andrushchenko <oleksandr_andrushchenko@epam.com>
> Only one minor nit (see below). With that addressed (or fixed when
> committing):
will fix
> Reviewed-by: Juergen Gross <jgross@suse.com>
Thank you
>
> Juergen
>
>> ---
>> sound/Kconfig | 2 +
>> sound/Makefile | 2 +-
>> sound/xen/Kconfig | 10 +++
>> sound/xen/Makefile | 5 ++
>> sound/xen/xen_snd_front.c | 196 ++++++++++++++++++++++++++++++++++++++++++++++
>> sound/xen/xen_snd_front.h | 18 +++++
>> 6 files changed, 232 insertions(+), 1 deletion(-)
>> create mode 100644 sound/xen/Kconfig
>> create mode 100644 sound/xen/Makefile
>> create mode 100644 sound/xen/xen_snd_front.c
>> create mode 100644 sound/xen/xen_snd_front.h
>>
>> diff --git a/sound/xen/xen_snd_front.c b/sound/xen/xen_snd_front.c
>> new file mode 100644
>> index 000000000000..f406a8f52c51
>> --- /dev/null
>> +++ b/sound/xen/xen_snd_front.c
>> @@ -0,0 +1,196 @@
>> +static void sndback_changed(struct xenbus_device *xb_dev,
>> + enum xenbus_state backend_state)
>> +{
>> + struct xen_snd_front_info *front_info = dev_get_drvdata(&xb_dev->dev);
>> + int ret;
>> +
>> + dev_dbg(&xb_dev->dev, "Backend state is %s, front is %s\n",
>> + xenbus_strstate(backend_state),
>> + xenbus_strstate(xb_dev->state));
>> +
>> + switch (backend_state) {
>> + case XenbusStateReconfiguring:
>> + /* fall through */
>> + case XenbusStateReconfigured:
>> + /* fall through */
>> + case XenbusStateInitialised:
>> + /* fall through */
>> + break;
>> +
>> + case XenbusStateInitialising:
>> + /* recovering after backend unexpected closure */
>> + sndback_disconnect(front_info);
>> + break;
>> +
>> + case XenbusStateInitWait:
>> + /* recovering after backend unexpected closure */
>> + sndback_disconnect(front_info);
>> +
>> + ret = sndback_initwait(front_info);
>> + if (ret < 0)
>> + xenbus_dev_fatal(xb_dev, ret, "initializing frontend");
>> + else
>> + xenbus_switch_state(xb_dev, XenbusStateInitialised);
>> + break;
>> +
>> + case XenbusStateConnected:
>> + if (xb_dev->state != XenbusStateInitialised)
>> + break;
>> +
>> + ret = sndback_connect(front_info);
>> + if (ret < 0)
>> + xenbus_dev_fatal(xb_dev, ret, "initializing frontend");
>> + else
>> + xenbus_switch_state(xb_dev, XenbusStateConnected);
>> + break;
>> +
>> + case XenbusStateClosing:
>> + /*
>> + * in this state backend starts freeing resources,
>> + * so let it go into closed state first, so we can also
>> + * remove ours
>> + */
> Please start the sentence with a capital letter and end it with a
> full stop.
>
>
> Juergen
next prev parent reply other threads:[~2018-04-17 8:24 UTC|newest]
Thread overview: 40+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-04-16 6:24 [PATCH v2 0/5] ALSA: xen-front: Add Xen para-virtualized frontend driver Oleksandr Andrushchenko
2018-04-16 6:24 ` [PATCH v2 1/5] ALSA: xen-front: Introduce Xen para-virtualized sound " Oleksandr Andrushchenko
2018-04-16 12:25 ` Juergen Gross
2018-04-17 8:24 ` Oleksandr Andrushchenko [this message]
2018-04-24 13:55 ` Takashi Iwai
2018-04-24 13:59 ` Oleksandr Andrushchenko
2018-04-16 6:24 ` [PATCH v2 2/5] ALSA: xen-front: Read sound driver configuration from Xen store Oleksandr Andrushchenko
2018-04-16 12:55 ` Juergen Gross
2018-04-17 8:42 ` Oleksandr Andrushchenko
2018-04-17 11:08 ` Juergen Gross
2018-04-16 6:24 ` [PATCH v2 3/5] ALSA: xen-front: Implement Xen event channel handling Oleksandr Andrushchenko
2018-04-16 13:12 ` Juergen Gross
2018-04-17 8:58 ` Oleksandr Andrushchenko
2018-04-17 11:14 ` Juergen Gross
2018-04-17 11:21 ` Oleksandr Andrushchenko
2018-04-16 13:53 ` kbuild test robot
2018-04-24 14:20 ` Takashi Iwai
2018-04-24 14:29 ` Oleksandr Andrushchenko
2018-04-24 14:35 ` Takashi Iwai
2018-04-24 14:58 ` Oleksandr Andrushchenko
2018-04-24 15:02 ` Takashi Iwai
2018-04-24 16:23 ` Oleksandr Andrushchenko
2018-04-25 8:26 ` Oleksandr Andrushchenko
2018-04-25 9:02 ` Takashi Iwai
2018-04-25 9:04 ` Oleksandr Andrushchenko
2018-04-16 6:24 ` [PATCH v2 4/5] ALSA: xen-front: Implement handling of shared buffers Oleksandr Andrushchenko
2018-04-16 13:39 ` Juergen Gross
2018-04-17 9:22 ` Oleksandr Andrushchenko
2018-04-17 11:15 ` Juergen Gross
2018-04-16 6:24 ` [PATCH v2 5/5] ALSA: xen-front: Implement ALSA virtual sound driver Oleksandr Andrushchenko
2018-04-16 14:09 ` Juergen Gross
2018-04-17 11:32 ` Oleksandr Andrushchenko
2018-04-17 12:26 ` Oleksandr Andrushchenko
2018-04-17 12:32 ` Juergen Gross
2018-04-17 12:34 ` Oleksandr Andrushchenko
2018-04-16 14:59 ` kbuild test robot
2018-04-17 12:42 ` [PATCH v2 0/5] ALSA: xen-front: Add Xen para-virtualized frontend driver Oleksandr Andrushchenko
2018-04-18 15:15 ` Oleksandr Andrushchenko
2018-04-23 6:34 ` Oleksandr Andrushchenko
2018-05-02 7:59 ` 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=ea707fd4-fb72-aa8a-f5ac-dd9ff89dea9b@gmail.com \
--to=andr2000@gmail.com \
--cc=alsa-devel@alsa-project.org \
--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=tiwai@suse.com \
--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;
as well as URLs for NNTP newsgroup(s).