All of lore.kernel.org
 help / color / mirror / Atom feed
From: Oleksandr Andrushchenko <andr2000@gmail.com>
To: xen-devel@lists.xenproject.org, konrad.wilk@oracle.com,
	jgross@suse.com, boris.ostrovsky@oracle.com, mchehab@kernel.org,
	linux-media@vger.kernel.org, sakari.ailus@linux.intel.com,
	koji.matsuoka.xm@renesas.com, hverkuil@xs4all.nl
Cc: Oleksandr Andrushchenko <oleksandr_andrushchenko@epam.com>
Subject: [PATCH v2 0/1] cameraif: add ABI for para-virtual camera
Date: Tue, 11 Sep 2018 11:29:51 +0300	[thread overview]
Message-ID: <20180911082952.23322-1-andr2000@gmail.com> (raw)

From: Oleksandr Andrushchenko <oleksandr_andrushchenko@epam.com>

Hello!

At the moment Xen [1] already supports some virtual multimedia
features [2] such as virtual display, sound. It supports keyboards,
pointers and multi-touch devices all allowing Xen to be used in
automotive appliances, In-Vehicle Infotainment (IVI) systems
and many more.

This work adds a new Xen para-virtualized protocol for a virtual
camera device which extends multimedia capabilities of Xen even
farther: video conferencing, IVI, high definition maps etc.

The initial goal is to support most needed functionality with the
final idea to make it possible to extend the protocol if need be:

1. Provide means for base virtual device configuration:
 - pixel formats
 - resolutions
 - frame rates
2. Support basic camera controls:
 - contrast
 - brightness
 - hue
 - saturation
3. Support streaming control
4. Support zero-copying use-cases

I hope that Xen and V4L and other communities could give their
valuable feedback on this work, so I can update the protocol
to better fit any additional requirements I might have missed.

I would like to thank Hans Verkuil <hverkuil@xs4all.nl> for valuable
comments and help.

Thank you,
Oleksandr Andrushchenko

Changes since v1:
=================

1. Added XenStore entries:
 - frame-rates
2. Do not require the FOURCC code in XenStore to be upper case only
3. Added/changed command set:
 - configuration get/set
 - buffer queue/dequeue
 - control get
4. Added control flags, e.g. read-only etc.
5. Added colorspace configuration support, relevant constants
6. Added events:
 - configuration change
 - control change
7. Changed control values to 64-bit
8. Added sequence number to frame avail event
9. Coding style cleanup

[1] https://www.xenproject.org/
[2] https://xenbits.xen.org/gitweb/?p=xen.git;a=tree;f=xen/include/public/io

Oleksandr Andrushchenko (1):
  cameraif: add ABI for para-virtual camera

 xen/include/public/io/cameraif.h | 1263 ++++++++++++++++++++++++++++++
 1 file changed, 1263 insertions(+)
 create mode 100644 xen/include/public/io/cameraif.h

-- 
2.18.0


_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xenproject.org
https://lists.xenproject.org/mailman/listinfo/xen-devel

WARNING: multiple messages have this Message-ID (diff)
From: Oleksandr Andrushchenko <andr2000@gmail.com>
To: xen-devel@lists.xenproject.org, konrad.wilk@oracle.com,
	jgross@suse.com, boris.ostrovsky@oracle.com, mchehab@kernel.org,
	linux-media@vger.kernel.org, sakari.ailus@linux.intel.com,
	koji.matsuoka.xm@renesas.com, hverkuil@xs4all.nl
Cc: Oleksandr Andrushchenko <oleksandr_andrushchenko@epam.com>
Subject: [Xen-devel][PATCH v2 0/1] cameraif: add ABI for para-virtual camera
Date: Tue, 11 Sep 2018 11:29:51 +0300	[thread overview]
Message-ID: <20180911082952.23322-1-andr2000@gmail.com> (raw)

From: Oleksandr Andrushchenko <oleksandr_andrushchenko@epam.com>

Hello!

At the moment Xen [1] already supports some virtual multimedia
features [2] such as virtual display, sound. It supports keyboards,
pointers and multi-touch devices all allowing Xen to be used in
automotive appliances, In-Vehicle Infotainment (IVI) systems
and many more.

This work adds a new Xen para-virtualized protocol for a virtual
camera device which extends multimedia capabilities of Xen even
farther: video conferencing, IVI, high definition maps etc.

The initial goal is to support most needed functionality with the
final idea to make it possible to extend the protocol if need be:

1. Provide means for base virtual device configuration:
 - pixel formats
 - resolutions
 - frame rates
2. Support basic camera controls:
 - contrast
 - brightness
 - hue
 - saturation
3. Support streaming control
4. Support zero-copying use-cases

I hope that Xen and V4L and other communities could give their
valuable feedback on this work, so I can update the protocol
to better fit any additional requirements I might have missed.

I would like to thank Hans Verkuil <hverkuil@xs4all.nl> for valuable
comments and help.

Thank you,
Oleksandr Andrushchenko

Changes since v1:
=================

1. Added XenStore entries:
 - frame-rates
2. Do not require the FOURCC code in XenStore to be upper case only
3. Added/changed command set:
 - configuration get/set
 - buffer queue/dequeue
 - control get
4. Added control flags, e.g. read-only etc.
5. Added colorspace configuration support, relevant constants
6. Added events:
 - configuration change
 - control change
7. Changed control values to 64-bit
8. Added sequence number to frame avail event
9. Coding style cleanup

[1] https://www.xenproject.org/
[2] https://xenbits.xen.org/gitweb/?p=xen.git;a=tree;f=xen/include/public/io

Oleksandr Andrushchenko (1):
  cameraif: add ABI for para-virtual camera

 xen/include/public/io/cameraif.h | 1263 ++++++++++++++++++++++++++++++
 1 file changed, 1263 insertions(+)
 create mode 100644 xen/include/public/io/cameraif.h

-- 
2.18.0

             reply	other threads:[~2018-09-11  8:30 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-09-11  8:29 Oleksandr Andrushchenko [this message]
2018-09-11  8:29 ` [Xen-devel][PATCH v2 0/1] cameraif: add ABI for para-virtual camera Oleksandr Andrushchenko
2018-09-11  8:29 ` [PATCH v2 1/1] " Oleksandr Andrushchenko
2018-09-11  8:29   ` [Xen-devel][PATCH " Oleksandr Andrushchenko
2018-09-12  7:52   ` [PATCH " Hans Verkuil
2018-09-12  7:52     ` [Xen-devel][PATCH " Hans Verkuil
2018-09-12 10:09     ` [PATCH " Oleksandr Andrushchenko
2018-09-12 10:09       ` [Xen-devel][PATCH " Oleksandr Andrushchenko
2018-09-12 12:25       ` [PATCH " Hans Verkuil
2018-09-12 12:25         ` [Xen-devel][PATCH " Hans Verkuil
2018-09-12 13:02         ` [PATCH " Oleksandr Andrushchenko
2018-09-12 13:02           ` [Xen-devel][PATCH " Oleksandr Andrushchenko
2018-09-12 13:38           ` [PATCH " Hans Verkuil
2018-09-12 13:38             ` [Xen-devel][PATCH " Hans Verkuil
2018-09-12 14:15             ` [PATCH " Oleksandr Andrushchenko
2018-09-12 14:15               ` [Xen-devel][PATCH " Oleksandr Andrushchenko
2018-09-12 14:38               ` [PATCH " Hans Verkuil
2018-09-12 14:38                 ` [Xen-devel][PATCH " Hans Verkuil
2018-09-13  5:34                 ` [PATCH " Oleksandr Andrushchenko
2018-09-13  5:34                   ` [Xen-devel][PATCH " Oleksandr Andrushchenko
2018-09-12  9:16   ` [PATCH " Hans Verkuil
2018-09-12  9:16     ` [Xen-devel][PATCH " Hans Verkuil
2018-09-12 10:12     ` [PATCH " Oleksandr Andrushchenko
2018-09-12 10:12       ` [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=20180911082952.23322-1-andr2000@gmail.com \
    --to=andr2000@gmail.com \
    --cc=boris.ostrovsky@oracle.com \
    --cc=hverkuil@xs4all.nl \
    --cc=jgross@suse.com \
    --cc=koji.matsuoka.xm@renesas.com \
    --cc=konrad.wilk@oracle.com \
    --cc=linux-media@vger.kernel.org \
    --cc=mchehab@kernel.org \
    --cc=oleksandr_andrushchenko@epam.com \
    --cc=sakari.ailus@linux.intel.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.