| /linux-3.3/Documentation/isdn/ |
| D | INTERFACE | 10 An HL-driver can register itself at LL by calling the function
46 This field has to be set by the HL-driver to the number of channels
48 the LL puts an id there, which has to be used by the HL-driver when
55 Also to be preset by the HL-driver. With this value the HL-driver
60 To be preset by the HL-driver. Using this field, the HL-driver
72 To be preset by the HL-driver, if it supports sk_buff's. The driver
81 This field will be set by LL. The HL-driver delivers received data-
82 packets by calling this function. Upon calling, the HL-driver must
86 int driver-Id
87 int Channel-number locally to the driver. (starting with 0)
[all …]
|
| /linux-3.3/drivers/media/video/gspca/ |
| D | Kconfig | 11 This driver uses the Video For Linux API. You must say Y or M to
12 "Video For Linux" to use this driver.
14 To compile this driver as modules, choose M here: the
25 tristate "Benq USB Camera Driver"
30 To compile this driver as a module, choose M here: the
34 tristate "Conexant Camera Driver"
39 To compile this driver as a module, choose M here: the
43 tristate "cpia CPiA (version 1) Camera Driver"
48 applications to understand the videoformat generated by this driver.
50 To compile this driver as a module, choose M here: the
[all …]
|
| /linux-3.3/drivers/video/backlight/ |
| D | Kconfig | 41 SPI driver for Epson L4F00242T03. This provides basic support
48 SPI driver for Samsung LMS283GF05. This provides basic support
56 power control driver for it. The panel starts up in power
57 off state, so you need this driver in order to see any
66 then say y to include a power driver for it.
81 then say y to include a power driver for it.
86 This driver provides a platform-device registered LCD power
90 tristate "Sharp SL-6000 LCD Driver"
93 If you have an Sharp SL-6000 Zaurus say Y to enable a driver
97 tristate "HP Jornada 700 series LCD Driver"
[all …]
|
| /linux-3.3/Documentation/scsi/ |
| D | 00-INDEX | 4 - info on driver for 53c700 based adapters
6 - info on driver for adapters with BusLogic chips
10 - Changes to driver for ARECA's SATA RAID controller cards
12 - IBM ServeRAID driver Changelog
14 - Changes to lpfc driver
20 - Changes to ncr53c8xx driver
22 - Changes to sym53c8xx driver
24 - Changes to second generation of sym53c8xx driver
26 - info on driver for BusLogic FlashPoint adapters
28 - Licence of the Flashpoint driver
[all …]
|
| /linux-3.3/drivers/bluetooth/ |
| D | Kconfig | 6 tristate "HCI USB driver"
9 Bluetooth HCI USB driver.
10 This driver is required if you want to use Bluetooth devices with
17 tristate "HCI SDIO driver"
20 Bluetooth HCI SDIO driver.
21 This driver is required if you want to use Bluetooth device with
28 tristate "HCI UART driver"
30 Bluetooth HCI UART driver.
31 This driver is required if you want to use Bluetooth devices with
32 serial port interface. You will also need this driver if you have
[all …]
|
| /linux-3.3/drivers/usb/serial/ |
| D | Kconfig | 17 To compile this driver as a module, choose M here: the
51 bool "USB Generic Serial Driver"
53 Say Y here if you want to use the generic USB serial driver. Please
55 using this driver. It is recommended that the "USB Serial converter
56 support" be compiled as a module for this driver to be used
60 tristate "USB AIRcable Bluetooth Dongle Driver"
64 To compile this driver as a module, choose M here: the module
68 tristate "USB ARK Micro 3116 USB Serial Driver"
73 To compile this driver as a module, choose M here: the
77 tristate "USB Belkin and Peracom Single Port Serial Driver"
[all …]
|
| D | bus.c | 22 struct usb_serial_driver *driver; in usb_serial_device_match() local
33 driver = to_usb_serial_driver(drv); in usb_serial_device_match()
35 if (driver == port->serial->type) in usb_serial_device_match()
53 struct usb_serial_driver *driver; in usb_serial_device_probe() local
66 driver = port->serial->type; in usb_serial_device_probe()
67 if (driver->port_probe) { in usb_serial_device_probe()
68 retval = driver->port_probe(port); in usb_serial_device_probe()
75 if (driver->port_remove) in usb_serial_device_probe()
76 retval = driver->port_remove(port); in usb_serial_device_probe()
84 driver->description, minor); in usb_serial_device_probe()
[all …]
|
| /linux-3.3/Documentation/PCI/ |
| D | PCIEBUS-HOWTO.txt | 1 The PCI Express Port Bus Driver Guide HOWTO
7 This guide describes the basics of the PCI Express Port Bus driver
9 register/unregister with the PCI Express Port Bus Driver.
13 3. What is the PCI Express Port Bus Driver
30 be handled by a single complex driver or be individually distributed
33 4. Why use the PCI Express Port Bus Driver?
35 In existing Linux kernels, the Linux Device Driver Model allows a
36 physical device to be handled by only a single driver. The PCI
39 may have its own software service driver. In this case several
42 driver is loaded first, it claims a PCI-PCI Bridge Root Port. The
[all …]
|
| /linux-3.3/Documentation/console/ |
| D | console.txt | 6 This type will be called 'system driver', and only one system driver is allowed
7 to exist. The system driver is persistent and it can never be unloaded, though
11 'modular driver' by this document. Multiple modular drivers can coexist at
12 any time with each driver sharing the console with other drivers including
13 the system driver. However, modular drivers cannot take over the console
14 that is currently occupied by another modular driver. (Exception: Drivers that
16 of driver occupying the consoles.) They can only take over the console that is
17 occupied by the system driver. In the same token, if the modular driver is
18 released by the console, the system driver will take over.
22 take_over_console() - load and bind driver to console layer
[all …]
|
| /linux-3.3/Documentation/driver-model/ |
| D | porting.txt | 2 Porting Drivers to the New Driver Model
11 Please refer to Documentation/driver-model/*.txt for definitions of
12 various driver types and concepts.
15 at the bus driver layer. This was intentional, to minimize the
19 In a nutshell, the driver model consists of a set of objects that can
23 The generic objects must be registered with the driver model core. By
35 Step 1: Registering the bus driver.
38 - Define a struct bus_type for the bus driver.
57 The bus type may be unregistered (if the bus driver may be compiled
126 bus driver should initialize the generic device. The most important
[all …]
|
| D | binding.txt | 2 Driver Binding
4 Driver binding is the process of associating a device with a device
5 driver that can control it. Bus drivers have typically handled this
7 devices and the drivers. With generic device and device driver
18 for a driver, it is inserted at the end of this list. These are the
19 two events which trigger driver binding.
27 ID of the device must match one of the device IDs that the driver
30 algorithm, it is up to the bus driver to provide a callback to compare
31 a device against the IDs of a driver. The bus returns 1 if a match was
36 If a match is found, the device's driver field is set to the driver
[all …]
|
| /linux-3.3/drivers/media/video/ |
| D | Kconfig | 145 To compile this driver as a module, choose M here: the
154 To compile this driver as a module, choose M here: the
163 To compile this driver as a module, choose M here: the
172 To compile this driver as a module, choose M here: the
181 To compile this driver as a module, choose M here: the
190 To compile this driver as a module, choose M here: the
200 To compile this driver as a module, choose M here: the
210 To compile this driver as a module, choose M here: the
219 To compile this driver as a module, choose M here: the
229 To compile this driver as a module, choose M here: the
[all …]
|
| /linux-3.3/drivers/gpu/drm/gma500/ |
| D | mmu.c | 51 /* protects driver- and pd structures. Always take in read mode
84 struct psb_mmu_driver *driver; member
110 static inline void psb_mmu_clflush(struct psb_mmu_driver *driver, in psb_mmu_clflush() argument
113 if (!driver->has_clflush) in psb_mmu_clflush()
121 static void psb_page_clflush(struct psb_mmu_driver *driver, struct page* page) in psb_page_clflush() argument
123 uint32_t clflush_add = driver->clflush_add >> PAGE_SHIFT; in psb_page_clflush()
138 static void psb_pages_clflush(struct psb_mmu_driver *driver, in psb_pages_clflush() argument
143 if (!driver->has_clflush) in psb_pages_clflush()
147 psb_page_clflush(driver, *page++); in psb_pages_clflush()
150 static void psb_mmu_flush_pd_locked(struct psb_mmu_driver *driver, in psb_mmu_flush_pd_locked() argument
[all …]
|
| /linux-3.3/drivers/net/hamradio/ |
| D | Kconfig | 2 tristate "Serial port KISS driver"
16 To compile this driver as a module, choose M here: the module
20 tristate "Serial port 6PACK driver"
30 Note that this driver is still experimental and might cause
32 driver, read <file:Documentation/networking/6pack.txt>.
34 To compile this driver as a module, choose M here: the module
38 tristate "BPQ Ethernet driver"
48 tristate "High-speed (DMA) SCC driver for AX.25"
51 This is a driver for high-speed SCC boards, i.e. those supporting
57 Currently, this driver supports Ottawa PI/PI2, Paccomm/Gracilis
[all …]
|
| /linux-3.3/drivers/watchdog/ |
| D | Kconfig | 16 reboot the machine) and a driver for hardware watchdog boards, which
32 bool "WatchDog Timer Driver Core"
34 Say Y here if you want to use the new watchdog timer driver core.
35 This driver provides a framework for all watchdog timer drivers
63 To compile this driver as a module, choose M here: the
112 driver as a module, which will be called wdt285.
114 This driver does not work on all machines. In particular, early CATS
125 NetWinder machines. Alternatively say M to compile the driver as
136 This driver can be built as a module by choosing M. The module
146 in the Intel IXP4xx network processors. This driver can
[all …]
|
| /linux-3.3/Documentation/usb/ |
| D | gadget_serial.txt | 2 Linux Gadget Serial Driver v2.0
24 This document and the gadget serial driver itself are
27 If you have questions, problems, or suggestions for this driver
33 Versions of the gadget serial driver are available for the
35 version 2.3 or later of the gadget serial driver in a 2.6
44 With version 2.3 of the driver, major and minor device nodes are
53 The gadget serial driver is a Linux USB gadget driver, a USB device
54 side driver. It runs on a Linux system that has USB device side
58 The gadget serial driver talks over USB to either a CDC ACM driver
59 or a generic USB serial driver running on a host PC.
[all …]
|
| D | usb-serial.txt | 3 The USB serial driver currently supports a number of different USB to
13 Currently the driver can handle up to 256 different serial interfaces at
16 The major number that the driver uses is 188 so to use the driver,
28 When the device is connected and recognized by the driver, the driver
41 The driver is officially supported by Connect Tech Inc.
44 For any questions or problems with this driver, please contact
48 HandSpring Visor, Palm USB, and Clié USB driver
50 This driver works with all HandSpring USB, Palm USB, and Sony Clié USB
56 possible. The driver cleans up properly when the device is removed, or
85 There is a webpage and mailing lists for this portion of the driver at:
[all …]
|
| /linux-3.3/drivers/input/misc/ |
| D | Kconfig | 22 To compile this driver as a module, choose M here: the module
32 To compile this driver as a module, choose M here: the module
42 To compile this driver as a module, choose M here: the
52 To compile this driver as a module, choose M here: the
62 To compile this driver as a module, choose M here: the
73 To compile this driver as a module, choose M here: the
85 To compile this driver as a module, choose M here: the
93 This option enables device driver support for the vibrator
94 on Qualcomm PM8xxx chip. This driver supports ff-memless interface
97 To compile this driver as module, choose M here: the
[all …]
|
| /linux-3.3/Documentation/networking/ |
| D | 00-INDEX | 4 - information on the 3Com TokenLink Velocity XL (3c5359) driver.
6 - information on the 3Com EtherLink Plus (3c505) driver.
14 - PLIP: The Parallel Line Internet Protocol device driver
16 - README for the Intel PRO/Wireless 2100 driver.
18 - README for the Intel PRO/Wireless 2915ABG and 2200BG driver.
26 - info on the using the ARCnet driver itself.
34 - info on the driver for Baycom style amateur radio modems
36 - Linux Ethernet Bonding Driver HOWTO: link aggregation in Linux.
42 - info on the COPS LocalTalk Linux driver
44 - the Crystal LAN (CS8900/20-based) Ethernet ISA adapter driver
[all …]
|
| /linux-3.3/sound/drivers/ |
| D | Kconfig | 42 driver for the PC speaker which allows it to act like a primitive
44 This driver also replaces the pcspkr driver for beeps.
49 driver may lead to a problem. Namely, it may get loaded
50 before the other sound driver of yours, making the
52 what you want. To make this driver play nicely with other
53 sound driver, you can add this into your /etc/modprobe.conf:
56 You don't need this driver if you only want your pc-speaker to beep.
57 You don't need this driver if you have a tablet piezo beeper
68 Say Y here to include the dummy driver. This driver does
74 To compile this driver as a module, choose M here: the module
[all …]
|
| /linux-3.3/drivers/usb/gadget/ |
| D | udc-core.c | 31 * @driver - the gadget driver pointer. For use by the class code
34 * @list - for use by the udc class driver
37 * to hold information about udc driver and gadget together.
40 struct usb_gadget_driver *driver; member
55 * @driver: The driver we want to bind to @gadget
56 * @bind: The bind function for @driver
58 * This call is issued by the UDC Class driver when it's about
59 * to register a gadget driver to the device controller, before
60 * calling gadget driver's bind() method.
68 struct usb_gadget_driver *driver, in usb_gadget_start() argument
[all …]
|
| /linux-3.3/drivers/usb/misc/ |
| D | Kconfig | 2 # USB Miscellaneous driver configuration
11 This driver loads firmware to Emagic EMI 6|2m low latency USB
15 USB Audio driver.
26 This driver loads firmware to Emagic EMI 2|6 low latency USB
30 USB Audio driver.
32 To compile this driver as a module, choose M here: the
42 To compile this driver as a module, choose M here. The module
51 To compile this driver as a module, choose M here: the
62 To compile this driver as a module, choose M here: the
79 tristate "USB LCD driver support"
[all …]
|
| /linux-3.3/drivers/net/wireless/hostap/ |
| D | Kconfig | 18 Shared driver code for IEEE 802.11b wireless cards based on
19 Intersil Prism2/2.5/3 chipset. This driver supports so called
24 Host AP driver configuration and tools. This site includes
28 This option includes the base Host AP driver code that is shared by
30 PLX/PCI/CS version of the driver to actually use the driver.
32 The driver can be compiled as a module and it will be called
36 bool "Support downloading firmware images with Host AP driver"
39 Configure Host AP driver to include support for firmware image
52 Allow Host AP driver to write firmware images to the non-volatile
61 tristate "Host AP driver for Prism2/2.5/3 in PLX9052 PCI adaptors"
[all …]
|
| /linux-3.3/drivers/uio/ |
| D | Kconfig | 5 Enable this to allow the userspace driver core code to be
8 to be written in userspace. Note that a small kernel driver
16 tristate "generic Hilscher CIF Card driver"
19 Driver for Hilscher CIF DeviceNet and Profibus cards. This
20 driver requires a userspace component called cif that handles
24 To compile this driver as a module, choose M here: the module
28 tristate "Userspace I/O platform driver"
30 Generic platform driver for Userspace I/O devices.
35 tristate "Userspace I/O platform driver with generic IRQ handling"
37 Platform driver for Userspace I/O devices, including generic
[all …]
|
| /linux-3.3/drivers/block/paride/ |
| D | Kconfig | 15 This option enables the high-level driver for IDE-type disk devices
18 parallel port IDE driver, otherwise you should answer M to build
20 must also have at least one parallel port protocol driver in your
21 system. Among the devices supported by this driver are the SyQuest
29 This option enables the high-level driver for ATAPI CD-ROM devices
32 parallel port ATAPI CD-ROM driver, otherwise you should answer M to
34 must also have at least one parallel port protocol driver in your
35 system. Among the devices supported by this driver are the
45 This option enables the high-level driver for ATAPI disk devices
48 parallel port ATAPI disk driver, otherwise you should answer M
[all …]
|