Dear Linux folks,
On the Dell XPS 13 9370, Linux 4.16-rc6 outputs the messages below.
```
[ 2.338094] calling uvc_init+0x0/0x1000 [uvcvideo] @ 295
[ 2.338569] calling iTCO_wdt_init_module+0x0/0x1000 [iTCO_wdt] @ 280
[ 2.338570] iTCO_wdt: Intel TCO WatchDog Timer Driver v1.11
[ 2.338713] iTCO_wdt: Found a Intel PCH TCO device (Version=4,
TCOBASE=0x0400)
[ 2.338755] uvcvideo: Found UVC 1.00 device Integrated_Webcam_HD
(0bda:58f4)
[ 2.338827] iTCO_wdt: initialized. heartbeat=30 sec (nowayout=0)
[ 2.338851] initcall iTCO_wdt_init_module+0x0/0x1000 [iTCO_wdt]
returned 0 after 271 usecs
[ 2.340669] uvcvideo 1-5:1.0: Entity type for entity Extension 4 was
not initialized!
[ 2.340670] uvcvideo 1-5:1.0: Entity type for entity Extension 7 was
not initialized!
[ 2.340672] uvcvideo 1-5:1.0: Entity type for entity Processing 2 was
not initialized!
[ 2.340673] uvcvideo 1-5:1.0: Entity type for entity Camera 1 was not
initialized!
[ 2.340736] input: Integrated_Webcam_HD: Integrate as
/devices/pci0000:00/0000:00:14.0/usb1/1-5/1-5:1.0/input/input9
[ 2.341447] uvcvideo: Unknown video format
00000032-0002-0010-8000-00aa00389b71
[ 2.341450] uvcvideo: Found UVC 1.00 device Integrated_Webcam_HD
(0bda:58f4)
[ 2.343371] uvcvideo: Unable to create debugfs 1-2 directory.
[ 2.343420] uvcvideo 1-5:1.2: Entity type for entity Extension 10 was
not initialized!
[ 2.343422] uvcvideo 1-5:1.2: Entity type for entity Extension 12 was
not initialized!
[ 2.343423] uvcvideo 1-5:1.2: Entity type for entity Processing 9 was
not initialized!
[ 2.343424] uvcvideo 1-5:1.2: Entity type for entity Camera 11 was
not initialized!
[ 2.343472] input: Integrated_Webcam_HD: Integrate as
/devices/pci0000:00/0000:00:14.0/usb1/1-5/1-5:1.2/input/input10
[ 2.343496] usbcore: registered new interface driver uvcvideo
[ 2.343496] USB Video Class driver (1.1.1)
[ 2.343501] initcall uvc_init+0x0/0x1000 [uvcvideo] returned 0 after
5275 usecs
```
Please tell me, what I can do to improve the situation.
Kind regards,
Paul
Hi Paul,
On Tuesday, 20 March 2018 14:20:14 EET Paul Menzel wrote:
> Dear Linux folks,
>
>
> On the Dell XPS 13 9370, Linux 4.16-rc6 outputs the messages below.
>
> ```
> [ 2.338094] calling uvc_init+0x0/0x1000 [uvcvideo] @ 295
> [ 2.338569] calling iTCO_wdt_init_module+0x0/0x1000 [iTCO_wdt] @ 280
> [ 2.338570] iTCO_wdt: Intel TCO WatchDog Timer Driver v1.11
> [ 2.338713] iTCO_wdt: Found a Intel PCH TCO device (Version=4,
> TCOBASE=0x0400)
> [ 2.338755] uvcvideo: Found UVC 1.00 device Integrated_Webcam_HD
> (0bda:58f4)
> [ 2.338827] iTCO_wdt: initialized. heartbeat=30 sec (nowayout=0)
> [ 2.338851] initcall iTCO_wdt_init_module+0x0/0x1000 [iTCO_wdt]
> returned 0 after 271 usecs
> [ 2.340669] uvcvideo 1-5:1.0: Entity type for entity Extension 4 was
> not initialized!
> [ 2.340670] uvcvideo 1-5:1.0: Entity type for entity Extension 7 was
> not initialized!
> [ 2.340672] uvcvideo 1-5:1.0: Entity type for entity Processing 2 was
> not initialized!
> [ 2.340673] uvcvideo 1-5:1.0: Entity type for entity Camera 1 was not
> initialized!
> [ 2.340736] input: Integrated_Webcam_HD: Integrate as
> /devices/pci0000:00/0000:00:14.0/usb1/1-5/1-5:1.0/input/input9
> [ 2.341447] uvcvideo: Unknown video format
> 00000032-0002-0010-8000-00aa00389b71
> [ 2.341450] uvcvideo: Found UVC 1.00 device Integrated_Webcam_HD
> (0bda:58f4)
> [ 2.343371] uvcvideo: Unable to create debugfs 1-2 directory.
> [ 2.343420] uvcvideo 1-5:1.2: Entity type for entity Extension 10 was
> not initialized!
> [ 2.343422] uvcvideo 1-5:1.2: Entity type for entity Extension 12 was
> not initialized!
> [ 2.343423] uvcvideo 1-5:1.2: Entity type for entity Processing 9 was
> not initialized!
> [ 2.343424] uvcvideo 1-5:1.2: Entity type for entity Camera 11 was
> not initialized!
> [ 2.343472] input: Integrated_Webcam_HD: Integrate as
> /devices/pci0000:00/0000:00:14.0/usb1/1-5/1-5:1.2/input/input10
> [ 2.343496] usbcore: registered new interface driver uvcvideo
> [ 2.343496] USB Video Class driver (1.1.1)
> [ 2.343501] initcall uvc_init+0x0/0x1000 [uvcvideo] returned 0 after
> 5275 usecs
> ```
>
> Please tell me, what I can do to improve the situation.
Some vendors routinely implement new formats without bothering to send a patch
for the uvcvideo driver. It would be easy to do so, but it requires knowing
which format is meant by the GUID. Most format GUIDs are of the form
32595559-0000-0010-8000-00aa00389b71 that starts with a 4CC, but that's not
the case here.
Could you send me the output of
lsusb -v -d 0bda:58f4
running as root if possible ?
--
Regards,
Laurent Pinchart
Dear Laurent,
On 03/20/18 14:30, Laurent Pinchart wrote:
> On Tuesday, 20 March 2018 14:20:14 EET Paul Menzel wrote:
>> On the Dell XPS 13 9370, Linux 4.16-rc6 outputs the messages below.
>>
>> ```
[…]
>> [ 2.340736] input: Integrated_Webcam_HD: Integrate as
>> /devices/pci0000:00/0000:00:14.0/usb1/1-5/1-5:1.0/input/input9
>> [ 2.341447] uvcvideo: Unknown video format
>> 00000032-0002-0010-8000-00aa00389b71 >> [ 2.341450] uvcvideo: Found UVC 1.00 device Integrated_Webcam_HD
>> (0bda:58f4)
[…]
>> ```
>>
>> Please tell me, what I can do to improve the situation.
>
> Some vendors routinely implement new formats without bothering to send a patch
> for the uvcvideo driver. It would be easy to do so, but it requires knowing
> which format is meant by the GUID. Most format GUIDs are of the form
> 32595559-0000-0010-8000-00aa00389b71 that starts with a 4CC, but that's not
> the case here.
I am adding Mario to the receiver list, though he is currently on vacation.
> Could you send me the output of
>
> lsusb -v -d 0bda:58f4
>
> running as root if possible ?
Sure, please find it attached.
Kind regards,
Paul
Le mardi 20 mars 2018 à 13:20 +0100, Paul Menzel a écrit :
> Dear Linux folks,
>
>
> On the Dell XPS 13 9370, Linux 4.16-rc6 outputs the messages below.
>
> ```
> [ 2.338094] calling uvc_init+0x0/0x1000 [uvcvideo] @ 295
> [ 2.338569] calling iTCO_wdt_init_module+0x0/0x1000 [iTCO_wdt] @ 280
> [ 2.338570] iTCO_wdt: Intel TCO WatchDog Timer Driver v1.11
> [ 2.338713] iTCO_wdt: Found a Intel PCH TCO device (Version=4,
> TCOBASE=0x0400)
> [ 2.338755] uvcvideo: Found UVC 1.00 device Integrated_Webcam_HD
> (0bda:58f4)
> [ 2.338827] iTCO_wdt: initialized. heartbeat=30 sec (nowayout=0)
> [ 2.338851] initcall iTCO_wdt_init_module+0x0/0x1000 [iTCO_wdt]
> returned 0 after 271 usecs
> [ 2.340669] uvcvideo 1-5:1.0: Entity type for entity Extension 4 was
> not initialized!
> [ 2.340670] uvcvideo 1-5:1.0: Entity type for entity Extension 7 was
> not initialized!
> [ 2.340672] uvcvideo 1-5:1.0: Entity type for entity Processing 2 was
> not initialized!
> [ 2.340673] uvcvideo 1-5:1.0: Entity type for entity Camera 1 was not
> initialized!
> [ 2.340736] input: Integrated_Webcam_HD: Integrate as
> /devices/pci0000:00/0000:00:14.0/usb1/1-5/1-5:1.0/input/input9
> [ 2.341447] uvcvideo: Unknown video format
> 00000032-0002-0010-8000-00aa00389b71
While the 0002 is suspicious, this is pretty close to a color format.
I've recently come across of similar format using D3DFORMAT instead of
GUID. According to the vendor*, this camera module includes an infrared
camera (340x340), so I suspect this is to specify the format it
outputs. A good guess to start with would be that this is
D3DFMT_X8L8V8U8 (0x32). To test it, you could map this
V4L2_PIX_FMT_YUV32/xRGB and see if the driver is happy with the buffer
size. Then render it to make sure it looks some image of some sort. A
new format will need to be defined as this format is in the wrong
order, and is ambiguous (it may mean AYUV or xYUV). I'm not sure if we
need specific formats to differentiate infrared data from YUV images,
need to be discussed.
*https://dustinweb.azureedge.net/media/338953/xps-13-9370.pdf
> [ 2.341450] uvcvideo: Found UVC 1.00 device Integrated_Webcam_HD
> (0bda:58f4)
> [ 2.343371] uvcvideo: Unable to create debugfs 1-2 directory.
> [ 2.343420] uvcvideo 1-5:1.2: Entity type for entity Extension 10 was
> not initialized!
> [ 2.343422] uvcvideo 1-5:1.2: Entity type for entity Extension 12 was
> not initialized!
> [ 2.343423] uvcvideo 1-5:1.2: Entity type for entity Processing 9 was
> not initialized!
> [ 2.343424] uvcvideo 1-5:1.2: Entity type for entity Camera 11 was
> not initialized!
> [ 2.343472] input: Integrated_Webcam_HD: Integrate as
> /devices/pci0000:00/0000:00:14.0/usb1/1-5/1-5:1.2/input/input10
> [ 2.343496] usbcore: registered new interface driver uvcvideo
> [ 2.343496] USB Video Class driver (1.1.1)
> [ 2.343501] initcall uvc_init+0x0/0x1000 [uvcvideo] returned 0 after
> 5275 usecs
> ```
>
> Please tell me, what I can do to improve the situation.
>
>
> Kind regards,
>
> Paul
>
Hi Nicolas,
On Tuesday, 20 March 2018 19:45:51 EET Nicolas Dufresne wrote:
> Le mardi 20 mars 2018 ? 13:20 +0100, Paul Menzel a ?crit :
> > Dear Linux folks,
> >
> >
> > On the Dell XPS 13 9370, Linux 4.16-rc6 outputs the messages below.
> >
> > ```
> > [ 2.338094] calling uvc_init+0x0/0x1000 [uvcvideo] @ 295
> > [ 2.338569] calling iTCO_wdt_init_module+0x0/0x1000 [iTCO_wdt] @ 280
> > [ 2.338570] iTCO_wdt: Intel TCO WatchDog Timer Driver v1.11
> > [ 2.338713] iTCO_wdt: Found a Intel PCH TCO device (Version=4,
> > TCOBASE=0x0400)
> > [ 2.338755] uvcvideo: Found UVC 1.00 device Integrated_Webcam_HD
> > (0bda:58f4)
> > [ 2.338827] iTCO_wdt: initialized. heartbeat=30 sec (nowayout=0)
> > [ 2.338851] initcall iTCO_wdt_init_module+0x0/0x1000 [iTCO_wdt]
> > returned 0 after 271 usecs
> > [ 2.340669] uvcvideo 1-5:1.0: Entity type for entity Extension 4 was
> > not initialized!
> > [ 2.340670] uvcvideo 1-5:1.0: Entity type for entity Extension 7 was
> > not initialized!
> > [ 2.340672] uvcvideo 1-5:1.0: Entity type for entity Processing 2 was
> > not initialized!
> > [ 2.340673] uvcvideo 1-5:1.0: Entity type for entity Camera 1 was not
> > initialized!
> > [ 2.340736] input: Integrated_Webcam_HD: Integrate as
> > /devices/pci0000:00/0000:00:14.0/usb1/1-5/1-5:1.0/input/input9
> > [ 2.341447] uvcvideo: Unknown video format
> > 00000032-0002-0010-8000-00aa00389b71
>
> While the 0002 is suspicious, this is pretty close to a color format.
> I've recently come across of similar format using D3DFORMAT instead of
> GUID. According to the vendor*, this camera module includes an infrared
> camera (340x340), so I suspect this is to specify the format it
> outputs. A good guess to start with would be that this is
> D3DFMT_X8L8V8U8 (0x32).
Isn't 0x32 D3DFMT_L8, not D3DFMT_X8L8V8U8 ?
> To test it, you could map this
> V4L2_PIX_FMT_YUV32/xRGB and see if the driver is happy with the buffer
> size.
VideoStreaming Interface Descriptor:
bLength 30
bDescriptorType 36
bDescriptorSubtype 5 (FRAME_UNCOMPRESSED)
bFrameIndex 1
bmCapabilities 0x00
Still image unsupported
wWidth 340
wHeight 340
dwMinBitRate 55488000
dwMaxBitRate 55488000
dwMaxVideoFrameBufferSize 115600
dwDefaultFrameInterval 166666
bFrameIntervalType 1
dwFrameInterval( 0) 166666
340*340 is 115600, so this should be a 8-bit format.
> Then render it to make sure it looks some image of some sort. A
> new format will need to be defined as this format is in the wrong
> order, and is ambiguous (it may mean AYUV or xYUV). I'm not sure if we
> need specific formats to differentiate infrared data from YUV images,
> need to be discussed.
If the format is indeed D3DFMT_L8, it should map to V4L2_PIX_FMT_GREY (8-bit
luminance). I suspect the camera transmits a depth map though.
> *https://dustinweb.azureedge.net/media/338953/xps-13-9370.pdf
>
> > [ 2.341450] uvcvideo: Found UVC 1.00 device Integrated_Webcam_HD
> > (0bda:58f4)
> > [ 2.343371] uvcvideo: Unable to create debugfs 1-2 directory.
> > [ 2.343420] uvcvideo 1-5:1.2: Entity type for entity Extension 10 was
> > not initialized!
> > [ 2.343422] uvcvideo 1-5:1.2: Entity type for entity Extension 12 was
> > not initialized!
> > [ 2.343423] uvcvideo 1-5:1.2: Entity type for entity Processing 9 was
> > not initialized!
> > [ 2.343424] uvcvideo 1-5:1.2: Entity type for entity Camera 11 was
> > not initialized!
> > [ 2.343472] input: Integrated_Webcam_HD: Integrate as
> > /devices/pci0000:00/0000:00:14.0/usb1/1-5/1-5:1.2/input/input10
> > [ 2.343496] usbcore: registered new interface driver uvcvideo
> > [ 2.343496] USB Video Class driver (1.1.1)
> > [ 2.343501] initcall uvc_init+0x0/0x1000 [uvcvideo] returned 0 after
> > 5275 usecs
> > ```
> >
> > Please tell me, what I can do to improve the situation.
--
Regards,
Laurent Pinchart
Le mardi 20 mars 2018 à 20:04 +0200, Laurent Pinchart a écrit :
> Hi Nicolas,
>
> On Tuesday, 20 March 2018 19:45:51 EET Nicolas Dufresne wrote:
> > Le mardi 20 mars 2018 à 13:20 +0100, Paul Menzel a écrit :
> > > Dear Linux folks,
> > >
> > >
> > > On the Dell XPS 13 9370, Linux 4.16-rc6 outputs the messages below.
> > >
> > > ```
> > > [ 2.338094] calling uvc_init+0x0/0x1000 [uvcvideo] @ 295
> > > [ 2.338569] calling iTCO_wdt_init_module+0x0/0x1000 [iTCO_wdt] @ 280
> > > [ 2.338570] iTCO_wdt: Intel TCO WatchDog Timer Driver v1.11
> > > [ 2.338713] iTCO_wdt: Found a Intel PCH TCO device (Version=4,
> > > TCOBASE=0x0400)
> > > [ 2.338755] uvcvideo: Found UVC 1.00 device Integrated_Webcam_HD
> > > (0bda:58f4)
> > > [ 2.338827] iTCO_wdt: initialized. heartbeat=30 sec (nowayout=0)
> > > [ 2.338851] initcall iTCO_wdt_init_module+0x0/0x1000 [iTCO_wdt]
> > > returned 0 after 271 usecs
> > > [ 2.340669] uvcvideo 1-5:1.0: Entity type for entity Extension 4 was
> > > not initialized!
> > > [ 2.340670] uvcvideo 1-5:1.0: Entity type for entity Extension 7 was
> > > not initialized!
> > > [ 2.340672] uvcvideo 1-5:1.0: Entity type for entity Processing 2 was
> > > not initialized!
> > > [ 2.340673] uvcvideo 1-5:1.0: Entity type for entity Camera 1 was not
> > > initialized!
> > > [ 2.340736] input: Integrated_Webcam_HD: Integrate as
> > > /devices/pci0000:00/0000:00:14.0/usb1/1-5/1-5:1.0/input/input9
> > > [ 2.341447] uvcvideo: Unknown video format
> > > 00000032-0002-0010-8000-00aa00389b71
> >
> > While the 0002 is suspicious, this is pretty close to a color format.
> > I've recently come across of similar format using D3DFORMAT instead of
> > GUID. According to the vendor*, this camera module includes an infrared
> > camera (340x340), so I suspect this is to specify the format it
> > outputs. A good guess to start with would be that this is
> > D3DFMT_X8L8V8U8 (0x32).
>
> Isn't 0x32 D3DFMT_L8, not D3DFMT_X8L8V8U8 ?
You are right, sorry about that, I totally miss-translate. It felt
weird. This is much more likely yes. So maybe it's the same mapping
(but with the -00002- instead) as what I added for the HoloLense
Camera.
>
> > To test it, you could map this
> > V4L2_PIX_FMT_YUV32/xRGB and see if the driver is happy with the buffer
> > size.
>
> VideoStreaming Interface Descriptor:
> bLength 30
> bDescriptorType 36
> bDescriptorSubtype 5 (FRAME_UNCOMPRESSED)
> bFrameIndex 1
> bmCapabilities 0x00
> Still image unsupported
> wWidth 340
> wHeight 340
> dwMinBitRate 55488000
> dwMaxBitRate 55488000
> dwMaxVideoFrameBufferSize 115600
> dwDefaultFrameInterval 166666
> bFrameIntervalType 1
> dwFrameInterval( 0) 166666
>
> 340*340 is 115600, so this should be a 8-bit format.
Indeed, that matches.
>
> > Then render it to make sure it looks some image of some sort. A
> > new format will need to be defined as this format is in the wrong
> > order, and is ambiguous (it may mean AYUV or xYUV). I'm not sure if we
> > need specific formats to differentiate infrared data from YUV images,
> > need to be discussed.
>
> If the format is indeed D3DFMT_L8, it should map to V4L2_PIX_FMT_GREY (8-bit
> luminance). I suspect the camera transmits a depth map though.
I wonder if we should think of a way to tell userspace this is fnfrared
data rather then black and white ?
>
> > *https://dustinweb.azureedge.net/media/338953/xps-13-9370.pdf
> >
> > > [ 2.341450] uvcvideo: Found UVC 1.00 device Integrated_Webcam_HD
> > > (0bda:58f4)
> > > [ 2.343371] uvcvideo: Unable to create debugfs 1-2 directory.
> > > [ 2.343420] uvcvideo 1-5:1.2: Entity type for entity Extension 10 was
> > > not initialized!
> > > [ 2.343422] uvcvideo 1-5:1.2: Entity type for entity Extension 12 was
> > > not initialized!
> > > [ 2.343423] uvcvideo 1-5:1.2: Entity type for entity Processing 9 was
> > > not initialized!
> > > [ 2.343424] uvcvideo 1-5:1.2: Entity type for entity Camera 11 was
> > > not initialized!
> > > [ 2.343472] input: Integrated_Webcam_HD: Integrate as
> > > /devices/pci0000:00/0000:00:14.0/usb1/1-5/1-5:1.2/input/input10
> > > [ 2.343496] usbcore: registered new interface driver uvcvideo
> > > [ 2.343496] USB Video Class driver (1.1.1)
> > > [ 2.343501] initcall uvc_init+0x0/0x1000 [uvcvideo] returned 0 after
> > > 5275 usecs
> > > ```
> > >
> > > Please tell me, what I can do to improve the situation.
>
>
Hi Nicolas,
On Wednesday, 21 March 2018 05:38:59 EET Nicolas Dufresne wrote:
> Le mardi 20 mars 2018 ? 20:04 +0200, Laurent Pinchart a ?crit :
> > On Tuesday, 20 March 2018 19:45:51 EET Nicolas Dufresne wrote:
> > > Le mardi 20 mars 2018 ? 13:20 +0100, Paul Menzel a ?crit :
> > > > Dear Linux folks,
> > > >
> > > >
> > > > On the Dell XPS 13 9370, Linux 4.16-rc6 outputs the messages below.
> > > >
> > > > ```
> > > > [ 2.338094] calling uvc_init+0x0/0x1000 [uvcvideo] @ 295
> > > > [ 2.338569] calling iTCO_wdt_init_module+0x0/0x1000 [iTCO_wdt] @
> > > > 280
> > > > [ 2.338570] iTCO_wdt: Intel TCO WatchDog Timer Driver v1.11
> > > > [ 2.338713] iTCO_wdt: Found a Intel PCH TCO device (Version=4,
> > > > TCOBASE=0x0400)
> > > > [ 2.338755] uvcvideo: Found UVC 1.00 device Integrated_Webcam_HD
> > > > (0bda:58f4)
> > > > [ 2.338827] iTCO_wdt: initialized. heartbeat=30 sec (nowayout=0)
> > > > [ 2.338851] initcall iTCO_wdt_init_module+0x0/0x1000 [iTCO_wdt]
> > > > returned 0 after 271 usecs
> > > > [ 2.340669] uvcvideo 1-5:1.0: Entity type for entity Extension 4
> > > > was
> > > > not initialized!
> > > > [ 2.340670] uvcvideo 1-5:1.0: Entity type for entity Extension 7
> > > > was
> > > > not initialized!
> > > > [ 2.340672] uvcvideo 1-5:1.0: Entity type for entity Processing 2
> > > > was
> > > > not initialized!
> > > > [ 2.340673] uvcvideo 1-5:1.0: Entity type for entity Camera 1 was
> > > > not
> > > > initialized!
> > > > [ 2.340736] input: Integrated_Webcam_HD: Integrate as
> > > > /devices/pci0000:00/0000:00:14.0/usb1/1-5/1-5:1.0/input/input9
> > > > [ 2.341447] uvcvideo: Unknown video format
> > > > 00000032-0002-0010-8000-00aa00389b71
> > >
> > > While the 0002 is suspicious, this is pretty close to a color format.
> > > I've recently come across of similar format using D3DFORMAT instead of
> > > GUID. According to the vendor*, this camera module includes an infrared
> > > camera (340x340), so I suspect this is to specify the format it
> > > outputs. A good guess to start with would be that this is
> > > D3DFMT_X8L8V8U8 (0x32).
> >
> > Isn't 0x32 D3DFMT_L8, not D3DFMT_X8L8V8U8 ?
>
> You are right, sorry about that, I totally miss-translate. It felt
> weird. This is much more likely yes. So maybe it's the same mapping
> (but with the -00002- instead) as what I added for the HoloLense
> Camera.
>
> > > To test it, you could map this
> > > V4L2_PIX_FMT_YUV32/xRGB and see if the driver is happy with the buffer
> > > size.
> >
> > VideoStreaming Interface Descriptor:
> > bLength 30
> > bDescriptorType 36
> > bDescriptorSubtype 5 (FRAME_UNCOMPRESSED)
> > bFrameIndex 1
> > bmCapabilities 0x00
> >
> > Still image unsupported
> >
> > wWidth 340
> > wHeight 340
> > dwMinBitRate 55488000
> > dwMaxBitRate 55488000
> > dwMaxVideoFrameBufferSize 115600
> > dwDefaultFrameInterval 166666
> > bFrameIntervalType 1
> > dwFrameInterval( 0) 166666
> >
> > 340*340 is 115600, so this should be a 8-bit format.
>
> Indeed, that matches.
>
> > > Then render it to make sure it looks some image of some sort. A
> > > new format will need to be defined as this format is in the wrong
> > > order, and is ambiguous (it may mean AYUV or xYUV). I'm not sure if we
> > > need specific formats to differentiate infrared data from YUV images,
> > > need to be discussed.
> >
> > If the format is indeed D3DFMT_L8, it should map to V4L2_PIX_FMT_GREY
> > (8-bit luminance). I suspect the camera transmits a depth map though.
>
> I wonder if we should think of a way to tell userspace this is fnfrared
> data rather then black and white ?
I think we need such a mechanism, yes. Would you like to propose one ? :-)
I've found https://www.magnumdb.com/search?q=value%3A
%2200000032-0002-0010-8000-00aa00389b71%22 and https://docs.microsoft.com/en-us/windows-hardware/drivers/stream/infrared-stream-support-in-uvc that confirm
this is a 8-bit IR format.
> > > *https://dustinweb.azureedge.net/media/338953/xps-13-9370.pdf
> > >
> > > > [ 2.341450] uvcvideo: Found UVC 1.00 device Integrated_Webcam_HD
> > > > (0bda:58f4)
> > > > [ 2.343371] uvcvideo: Unable to create debugfs 1-2 directory.
> > > > [ 2.343420] uvcvideo 1-5:1.2: Entity type for entity Extension 10
> > > > was
> > > > not initialized!
> > > > [ 2.343422] uvcvideo 1-5:1.2: Entity type for entity Extension 12
> > > > was
> > > > not initialized!
> > > > [ 2.343423] uvcvideo 1-5:1.2: Entity type for entity Processing 9
> > > > was
> > > > not initialized!
> > > > [ 2.343424] uvcvideo 1-5:1.2: Entity type for entity Camera 11 was
> > > > not initialized!
> > > > [ 2.343472] input: Integrated_Webcam_HD: Integrate as
> > > > /devices/pci0000:00/0000:00:14.0/usb1/1-5/1-5:1.2/input/input10
> > > > [ 2.343496] usbcore: registered new interface driver uvcvideo
> > > > [ 2.343496] USB Video Class driver (1.1.1)
> > > > [ 2.343501] initcall uvc_init+0x0/0x1000 [uvcvideo] returned 0
> > > > after
> > > > 5275 usecs
> > > > ```
> > > >
> > > > Please tell me, what I can do to improve the situation.
--
Regards,
Laurent Pinchart
Hi Paul,
On Tuesday, 20 March 2018 18:46:24 EET Paul Menzel wrote:
> On 03/20/18 14:30, Laurent Pinchart wrote:
> > On Tuesday, 20 March 2018 14:20:14 EET Paul Menzel wrote:
> >> On the Dell XPS 13 9370, Linux 4.16-rc6 outputs the messages below.
> >>
> >> ```
>
> […]
>
> >> [ 2.340736] input: Integrated_Webcam_HD: Integrate as
> >> /devices/pci0000:00/0000:00:14.0/usb1/1-5/1-5:1.0/input/input9
> >> [ 2.341447] uvcvideo: Unknown video format
> >> 00000032-0002-0010-8000-00aa00389b71 >> [ 2.341450] uvcvideo: Found
> >> UVC 1.00 device Integrated_Webcam_HD (0bda:58f4)
>
> […]
>
> >> ```
> >>
> >> Please tell me, what I can do to improve the situation.
> >
> > Some vendors routinely implement new formats without bothering to send a
> > patch for the uvcvideo driver. It would be easy to do so, but it requires
> > knowing which format is meant by the GUID. Most format GUIDs are of the
> > form 32595559-0000-0010-8000-00aa00389b71 that starts with a 4CC, but
> > that's not the case here.
>
> I am adding Mario to the receiver list, though he is currently on vacation.
>
> > Could you send me the output of
> >
> > lsusb -v -d 0bda:58f4
> >
> > running as root if possible ?
>
> Sure, please find it attached.
Thank you.
Could you please try the following patch ?
commit 7b3dea984b380f5b4b5c1956a9c6c23966af2149
Author: Laurent Pinchart <[email protected]>
Date: Wed Mar 21 11:16:40 2018 +0200
media: uvcvideo: Add KSMedia 8-bit IR format support
Add support for the 8-bit IR format GUID defined in the Microsoft Kernel
Streaming Media API.
Reported-by: Paul Menzel <[email protected]>
Signed-off-by: Laurent Pinchart <[email protected]>
diff --git a/drivers/media/usb/uvc/uvc_driver.c b/drivers/media/usb/uvc/uvc_driver.c
index 2469b49b2b30..3691d87ef869 100644
--- a/drivers/media/usb/uvc/uvc_driver.c
+++ b/drivers/media/usb/uvc/uvc_driver.c
@@ -99,6 +99,11 @@ static struct uvc_format_desc uvc_fmts[] = {
.guid = UVC_GUID_FORMAT_D3DFMT_L8,
.fcc = V4L2_PIX_FMT_GREY,
},
+ {
+ .name = "IR 8-bit (L8_IR)",
+ .guid = UVC_GUID_FORMAT_KSMEDIA_L8_IR,
+ .fcc = V4L2_PIX_FMT_GREY,
+ },
{
.name = "Greyscale 10-bit (Y10 )",
.guid = UVC_GUID_FORMAT_Y10,
diff --git a/drivers/media/usb/uvc/uvcvideo.h b/drivers/media/usb/uvc/uvcvideo.h
index be5cf179228b..6b955e0dd956 100644
--- a/drivers/media/usb/uvc/uvcvideo.h
+++ b/drivers/media/usb/uvc/uvcvideo.h
@@ -157,6 +157,9 @@
#define UVC_GUID_FORMAT_D3DFMT_L8 \
{0x32, 0x00, 0x00, 0x00, 0x00, 0x00, 0x10, 0x00, \
0x80, 0x00, 0x00, 0xaa, 0x00, 0x38, 0x9b, 0x71}
+#define UVC_GUID_FORMAT_KSMEDIA_L8_IR \
+ {0x32, 0x00, 0x00, 0x00, 0x02, 0x00, 0x10, 0x00, \
+ 0x80, 0x00, 0x00, 0xaa, 0x00, 0x38, 0x9b, 0x71}
/* ------------------------------------------------------------------------
--
Regards,
Laurent Pinchart
Dear Laurent,
On 03/21/2018 10:25 AM, Laurent Pinchart wrote:
> On Tuesday, 20 March 2018 18:46:24 EET Paul Menzel wrote:
>> On 03/20/18 14:30, Laurent Pinchart wrote:
>>> On Tuesday, 20 March 2018 14:20:14 EET Paul Menzel wrote:
>>>> On the Dell XPS 13 9370, Linux 4.16-rc6 outputs the messages below.
>>>>
>>>> ```
>>
>> […]
>>
>>>> [ 2.340736] input: Integrated_Webcam_HD: Integrate as
>>>> /devices/pci0000:00/0000:00:14.0/usb1/1-5/1-5:1.0/input/input9
>>>> [ 2.341447] uvcvideo: Unknown video format
>>>> 00000032-0002-0010-8000-00aa00389b71 >> [ 2.341450] uvcvideo: Found
>>>> UVC 1.00 device Integrated_Webcam_HD (0bda:58f4)
>>
>> […]
>>
>>>> ```
>>>>
>>>> Please tell me, what I can do to improve the situation.
>>>
>>> Some vendors routinely implement new formats without bothering to send a
>>> patch for the uvcvideo driver. It would be easy to do so, but it requires
>>> knowing which format is meant by the GUID. Most format GUIDs are of the
>>> form 32595559-0000-0010-8000-00aa00389b71 that starts with a 4CC, but
>>> that's not the case here.
>>
>> I am adding Mario to the receiver list, though he is currently on vacation.
>>
>>> Could you send me the output of
>>>
>>> lsusb -v -d 0bda:58f4
>>>
>>> running as root if possible ?
>>
>> Sure, please find it attached.
>
> Thank you.
>
> Could you please try the following patch ?
>
> commit 7b3dea984b380f5b4b5c1956a9c6c23966af2149
> Author: Laurent Pinchart <[email protected]>
> Date: Wed Mar 21 11:16:40 2018 +0200
>
> media: uvcvideo: Add KSMedia 8-bit IR format support
>
> Add support for the 8-bit IR format GUID defined in the Microsoft Kernel
> Streaming Media API.
>
> Reported-by: Paul Menzel <[email protected]>
> Signed-off-by: Laurent Pinchart <[email protected]>
>
> diff --git a/drivers/media/usb/uvc/uvc_driver.c b/drivers/media/usb/uvc/uvc_driver.c
> index 2469b49b2b30..3691d87ef869 100644
> --- a/drivers/media/usb/uvc/uvc_driver.c
> +++ b/drivers/media/usb/uvc/uvc_driver.c
> @@ -99,6 +99,11 @@ static struct uvc_format_desc uvc_fmts[] = {
> .guid = UVC_GUID_FORMAT_D3DFMT_L8,
> .fcc = V4L2_PIX_FMT_GREY,
> },
> + {
> + .name = "IR 8-bit (L8_IR)",
> + .guid = UVC_GUID_FORMAT_KSMEDIA_L8_IR,
> + .fcc = V4L2_PIX_FMT_GREY,
> + },
> {
> .name = "Greyscale 10-bit (Y10 )",
> .guid = UVC_GUID_FORMAT_Y10,
> diff --git a/drivers/media/usb/uvc/uvcvideo.h b/drivers/media/usb/uvc/uvcvideo.h
> index be5cf179228b..6b955e0dd956 100644
> --- a/drivers/media/usb/uvc/uvcvideo.h
> +++ b/drivers/media/usb/uvc/uvcvideo.h
> @@ -157,6 +157,9 @@
> #define UVC_GUID_FORMAT_D3DFMT_L8 \
> {0x32, 0x00, 0x00, 0x00, 0x00, 0x00, 0x10, 0x00, \
> 0x80, 0x00, 0x00, 0xaa, 0x00, 0x38, 0x9b, 0x71}
> +#define UVC_GUID_FORMAT_KSMEDIA_L8_IR \
> + {0x32, 0x00, 0x00, 0x00, 0x02, 0x00, 0x10, 0x00, \
> + 0x80, 0x00, 0x00, 0xaa, 0x00, 0x38, 0x9b, 0x71}
>
>
> /* ------------------------------------------------------------------------
Sure. After fighting how to apply with Mozilla Thunderbird as my mailer
– hints are welcome –, the warning is gone.
```
[ 2.569788] calling uvc_init+0x0/0x1000 [uvcvideo] @ 297
[ 2.570011] calling cryptd_init+0x0/0x1000 [cryptd] @ 287
[ 2.570018] cryptd: max_cpu_qlen set to 1000
[ 2.570022] initcall cryptd_init+0x0/0x1000 [cryptd] returned 0 after
7 usecs
[ 2.570030] calling init_nls_cp437+0x0/0x1000 [nls_cp437] @ 332
[ 2.570033] initcall init_nls_cp437+0x0/0x1000 [nls_cp437] returned 0
after 0 usecs
[ 2.570502] uvcvideo: Found UVC 1.00 device Integrated_Webcam_HD
(0bda:58f4)
[ 2.573583] uvcvideo 1-5:1.0: Entity type for entity Extension 4 was
not initialized!
[ 2.573585] uvcvideo 1-5:1.0: Entity type for entity Extension 7 was
not initialized!
[ 2.573586] uvcvideo 1-5:1.0: Entity type for entity Processing 2 was
not initialized!
[ 2.573587] uvcvideo 1-5:1.0: Entity type for entity Camera 1 was not
initialized!
[ 2.573652] input: Integrated_Webcam_HD: Integrate as
/devices/pci0000:00/0000:00:14.0/usb1/1-5/1-5:1.0/input/input10
[ 2.574192] uvcvideo: Found UVC 1.00 device Integrated_Webcam_HD
(0bda:58f4)
[ 2.575629] proc_thermal 0000:00:04.0: enabling device (0000 -> 0002)
[ 2.576052] uvcvideo: Unable to create debugfs 1-2 directory.
[ 2.576118] uvcvideo 1-5:1.2: Entity type for entity Extension 10 was
not initialized!
[ 2.576119] uvcvideo 1-5:1.2: Entity type for entity Extension 12 was
not initialized!
[ 2.576120] uvcvideo 1-5:1.2: Entity type for entity Processing 9 was
not initialized!
[ 2.576121] uvcvideo 1-5:1.2: Entity type for entity Camera 11 was
not initialized!
[ 2.576184] input: Integrated_Webcam_HD: Integrate as
/devices/pci0000:00/0000:00:14.0/usb1/1-5/1-5:1.2/input/input11
[ 2.576229] usbcore: registered new interface driver uvcvideo
[ 2.576230] USB Video Class driver (1.1.1)
[ 2.576236] initcall uvc_init+0x0/0x1000 [uvcvideo] returned 0 after
6290 usecs
```
Tested-by: Paul Menzel <[email protected]>
Kind regards,
Paul
Le mercredi 21 mars 2018 à 10:55 +0200, Laurent Pinchart a écrit :
> Hi Nicolas,
>
> On Wednesday, 21 March 2018 05:38:59 EET Nicolas Dufresne wrote:
> > Le mardi 20 mars 2018 à 20:04 +0200, Laurent Pinchart a écrit :
> > > On Tuesday, 20 March 2018 19:45:51 EET Nicolas Dufresne wrote:
> > > > Le mardi 20 mars 2018 à 13:20 +0100, Paul Menzel a écrit :
> > > > > Dear Linux folks,
> > > > >
> > > > >
> > > > > On the Dell XPS 13 9370, Linux 4.16-rc6 outputs the messages below.
> > > > >
> > > > > ```
> > > > > [ 2.338094] calling uvc_init+0x0/0x1000 [uvcvideo] @ 295
> > > > > [ 2.338569] calling iTCO_wdt_init_module+0x0/0x1000 [iTCO_wdt] @
> > > > > 280
> > > > > [ 2.338570] iTCO_wdt: Intel TCO WatchDog Timer Driver v1.11
> > > > > [ 2.338713] iTCO_wdt: Found a Intel PCH TCO device (Version=4,
> > > > > TCOBASE=0x0400)
> > > > > [ 2.338755] uvcvideo: Found UVC 1.00 device Integrated_Webcam_HD
> > > > > (0bda:58f4)
> > > > > [ 2.338827] iTCO_wdt: initialized. heartbeat=30 sec (nowayout=0)
> > > > > [ 2.338851] initcall iTCO_wdt_init_module+0x0/0x1000 [iTCO_wdt]
> > > > > returned 0 after 271 usecs
> > > > > [ 2.340669] uvcvideo 1-5:1.0: Entity type for entity Extension 4
> > > > > was
> > > > > not initialized!
> > > > > [ 2.340670] uvcvideo 1-5:1.0: Entity type for entity Extension 7
> > > > > was
> > > > > not initialized!
> > > > > [ 2.340672] uvcvideo 1-5:1.0: Entity type for entity Processing 2
> > > > > was
> > > > > not initialized!
> > > > > [ 2.340673] uvcvideo 1-5:1.0: Entity type for entity Camera 1 was
> > > > > not
> > > > > initialized!
> > > > > [ 2.340736] input: Integrated_Webcam_HD: Integrate as
> > > > > /devices/pci0000:00/0000:00:14.0/usb1/1-5/1-5:1.0/input/input9
> > > > > [ 2.341447] uvcvideo: Unknown video format
> > > > > 00000032-0002-0010-8000-00aa00389b71
> > > >
> > > > While the 0002 is suspicious, this is pretty close to a color format.
> > > > I've recently come across of similar format using D3DFORMAT instead of
> > > > GUID. According to the vendor*, this camera module includes an infrared
> > > > camera (340x340), so I suspect this is to specify the format it
> > > > outputs. A good guess to start with would be that this is
> > > > D3DFMT_X8L8V8U8 (0x32).
> > >
> > > Isn't 0x32 D3DFMT_L8, not D3DFMT_X8L8V8U8 ?
> >
> > You are right, sorry about that, I totally miss-translate. It felt
> > weird. This is much more likely yes. So maybe it's the same mapping
> > (but with the -00002- instead) as what I added for the HoloLense
> > Camera.
> >
> > > > To test it, you could map this
> > > > V4L2_PIX_FMT_YUV32/xRGB and see if the driver is happy with the buffer
> > > > size.
> > >
> > > VideoStreaming Interface Descriptor:
> > > bLength 30
> > > bDescriptorType 36
> > > bDescriptorSubtype 5 (FRAME_UNCOMPRESSED)
> > > bFrameIndex 1
> > > bmCapabilities 0x00
> > >
> > > Still image unsupported
> > >
> > > wWidth 340
> > > wHeight 340
> > > dwMinBitRate 55488000
> > > dwMaxBitRate 55488000
> > > dwMaxVideoFrameBufferSize 115600
> > > dwDefaultFrameInterval 166666
> > > bFrameIntervalType 1
> > > dwFrameInterval( 0) 166666
> > >
> > > 340*340 is 115600, so this should be a 8-bit format.
> >
> > Indeed, that matches.
> >
> > > > Then render it to make sure it looks some image of some sort. A
> > > > new format will need to be defined as this format is in the wrong
> > > > order, and is ambiguous (it may mean AYUV or xYUV). I'm not sure if we
> > > > need specific formats to differentiate infrared data from YUV images,
> > > > need to be discussed.
> > >
> > > If the format is indeed D3DFMT_L8, it should map to V4L2_PIX_FMT_GREY
> > > (8-bit luminance). I suspect the camera transmits a depth map though.
> >
> > I wonder if we should think of a way to tell userspace this is fnfrared
> > data rather then black and white ?
>
> I think we need such a mechanism, yes. Would you like to propose one ? :-)
Ok, meanwhile I've looked over how this camera was used. It seems
that's it's combined with a IR light in order to create a near field
depth. As we already exposes couple of depth sensors as GREY, I think
your patch is ok, and should be merged. It's not really clear in
general how the driver can really figure-out what type of data is
delivered. So I'm not sure where to start.
>
> I've found https://www.magnumdb.com/search?q=value%3A
> %2200000032-0002-0010-8000-00aa00389b71%22 and https://docs.microsoft.com/en-us/windows-hardware/drivers/stream/infrared-stream-support-in-uvc that confirm
> this is a 8-bit IR format.
>
> > > > *https://dustinweb.azureedge.net/media/338953/xps-13-9370.pdf
> > > >
> > > > > [ 2.341450] uvcvideo: Found UVC 1.00 device Integrated_Webcam_HD
> > > > > (0bda:58f4)
> > > > > [ 2.343371] uvcvideo: Unable to create debugfs 1-2 directory.
> > > > > [ 2.343420] uvcvideo 1-5:1.2: Entity type for entity Extension 10
> > > > > was
> > > > > not initialized!
> > > > > [ 2.343422] uvcvideo 1-5:1.2: Entity type for entity Extension 12
> > > > > was
> > > > > not initialized!
> > > > > [ 2.343423] uvcvideo 1-5:1.2: Entity type for entity Processing 9
> > > > > was
> > > > > not initialized!
> > > > > [ 2.343424] uvcvideo 1-5:1.2: Entity type for entity Camera 11 was
> > > > > not initialized!
> > > > > [ 2.343472] input: Integrated_Webcam_HD: Integrate as
> > > > > /devices/pci0000:00/0000:00:14.0/usb1/1-5/1-5:1.2/input/input10
> > > > > [ 2.343496] usbcore: registered new interface driver uvcvideo
> > > > > [ 2.343496] USB Video Class driver (1.1.1)
> > > > > [ 2.343501] initcall uvc_init+0x0/0x1000 [uvcvideo] returned 0
> > > > > after
> > > > > 5275 usecs
> > > > > ```
> > > > >
> > > > > Please tell me, what I can do to improve the situation.
>
>
> -----Original Message-----
> From: Paul Menzel [mailto:[email protected]]
> Sent: Wednesday, March 21, 2018 7:35 AM
> To: Laurent Pinchart <[email protected]>
> Cc: [email protected]; [email protected]; it+linux-
> [email protected]; Limonciello, Mario <[email protected]>
> Subject: Re: uvcvideo: Unknown video format,00000032-0002-0010-8000-
> 00aa00389b71
>
> Dear Laurent,
>
>
> On 03/21/2018 10:25 AM, Laurent Pinchart wrote:
>
> > On Tuesday, 20 March 2018 18:46:24 EET Paul Menzel wrote:
> >> On 03/20/18 14:30, Laurent Pinchart wrote:
> >>> On Tuesday, 20 March 2018 14:20:14 EET Paul Menzel wrote:
> >>>> On the Dell XPS 13 9370, Linux 4.16-rc6 outputs the messages below.
> >>>>
> >>>> ```
> >>
> >> […]
> >>
> >>>> [ 2.340736] input: Integrated_Webcam_HD: Integrate as
> >>>> /devices/pci0000:00/0000:00:14.0/usb1/1-5/1-5:1.0/input/input9
> >>>> [ 2.341447] uvcvideo: Unknown video format
> >>>> 00000032-0002-0010-8000-00aa00389b71 >> [ 2.341450] uvcvideo: Found
> >>>> UVC 1.00 device Integrated_Webcam_HD (0bda:58f4)
> >>
> >> […]
> >>
> >>>> ```
> >>>>
> >>>> Please tell me, what I can do to improve the situation.
> >>>
> >>> Some vendors routinely implement new formats without bothering to send a
> >>> patch for the uvcvideo driver. It would be easy to do so, but it requires
> >>> knowing which format is meant by the GUID. Most format GUIDs are of the
> >>> form 32595559-0000-0010-8000-00aa00389b71 that starts with a 4CC, but
> >>> that's not the case here.
> >>
> >> I am adding Mario to the receiver list, though he is currently on vacation.
> >>
> >>> Could you send me the output of
> >>>
> >>> lsusb -v -d 0bda:58f4
> >>>
> >>> running as root if possible ?
> >>
> >> Sure, please find it attached.
> >
> > Thank you.
> >
> > Could you please try the following patch ?
> >
> > commit 7b3dea984b380f5b4b5c1956a9c6c23966af2149
> > Author: Laurent Pinchart <[email protected]>
> > Date: Wed Mar 21 11:16:40 2018 +0200
> >
> > media: uvcvideo: Add KSMedia 8-bit IR format support
> >
> > Add support for the 8-bit IR format GUID defined in the Microsoft Kernel
> > Streaming Media API.
> >
> > Reported-by: Paul Menzel <[email protected]>
> > Signed-off-by: Laurent Pinchart <[email protected]>
> >
> > diff --git a/drivers/media/usb/uvc/uvc_driver.c
> b/drivers/media/usb/uvc/uvc_driver.c
> > index 2469b49b2b30..3691d87ef869 100644
> > --- a/drivers/media/usb/uvc/uvc_driver.c
> > +++ b/drivers/media/usb/uvc/uvc_driver.c
> > @@ -99,6 +99,11 @@ static struct uvc_format_desc uvc_fmts[] = {
> > .guid = UVC_GUID_FORMAT_D3DFMT_L8,
> > .fcc = V4L2_PIX_FMT_GREY,
> > },
> > + {
> > + .name = "IR 8-bit (L8_IR)",
> > + .guid = UVC_GUID_FORMAT_KSMEDIA_L8_IR,
> > + .fcc = V4L2_PIX_FMT_GREY,
> > + },
> > {
> > .name = "Greyscale 10-bit (Y10 )",
> > .guid = UVC_GUID_FORMAT_Y10,
> > diff --git a/drivers/media/usb/uvc/uvcvideo.h b/drivers/media/usb/uvc/uvcvideo.h
> > index be5cf179228b..6b955e0dd956 100644
> > --- a/drivers/media/usb/uvc/uvcvideo.h
> > +++ b/drivers/media/usb/uvc/uvcvideo.h
> > @@ -157,6 +157,9 @@
> > #define UVC_GUID_FORMAT_D3DFMT_L8 \
> > {0x32, 0x00, 0x00, 0x00, 0x00, 0x00, 0x10, 0x00, \
> > 0x80, 0x00, 0x00, 0xaa, 0x00, 0x38, 0x9b, 0x71}
> > +#define UVC_GUID_FORMAT_KSMEDIA_L8_IR \
> > + {0x32, 0x00, 0x00, 0x00, 0x02, 0x00, 0x10, 0x00, \
> > + 0x80, 0x00, 0x00, 0xaa, 0x00, 0x38, 0x9b, 0x71}
> >
> >
> > /* ------------------------------------------------------------------------
>
> Sure. After fighting how to apply with Mozilla Thunderbird as my mailer
> – hints are welcome –, the warning is gone.
>
> ```
> [ 2.569788] calling uvc_init+0x0/0x1000 [uvcvideo] @ 297
> [ 2.570011] calling cryptd_init+0x0/0x1000 [cryptd] @ 287
> [ 2.570018] cryptd: max_cpu_qlen set to 1000
> [ 2.570022] initcall cryptd_init+0x0/0x1000 [cryptd] returned 0 after
> 7 usecs
> [ 2.570030] calling init_nls_cp437+0x0/0x1000 [nls_cp437] @ 332
> [ 2.570033] initcall init_nls_cp437+0x0/0x1000 [nls_cp437] returned 0
> after 0 usecs
> [ 2.570502] uvcvideo: Found UVC 1.00 device Integrated_Webcam_HD
> (0bda:58f4)
> [ 2.573583] uvcvideo 1-5:1.0: Entity type for entity Extension 4 was
> not initialized!
> [ 2.573585] uvcvideo 1-5:1.0: Entity type for entity Extension 7 was
> not initialized!
> [ 2.573586] uvcvideo 1-5:1.0: Entity type for entity Processing 2 was
> not initialized!
> [ 2.573587] uvcvideo 1-5:1.0: Entity type for entity Camera 1 was not
> initialized!
> [ 2.573652] input: Integrated_Webcam_HD: Integrate as
> /devices/pci0000:00/0000:00:14.0/usb1/1-5/1-5:1.0/input/input10
> [ 2.574192] uvcvideo: Found UVC 1.00 device Integrated_Webcam_HD
> (0bda:58f4)
> [ 2.575629] proc_thermal 0000:00:04.0: enabling device (0000 -> 0002)
> [ 2.576052] uvcvideo: Unable to create debugfs 1-2 directory.
> [ 2.576118] uvcvideo 1-5:1.2: Entity type for entity Extension 10 was
> not initialized!
> [ 2.576119] uvcvideo 1-5:1.2: Entity type for entity Extension 12 was
> not initialized!
> [ 2.576120] uvcvideo 1-5:1.2: Entity type for entity Processing 9 was
> not initialized!
> [ 2.576121] uvcvideo 1-5:1.2: Entity type for entity Camera 11 was
> not initialized!
> [ 2.576184] input: Integrated_Webcam_HD: Integrate as
> /devices/pci0000:00/0000:00:14.0/usb1/1-5/1-5:1.2/input/input11
> [ 2.576229] usbcore: registered new interface driver uvcvideo
> [ 2.576230] USB Video Class driver (1.1.1)
> [ 2.576236] initcall uvc_init+0x0/0x1000 [uvcvideo] returned 0 after
> 6290 usecs
> ```
>
> Tested-by: Paul Menzel <[email protected]>
>
Great to hear. Laurent, when you submit this with Paul's tag would you
please consider to also CC @stable.