xen-devel.lists.xenproject.org archive mirror
 help / color / mirror / Atom feed
From: Oleksandr Andrushchenko <andr2000@gmail.com>
To: Juergen Gross <jgross@suse.com>,
	xen-devel@lists.xenproject.org, linux-kernel@vger.kernel.org,
	linux-media@vger.kernel.org, konrad.wilk@oracle.com,
	hverkuil@xs4all.nl, boris.ostrovsky@oracle.com
Cc: Oleksandr Andrushchenko <oleksandr_andrushchenko@epam.com>
Subject: Re: [Xen-devel] [PATCH] xen/cameraif: add ABI for para-virtual camera
Date: Tue, 9 Apr 2019 12:33:36 +0300	[thread overview]
Message-ID: <5bb8c828-b0ae-86c3-dacf-88bf6032dd6f@gmail.com> (raw)
In-Reply-To: <9b9ba6b9-f045-80e2-fe8a-595728fb1ec0@suse.com>

On 4/9/19 12:28 PM, Juergen Gross wrote:
> On 09/04/2019 11:15, Oleksandr Andrushchenko wrote:
>> From: Oleksandr Andrushchenko <oleksandr_andrushchenko@epam.com>
>>
>> This is the ABI for the two halves of a para-virtualized
>> camera driver which extends Xen's reach multimedia capabilities even
>> further enabling it for video conferencing, In-Vehicle Infotainment,
>> 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
>>
>> Signed-off-by: Oleksandr Andrushchenko <oleksandr_andrushchenko@epam.com>
>> Cc: Juergen Gross <jgross@suse.com>
>> Cc: Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>
>> Cc: Hans Verkuil <hverkuil@xs4all.nl>
> I'm in principle fine with this patch, but it should be sent as part of
> a series using that header. In case the related driver isn't accepted
> we'd end up with a stale header file.
Hm, I am doing this as I did for the rest of protocols before:
1. Get the protocol in Xen
2. Get the copy in Linux
3. Upstream driver (use header)

Even if the driver is not accepted (hope this won't happen)
then this patch makes Xen and Linux properly aligned anyway.
Which is IMO good
>
> Juergen
Thank you,
Oleksandr

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

  reply	other threads:[~2019-04-09  9:33 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-04-09  9:15 [Xen-devel] [PATCH] xen/cameraif: add ABI for para-virtual camera Oleksandr Andrushchenko
2019-04-09  9:18 ` Oleksandr Andrushchenko
2019-04-09  9:18 ` Oleksandr Andrushchenko
2019-04-09  9:18 ` [Xen-devel] " Wei Liu
2019-04-09  9:19   ` Wei Liu
2019-04-09  9:19   ` [Xen-devel] " Wei Liu
2019-04-09  9:18 ` Wei Liu
2019-04-09  9:28 ` Juergen Gross
2019-04-09  9:28 ` [Xen-devel] " Juergen Gross
2019-04-09  9:33   ` Oleksandr Andrushchenko [this message]
2019-04-09  9:46     ` Juergen Gross
2019-04-09  9:46     ` [Xen-devel] " Juergen Gross
2019-04-09 13:26       ` Oleksandr Andrushchenko
2019-04-09 13:26       ` Oleksandr Andrushchenko
2019-04-09  9:33   ` 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=5bb8c828-b0ae-86c3-dacf-88bf6032dd6f@gmail.com \
    --to=andr2000@gmail.com \
    --cc=boris.ostrovsky@oracle.com \
    --cc=hverkuil@xs4all.nl \
    --cc=jgross@suse.com \
    --cc=konrad.wilk@oracle.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-media@vger.kernel.org \
    --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 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).