All of lore.kernel.org
 help / color / mirror / Atom feed
From: Oleksandr Andrushchenko <andr2000@gmail.com>
To: alsa-devel@alsa-project.org, xen-devel@lists.xenproject.org,
	konrad.wilk@oracle.com, tiwai@suse.de
Cc: andr2000@gmail.com,
	Oleksandr Andrushchenko <oleksandr_andrushchenko@epam.com>
Subject: [Xen-devel][PATCH v2 0/3] sndif: add explicit back and front synchronization
Date: Wed, 14 Mar 2018 18:02:42 +0200	[thread overview]
Message-ID: <1521043365-26813-1-git-send-email-andr2000@gmail.com> (raw)

From: Oleksandr Andrushchenko <oleksandr_andrushchenko@epam.com>

Hello, all!

In order to provide explicit synchronization between backend and
frontend the following changes are introduced in the protocol:
 - bump protocol version to 2
 - add new ring buffer for sending asynchronous events from
   backend to frontend to report number of bytes played by the
   frontend (XENSND_EVT_CUR_POS)
 - introduce trigger events for playback control: start/stop/pause/resume
 - add "req-" prefix to event-channel and ring-ref to unify naming
   of the Xen event channels for requests and events


Changes since v1:

1. Changed protocol version definition from string to integer,
so it can easily be used in comparisons.
Konrad, I have removed your r-b tag for the reason of this change.

2. In order to provide explicit stream parameter negotiation between
backend and frontend the following changes are introduced in the protocol:
add XENSND_OP_HW_PARAM_QUERY request to read/update
configuration space for the parameter given: request passes
desired parameter interval (mask) and the response to this request
returns min/max interval (mask) for the parameter to be used.

Parameters supported by this request/response:
 - format mask
 - sample rate interval
 - number of channels interval
 - buffer size, interval, frames
 - period size, interval, frames

Thank you,
Oleksandr Andrushchenko

Oleksandr Andrushchenko (3):
  sndif: Introduce protocol version
  sndif: Add explicit back and front synchronization
  sndif: Add explicit back and front parameter negotiation

 xen/include/public/io/sndif.h | 295 ++++++++++++++++++++++++++++++++++++++++--
 1 file changed, 286 insertions(+), 9 deletions(-)

-- 
2.7.4

             reply	other threads:[~2018-03-14 16:02 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-03-14 16:02 Oleksandr Andrushchenko [this message]
2018-03-14 16:02 ` [Xen-devel][PATCH v2 1/3] sndif: Introduce protocol version Oleksandr Andrushchenko
2018-03-15 20:14   ` [PATCH " Konrad Rzeszutek Wilk
2018-03-15 20:14   ` [Xen-devel][PATCH " Konrad Rzeszutek Wilk
2018-03-14 16:02 ` [PATCH " Oleksandr Andrushchenko
2018-03-14 16:02 ` [PATCH v2 2/3] sndif: Add explicit back and front synchronization Oleksandr Andrushchenko
2018-03-14 16:02 ` [Xen-devel][PATCH " Oleksandr Andrushchenko
2018-03-15 20:17   ` Konrad Rzeszutek Wilk
2018-03-16  6:24     ` Oleksandr Andrushchenko
2018-03-16  6:24     ` [PATCH " Oleksandr Andrushchenko
2018-03-15 20:17   ` Konrad Rzeszutek Wilk
2018-03-14 16:02 ` [PATCH v2 3/3] sndif: Add explicit back and front parameter negotiation Oleksandr Andrushchenko
2018-03-14 16:02 ` [Xen-devel][PATCH " 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=1521043365-26813-1-git-send-email-andr2000@gmail.com \
    --to=andr2000@gmail.com \
    --cc=alsa-devel@alsa-project.org \
    --cc=konrad.wilk@oracle.com \
    --cc=oleksandr_andrushchenko@epam.com \
    --cc=tiwai@suse.de \
    --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 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.