But if I want to add new gadget to list what I need to do? My device configuration is as follows: T: Bus=02 Lev=02 Prnt=02 Port=01 Cnt=01 Dev#= 14 Spd=12 MxCh= 0 D: Ver= 1.10 Cls=ff(vend.) Sub=00 Prot=00 MxPS= 8 #Cfgs= 1 P: Vendor=1a86 ProdID=7523 Rev= 2.54 S: Product=USB2.0-Serial C:* #Ifs= 1 Cfg#= 1 Atr=80 MxPwr= 96mA I:* If#= 0 Alt= 0 #EPs= 3 Cls=ff(vend.) Sub=01 Prot=02 Driver=ch341 E: Ad=82(I) Atr=02(Bulk) MxPS= 32 Ivl=0ms E: Ad=02(O) Atr=02(Bulk) MxPS= 32 Ivl=0ms E: Ad=81(I) Atr=03(Int.) MxPS= 8 Ivl=1ms Thanks & regards, Narendra kumar. -----Original Message----- From: Huang Rui [mailto:ray.huang@xxxxxxx] Sent: 07 May 2015 11:03 To: Narendra Kumar Chepuri Cc: linux-usb@xxxxxxxxxxxxxxx Subject: Re: USB test run process On Thu, May 07, 2015 at 10:58:27AM +0530, Narendra Kumar Chepuri wrote: > So in that case which king of devices should used for testing can you > tell specifically, you might have used some usb devcies for testing > drivers right? > Please see drivers/usb/misc/usbtest.c static const struct usb_device_id id_table[] = { /*-------------------------------------------------------------*/ /* EZ-USB devices which download firmware to replace (or in our * case augment) the default device implementation. */ /* generic EZ-USB FX controller */ { USB_DEVICE(0x0547, 0x2235), .driver_info = (unsigned long) &ez1_info, }, /* CY3671 development board with EZ-USB FX */ { USB_DEVICE(0x0547, 0x0080), .driver_info = (unsigned long) &ez1_info, }, /* generic EZ-USB FX2 controller (or development board) */ { USB_DEVICE(0x04b4, 0x8613), .driver_info = (unsigned long) &ez2_info, }, /* re-enumerated usb test device firmware */ { USB_DEVICE(0xfff0, 0xfff0), .driver_info = (unsigned long) &fw_info, }, /* "Gadget Zero" firmware runs under Linux */ { USB_DEVICE(0x0525, 0xa4a0), .driver_info = (unsigned long) &gz_info, }, ... } Above devices are used to test. Actually, testusb is always used for gadget device testing with gadget zero. Thanks, Rui -- To unsubscribe from this list: send the line "unsubscribe linux-usb" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
