From: Ian Arkver <ian.arkver.dev@gmail.com>
To: Satish Kumar Nagireddy <satish.nagireddy.nagireddy@xilinx.com>,
linux-media@vger.kernel.org, laurent.pinchart@ideasonboard.com,
michal.simek@xilinx.com, hyun.kwon@xilinx.com
Cc: Satish Kumar Nagireddy <satishna@xilinx.com>
Subject: Re: [PATCH v2 9/9] [media] Add documentation for YUV420 bus format
Date: Fri, 9 Feb 2018 13:58:22 +0000 [thread overview]
Message-ID: <97e51a9a-04da-e441-25ea-945acc249f80@gmail.com> (raw)
In-Reply-To: <1518139327-21947-1-git-send-email-satishna@xilinx.com>
On 09/02/18 01:22, Satish Kumar Nagireddy wrote:
> The code is MEDIA_BUS_FMT_VYYUYY8_1X24
>
> Signed-off-by: Satish Kumar Nagireddy <satishna@xilinx.com>
> ---
> Documentation/media/uapi/v4l/subdev-formats.rst | 34 +++++++++++++++++++++++++
> 1 file changed, 34 insertions(+)
>
> diff --git a/Documentation/media/uapi/v4l/subdev-formats.rst b/Documentation/media/uapi/v4l/subdev-formats.rst
> index b1eea44..a4d7d87 100644
> --- a/Documentation/media/uapi/v4l/subdev-formats.rst
> +++ b/Documentation/media/uapi/v4l/subdev-formats.rst
> @@ -7283,6 +7283,40 @@ The following table list existing packed 48bit wide YUV formats.
> - y\ :sub:`1`
> - y\ :sub:`0`
>
> + - MEDIA_BUS_FMT_VYYUYY8_1X24
> + - 0x202c
> + -
> + -
> + -
> + -
> + -
> + -
> + -
> + -
> + - v\ :sub:`7`
> + - v\ :sub:`6`
> + - v\ :sub:`5`
> + - v\ :sub:`4`
> + - v\ :sub:`3`
> + - v\ :sub:`2`
> + - v\ :sub:`1`
> + - v\ :sub:`0`
> + - u\ :sub:`7`
> + - u\ :sub:`6`
> + - u\ :sub:`5`
> + - u\ :sub:`4`
> + - u\ :sub:`3`
> + - u\ :sub:`2`
> + - u\ :sub:`1`
> + - u\ :sub:`0`
> + - y\ :sub:`7`
> + - y\ :sub:`6`
> + - y\ :sub:`5`
> + - y\ :sub:`4`
> + - y\ :sub:`3`
> + - y\ :sub:`2`
> + - y\ :sub:`1`
> + - y\ :sub:`0`
If this bus format name doesn't really describe how the pixels are sent
on the bus, maybe the documentation should? Is this for something like
MIPI CSI-2 YUV420 non-legacy modes where the bus format alternates on
odd/even lines?
Regards,
IanJ
>
> .. raw:: latex
>
> --
> 2.7.4
>
> This email and any attachments are intended for the sole use of the named recipient(s) and contain(s) confidential information that may be proprietary, privileged or copyrighted under applicable law. If you are not the intended recipient, do not read, copy, or forward this email message or any attachments. Delete this email message and any attachments immediately.
>
prev parent reply other threads:[~2018-02-09 13:58 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-02-09 1:22 [PATCH v2 9/9] [media] Add documentation for YUV420 bus format Satish Kumar Nagireddy
2018-02-09 13:58 ` Ian Arkver [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=97e51a9a-04da-e441-25ea-945acc249f80@gmail.com \
--to=ian.arkver.dev@gmail.com \
--cc=hyun.kwon@xilinx.com \
--cc=laurent.pinchart@ideasonboard.com \
--cc=linux-media@vger.kernel.org \
--cc=michal.simek@xilinx.com \
--cc=satish.nagireddy.nagireddy@xilinx.com \
--cc=satishna@xilinx.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox