From: Mauro Carvalho Chehab <mchehab@s-opensource.com>
To: Linux Doc Mailing List <linux-doc@vger.kernel.org>,
Linux Media Mailing List <linux-media@vger.kernel.org>
Cc: Mauro Carvalho Chehab <mchehab@s-opensource.com>,
Mauro Carvalho Chehab <mchehab@infradead.org>,
linux-kernel@vger.kernel.org, Jonathan Corbet <corbet@lwn.net>
Subject: [PATCH v3 0/7] document types of hardware control for V4L2
Date: Fri, 25 Aug 2017 12:11:50 -0300 [thread overview]
Message-ID: <cover.1503673702.git.mchehab@s-opensource.com> (raw)
On 2010, we introduced a new way to control complex V4L2 devices used
on embedded systems, but this was never documented, nor it is possible
for an userspace applicatin to detect the kind of control a device supports.
This series fill the gap.
Mauro Carvalho Chehab (7):
media: add glossary.rst with a glossary of terms used at V4L2 spec
media: open.rst: better document device node naming
media: open.rst: remove the minor number range
media: open.rst: document devnode-centric and mc-centric types
media: open.rst: Adjust some terms to match the glossary
media: videodev2: add a flag for MC-centric devices
media: open.rst: add a notice about subdev-API on vdev-centric
v3:
- Add a glossary to be used by the new documentation about hardware control;
- Add a patch removing minor number range
- Use glossary terms at open.rst
- Split the notice about subdev-API on vdev-centric, as this change
will require further discussions.
v2:
- added a patch at the beginning of the series better defining the
device node naming rules;
- better defined the differenes between device hardware and V4L2 device node
as suggested by Laurent and with changes proposed by Hans and Sakari
- changed the caps flag to indicate MC-centric devices
- removed the final patch that would use the new caps flag. I'll write it
once we agree on the new caps flag.
Documentation/media/uapi/v4l/glossary.rst | 95 +++++++++++++++++
Documentation/media/uapi/v4l/open.rst | 125 ++++++++++++++++++++---
Documentation/media/uapi/v4l/v4l2.rst | 1 +
Documentation/media/uapi/v4l/vidioc-querycap.rst | 5 +
include/uapi/linux/videodev2.h | 2 +
5 files changed, 214 insertions(+), 14 deletions(-)
create mode 100644 Documentation/media/uapi/v4l/glossary.rst
--
2.13.3
next reply other threads:[~2017-08-25 15:12 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-08-25 15:11 Mauro Carvalho Chehab [this message]
2017-08-25 15:11 ` [PATCH v3 1/7] media: add glossary.rst with a glossary of terms used at V4L2 spec Mauro Carvalho Chehab
2017-08-25 15:11 ` [PATCH v3 2/7] media: open.rst: better document device node naming Mauro Carvalho Chehab
2017-08-25 15:11 ` [PATCH v3 3/7] media: open.rst: remove the minor number range Mauro Carvalho Chehab
2017-08-25 15:11 ` [PATCH v3 4/7] media: open.rst: document devnode-centric and mc-centric types Mauro Carvalho Chehab
2017-08-25 15:11 ` [PATCH v3 5/7] media: open.rst: Adjust some terms to match the glossary Mauro Carvalho Chehab
2017-08-25 15:11 ` [PATCH v3 6/7] media: videodev2: add a flag for MC-centric devices Mauro Carvalho Chehab
2017-08-25 15:11 ` [PATCH v3 7/7] media: open.rst: add a notice about subdev-API on vdev-centric Mauro Carvalho Chehab
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=cover.1503673702.git.mchehab@s-opensource.com \
--to=mchehab@s-opensource.com \
--cc=corbet@lwn.net \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-media@vger.kernel.org \
--cc=mchehab@infradead.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).