em28xx: add support for the em2765 bridge
Subsystems (2)
v3 cover em28xx: add support for the em2765 bridge
This patch series adds basic support for the em25xx/276x/7x/8x camera bridges. These devices differ from the em2710/2750 and em28xx bridges in several points:
1) a second i2c bus is provided which has to be accessed with a different read/write algorithm (=> patch 1)
2) a different frame data format is used (=> patch 3)
3) additional output formats (e.g. mpeg) are provided. This patch series does not (yet) add support for them, but it fixes the output format selection for these bridges (the current code sets bit 5 of the output format register, which has a different meaning for the other bridges and breaks capturing with em25xx family sdevices). (=> patch 4)
4) registers 0x34+0x35 (VBI_START_H/V for em28xx devices) are used for a different (unknown) purpose. This needs to be investigated further (could be zooming, cropping, image statistics or AWB/AE window selection). At normal operation, these registers are set to capturing (input) width/height / 16. (=> patch 5)
Patch 2 adds the chip id of the em2765 as found in the "SpeedLink Vicious And Devine Laplace" webcam. The changes have also been tested with this device.
Changes since v1:
- rebased on the recent em28xx i2c bus changes (real support for 2 busses)
- moved i2c algorithm depending transfer function calls to separate functions
Changes since v2:
- fixed some coding style issues and comments
Frank Schäfer (5):
em28xx: add support for em25xx i2c bus B read/write/check device
operations
em28xx: add chip id of the em2765
em28xx: add support for em25xx/em276x/em277x/em278x frame data
processing
em28xx: make em28xx_set_outfmt() working with EM25xx family bridges
em28xx: write output frame resolution to regs 0x34+0x35 for em25xx
family bridges
drivers/media/usb/em28xx/em28xx-cards.c | 19 ++- drivers/media/usb/em28xx/em28xx-core.c | 28 +++- drivers/media/usb/em28xx/em28xx-i2c.c | 236 ++++++++++++++++++++++++++----- drivers/media/usb/em28xx/em28xx-reg.h | 10 +- drivers/media/usb/em28xx/em28xx-video.c | 74 +++++++++- drivers/media/usb/em28xx/em28xx.h | 11 +-
6 Dateien geändert, 329 Zeilen hinzugefügt(+), 49 Zeilen entfernt(-)
Signature · 1 line
1.7.10.4
PATCH v3 1/5 em28xx: add support for em25xx i2c bus B read/write/check device operations
The webcam "SpeedLink VAD Laplace" (em2765 + ov2640) uses a special algorithm for i2c communication with the sensor, which is connected to a second i2c bus.
We don't know yet how to find out which devices support/use it. It's very likely used by all em25xx and em276x+ bridges. Tests with other em28xx chips (em2820, em2882/em2883) show, that this algorithm always succeeds there although no slave device is connected.
The algorithm likely also works for real i2c client devices (OV2640 uses SCCB), because the Windows driver seems to use it for probing Samsung and Kodak sensors.
--- drivers/media/usb/em28xx/em28xx-cards.c | 8 +- drivers/media/usb/em28xx/em28xx-i2c.c | 236 ++++++++++++++++++++++++++----- drivers/media/usb/em28xx/em28xx.h | 10 +-
3 Dateien geändert, 212 Zeilen hinzugefügt(+), 42 Zeilen entfernt(-)
drivers/media/usb/em28xx/em28xx-cards.c +6 -2
@@ -3139,15 +3139,19 @@ static int em28xx_init_dev(struct em28xx *dev, struct usb_device *udev,rt_mutex_init (&dev->i2c_bus_lock);/* register i2c bus 0 */ - retval =em28xx_i2c_register (dev,0 ); +if (dev->board.is_em2800) + retval =em28xx_i2c_register (dev,0 ,EM28XX_I2C_ALGO_EM2800 ); +else + retval =em28xx_i2c_register (dev,0 ,EM28XX_I2C_ALGO_EM28XX );if (retval <0 ) {em28xx_errdev ("%s: em28xx_i2c_register bus 0 - error [%d]!\n" , __func__, retval); goto unregister_dev; } +/* register i2c bus 1 */ if (dev->def_i2c_bus) { - retval =em28xx_i2c_register (dev,1 ); + retval =em28xx_i2c_register (dev,1 ,EM28XX_I2C_ALGO_EM28XX );if (retval <0 ) {em28xx_errdev ("%s: em28xx_i2c_register bus 1 - error [%d]!\n" , __func__, retval);
drivers/media/usb/em28xx/em28xx-i2c.c +197 -39
293 lines not on this page · raw message
drivers/media/usb/em28xx/em28xx.h +9 -1
@@ -461,10 +461,17 @@ struct em28xx_fh {enum v4l2_buf_type type; }; +enum em28xx_i2c_algo_type { +EM28XX_I2C_ALGO_EM28XX =0 , +EM28XX_I2C_ALGO_EM2800 , +EM28XX_I2C_ALGO_EM25XX_BUS_B , +}; +struct em28xx_i2c_bus {struct em28xx *dev;unsigned bus; +enum em28xx_i2c_algo_type algo_type; };
@@ -651,7 +658,8 @@ struct em28xx_ops {/* Provided by em28xx-i2c.c */ void em28xx_do_i2c_scan (struct em28xx *dev,unsigned bus); -int em28xx_i2c_register (struct em28xx *dev,unsigned bus); +int em28xx_i2c_register (struct em28xx *dev,unsigned bus, +enum em28xx_i2c_algo_type algo_type);int em28xx_i2c_unregister (struct em28xx *dev,unsigned bus);/* Provided by em28xx-core.c */
Signature · 1 line
1.7.10.4
PATCH v3 2/5 em28xx: add chip id of the em2765
In reply to Frank SchäferThis chip can be found in the SpeedLink VAD Laplace webcam (1ae7:9003 and 1ae7:9004).
--- drivers/media/usb/em28xx/em28xx-cards.c | 13 ++++++++++++- drivers/media/usb/em28xx/em28xx-reg.h | 1 + drivers/media/usb/em28xx/em28xx.h | 1 +
3 Dateien geändert, 14 Zeilen hinzugefügt(+), 1 Zeile entfernt(-)
drivers/media/usb/em28xx/em28xx-cards.c +12 -1
@@ -3041,6 +3041,12 @@ static int em28xx_init_dev(struct em28xx *dev, struct usb_device *udev,case CHIP_ID_EM2750 : chip_name ="em2750" ;break ; +case CHIP_ID_EM2765 : + chip_name ="em2765" ; + dev->wait_after_write =0 ; + dev->is_em25xx =1 ; + dev->eeprom_addrwidth_16bit =1 ; +break ;case CHIP_ID_EM2820 : chip_name ="em2710/2820" ;break ;
@@ -3151,7 +3157,12 @@ static int em28xx_init_dev(struct em28xx *dev, struct usb_device *udev,/* register i2c bus 1 */ if (dev->def_i2c_bus) { - retval =em28xx_i2c_register (dev,1 ,EM28XX_I2C_ALGO_EM28XX ); +if (dev->is_em25xx) + retval =em28xx_i2c_register (dev,1 , +EM28XX_I2C_ALGO_EM25XX_BUS_B ); +else + retval =em28xx_i2c_register (dev,1 , +EM28XX_I2C_ALGO_EM28XX );if (retval <0 ) {em28xx_errdev ("%s: em28xx_i2c_register bus 1 - error [%d]!\n" , __func__, retval);
drivers/media/usb/em28xx/em28xx-reg.h +1 -0
@@ -219,6 +219,7 @@ enum em28xx_chip_id {CHIP_ID_EM2860 =34 ,CHIP_ID_EM2870 =35 ,CHIP_ID_EM2883 =36 , +CHIP_ID_EM2765 =54 ,CHIP_ID_EM2874 =65 ,CHIP_ID_EM2884 =68 , CHIP_ID_EM28174 = 113,
drivers/media/usb/em28xx/em28xx.h +1 -0
@@ -482,6 +482,7 @@ struct em28xx {int model;/* index in the device_data struct */ int devno;/* marks the number of this device */ enum em28xx_chip_id chip_id; + unsigned int is_em25xx:1; /* em25xx/em276x/7x/8x family bridge */ unsigned char disconnected:1; /* device has been diconnected */
Signature · 1 line
1.7.10.4
PATCH v3 3/5 em28xx: add support for em25xx/em276x/em277x/em278x frame data processing
In reply to Frank SchäferThe em25xx/em276x/em277x/em278x frame data format is different to the one used by the em2710/em2750/em28xx chips.
With the recent cleanups and reorganization of the frame data processing code it can be easily extended to support these devices.
--- drivers/media/usb/em28xx/em28xx-video.c | 74 ++++++++++++++++++++++++++++++-
1 Datei geändert, 73 Zeilen hinzugefügt(+), 1 Zeile entfernt(-)
drivers/media/usb/em28xx/em28xx-video.c +73 -1
@@ -76,6 +76,16 @@ MODULE_DESCRIPTION(DRIVER_DESC);MODULE_LICENSE ("GPL" );MODULE_VERSION (EM28XX_VERSION ); + +#define EM25XX_FRMDATAHDR_BYTE1 0x02 +#define EM25XX_FRMDATAHDR_BYTE2_STILL_IMAGE 0x20 +#define EM25XX_FRMDATAHDR_BYTE2_FRAME_END 0x02 +#define EM25XX_FRMDATAHDR_BYTE2_FRAME_ID 0x01 +#define EM25XX_FRMDATAHDR_BYTE2_MASK (EM25XX_FRMDATAHDR_BYTE2_STILL_IMAGE | \ + EM25XX_FRMDATAHDR_BYTE2_FRAME_END | \ + EM25XX_FRMDATAHDR_BYTE2_FRAME_ID) + +static unsigned int video_nr[] = {[0 ... (EM28XX_MAXBOARDS -1 )] =-1U };static unsigned int vbi_nr[] = {[0 ... (EM28XX_MAXBOARDS -1 )] =-1U };static unsigned int radio_nr[] = {[0 ... (EM28XX_MAXBOARDS -1 )] =-1U };
@@ -408,6 +418,62 @@ static inline void process_frame_data_em28xx(struct em28xx *dev,em28xx_copy_video (dev, buf, data_pkt, data_len); } +/* +* Process data packet according to the em25xx/em276x/7x/8x frame data format +*/ +static inline void process_frame_data_em25xx (struct em28xx *dev, +unsigned char *data_pkt, +unsigned int data_len) +{ +struct em28xx_buffer *buf = dev->usb_ctl.vid_buf; +struct em28xx_dmaqueue *dmaq = &dev->vidq; +bool frame_end =0 ; + +/* Check for header */ +/* NOTE: at least with bulk transfers, only the first packet +* has a header and has always set the FRAME_END bit */ +if (data_len >=2 ) {/* em25xx header is only 2 bytes long */ +if ((data_pkt[0 ] ==EM25XX_FRMDATAHDR_BYTE1 ) && + ((data_pkt[1 ] & ~EM25XX_FRMDATAHDR_BYTE2_MASK ) ==0x00 )) { + dev->top_field = !(data_pkt[1 ] & +EM25XX_FRMDATAHDR_BYTE2_FRAME_ID ); + frame_end = data_pkt[1 ] & +EM25XX_FRMDATAHDR_BYTE2_FRAME_END ; + data_pkt +=2 ; + data_len -=2 ; + } + +/* Finish field and prepare next (BULK only) */ +if (dev->analog_xfer_bulk && frame_end) { + buf =finish_field_prepare_next (dev, buf, dmaq); + dev->usb_ctl.vid_buf = buf; + } +/* NOTE: in ISOC mode when a new frame starts and buf==NULL, +* we COULD already prepare a buffer here to avoid skipping the +* first frame. +*/ + } + +/* Copy data */ +if (buf !=NULL && data_len >0 ) +em28xx_copy_video (dev, buf, data_pkt, data_len); + +/* Finish frame (ISOC only) => avoids lag of 1 frame */ +if (!dev->analog_xfer_bulk && frame_end) { + buf =finish_field_prepare_next (dev, buf, dmaq); + dev->usb_ctl.vid_buf = buf; + } + +/* NOTE: Tested with USB bulk transfers only ! +* The wording in the datasheet suggests that isoc might work different. +* The current code assumes that with isoc transfers each packet has a +* header like with the other em28xx devices. +*/ +/* NOTE: Support for interlaced mode is pure theory. It has not been +* tested and it is unknown if these devices actually support it. */ +/* NOTE: No VBI support yet (these chips likely do not support VBI). */ +} +/* Processes and copies the URB data content (video and VBI data) */ static inline int em28xx_urb_data_copy (struct em28xx *dev,struct urb *urb) {
@@ -460,7 +526,13 @@ static inline int em28xx_urb_data_copy(struct em28xx *dev, struct urb *urb)continue ; } -process_frame_data_em28xx (dev, usb_data_pkt, usb_data_len); +if (dev->is_em25xx) +process_frame_data_em25xx (dev, + usb_data_pkt, usb_data_len); +else +process_frame_data_em28xx (dev, + usb_data_pkt, usb_data_len); + }return 1 ; }
Signature · 1 line
1.7.10.4
PATCH v3 4/5 em28xx: make em28xx_set_outfmt() working with EM25xx family bridges
In reply to Frank SchäferStreaming doesn't work with the EM2765 if bit 5 of the output format register 0x27 is set.
It's actually not clear if really has to be set for the other chips, but for now let's keep it to avoid regressions and add a comment to the code.
--- drivers/media/usb/em28xx/em28xx-core.c | 21 ++++++++++++++++-----
1 Datei geändert, 16 Zeilen hinzugefügt(+), 5 Zeilen entfernt(-)
drivers/media/usb/em28xx/em28xx-core.c +16 -5
@@ -697,12 +697,23 @@ int em28xx_vbi_supported(struct em28xx *dev)int em28xx_set_outfmt (struct em28xx *dev) {int ret; -u8 vinctrl; - - ret =em28xx_write_reg_bits (dev,EM28XX_R27_OUTFMT , - dev->format->reg |0x20 ,0xff ); +u8 fmt, vinctrl; + + fmt = dev->format->reg; +if (!dev->is_em25xx) + fmt |=0x20 ; +/* +* NOTE: it's not clear if this is really needed ! +* The datasheets say bit 5 is a reserved bit and devices seem to work +* fine without it. But the Windows driver sets it for em2710/50+em28xx +* devices and we've always been setting it, too. +* +* em2765 (em25xx, em276x/7x/8x) devices do NOT work with this bit set, +* it's likely used for an additional (compressed ?) format there. +*/ + ret =em28xx_write_reg (dev,EM28XX_R27_OUTFMT , fmt);if (ret <0 ) -return ret; +return ret; ret =em28xx_write_reg (dev,EM28XX_R10_VINMODE , dev->vinmode);if (ret <0 )
Signature · 1 line
1.7.10.4
PATCH v3 5/5 em28xx: write output frame resolution to regs 0x34+0x35 for em25xx family bridges
In reply to Frank SchäferThe Windows driver writes the output resolution to registers 0x34 (width / 16) and 0x35 (height / 16) always.
We don't know yet what these registers are used for.
--- drivers/media/usb/em28xx/em28xx-core.c | 7 +++++++ drivers/media/usb/em28xx/em28xx-reg.h | 9 ++++++++-
2 Dateien geändert, 15 Zeilen hinzugefügt(+), 1 Zeile entfernt(-)
drivers/media/usb/em28xx/em28xx-core.c +7 -0
@@ -767,6 +767,13 @@ static void em28xx_capture_area_set(struct em28xx *dev, u8 hstart, u8 vstart,em28xx_write_regs (dev,EM28XX_R1E_CWIDTH , &cwidth,1 );em28xx_write_regs (dev,EM28XX_R1F_CHEIGHT , &cheight,1 );em28xx_write_regs (dev,EM28XX_R1B_OFLOW , &overflow,1 ); + +/* FIXME: function/meaning of these registers ? */ +/* FIXME: align width+height to multiples of 4 ?! */ +if (dev->is_em25xx) { +em28xx_write_reg (dev,0x34 , width >>4 ); +em28xx_write_reg (dev,0x35 , height >>4 ); + } }static int em28xx_scaler_set (struct em28xx *dev,u16 h,u16 v)
drivers/media/usb/em28xx/em28xx-reg.h +8 -1
@@ -48,7 +48,7 @@#define EM28XX_CHIPCFG2_TS_PACKETSIZE_752 0x03 -/* GPIO/GPO registers */ +/* GPIO/GPO registers */ #define EM2880_R04_GPO 0x04/* em2880-em2883 only */ #define EM28XX_R08_GPIO 0x08/* em2820 or upper */
@@ -167,6 +167,13 @@#define EM28XX_R34_VBI_START_H 0x34#define EM28XX_R35_VBI_START_V 0x35 +/* +* NOTE: the EM276x (and EM25xx, EM277x/8x ?) (camera bridges) use these +* registers for a different unknown purpose. +* => register 0x34 is set to capture width / 16 +* => register 0x35 is set to capture height / 16 +*/ +#define EM28XX_R36_VBI_WIDTH 0x36#define EM28XX_R37_VBI_HEIGHT 0x37
Signature · 1 line
1.7.10.4