diff options
author | Luca Risolia <luca.risolia@studio.unibo.it> | 2007-03-26 15:12:04 -0400 |
---|---|---|
committer | Mauro Carvalho Chehab <mchehab@infradead.org> | 2007-04-27 14:45:08 -0400 |
commit | f423b9a86a6dd3d2bc08d78f4d21525a14c40a6b (patch) | |
tree | cac9dcd72bd298478559cdae7061b1a942cb4b0f /Documentation/video4linux | |
parent | 9ab7e323af9f9efad3e20a14faa4d947adfac381 (diff) |
V4L/DVB (5474): SN9C1xx driver updates
@ Don't assume that SOF headers can't cross packets boundaries
@ Fix compression quality selection
+ Add support for MI-0360 image sensor
* Documentation updates
@ Fix sysfs
@ MI0343 rewritten
* HV7131R color fixes and add new ABLC control
* Rename the archive from "sn9c102" to "sn9c1xx"
* fix typos
* better support for TAS5110D
@ fix OV7630 wrong colors
@ Don't return an error if no input buffers are enqueued yet on VIDIOC_STREAMON
* Add informations about colorspaces
* More appropriate error codes in case of failure of some system calls
* More precise hardware detection
* Add more informations about supported hardware in the documentation
+ More supported devices
+ Add support for HV7131R image sensor
Signed-off-by: Luca Risolia <luca.risolia@studio.unibo.it>
Signed-off-by: Mauro Carvalho Chehab <mchehab@infradead.org>
Diffstat (limited to 'Documentation/video4linux')
-rw-r--r-- | Documentation/video4linux/sn9c102.txt | 64 |
1 files changed, 38 insertions, 26 deletions
diff --git a/Documentation/video4linux/sn9c102.txt b/Documentation/video4linux/sn9c102.txt index 2913da3d087..5fe0ad7dfc2 100644 --- a/Documentation/video4linux/sn9c102.txt +++ b/Documentation/video4linux/sn9c102.txt | |||
@@ -25,7 +25,7 @@ Index | |||
25 | 25 | ||
26 | 1. Copyright | 26 | 1. Copyright |
27 | ============ | 27 | ============ |
28 | Copyright (C) 2004-2006 by Luca Risolia <luca.risolia@studio.unibo.it> | 28 | Copyright (C) 2004-2007 by Luca Risolia <luca.risolia@studio.unibo.it> |
29 | 29 | ||
30 | 30 | ||
31 | 2. Disclaimer | 31 | 2. Disclaimer |
@@ -216,10 +216,10 @@ Description: Debugging information level, from 0 to 3: | |||
216 | 1 = critical errors | 216 | 1 = critical errors |
217 | 2 = significant informations | 217 | 2 = significant informations |
218 | 3 = more verbose messages | 218 | 3 = more verbose messages |
219 | Level 3 is useful for testing only, when only one device | 219 | Level 3 is useful for testing only. It also shows some more |
220 | is used. It also shows some more informations about the | 220 | informations about the hardware being detected. |
221 | hardware being detected. This parameter can be changed at | 221 | This parameter can be changed at runtime thanks to the /sys |
222 | runtime thanks to the /sys filesystem interface. | 222 | filesystem interface. |
223 | Default: 2 | 223 | Default: 2 |
224 | ------------------------------------------------------------------------------- | 224 | ------------------------------------------------------------------------------- |
225 | 225 | ||
@@ -235,7 +235,7 @@ created in the /sys/class/video4linux/videoX directory. You can set the green | |||
235 | channel's gain by writing the desired value to it. The value may range from 0 | 235 | channel's gain by writing the desired value to it. The value may range from 0 |
236 | to 15 for the SN9C101 or SN9C102 bridges, from 0 to 127 for the SN9C103, | 236 | to 15 for the SN9C101 or SN9C102 bridges, from 0 to 127 for the SN9C103, |
237 | SN9C105 and SN9C120 bridges. | 237 | SN9C105 and SN9C120 bridges. |
238 | Similarly, only for the SN9C103, SN9C105 and SN9120 controllers, blue and red | 238 | Similarly, only for the SN9C103, SN9C105 and SN9C120 controllers, blue and red |
239 | gain control files are available in the same directory, for which accepted | 239 | gain control files are available in the same directory, for which accepted |
240 | values may range from 0 to 127. | 240 | values may range from 0 to 127. |
241 | 241 | ||
@@ -402,38 +402,49 @@ Vendor ID Product ID | |||
402 | 0x0c45 0x60bc | 402 | 0x0c45 0x60bc |
403 | 0x0c45 0x60be | 403 | 0x0c45 0x60be |
404 | 0x0c45 0x60c0 | 404 | 0x0c45 0x60c0 |
405 | 0x0c45 0x60c2 | ||
405 | 0x0c45 0x60c8 | 406 | 0x0c45 0x60c8 |
406 | 0x0c45 0x60cc | 407 | 0x0c45 0x60cc |
407 | 0x0c45 0x60ea | 408 | 0x0c45 0x60ea |
408 | 0x0c45 0x60ec | 409 | 0x0c45 0x60ec |
410 | 0x0c45 0x60ef | ||
409 | 0x0c45 0x60fa | 411 | 0x0c45 0x60fa |
410 | 0x0c45 0x60fb | 412 | 0x0c45 0x60fb |
411 | 0x0c45 0x60fc | 413 | 0x0c45 0x60fc |
412 | 0x0c45 0x60fe | 414 | 0x0c45 0x60fe |
415 | 0x0c45 0x6102 | ||
416 | 0x0c45 0x6108 | ||
417 | 0x0c45 0x610f | ||
413 | 0x0c45 0x6130 | 418 | 0x0c45 0x6130 |
419 | 0x0c45 0x6138 | ||
414 | 0x0c45 0x613a | 420 | 0x0c45 0x613a |
415 | 0x0c45 0x613b | 421 | 0x0c45 0x613b |
416 | 0x0c45 0x613c | 422 | 0x0c45 0x613c |
417 | 0x0c45 0x613e | 423 | 0x0c45 0x613e |
418 | 424 | ||
419 | The list above does not imply that all those devices work with this driver: up | 425 | The list above does not imply that all those devices work with this driver: up |
420 | until now only the ones that assemble the following image sensors are | 426 | until now only the ones that assemble the following pairs of SN9C1xx bridges |
421 | supported; kernel messages will always tell you whether this is the case (see | 427 | and image sensors are supported; kernel messages will always tell you whether |
422 | "Module loading" paragraph): | 428 | this is the case (see "Module loading" paragraph): |
423 | 429 | ||
424 | Model Manufacturer | 430 | Image sensor / SN9C1xx bridge | SN9C10[12] SN9C103 SN9C105 SN9C120 |
425 | ----- ------------ | 431 | ------------------------------------------------------------------------------- |
426 | HV7131D Hynix Semiconductor, Inc. | 432 | HV7131D Hynix Semiconductor | Yes No No No |
427 | MI-0343 Micron Technology, Inc. | 433 | HV7131R Hynix Semiconductor | No Yes Yes Yes |
428 | OV7630 OmniVision Technologies, Inc. | 434 | MI-0343 Micron Technology | Yes No No No |
429 | OV7660 OmniVision Technologies, Inc. | 435 | MI-0360 Micron Technology | No Yes No No |
430 | PAS106B PixArt Imaging, Inc. | 436 | OV7630 OmniVision Technologies | Yes Yes No No |
431 | PAS202BCA PixArt Imaging, Inc. | 437 | OV7660 OmniVision Technologies | No No Yes Yes |
432 | PAS202BCB PixArt Imaging, Inc. | 438 | PAS106B PixArt Imaging | Yes No No No |
433 | TAS5110C1B Taiwan Advanced Sensor Corporation | 439 | PAS202B PixArt Imaging | Yes Yes No No |
434 | TAS5130D1B Taiwan Advanced Sensor Corporation | 440 | TAS5110C1B Taiwan Advanced Sensor | Yes No No No |
435 | 441 | TAS5110D Taiwan Advanced Sensor | Yes No No No | |
436 | Some of the available control settings of each image sensor are supported | 442 | TAS5130D1B Taiwan Advanced Sensor | Yes No No No |
443 | |||
444 | "Yes" means that the pair is supported by the driver, while "No" means that the | ||
445 | pair does not exist or is not supported by the driver. | ||
446 | |||
447 | Only some of the available control settings of each image sensor are supported | ||
437 | through the V4L2 interface. | 448 | through the V4L2 interface. |
438 | 449 | ||
439 | Donations of new models for further testing and support would be much | 450 | Donations of new models for further testing and support would be much |
@@ -482,8 +493,8 @@ The SN9C1xx PC Camera Controllers can send images in two possible video | |||
482 | formats over the USB: either native "Sequential RGB Bayer" or compressed. | 493 | formats over the USB: either native "Sequential RGB Bayer" or compressed. |
483 | The compression is used to achieve high frame rates. With regard to the | 494 | The compression is used to achieve high frame rates. With regard to the |
484 | SN9C101, SN9C102 and SN9C103, the compression is based on the Huffman encoding | 495 | SN9C101, SN9C102 and SN9C103, the compression is based on the Huffman encoding |
485 | algorithm described below, while the SN9C105 and SN9C120 the compression is | 496 | algorithm described below, while with regard to the SN9C105 and SN9C120 the |
486 | based on the JPEG standard. | 497 | compression is based on the JPEG standard. |
487 | The current video format may be selected or queried from the user application | 498 | The current video format may be selected or queried from the user application |
488 | by calling the VIDIOC_S_FMT or VIDIOC_G_FMT ioctl's, as described in the V4L2 | 499 | by calling the VIDIOC_S_FMT or VIDIOC_G_FMT ioctl's, as described in the V4L2 |
489 | API specifications. | 500 | API specifications. |
@@ -573,4 +584,5 @@ order): | |||
573 | - Mizuno Takafumi for the donation of a webcam; | 584 | - Mizuno Takafumi for the donation of a webcam; |
574 | - an "anonymous" donator (who didn't want his name to be revealed) for the | 585 | - an "anonymous" donator (who didn't want his name to be revealed) for the |
575 | donation of a webcam. | 586 | donation of a webcam. |
576 | - an anonymous donator for the donation of four webcams. | 587 | - an anonymous donator for the donation of four webcams and two boards with ten |
588 | image sensors. | ||