From: Laurent Pinchart <laurent.pinchart@ideasonboard.com>
To: dorodnic@gmail.com
Cc: linux-media@vger.kernel.org, evgeni.raikhel@intel.com,
Sergey Dorodnicov <sergey.dorodnicov@intel.com>
Subject: Re: [PATCH v2 2/2] [media] CNF4 pixel format for media subsystem
Date: Thu, 01 Nov 2018 18:10:08 +0200 [thread overview]
Message-ID: <1887189.gMKOtKLMbF@avalon> (raw)
In-Reply-To: <1536734527-3770-3-git-send-email-sergey.dorodnicov@intel.com>
Hi Sergey,
Thank you for the patch.
As for patch 1/2, the subject line needs a prefix. Furthermore it doesn't
really describe the patch. I propose writing it as
media: uvcvideo: Add support for the CNF4 format
On Wednesday, 12 September 2018 09:42:07 EET dorodnic@gmail.com wrote:
> From: Sergey Dorodnicov <sergey.dorodnicov@intel.com>
>
> Registering new GUID used by Intel RealSense cameras with fourcc CNF4,
> encoding depth sensor confidence information for every pixel.
And there I would write "Register the GUID ...".
Apart from that the patch looks good to me,
Reviewed-by: Laurent Pinchart <laurent.pinchart@ideasonboard.com>
If you're fine with the subject line change there's no need to resubmit, I'll
fix it when applying the patch to my tree.
> Signed-off-by: Sergey Dorodnicov <sergey.dorodnicov@intel.com>
> Signed-off-by: Evgeni Raikhel <evgeni.raikhel@intel.com>
> ---
> drivers/media/usb/uvc/uvc_driver.c | 5 +++++
> drivers/media/usb/uvc/uvcvideo.h | 3 +++
> 2 files changed, 8 insertions(+)
>
> diff --git a/drivers/media/usb/uvc/uvc_driver.c
> b/drivers/media/usb/uvc/uvc_driver.c index d46dc43..19f129f 100644
> --- a/drivers/media/usb/uvc/uvc_driver.c
> +++ b/drivers/media/usb/uvc/uvc_driver.c
> @@ -214,6 +214,11 @@ static struct uvc_format_desc uvc_fmts[] = {
> .guid = UVC_GUID_FORMAT_INZI,
> .fcc = V4L2_PIX_FMT_INZI,
> },
> + {
> + .name = "4-bit Depth Confidence (Packed)",
> + .guid = UVC_GUID_FORMAT_CNF4,
> + .fcc = V4L2_PIX_FMT_CNF4,
> + },
> };
>
> /* ------------------------------------------------------------------------
> diff --git a/drivers/media/usb/uvc/uvcvideo.h
> b/drivers/media/usb/uvc/uvcvideo.h index e5f5d84..779bab2 100644
> --- a/drivers/media/usb/uvc/uvcvideo.h
> +++ b/drivers/media/usb/uvc/uvcvideo.h
> @@ -154,6 +154,9 @@
> #define UVC_GUID_FORMAT_INVI \
> { 'I', 'N', 'V', 'I', 0xdb, 0x57, 0x49, 0x5e, \
> 0x8e, 0x3f, 0xf4, 0x79, 0x53, 0x2b, 0x94, 0x6f}
> +#define UVC_GUID_FORMAT_CNF4 \
> + { 'C', ' ', ' ', ' ', 0x00, 0x00, 0x10, 0x00, \
> + 0x80, 0x00, 0x00, 0xaa, 0x00, 0x38, 0x9b, 0x71}
>
> #define UVC_GUID_FORMAT_D3DFMT_L8 \
> {0x32, 0x00, 0x00, 0x00, 0x00, 0x00, 0x10, 0x00, \
--
Regards,
Laurent Pinchart
next prev parent reply other threads:[~2018-11-02 1:13 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-09-12 6:42 [PATCH v2 0/2] [media] Depth confidence pixel-format for Intel RealSense cameras dorodnic
2018-09-12 6:39 ` Hans Verkuil
2018-10-03 12:08 ` Raikhel, Evgeni
2018-10-03 12:26 ` Hans Verkuil
2018-11-01 14:42 ` Sergey Dorodnic
2018-09-12 6:42 ` [PATCH v2 1/2] [media] CNF4 fourcc for 4 bit-per-pixel packed depth confidence information dorodnic
2018-11-01 16:10 ` Laurent Pinchart
2018-09-12 6:42 ` [PATCH v2 2/2] [media] CNF4 pixel format for media subsystem dorodnic
2018-11-01 16:10 ` Laurent Pinchart [this message]
2018-11-04 16:10 ` Sergey Dorodnic
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=1887189.gMKOtKLMbF@avalon \
--to=laurent.pinchart@ideasonboard.com \
--cc=dorodnic@gmail.com \
--cc=evgeni.raikhel@intel.com \
--cc=linux-media@vger.kernel.org \
--cc=sergey.dorodnicov@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox