Scsi - Index of
Scsi - Index of Scsi - Index of
不了,比如我有个Intel 的U 盘,那里边的固有的信息肯定是在Intel 出厂的时候就被烙在里边了,厂家早已 把它的一切,烙上Intel 印.所以当我插入U 盘,用cat /proc/scsi/scsi 命令看一下的话,"Vendor"那一项 显 示的肯定是Intel. 关于这几种描述符,usb core 在总线扫描那会就会去读取,会去获得里边的信息,其 中,device 描述符描述的是整个device,注意了,这个device 和咱们一直讲的device 和driver 那里的 device 是不一样的.因为一个usb device 实际上指的是一种宏观上的概念,它可以是一种多功能的设备, 改革开放之后,多功能的东西越来越多了,比如外企常见的多功能一体机,就是集打印机,复印机,扫描仪,传 真机于一体的设备, 当然,这不属于usb 设备,但是usb 设备当然也有这种情况,比如电台DJ 可能会用到 的, 一个键盘,上边带一个扬声器,它们用两个usb 接口接到usb hub 上去,而device 描述符描述的就是这整 个 设备的特点.那么configuration 描述符呢,老实说,对我们了解U 盘驱动真是没有什么意义,但是作为一个 有责任心的男人,此刻,我必须为它多说几句,虽然只是很简单的说几句.一个设备可以有一种或者几种配置, 这能理解吧?没见过具体的usb 设备?那么好,手机见过吧,每个手机都会有多种配置,或者说"设定",比如,我 的这款,Nokia6300,手机语言,可以设定为English,繁体中文,简体中文,一旦选择了其中一种,那么手机里 边所显示的所有的信息都是该种语言/字体.还有最简单的例子,操作模式也有好几种,标准,无声,会议,etc. 基本上如果我设为"会议",那么就是只振动不发声,要是设为无声,那么就啥动静也不会有,只能凭感觉了,以 前去公司面试的话通常就是设为无声,因为觉得振动也不好,让人家面试官听到了还是不合适.那么usb设备 的配置也是如此,不同的usb 设备当然有不同的配置了,或者说需要配置哪些东西也会不一样.好了,关于配 置,就说这么多,更多的我们暂时也不需要了解了. 对于usb 设备驱动程序编写者来说,更为关键的是下面两个,interface 和endpoint.先说,interface.第一 句,一个interface 对应一个usb 设备驱动程序.没错,还说前边那个例子,一个usb 设备,两种功能,一个键 盘, 上面带一个扬声器,两个接口,那这样肯定得要两个驱动程序,一个是键盘驱动程序,一个是音频流驱动程序. 道上的兄弟喜欢把这样两个整合在一起的东西叫做一个设备,那好,让他们去叫吧,我门用interface 来区分 这两者行了吧.于是有了我们前面提到的那个数据结构,struct usb_interface.它定义于 include/linux/usb.h: 71 /** 72 * struct usb_interface - what usb device drivers talk to 73 * @altsetting: array of interface structures, one for each alternate 74 * setting that may be selected. Each one includes a set of 75 * endpoint configurations. They will be in no particular order. 76 * @num_altsetting: number of altsettings defined. 77 * @cur_altsetting: the current altsetting. 78 * @driver: the USB driver that is bound to this interface. 79 * @minor: the minor number assigned to this interface, if this 80 * interface is bound to a driver that uses the USB major number. 81 * If this interface does not use the USB major, this field should 82 * be unused. The driver should set this value in the probe() 83 * function of the driver, after it has been assigned a minor 84 * number from the USB core by calling usb_register_dev(). 85 * @condition: binding state of the interface: not bound, binding 86 * (in probe()), bound to a driver, or unbinding (in disconnect()) 87 * @dev: driver model's view of this device
22 88 * @class_dev: driver model's class view of this device. 89 * 90 * USB device drivers attach to interfaces on a physical device. Each 91 * interface encapsulates a single high level function, such as feeding 92 * an audio stream to a speaker or reporting a change in a volume control. 93 * Many USB devices only have one interface. The protocol used to talk to 94 * an interface's endpoints can be defined in a usb "class" specification, 95 * or by a product's vendor. The (default) control endpoint is part of 96 * every interface, but is never listed among the interface's descriptors. 97 * 98 * The driver that is bound to the interface can use standard driver model 99 * calls such as dev_get_drvdata() on the dev member of this structure. 100 * 101 * Each interface may have alternate settings. The initial configuration 102 * of a device sets altsetting 0, but the device driver can change 103 * that setting using usb_set_interface(). Alternate settings are often 104 * used to control the the use of periodic endpoints, such as by having 105 * different endpoints use different amounts of reserved USB bandwidth. 106 * All standards-conformant USB devices that use isochronous endpoints 107 * will use them in non-default settings. 108 * 109 * The USB specification says that alternate setting numbers must run from 110 * 0 to one less than the total number of alternate settings. But some 111 * devices manage to mess this up, and the structures aren't necessarily 112 * stored in numerical order anyhow. Use usb_altnum_to_altsetting() to 113 * look up an alternate setting in the altsetting array based on its number. 114 */ 115 struct usb_interface { 116 /* array of alternate settings for this interface, 117 * stored in no particular order */ 118 struct usb_host_interface *altsetting; 119 120 struct usb_host_interface *cur_altsetting; /* the currently 121 * active alternate setting */ 122 unsigned num_altsetting; /* number of alternate settings */ 123 124 int minor; /* minor number this interface is bound to */ 125 enum usb_interface_condition condition; /* state of binding */ 126 struct device dev; /* interface specific device info */ 127 struct class_device *class_dev; 128 }; 129 #define to_usb_interface(d) container_of(d, struct usb_interface, dev) 130 #define interface_to_usbdev(intf) \
- Page 1 and 2: 摘要 ............................
- Page 3 and 4: 迷雾重重的Bulk 传输(二)....
- Page 5 and 6: 引子 也许是在复旦养成了
- Page 7 and 8: usb.h datafab.h dpcm.h initializers
- Page 9 and 10: 的Linux 内核划分为许许多
- Page 11 and 12: 目录下执行make 了.Ok,make 之
- Page 13 and 14: 只 是一个usb 接口.这些口
- Page 15 and 16: 中也定义了这么一些数据
- Page 17 and 18: 511 * @driver: the driver model cor
- Page 19 and 20: 233 .owner = THIS_MODULE, 234 .name
- Page 21 and 22: 91 * construct these entries. Each
- Page 23: 324 struct usb_host_config *actconf
- Page 27 and 28: 必须给各个地方取名,完了
- Page 29 and 30: 26 136 trans_cmnd transport; /* tra
- Page 31 and 32: 944 init_MUTEX_LOCKED(&(us->sema));
- Page 33 and 34: 147 #if !defined(CONFIG_BLK_DEV_UB)
- Page 35 and 36: 124 #define USB_DEVICE_ID_MATCH_DEV
- Page 37 and 38: intf 来代替. us 之所以重要,
- Page 39 and 40: 睡眠,那就得用GPF_ATOMIC,这
- Page 41 and 42: 504 if (msg >= 0 && !(unusual_dev->
- Page 43 and 44: 179 } 180 181 static struct us_unus
- Page 45 and 46: 711 /* Submitted by Hartmut Wahl */
- Page 47 and 48: 3. useProtocol 为US_SC_DEVICE, use
- Page 49 and 50: Bus 004 Device 001: ID 0000:0000 Bu
- Page 51 and 52: 993 result = get_pipes(us); 994 if
- Page 53 and 54: 631 us->transport_reset = usb_stor_
- Page 55 and 56: 659 us->max_lun = 0; 660 break; 661
- Page 57 and 58: 740 /* Calculate and store the pipe
- Page 59 and 60: storage 会有两个bulk 端点,用
- Page 61 and 62: 比如说,复旦大学,有一个主
- Page 63 and 64: 1079 #define PIPE_ISOCHRONOUS 0 108
- Page 65 and 66: 782 us->unusual_dev->initFunction(u
- Page 67 and 68: 630 * each frame is in the fields o
- Page 69 and 70: 716 * Bulk URBs may 717 * use the U
- Page 71 and 72: 802 int number_of_packets; /* (in)
- Page 73 and 74: 先说互斥锁.它诞生于这样
不了,比如我有个Intel 的U 盘,那里边的固有的信息肯定是在Intel 出厂的时候就被烙在里边了,厂家早已<br />
把它的一切,烙上Intel 印.所以当我插入U 盘,用cat /proc/scsi/scsi 命令看一下的话,"Vendor"那一项<br />
显<br />
示的肯定是Intel. 关于这几种描述符,usb core 在总线扫描那会就会去读取,会去获得里边的信息,其<br />
中,device 描述符描述的是整个device,注意了,这个device 和咱们一直讲的device 和driver 那里的<br />
device 是不一样的.因为一个usb device 实际上指的是一种宏观上的概念,它可以是一种多功能的设备,<br />
改革开放之后,多功能的东西越来越多了,比如外企常见的多功能一体机,就是集打印机,复印机,扫描仪,传<br />
真机于一体的设备, 当然,这不属于usb 设备,但是usb 设备当然也有这种情况,比如电台DJ 可能会用到<br />
的,<br />
一个键盘,上边带一个扬声器,它们用两个usb 接口接到usb hub 上去,而device 描述符描述的就是这整<br />
个<br />
设备的特点.那么configuration 描述符呢,老实说,对我们了解U 盘驱动真是没有什么意义,但是作为一个<br />
有责任心的男人,此刻,我必须为它多说几句,虽然只是很简单的说几句.一个设备可以有一种或者几种配置,<br />
这能理解吧?没见过具体的usb 设备?那么好,手机见过吧,每个手机都会有多种配置,或者说"设定",比如,我<br />
的这款,Nokia6300,手机语言,可以设定为English,繁体中文,简体中文,一旦选择了其中一种,那么手机里<br />
边所显示的所有的信息都是该种语言/字体.还有最简单的例子,操作模式也有好几种,标准,无声,会议,etc.<br />
基本上如果我设为"会议",那么就是只振动不发声,要是设为无声,那么就啥动静也不会有,只能凭感觉了,以<br />
前去公司面试的话通常就是设为无声,因为觉得振动也不好,让人家面试官听到了还是不合适.那么usb设备<br />
的配置也是如此,不同的usb 设备当然有不同的配置了,或者说需要配置哪些东西也会不一样.好了,关于配<br />
置,就说这么多,更多的我们暂时也不需要了解了.<br />
对于usb 设备驱动程序编写者来说,更为关键的是下面两个,interface 和endpoint.先说,interface.第一<br />
句,一个interface 对应一个usb 设备驱动程序.没错,还说前边那个例子,一个usb 设备,两种功能,一个键<br />
盘,<br />
上面带一个扬声器,两个接口,那这样肯定得要两个驱动程序,一个是键盘驱动程序,一个是音频流驱动程序.<br />
道上的兄弟喜欢把这样两个整合在一起的东西叫做一个设备,那好,让他们去叫吧,我门用interface 来区分<br />
这两者行了吧.于是有了我们前面提到的那个数据结构,struct usb_interface.它定义于<br />
include/linux/usb.h:<br />
71 /**<br />
72 * struct usb_interface - what usb device drivers talk to<br />
73 * @altsetting: array <strong>of</strong> interface structures, one for each alternate<br />
74 * setting that may be selected. Each one includes a set <strong>of</strong><br />
75 * endpoint configurations. They will be in no particular order.<br />
76 * @num_altsetting: number <strong>of</strong> altsettings defined.<br />
77 * @cur_altsetting: the current altsetting.<br />
78 * @driver: the USB driver that is bound to this interface.<br />
79 * @minor: the minor number assigned to this interface, if this<br />
80 * interface is bound to a driver that uses the USB major number.<br />
81 * If this interface does not use the USB major, this field should<br />
82 * be unused. The driver should set this value in the probe()<br />
83 * function <strong>of</strong> the driver, after it has been assigned a minor<br />
84 * number from the USB core by calling usb_register_dev().<br />
85 * @condition: binding state <strong>of</strong> the interface: not bound, binding<br />
86 * (in probe()), bound to a driver, or unbinding (in disconnect())<br />
87 * @dev: driver model's view <strong>of</strong> this device
Change language