From: Randy Dunlap <rdunlap@infradead.org>
To: Alexandre Courbot <acourbot@chromium.org>,
Mauro Carvalho Chehab <mchehab@kernel.org>,
Hans Verkuil <hverkuil@xs4all.nl>,
Laurent Pinchart <laurent.pinchart@ideasonboard.com>,
Pawel Osciak <posciak@chromium.org>,
Marek Szyprowski <m.szyprowski@samsung.com>,
Tomasz Figa <tfiga@chromium.org>,
Sakari Ailus <sakari.ailus@linux.intel.com>,
Gustavo Padovan <gustavo.padovan@collabora.com>
Cc: linux-media@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [RFC PATCH 6/8] v4l2: document the request API interface
Date: Fri, 26 Jan 2018 12:40:10 -0800 [thread overview]
Message-ID: <98ccb2f3-156e-2f4e-4630-9d16d157d65b@infradead.org> (raw)
In-Reply-To: <20180126060216.147918-7-acourbot@chromium.org>
On 01/25/2018 10:02 PM, Alexandre Courbot wrote:
> Document how the request API can be used along with the existing V4L2
> interface.
>
> +Request API
> +===========
> +
> +The Request API has been designed to allow V4L2 to deal with requirements of
> +modern IPs (stateless codecs, MIPI cameras, ...) and APIs (Android Codec v2).
Hi,
Just a quick question: What are IPs?
Not Internet Protocols. Hopefully not Intellectual Properties.
Maybe Intelligent Processors?
thanks,
--
~Randy
next prev parent reply other threads:[~2018-01-26 20:40 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-01-26 6:02 [RFC PATCH 0/8] [media] Request API, take three Alexandre Courbot
2018-01-26 6:02 ` [RFC PATCH 1/8] media: add request API core and UAPI Alexandre Courbot
2018-01-26 6:02 ` [RFC PATCH 2/8] videodev2.h: Add request field to v4l2_buffer Alexandre Courbot
2018-01-26 6:02 ` [RFC PATCH 3/8] media: videobuf2: add support for requests Alexandre Courbot
2018-01-31 12:19 ` Sakari Ailus
2018-01-26 6:02 ` [RFC PATCH 4/8] media: vb2: add support for requests in QBUF ioctl Alexandre Courbot
2018-01-26 6:02 ` [RFC PATCH 5/8] media: Document the media request API Alexandre Courbot
2018-01-29 16:04 ` Hans Verkuil
2018-01-30 6:31 ` Alexandre Courbot
2018-01-26 6:02 ` [RFC PATCH 6/8] v4l2: document the request API interface Alexandre Courbot
2018-01-26 20:40 ` Randy Dunlap [this message]
2018-01-26 21:44 ` Nicolas Dufresne
2018-01-29 16:03 ` Hans Verkuil
2018-01-30 6:31 ` Alexandre Courbot
2018-01-31 8:26 ` Hans Verkuil
2018-02-06 22:19 ` Sakari Ailus
2018-01-26 6:02 ` [RFC PATCH 7/8] media: vim2m: add media device Alexandre Courbot
2018-01-26 6:02 ` [RFC PATCH 8/8] media: vim2m: add request support Alexandre Courbot
2018-01-29 11:21 ` [RFC PATCH 0/8] [media] Request API, take three Hans Verkuil
2018-01-30 6:31 ` Alexandre Courbot
2018-01-31 7:50 ` Hans Verkuil
2018-01-31 8:10 ` Tomasz Figa
2018-01-31 8:47 ` Hans Verkuil
2018-01-31 9:46 ` Tomasz Figa
2018-01-31 16:16 ` Hans Verkuil
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=98ccb2f3-156e-2f4e-4630-9d16d157d65b@infradead.org \
--to=rdunlap@infradead.org \
--cc=acourbot@chromium.org \
--cc=gustavo.padovan@collabora.com \
--cc=hverkuil@xs4all.nl \
--cc=laurent.pinchart@ideasonboard.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-media@vger.kernel.org \
--cc=m.szyprowski@samsung.com \
--cc=mchehab@kernel.org \
--cc=posciak@chromium.org \
--cc=sakari.ailus@linux.intel.com \
--cc=tfiga@chromium.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®