From: Laurent Pinchart <laurent.pinchart@ideasonboard.com>
To: Philipp Zabel <philipp.zabel@gmail.com>
Cc: linux-media@vger.kernel.org
Subject: Re: [PATCH 3/3] [media] uvcvideo: skip non-extension unit controls on Oculus Rift Sensors
Date: Sat, 15 Jul 2017 12:54:15 +0300 [thread overview]
Message-ID: <1988392.8ZGCFRfgf9@avalon> (raw)
In-Reply-To: <20170714201424.23592-3-philipp.zabel@gmail.com>
Hi Philipp,
Thank you for the patch.
On Friday 14 Jul 2017 22:14:24 Philipp Zabel wrote:
> The Oculus Rift Sensors (DK2 and CV1) allow to configure their sensor chips
> directly via I2C commands using extension unit controls. The processing and
> camera unit controls do not function at all.
Do the processing and camera units they report controls that don't work when
exercised ? Who in a sane state of mind could have designed such a terrible
product ?
If I understand you correctly, this device requires userspace code that knows
how to program the sensor (and possibly other chips). If that's the case, is
there an open-source implementation of that code publicly available ?
> Signed-off-by: Philipp Zabel <philipp.zabel@gmail.com>
> ---
> drivers/media/usb/uvc/uvc_ctrl.c | 14 ++++++++++++++
> 1 file changed, 14 insertions(+)
>
> diff --git a/drivers/media/usb/uvc/uvc_ctrl.c
> b/drivers/media/usb/uvc/uvc_ctrl.c index 86cb16a2e7f4..573e1f8735bf 100644
> --- a/drivers/media/usb/uvc/uvc_ctrl.c
> +++ b/drivers/media/usb/uvc/uvc_ctrl.c
> @@ -2165,6 +2165,10 @@ int uvc_ctrl_init_device(struct uvc_device *dev)
> {
> struct uvc_entity *entity;
> unsigned int i;
> + const struct usb_device_id xu_only[] = {
> + { USB_DEVICE(0x2833, 0x0201) },
> + { USB_DEVICE(0x2833, 0x0211) },
> + };
>
> /* Walk the entities list and instantiate controls */
> list_for_each_entry(entity, &dev->entities, list) {
> @@ -2172,6 +2176,16 @@ int uvc_ctrl_init_device(struct uvc_device *dev)
> unsigned int bControlSize = 0, ncontrols;
> __u8 *bmControls = NULL;
>
> + /* Oculus Sensors only handle extension unit controls */
> + if (UVC_ENTITY_TYPE(entity) != UVC_VC_EXTENSION_UNIT) {
> + for (i = 0; i < ARRAY_SIZE(xu_only); i++) {
> + if (usb_match_one_id(dev->intf, &xu_only[i]))
> + break;
> + }
> + if (i != ARRAY_SIZE(xu_only))
> + continue;
> + }
> +
> if (UVC_ENTITY_TYPE(entity) == UVC_VC_EXTENSION_UNIT) {
> bmControls = entity->extension.bmControls;
> bControlSize = entity->extension.bControlSize;
--
Regards,
Laurent Pinchart
next prev parent reply other threads:[~2017-07-15 9:54 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-07-14 20:14 [PATCH 1/3] [media] uvcvideo: variable size controls Philipp Zabel
2017-07-14 20:14 ` [PATCH 2/3] [media] uvcvideo: flag variable length control on Oculus Rift CV1 Sensor Philipp Zabel
2017-07-14 20:14 ` [PATCH 3/3] [media] uvcvideo: skip non-extension unit controls on Oculus Rift Sensors Philipp Zabel
2017-07-15 9:54 ` Laurent Pinchart [this message]
2017-07-15 13:13 ` Philipp Zabel
2017-07-17 2:25 ` Laurent Pinchart
2017-07-24 5:52 ` Philipp Zabel
2017-07-24 23:10 ` Laurent Pinchart
2017-07-25 5:51 ` Philipp Zabel
2017-07-15 9:49 ` [PATCH 1/3] [media] uvcvideo: variable size controls Laurent Pinchart
2017-07-15 12:54 ` Philipp Zabel
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=1988392.8ZGCFRfgf9@avalon \
--to=laurent.pinchart@ideasonboard.com \
--cc=linux-media@vger.kernel.org \
--cc=philipp.zabel@gmail.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