All of lore.kernel.org
 help / color / mirror / Atom feed
From: Mauro Carvalho Chehab <mchehab+huawei@kernel.org>
To: Linux Media Mailing List <linux-media@vger.kernel.org>
Cc: Mauro Carvalho Chehab <mchehab+huawei@kernel.org>,
	Hans Verkuil <hverkuil-cisco@xs4all.nl>,
	Laurent Pinchart <laurent.pinchart@ideasonboard.com>,
	Sakari Ailus <sakari.ailus@linux.intel.com>,
	Hans Verkuil <hans.verkuil@cisco.com>
Subject: [PATCH v9 0/5] Add a glossary for the media subsystem
Date: Fri,  8 May 2020 15:10:32 +0200	[thread overview]
Message-ID: <cover.1588943181.git.mchehab+huawei@kernel.org> (raw)

There are too many technical terms at the media subsystem, and sometimes
the same thing is refered differently at the documentation and on the ML
and IRC discussions.

Let's add a glossary to the uAPI documentation, in order to start using
a common vocabulary at the subsystem's discussion and to let things
clearer for people trying to understand the subsystem.

I'm pretty sure that this document doesn't cover everything, but it can
(and should) be improved overtime.

At version 9 (and hopefully the final version), I simplified how things were
described, avoiding to define things that may not be needed for this
initial version, in order to try reach a consensus when merging.

If something is not ok, or other terms need to be added, feel free to
submit other patches addressing it.

Mauro Carvalho Chehab (5):
  media: open.rst: better document device node naming
  media: open.rst: remove the minor number range
  media: docs: add glossary.rst with common terms used at V4L2 spec
  media: glossary.rst: add terms for MC-centric video-node-centric
  media: open.rst: document mc-centric and video-node-centric

 .../userspace-api/media/glossary.rst          | 214 ++++++++++++++++++
 Documentation/userspace-api/media/index.rst   |   3 +
 .../userspace-api/media/v4l/open.rst          | 106 +++++++--
 3 files changed, 309 insertions(+), 14 deletions(-)
 create mode 100644 Documentation/userspace-api/media/glossary.rst

-- 
2.26.2



             reply	other threads:[~2020-05-08 13:10 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-05-08 13:10 Mauro Carvalho Chehab [this message]
2020-05-08 13:10 ` [PATCH v9 1/5] media: open.rst: better document device node naming Mauro Carvalho Chehab
2020-05-08 13:24   ` Hans Verkuil
2020-05-08 13:35     ` Mauro Carvalho Chehab
2020-05-08 13:55       ` Hans Verkuil
2020-05-08 13:10 ` [PATCH v9 2/5] media: open.rst: remove the minor number range Mauro Carvalho Chehab
2020-05-08 13:10 ` [PATCH v9 3/5] media: docs: add glossary.rst with common terms used at V4L2 spec Mauro Carvalho Chehab
2020-05-08 13:40   ` Hans Verkuil
2020-05-08 14:25     ` Mauro Carvalho Chehab
2020-05-08 14:54       ` Hans Verkuil
2020-05-08 13:10 ` [PATCH v9 4/5] media: glossary.rst: add terms for MC-centric video-node-centric Mauro Carvalho Chehab
2020-05-08 13:46   ` Hans Verkuil
2020-05-08 14:36     ` Mauro Carvalho Chehab
2020-05-08 13:10 ` [PATCH v9 5/5] media: open.rst: document mc-centric and video-node-centric Mauro Carvalho Chehab
2020-05-08 13:54   ` 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=cover.1588943181.git.mchehab+huawei@kernel.org \
    --to=mchehab+huawei@kernel.org \
    --cc=hans.verkuil@cisco.com \
    --cc=hverkuil-cisco@xs4all.nl \
    --cc=laurent.pinchart@ideasonboard.com \
    --cc=linux-media@vger.kernel.org \
    --cc=sakari.ailus@linux.intel.com \
    /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.