mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Oleksandr Andrushchenko <andr2000@gmail.com>
To: konrad.wilk@oracle.com, tiwai@suse.de
Cc: xen-devel@lists.xenproject.org, linux-kernel@vger.kernel.org,
	alsa-devel@alsa-project.org, boris.ostrovsky@oracle.com,
	jgross@suse.com,
	"Oleksandr_Andrushchenko@epam.com"
	<Oleksandr_Andrushchenko@epam.com>
Subject: Re: [PATCH 0/5] for-linux/sndif: add explicit back and front synchronization
Date: Thu, 12 Apr 2018 19:11:15 +0300	[thread overview]
Message-ID: <d5ede3f5-200e-f1c7-71f4-4ebfb938ca48@gmail.com> (raw)
In-Reply-To: <20180412160102.15833-1-oleksandr_andrushchenko@epam.com>

Hello, Konrad, Takashi!

Could you please review the *Linux Kernel* version of the changes?
As I said in the cover letter below there is no functional changes
comparing to the corresponding Xen version, but spaces to tabs.
Still, formally, I have to drop the R-b tags and request for the new review.

Thank you,
Oleksandr

P.S. Minus GlobalLogic e-mails which bounce

On 04/12/2018 07:00 PM, Oleksandr Andrushchenko wrote:
> Hello, all!
>
> This is the syncup version of the sound protocol changes for
> Linux Kernel with the only difference from the corresponding Xen
> version being spaces to tabs conversion. Regradless of this only
> change I have dropped R-b tags received for Xen version.
>
> 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
>   - add XENSND_OP_HW_PARAM_QUERY request to read/update
>     stream configuration space: request passes desired intervals/formats for
>     the stream parameters and the response returns allowed intervals and
>     formats mask that can be used.
>   - MAJOR: changed req/resp/evt packet sizes from 32 to 64 octets
>   -  Reworked XENSND_OP_HW_PARAM_QUERY so it now sends all
>     parameters at once, allowing to check all the configuration
>     space.
>   - Minor documentation cleanup (added missed "reserved" fields)
>
> Oleksandr Andrushchenko (5):
>    xen/sndif: Introduce protocol version
>    xen/sndif: Fix missed "reserved" fields in comments
>    xen/sndif: Make requests and responses 64 octets long
>    xen/sndif: Add explicit back and front synchronization
>    xen/sndif: Add explicit back and front parameter negotiation
>
>   include/xen/interface/io/sndif.h | 322 +++++++++++++++++++++++++++++--
>   1 file changed, 306 insertions(+), 16 deletions(-)
>

  parent reply	other threads:[~2018-04-12 16:11 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-04-12 16:00 Oleksandr Andrushchenko
2018-04-12 16:00 ` [PATCH 1/5] xen/sndif: Introduce protocol version Oleksandr Andrushchenko
2018-04-12 16:00 ` [PATCH 2/5] xen/sndif: Fix missed "reserved" fields in comments Oleksandr Andrushchenko
2018-04-12 16:01 ` [PATCH 3/5] xen/sndif: Make requests and responses 64 octets long Oleksandr Andrushchenko
2018-04-12 16:01 ` [PATCH 4/5] xen/sndif: Add explicit back and front synchronization Oleksandr Andrushchenko
2018-04-12 16:01 ` [PATCH 5/5] xen/sndif: Add explicit back and front parameter negotiation Oleksandr Andrushchenko
2018-04-12 16:11 ` Oleksandr Andrushchenko [this message]
2018-04-12 16:55   ` [PATCH 0/5] for-linux/sndif: add explicit back and front synchronization Boris Ostrovsky
2018-04-12 16:55     ` Oleksandr Andrushchenko
2018-04-12 17:13       ` Boris Ostrovsky
2018-04-12 17:13         ` 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=d5ede3f5-200e-f1c7-71f4-4ebfb938ca48@gmail.com \
    --to=andr2000@gmail.com \
    --cc=Oleksandr_Andrushchenko@epam.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=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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox

all inboxes | Powered by JetHome®