From: Oleksandr Andrushchenko <andr2000@gmail.com>
To: xen-devel@lists.xenproject.org, konrad.wilk@oracle.com, jgross@suse.com
Cc: andr2000@gmail.com,
Oleksandr Andrushchenko <oleksandr_andrushchenko@epam.com>
Subject: [PATCH v2 4/4] xen/sndif: Change stream's unique-id to string
Date: Fri, 8 Jun 2018 09:08:31 +0300 [thread overview]
Message-ID: <20180608060831.20194-5-andr2000@gmail.com> (raw)
In-Reply-To: <20180608060831.20194-1-andr2000@gmail.com>
From: Oleksandr Andrushchenko <oleksandr_andrushchenko@epam.com>
Display and input protocols define "unique-id" XenBus field as string
which is much more flexible in defining unique identifiers comparing
to integer used by sound protocol. For example, this allows to provide
UUIDs as unique ID's. Align sound protocol with display and input
and redefine "unique-id" field as string.
Signed-off-by: Oleksandr Andrushchenko <oleksandr_andrushchenko@epam.com>
Reviewed-by: Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>
---
xen/include/public/io/sndif.h | 10 ++++------
1 file changed, 4 insertions(+), 6 deletions(-)
diff --git a/xen/include/public/io/sndif.h b/xen/include/public/io/sndif.h
index 417d3ebc7981..402033cf4946 100644
--- a/xen/include/public/io/sndif.h
+++ b/xen/include/public/io/sndif.h
@@ -278,13 +278,11 @@
* defined under the same device.
*
* unique-id
- * Values: <uint32_t>
+ * Values: <string>
*
- * After stream initialization it is assigned a unique ID (within the front
- * driver), so every stream of the frontend can be identified by the
- * backend by this ID. This is not equal to stream-idx as the later is
- * zero based within the device, but this index is contigous within the
- * driver.
+ * After stream initialization it is assigned a unique ID, so every
+ * stream of the frontend can be identified by the backend by this ID.
+ * This can be UUID or such.
*
*-------------------- Stream Request Transport Parameters --------------------
*
--
2.17.1
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xenproject.org
https://lists.xenproject.org/mailman/listinfo/xen-devel
next prev parent reply other threads:[~2018-06-08 6:08 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-06-08 6:08 [PATCH v2 0/4] Unique-id and fixes to some protocols Oleksandr Andrushchenko
2018-06-08 6:08 ` [PATCH v2 1/4] xen/kbdif: Move multi-touch device parameters to backend nodes Oleksandr Andrushchenko
2018-06-08 6:08 ` [PATCH v2 2/4] xen/kbdif: Add unique input device identifier Oleksandr Andrushchenko
2018-06-08 12:40 ` Juergen Gross
2018-06-08 6:08 ` [PATCH v2 3/4] xen/displif: Add unique display connector identifier Oleksandr Andrushchenko
2018-06-08 12:41 ` Juergen Gross
2018-06-08 6:08 ` Oleksandr Andrushchenko [this message]
2018-06-08 12:42 ` [PATCH v2 4/4] xen/sndif: Change stream's unique-id to string Juergen Gross
2018-06-08 12:52 ` [PATCH v2 0/4] Unique-id and fixes to some protocols Oleksandr Andrushchenko
2018-06-08 14:58 ` Konrad Rzeszutek Wilk
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=20180608060831.20194-5-andr2000@gmail.com \
--to=andr2000@gmail.com \
--cc=jgross@suse.com \
--cc=konrad.wilk@oracle.com \
--cc=oleksandr_andrushchenko@epam.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 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.