Android / kernel / common / 857aab34f04ff86666aa80e751ee696eff0113dd /. / drivers / hid / hid-multitouch.c. Blob: ecd4d2db9e800ca2397c3ad189a028. Most of the requests that are sent to device drivers are packaged in I/O request packets (IRPs). Each device is represented by a device node, and each device node has a device stack. For more information, see Device nodes and device stacks. Stantum (www.stantum.com) has been the pioneering company in multi-touch technology since 2002, and in 2005 was the first company to market commercial products using a truly reliable multi-touch user interface. Today, Stantum's patented and breakthrough multi-touch technology portfolio is available under license of IP bricks and associated.
Drivers Statement Of On-duty Hours
-->
Most of the requests that are sent to device drivers are packaged in I/O request packets (IRPs). Each device is represented by a device node, and each device node has a device stack. For more information, see Device nodes and device stacks. To send a read, write, or control request to a device, the I/O manager locates the device node for the device and then sends an IRP to the device stack of that node. Sometimes more than one device stack is involved in processing an I/O request. Regardless of how many device stacks are involved, the overall sequence of drivers that participate in an I/O request is called the driver stack for the request. We also use the term driver stack to refer to the layered set of drivers for a particular technology.
I/O requests that are processed by several device stacks
In some cases, more than one device stack is involved in processing an IRP. The following diagram illustrates a case where four device stacks are involved in processing a single IRP.
Here is how the IRP is processed at each numbered stage in the diagram:
The IRP is created by Disk.sys, which is the function driver in the device stack for the My USB Storage Device node. Disk.sys passes the IRP down the device stack to Usbstor.sys.
Notice that Usbstor.sys is the PDO driver for the My USB Storage Device node and the FDO driver for the USB Mass Storage Device node. At this point, it is not important to decide whether the IRP is owned by the (PDO, Usbstor.sys) pair or the (FDO, Usbstor.sys) pair. The IRP is owned by the driver, Usbstor.sys, and the driver has access to both the PDO and the FDO.
When Usbstor.sys has finished processing the IRP, it passes the IRP to Usbhub.sys. Usbhub.sys is the PDO driver for the USB Mass Storage Device node and the FDO driver for the USB Root Hub node. It is not important to decide whether the IRP is owned by the (PDO, Usbhub.sys) pair or the (FDO, Usbhub.sys) pair. The IRP is owned by the driver, Usbhub.sys, and the driver has access to both the PDO and the FDO.
When Usbhub.sys has finished processing the IRP, it passes the IRP to the (Usbuhci.sys, Usbport.sys) pair.
Usbuhci.sys is a miniport driver, and Usbport.sys is a port driver. The (miniport, port) pair plays the role of a single driver. In this case, both the miniport driver and the port driver are written by Microsoft. The (Usbuhci.sys, Usbport.sys) pair is the PDO driver for the USB Root Hub node, and the (Usbuhci.sys, Usbport.sys) pair is also the FDO driver for the USB Host Controller node. The (Usbuhci.sys, Usbport.sys) pair does the actual communication with the host controller hardware, which in turn communicates with the physical USB storage device.
The driver stack for an I/O request
Consider the sequence of four drivers that participated in the I/O request illustrated in the preceding diagram. We can get another view of the sequence by focusing on the drivers rather than on the device nodes and their individual device stacks. The following diagram shows the drivers in sequence from top to bottom. Notice that Disk.sys is associated with one device object, but each of the other three drivers is associated with two device objects.
The sequence of drivers that participate in an I/O request is called the driver stack for the I/O request. To illustrate a driver stack for an I/O request, we draw the drivers from top to bottom in the order that they participate in the request.
Notice that the driver stack for an I/O request is quite different from the device stack for a device node. Also notice that the driver stack for an I/O request does not necessarily remain in one branch of the device tree.
Technology driver stacks
Consider the driver stack for the I/O request shown in the preceding diagram. If we give each of the drivers a friendly name and make some slight changes to the diagram, we have a block diagram that is similar to many of those that appear in the Windows Driver Kit (WDK) documentation.
In the diagram, the driver stack is divided into three sections. We can think of each section as belonging to a particular technology or to a particular component or portion of the operating system. For example, we might say that the first section at the top of the driver stack belongs to the Volume Manager, the second section belongs to the storage component of the operating system, and the third section belongs to the core USB portion of the operating system.
Consider the drivers in the third section. These drivers are a subset of a larger set of core USB drivers that Microsoft provides for handling various kinds of USB requests and USB hardware. The following diagram shows what the entire USB core block diagram might look like.
A block diagram that shows all of the drivers for a particular technology or a particular component or portion of the operating system is called a technology driver stack. Typically, technology driver stacks are given names like the USB Core Driver Stack, the Storage Stack, the 1394 Driver Stack, and the Audio Driver Stack.
Drivers Statement Of On-duty Hours New Hire
Note The USB core block diagram in this topic shows one of several possible ways to illustrate the technology driver stacks for USB 1.0 and 2.0. For the official diagrams of the USB 1.0, 2.0, and 3.0 driver stacks, see USB Driver Stack Architecture.
Related topics
Drivers Status Check
| Rev. | Time | Author |
|---|---|---|
| 2cc6ab1android-2.6.38 | 2011-08-08 08:41:23 | Kyle Evans |
net: wireless: wl: set cryptography deps | ||
| 3154f71android-x86-2.2-r2 | 2011-06-27 19:24:49 | Benjamin Tissoires |
hid-multitouch: Add device id for another DWAV/eGalax variant | ||
| 95f1d67 | 2011-06-27 19:24:47 | Benjamin Tissoires |
hid-core: add 0eef:725e to hid_have_special_driver | ||
| 3dc114a | 2011-06-27 19:24:46 | Benjamin Tissoires |
HID: hid-multitouch: add support for a new Lumio dual-touch panel | ||
| 7244263 | 2011-06-27 19:24:44 | Benjamin Tissoires |
HID: hid-multitouch: correct VID for Stantum panels | ||
| 83461d1 | 2011-06-19 02:13:22 | Chih-Wei Huang |
HID: hid-multitouch: add another product id for eGalax touchscreen | ||
| 78a7c09 | 2011-06-19 02:12:04 | Chih-Wei Huang |
HID: don't use multi input quirk for TouchPack touchscreen | ||
| 31415df | 2011-06-13 10:37:09 | Benjamin Tissoires |
hid-multitouch: fix broken eGalax devices | ||
| ea4411b | 2011-06-02 16:22:31 | Benjamin Tissoires |
HID: hid-multitouch: cosmetic changes, sort classes and devices | ||
| c1db7df | 2011-06-02 16:21:54 | Benjamin Tissoires |
HID: hid-multitouch: class MT_CLS_STANTUM is redundant with MT_CLS_CONFIDENCE | ||
| cecfb0e | 2011-06-02 16:21:41 | Benjamin Tissoires |
HID: hid-multitouch: add support for Unitec panels | ||
| 8983aa7 | 2011-06-02 16:21:24 | Benjamin Tissoires |
HID: hid-multitouch: add support for Touch International panels | ||
| 3ac3e2c | 2011-06-02 16:21:14 | Benjamin Tissoires |
HID: hid-multitouch: add support for GoodTouch panels | ||
| 75d5e91 | 2011-06-02 16:21:02 | Benjamin Tissoires |
HID: hid-multitouch: add support for CVTouch panels | ||
| 7564dba | 2011-06-02 16:20:42 | Benjamin Tissoires |
HID: hid-multitouch: add support for ActionStar panels | ||
| 686d079 | 2011-06-02 16:20:02 | Benjamin Tissoires |
HID: hid-multitouch: add support for Elo TouchSystems 2515 IntelliTouch Plus | ||
| 56c5bd1 | 2011-06-02 16:19:49 | Benjamin Tissoires |
HID: hid-multitouch: Add support for Lumio panels | ||
| 8c7858b | 2011-06-02 16:19:35 | Benjamin Tissoires |
HID: hid-multitouch: add support for Ilitek dual-touch panel | ||
| d2757e6 | 2011-05-19 01:50:49 | Gustavo F. Padovan |
UBUNTU: SAUCE: Revert 'Bluetooth: Add new PID for Atheros 3011' | ||
| d5b44b1 | 2011-05-03 16:47:21 | Chih-Wei Huang |
x86: add driver for Lenovo ideapad S10-3T rotate button | ||
| 8e8d90a | 2011-04-29 11:39:47 | Chih-Wei Huang |
net: wireless: correct the dependeicnes of wl driver | ||
| 616fce5 | 2011-04-24 21:09:52 | Chih-Wei Huang |
net: wireless: add Makefile for Broadcom 802.11a/b/g/n hybrid device driver | ||
| a7fe3aa | 2011-04-22 21:04:44 | Benjamin Tissoires |
HID: add support for PenMount dual-touch panel | ||
| 39382ef | 2011-04-22 21:04:22 | Benjamin Tissoires |
HID: hid-multitouch: refactor last_field_index | ||
| 10b222a | 2011-04-22 21:04:11 | Benjamin Tissoires |
HID: multitouch: remove unused files | ||
| aa2b689 | 2011-04-22 21:03:44 | Henrik Rydberg |
HID: Do not create input devices for feature reports | ||
| 4a75c99 | 2011-04-20 19:05:40 | Benjamin Tissoires |
HID: hid-multitouch: merge hid-mosart into hid-multitouch | ||
| 34342ec | 2011-04-08 14:02:02 | Chih-Wei Huang |
android-x86: update android-x86_defconfig for 2.6.38 | ||
| 60ecbfe | 2011-04-06 12:16:53 | Benjamin Tissoires |
Convert hid-multitouch to android | ||
| 600e958 | 2011-04-06 12:14:50 | Benjamin Tissoires |
HID: add autodetection of multitouch devices | ||