From: Sakari Ailus <sakari.ailus@linux.intel.com>
To: Hans Verkuil <hverkuil@xs4all.nl>
Cc: linux-media@vger.kernel.org, laurent.pinchart@ideasonboard.com
Subject: Re: [PATCH 1/1] Documentation: media: Document media bus codes to use on serial busses
Date: Tue, 19 May 2020 11:44:40 +0300 [thread overview]
Message-ID: <20200519084440.GD20066@paasikivi.fi.intel.com> (raw)
In-Reply-To: <aede80cc-f891-c861-8ba3-f733088e5694@xs4all.nl>
Hi Hans,
Thanks for the review.
On Tue, May 19, 2020 at 09:56:04AM +0200, Hans Verkuil wrote:
> On 19/05/2020 09:21, Sakari Ailus wrote:
> > 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
>
> busses -> buses
>
> (actually, both spellings are used in about equal measures in the kernel, but
> the official spelling is 'buses').
I guess you mean "American"?
>
> were -> was
>
> (the support was added, 'support' is singular)
Agreed.
>
> > +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.
>
> To be honest, I'm confused by this text. Probably because I don't know enough
> about CSI. I'm not really sure what you mean with 'single sample per pixel'.
Good catch.
I went to look into mbus format documentation to see how this was expressed
there, only to find the subject is already covered. This need to be
referred to from CSI-2 documentation though.
I'll send v2.
--
Regards,
Sakari Ailus
prev parent reply other threads:[~2020-05-19 8:44 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-05-19 7:21 [PATCH 1/1] Documentation: media: Document media bus codes to use on serial busses Sakari Ailus
2020-05-19 7:56 ` Hans Verkuil
2020-05-19 8:44 ` Sakari Ailus [this message]
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=20200519084440.GD20066@paasikivi.fi.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