From: Sakari Ailus <sakari.ailus@iki.fi>
To: Dmitry Perchanov <dmitry.perchanov@intel.com>
Cc: linux-media@vger.kernel.org, laurent.pinchart@ideasonboard.com,
mchehab@kernel.org, linux-kernel@vger.kernel.org,
evgeni.raikhel@intel.com, demisrael@gmail.com
Subject: Re: [PATCH v3] media: uvcvideo: Enable Intel RealSense metadata for devices.
Date: Thu, 20 Apr 2023 12:24:18 +0300 [thread overview]
Message-ID: <ZEEEwt34bfmNEN99@valkosipuli.retiisi.eu> (raw)
In-Reply-To: <5587a4f1a0a7f3e2bd0ce886bb4ee3bcbf8f522a.camel@intel.com>
Hi Dmitry,
On Thu, Apr 20, 2023 at 12:06:55PM +0300, Dmitry Perchanov wrote:
> Intel RealSense UVC Depth cameras produce metadata in a
> vendor-specific format that is already supported by the uvcvideo driver.
> Enable handling of this metadata for 7 additional RealSense devices.
>
> Co-developed-by: Yu MENG <yu1.meng@intel.com>
> Co-developed-by: Evgeni Raikhel <evgeni.raikhel@intel.com>
> Signed-off-by: Dmitry Perchanov <dmitry.perchanov@intel.com>
Thanks for the update.
Is the D4XX format on these devices the same that's documented in
Documentation/userspace-api/media/v4l/pixfmt-meta-d4xx.rst ? I.e. there are
no additional fields or differences, and the version of the format is the
same?
The format documentation doesn't say which version number even the current
devices use (just refers to "xxx").
--
Kind regards,
Sakari Ailus
next prev parent reply other threads:[~2023-04-20 9:28 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-04-20 9:06 [PATCH v3] media: uvcvideo: Enable Intel RealSense metadata for devices Dmitry Perchanov
2023-04-20 9:24 ` Sakari Ailus [this message]
2023-04-20 11:26 ` Dmitry Perchanov
2023-04-20 11:27 ` Sakari Ailus
2023-04-20 10:31 ` Laurent Pinchart
2023-06-01 14:03 ` Dmitry Perchanov
2023-06-02 14:25 ` Laurent Pinchart
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=ZEEEwt34bfmNEN99@valkosipuli.retiisi.eu \
--to=sakari.ailus@iki.fi \
--cc=demisrael@gmail.com \
--cc=dmitry.perchanov@intel.com \
--cc=evgeni.raikhel@intel.com \
--cc=laurent.pinchart@ideasonboard.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-media@vger.kernel.org \
--cc=mchehab@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