From: Sakari Ailus <sakari.ailus@linux.intel.com>
To: linux-media@vger.kernel.org
Cc: laurent.pinchart@ideasonboard.com, hverkuil@xs4all.nl
Subject: [PATCH 1/1] Documentation: media: Document media bus codes to use on serial busses
Date: Tue, 19 May 2020 10:21:48 +0300 [thread overview]
Message-ID: <20200519072148.28071-1-sakari.ailus@linux.intel.com> (raw)
Document media bus codes on serial busses. The single sample per pixel
variant is to be chosen from all the possible variants. While this has
been the practice since the introduction of CSI-2 support, it never was
written down. Do it now.
Signed-off-by: Sakari Ailus <sakari.ailus@linux.intel.com>
---
Documentation/driver-api/media/csi2.rst | 10 ++++++++++
1 file changed, 10 insertions(+)
diff --git a/Documentation/driver-api/media/csi2.rst b/Documentation/driver-api/media/csi2.rst
index da8b356389f0..af078ac927bd 100644
--- a/Documentation/driver-api/media/csi2.rst
+++ b/Documentation/driver-api/media/csi2.rst
@@ -10,6 +10,16 @@ the host SoC. It is defined by the `MIPI alliance`_.
.. _`MIPI alliance`: http://www.mipi.org/
+Media bus formats
+-----------------
+
+Always use single sample per pixel formats on the CSI-2 bus.
+
+No new media bus formats were created when the support for serial busses were
+added. To avoid using different media bus codes to describe the same format, the
+practice is to use a format that has a single sample per pixel on the parallel
+bus.
+
Transmitter drivers
-------------------
--
2.20.1
next reply other threads:[~2020-05-19 7:23 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-05-19 7:21 Sakari Ailus [this message]
2020-05-19 7:56 ` [PATCH 1/1] Documentation: media: Document media bus codes to use on serial busses Hans Verkuil
2020-05-19 8:44 ` Sakari Ailus
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=20200519072148.28071-1-sakari.ailus@linux.intel.com \
--to=sakari.ailus@linux.intel.com \
--cc=hverkuil@xs4all.nl \
--cc=laurent.pinchart@ideasonboard.com \
--cc=linux-media@vger.kernel.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