Home
last modified time | relevance | path

Searched refs:Drivers (Results 1 – 179 of 179) sorted by relevance

/linux-4.4.14/drivers/net/phy/
DKconfig18 tristate "Drivers for the Aquantia PHYs"
23 tristate "Drivers for Atheros AT803X PHYs"
28 tristate "Drivers for the AMD PHYs"
33 tristate "Drivers for Marvell PHYs"
38 tristate "Drivers for Davicom PHYs"
43 tristate "Drivers for Quality Semiconductor PHYs"
48 tristate "Drivers for the Intel LXT PHYs"
53 tristate "Drivers for the Cicada PHYs"
58 tristate "Drivers for the Vitesse PHYs"
63 tristate "Drivers for the Teranetics PHYs"
[all …]
/linux-4.4.14/drivers/lguest/
DMakefile10 Drivers: PREFIX=D target
16 …@for f in Preparation Guest Drivers Launcher Host Switcher Mastery; do echo "{==- $$f -==}"; make …
17 Preparation Preparation! Guest Drivers Launcher Host Switcher Mastery:
DREADME26 III) Drivers
/linux-4.4.14/drivers/cpuidle/
DKconfig31 menu "ARM CPU Idle Drivers"
36 menu "MIPS CPU Idle Drivers"
41 menu "POWERPC CPU Idle Drivers"
DKconfig.powerpc2 # POWERPC CPU Idle Drivers
DKconfig.mips2 # MIPS CPU Idle Drivers
/linux-4.4.14/drivers/platform/mips/
DKconfig2 # MIPS Platform Specific Drivers
6 bool "MIPS Platform Specific Device Drivers"
/linux-4.4.14/Documentation/
Dmedia-framework.txt48 Drivers register media device instances by calling
87 Drivers unregister media device instances by calling
104 Drivers initialize entities by calling
118 Drivers must set the direction of every pad in the pads array before calling
127 Drivers register entities with a media device by calling
132 Entities are identified by a unique positive integer ID. Drivers can provide an
134 media controller framework to assign an ID automatically. Drivers that provide
138 Drivers unregister entities by calling
148 Drivers free resources associated with an entity by calling
178 managed by the entity driver. Drivers usually embed the array in a
[all …]
Dkernel-docs.txt42 * Title: "Linux Device Drivers, Third Edition"
59 7.-Interrupts and Interrupt Handling, 8.-Device Drivers, 9.-The
65 * Title: "Linux Device Drivers, 2nd Edition"
125 * Title: "Dynamic Kernels: Modularized Device Drivers"
174 * Title: "Device Drivers Concluded"
197 * Title: "Writing Linux Device Drivers"
326 * Title: "Programming Guide for Linux USB Device Drivers"
376 * Title: "Porting Linux 2.0 Drivers To Linux 2.2: Changes and New
384 * Title: "Porting Device Drivers To Linux 2.2: part II"
397 * Title: "An Introduction to SCSI Drivers"
[all …]
DSubmittingDrivers1 Submitting Drivers For The Linux Kernel
26 Who To Submit Drivers To
139 Linux Device Drivers, Third Edition (covers 2.6.10):
Dntb.txt1 # NTB Drivers
21 ## NTB Client Drivers
99 ## NTB Hardware Drivers
Dbraille-console.txt5 console (see serial-console.txt), and for braille device (in Device Drivers -
Dzorro.txt1 Writing Device Drivers for Zorro Devices
Drfkill.txt61 Drivers for radio transmitters normally implement an rfkill driver.
Dpnp.txt168 Linux Plug and Play Drivers
Ddebugging-via-ohci1394.txt40 Drivers
Dclk.txt256 Drivers don't need to manually protect resources shared between the operations
Drtc.txt2 Real Time Clock (RTC) Drivers for Linux
Drpmsg.txt179 Drivers should provide their channel (so the new endpoint would bind
DDMA-API-HOWTO.txt757 Drivers converted fully to this interface should not use virt_to_bus() any
942 DMA-safe. Drivers and subsystems depend on it. If an architecture
Dpinctrl.txt1292 Drivers needing both pin control and GPIOs
/linux-4.4.14/drivers/firmware/google/
DKconfig2 bool "Google Firmware Drivers"
10 menu "Google Firmware Drivers"
/linux-4.4.14/drivers/net/wireless/p54/
DKconfig12 <http://wireless.kernel.org/en/users/Drivers/p54>
24 <http://wireless.kernel.org/en/users/Drivers/p54>
38 <http://wireless.kernel.org/en/users/Drivers/p54>
/linux-4.4.14/Documentation/driver-model/
Ddriver.txt2 Device Drivers
97 Transition Bus Drivers
101 made easier. Drivers can ignore the generic structure altogether and
148 and the driver partially bound to the device. Drivers commonly use
158 Drivers often store a pointer to their state with dev_set_drvdata().
199 Drivers can declare attributes using a DRIVER_ATTR macro that works
Dbus.txt40 match(): Attaching Drivers to Devices
44 them are inherently bus-specific. Drivers typically declare an array
96 Drivers registered with the bus get a directory in the bus's drivers
Dclass.txt72 Device Drivers
92 Drivers registered with the class get a symlink in the drivers/ directory
Dplatform.txt1 Platform Devices and Drivers
113 Legacy Drivers: Device Probing
178 unbound devices on that bus are checked for matches. Drivers
187 Early Platform Devices and Drivers
Dporting.txt2 Porting Drivers to the New Driver Model
226 Step 3: Registering Drivers.
268 Drivers are exported via sysfs in their bus's 'driver's directory.
279 Step 4: Define Generic Methods for Drivers.
/linux-4.4.14/drivers/net/wireless/ath/
DKconfig14 http://wireless.kernel.org/en/users/Drivers/ath
18 http://wireless.kernel.org/en/users/Drivers/Atheros
/linux-4.4.14/Documentation/w1/
D00-INDEX4 - Drivers that provide support for specific family codes.
/linux-4.4.14/Documentation/sound/alsa/soc/
Dplatform.txt55 SoC DAI Drivers
69 SoC DSP Drivers
Doverview.txt20 * Drivers tended to power up the entire codec when playing (or
/linux-4.4.14/drivers/perf/
DKconfig2 # Performance Monitor Drivers
/linux-4.4.14/drivers/soc/
DKconfig1 menu "SOC (System On Chip) specific Drivers"
/linux-4.4.14/drivers/vme/boards/
DKconfig1 comment "VME Board Drivers"
/linux-4.4.14/drivers/vme/bridges/
DKconfig1 comment "VME Bridge Drivers"
/linux-4.4.14/drivers/scsi/megaraid/
DKconfig.megaraid2 bool "LSI Logic New Generation RAID Device Drivers"
5 LSI Logic RAID Device Drivers
/linux-4.4.14/arch/sh/drivers/
DKconfig4 menu "Additional SuperH Device Drivers"
/linux-4.4.14/drivers/usb/renesas_usbhs/
DKconfig2 # Renesas USBHS Controller Drivers
/linux-4.4.14/Documentation/gpio/
D00-INDEX10 - Drivers in other subsystems that can use GPIO to provide more
Dsysfs.txt144 symlinks from elsewhere in sysfs to the GPIO sysfs node. Drivers can
Dgpio.txt29 which GPIOs. Drivers can be written generically, so that board setup code
Dgpio-legacy.txt16 which GPIOs. Drivers can be written generically, so that board setup code
76 ARCH_WANT_OPTIONAL_GPIOLIB in their Kconfig. Drivers that can't work without
526 Controller Drivers: gpio_chip
764 symlinks from elsewhere in sysfs to the GPIO sysfs node. Drivers can
Ddriver.txt37 Controller Drivers: gpio_chip
Dconsumer.txt12 Drivers that can't work without standard GPIO calls should have Kconfig entries
/linux-4.4.14/Documentation/power/regulator/
Dregulator.txt11 Drivers can register a regulator by calling :-
/linux-4.4.14/sound/sh/
DKconfig9 Drivers that are implemented on ASoC can be found in
/linux-4.4.14/sound/arm/
DKconfig9 Drivers that are implemented on ASoC can be found in
/linux-4.4.14/net/dsa/
DKconfig5 # Drivers must select NET_DSA and the appropriate tagging format
/linux-4.4.14/drivers/android/
DKconfig4 bool "Android Drivers"
/linux-4.4.14/net/wimax/
DKconfig19 Device Drivers > Network device support > WiMAX Wireless
/linux-4.4.14/drivers/staging/vme/devices/
DKconfig1 comment "VME Device Drivers"
/linux-4.4.14/Documentation/console/
Dconsole.txt1 Console Drivers
14 that is currently occupied by another modular driver. (Exception: Drivers that
79 Device Drivers -> Character devices -> Support for binding and unbinding
/linux-4.4.14/Documentation/video4linux/
DZoran30 Drivers to use: videodev, i2c-core, i2c-algo-bit,
41 Drivers to use: videodev, i2c-core, i2c-algo-bit,
56 Drivers to use: videodev, i2c-core, i2c-algo-bit,
67 Drivers to use: videodev, i2c-core, i2c-algo-bit,
78 Drivers to use: videodev, i2c-core, i2c-algo-bit,
89 Drivers to use: videodev, i2c-core, i2c-algo-bit,
101 Drivers to use: videodev, i2c-core, i2c-algo-bit,
113 Drivers to use: videodev, i2c-core, i2c-algo-bit,
125 Drivers to use: videodev, i2c-core, i2c-algo-bit,
Dzr364xx.txt21 Location: Device Drivers -> Multimedia devices -> Video For Linux -> Video Capture Adapters -> V4L …
Dvideobuf287 Drivers using the vmalloc() method need not (and cannot) concern themselves
331 scatterlist structure described above. Drivers using the vmalloc() method
Dv4l2-framework.txt96 Drivers that want integration with the media device framework need to set
943 Drivers can extract their own file handle structure by using the container_of
Dv4l2-controls.txt731 Drivers do not have to care about this. The framework will automatically add
/linux-4.4.14/Documentation/x86/
Dpat.txt95 Drivers wanting to export some pages to userspace do it by using mmap
162 Drivers should use ioremap_[uc|wc] to access PCI BARs with [uc|wc] access
165 Drivers should use set_memory_[uc|wc|wt] to set access type for RAM ranges.
/linux-4.4.14/drivers/net/wireless/ath/wil6210/
DKconfig12 http://wireless.kernel.org/en/users/Drivers/wil6210
/linux-4.4.14/arch/avr32/boards/hammerhead/
DKconfig41 Device Drivers->Misc to be able to use FPGA functionality.
/linux-4.4.14/drivers/misc/mic/
DKconfig93 comment "Intel MIC Coprocessor State Management (COSM) Drivers"
96 tristate "Intel MIC Coprocessor State Management (COSM) Drivers"
/linux-4.4.14/drivers/net/wireless/ath/carl9170/
DKconfig14 <http://wireless.kernel.org/en/users/Drivers/carl9170>
/linux-4.4.14/Documentation/memory-devices/
Dti-emif.txt18 Device Drivers
/linux-4.4.14/Documentation/fb/
Dapi.txt248 drivers. Drivers must fill the red, blue and green offsets to 0 and lengths
253 ignored by drivers. Drivers must fill the red, blue and green offsets to 0
283 formats. Drivers are also encouraged to implement the FOURCC-based API for RGB
286 Drivers that support the FOURCC-based API report this capability by setting
Dmodedb.txt137 Drivers that support modedb boot options
Dintel810.txt246 Drivers".
Dfbcon.txt21 configuration tool. It is under Device Drivers->Graphics Support->Support for
/linux-4.4.14/drivers/video/fbdev/omap2/displays-new/
DKconfig1 menu "OMAP Display Device Drivers (new device model)"
/linux-4.4.14/Documentation/networking/
Dx25-iface.txt99 (1) Drivers for kernel versions 2.4.x and above should always check the
109 (2) Drivers for kernel versions 2.2.x should always check the global
Dnetif-msg.txt19 always implemented within +-1 of the specified level. Drivers tended
Di40e.txt39 -> Device Drivers
Ds2io.txt129 d. Enable NAPI feature(in kernel configuration Device Drivers ---> Network
Dbaycom.txt9 This document describes the Linux Kernel Drivers for simple Baycom style
Dregulatory.txt68 * Drivers
Dtimestamping.txt362 Drivers are free to use a more permissive configuration than the requested
420 3.1 Hardware Timestamping Implementation: Device Drivers
Dpktgen.txt40 TX ring cause delay. Drivers usually delay cleaning up the
Dixgbe.txt254 -> Device Drivers
Daltera_tse.txt51 Device Drivers ---> Network device support ---> Ethernet driver support --->
Dstmmac.txt22 Device Drivers ---> Network device support ---> Ethernet (1000 Mbit) --->
Dvortex.txt283 Additional documentation is available at Don Becker's Linux Drivers site:
Dphy.txt220 PHY Device Drivers
Dixgb.txt71 -> Device Drivers
Dscaling.txt345 the IRQ affinity table shown by /proc/interrupts. Drivers can use
Darcnet.txt79 Other Drivers and Info
Dbonding.txt2821 Donald Becker's Ethernet Drivers and diag programs may be found at :
/linux-4.4.14/lib/
DKconfig184 This option provides CRC8 function. Drivers may select this
303 Drivers may select this option to force specific constant
323 Drivers should declare a default value for this symbol if
330 Drivers should declare a default value for this symbol if
DKconfig.debug685 Drivers ought to be able to handle interrupts coming in at those
/linux-4.4.14/drivers/memstick/host/
DKconfig5 comment "MemoryStick Host Controller Drivers"
/linux-4.4.14/arch/sh/drivers/dma/
DKconfig69 G2 bus. Drivers that want this will generally enable this on
/linux-4.4.14/Documentation/devicetree/bindings/pwm/
Dpwm.txt22 Drivers for devices that use more than a single PWM device can use the
/linux-4.4.14/Documentation/arm/OMAP/
Domap_pm11 Drivers need to express PM parameters which:
73 to NULL. Drivers should use the following idiom:
/linux-4.4.14/drivers/net/wireless/ath/ath9k/
DKconfig36 http://wireless.kernel.org/en/users/Drivers/ath9k/products
170 For more information: http://wireless.kernel.org/en/users/Drivers/ath9k_htc
/linux-4.4.14/drivers/mmc/card/
DKconfig5 comment "MMC/SD/SDIO Card Drivers"
/linux-4.4.14/Documentation/arm/Samsung-S3C24XX/
DUSB-Host.txt18 Device Drivers --->
/linux-4.4.14/drivers/staging/iio/
DTODO75 ADI Drivers:
/linux-4.4.14/net/wireless/
DKconfig200 Drivers should select this option if they require cfg80211's
210 Drivers should select this themselves if needed.
/linux-4.4.14/drivers/
DKconfig1 menu "Device Drivers"
/linux-4.4.14/Documentation/sound/alsa/
DJoystick.txt1 Analog Joystick Support on ALSA Drivers
DProcfile.txt1 Proc Files of ALSA Drivers
/linux-4.4.14/arch/unicore32/configs/
Dunicore32_defconfig74 ### Device Drivers
/linux-4.4.14/Documentation/scsi/
Dcxgb3i.txt53 Device Drivers
/linux-4.4.14/Documentation/development-process/
D8.Conclusion30 Linux Device Drivers, 3rd Edition (Jonathan Corbet, Alessandro
D2.Process307 Greg Kroah-Hartman currently maintains the staging tree. Drivers that
/linux-4.4.14/Documentation/devicetree/bindings/powerpc/fsl/cpm_qe/qe/
Ducc.txt34 Drivers that currently use the deprecated properties should continue to
/linux-4.4.14/drivers/net/wireless/
DKconfig16 http://wireless.kernel.org/en/users/Drivers
163 http://wireless.kernel.org/en/users/Drivers/p54
/linux-4.4.14/Documentation/ptp/
Dptp.txt64 Drivers must ensure that all of the methods in interface are
/linux-4.4.14/Documentation/usb/
Dbulk-streams.txt50 Drivers will only be allowed to call this API once for the same endpoint
Derror-codes.txt6 Some of them are returned by the Host Controller Drivers (HCDs), which
Dhotplug.txt121 Drivers that connect directly to the USB subsystem should be declared
Dpower-management.txt368 Drivers need not be concerned about balancing changes to the usage
374 Drivers using the async routines are responsible for their own
419 Drivers can enable autosuspend for their devices by calling
Dusbmon.txt11 Controller Drivers (HCD). So, if HCD is buggy, the traces reported by
Dusb-serial.txt450 of the Device Drivers config menu. Currently only compatibility mode is
/linux-4.4.14/Documentation/dmaengine/
Ddmatest.txt11 Device Drivers -> DMA Engine support -> DMA Test client
Dprovider.txt266 - Drivers should try to pre-allocate any memory they might need
/linux-4.4.14/drivers/devfreq/
DKconfig67 comment "DEVFREQ Drivers"
/linux-4.4.14/arch/xtensa/configs/
Diss_defconfig273 # Device Drivers
341 # Input Device Drivers
420 # Watchdog Device Drivers
Dcommon_defconfig110 # Device Drivers
409 # Input Device Drivers
/linux-4.4.14/Documentation/acpi/
Dgpio-properties.txt54 ACPI GPIO Mappings Provided by Drivers
/linux-4.4.14/Documentation/block/
Dwriteback_cache_control.txt59 data can be completed successfully without doing any work. Drivers for
Dbiodoc.txt347 Drivers can now specify a request prepare function (q->prep_rq_fn) that the
464 - Drivers which can't process a large bio in one shot can use the bi_iter
654 that traverse bio chains on completion need to keep that in mind. Drivers
700 Drivers that do not interpret bios e.g those which do not handle multiple
1060 should still be SMP safe. Drivers are free to drop the queue
1061 lock themselves, if required. Drivers that explicitly used the
1102 Drivers should use elv_next_request to pick up requests and are no longer
1118 etc per queue now. Drivers that used to define their own merge functions i
1122 Drivers no longer have to map a {partition, sector offset} into the
/linux-4.4.14/drivers/net/wireless/realtek/rtlwifi/
DKconfig7 wireless drivers. Drivers rtl8192ce, rtl8192cu, rtl8192se, rtl8192de,
/linux-4.4.14/drivers/usb/musb/
DKconfig2 # USB Dual Role (OTG-ready) Controller Drivers
/linux-4.4.14/Documentation/devicetree/bindings/leds/
Dleds-lp55xx.txt1 Binding for TI/National Semiconductor LP55xx Led Drivers
/linux-4.4.14/drivers/extcon/
DKconfig15 comment "Extcon Device Drivers"
/linux-4.4.14/tools/lguest/
Dlguest.txt40 "Device Drivers":
/linux-4.4.14/Documentation/misc-devices/
Dspear-pcie-gadget.txt18 Device Drivers
/linux-4.4.14/Documentation/wimax/
DREADME.i2400m28 Configure the kernel; to enable the WiMAX drivers select Drivers >
29 Networking Drivers > WiMAX device support. Enable all of them as
/linux-4.4.14/drivers/net/wireless/iwlwifi/
DKconfig33 <http://wireless.kernel.org/en/users/Drivers/iwlwifi>.
/linux-4.4.14/Documentation/ABI/stable/
Dsysfs-bus-usb83 Drivers will not use reset for error handling for
/linux-4.4.14/Documentation/power/
Ddevices.txt21 Drivers will use one or both of these models to put devices into low-power
25 Drivers can enter low-power states as part of entering system-wide
228 Calling Drivers to Enter and Leave System Sleep States
378 will also switch off power supplies or reduce voltages. (Drivers supporting
449 Drivers need to be able to handle hardware which has been reset since the
456 Drivers must also be prepared to notice that the device has been removed
Druntime_pm.txt810 Inactivity is determined based on the power.last_busy field. Drivers should
828 Drivers may also continue to use the non-autosuspend helper functions; they
Dpci.txt18 3. PCI Device Drivers and Power Management
669 3. PCI Device Drivers and Power Management
/linux-4.4.14/Documentation/i2c/
Dupgrading-clients1 Upgrading I2C Drivers to the new 2.6 Driver Model
Dwriting-clients128 problematic. Drivers for I2C devices that issue interrupts need more (and
/linux-4.4.14/arch/cris/
DKconfig234 not be enabled under Drivers for built-in interfaces (as it has its
267 menu "Drivers for built-in interfaces"
/linux-4.4.14/Documentation/PCI/
Dpci-error-recovery.txt298 Drivers should not restart normal I/O processing operations
311 Drivers for multi-function cards will need to coordinate among
323 Drivers for PCI Express cards that require a fundamental reset must
Dpci.txt2 How To Write Linux PCI Drivers
15 A more complete resource is the third edition of "Linux Device Drivers"
334 Drivers for all PCI-X and PCIe compliant devices must call
DPCIEBUS-HOWTO.txt66 5. Configuring the PCI Express Port Bus Driver vs. Service Drivers
/linux-4.4.14/drivers/net/can/
DKconfig1 menu "CAN Device Drivers"
/linux-4.4.14/Documentation/ABI/testing/
Dsysfs-bus-pci75 drivers of all child devices under the bridge. Drivers
239 element. Drivers have the ability at probe time to reduce the
Dsysfs-bus-iio603 these attributes after everything is configured. Drivers may
657 these attributes after everything is configured. Drivers may
/linux-4.4.14/drivers/firmware/
DKconfig6 menu "Firmware Drivers"
/linux-4.4.14/drivers/input/
DKconfig190 comment "Input Device Drivers"
/linux-4.4.14/drivers/usb/gadget/
DKconfig133 # USB Gadget Drivers
203 tristate "USB Gadget Drivers"
/linux-4.4.14/Documentation/hid/
Dhid-transport.txt1 HID I/O Transport Drivers
44 Example Drivers:
/linux-4.4.14/arch/cris/arch-v32/
DKconfig19 not be enabled under Drivers for built-in interfaces (as it has its
/linux-4.4.14/drivers/usb/phy/
DKconfig10 # USB Transceiver Drivers
/linux-4.4.14/Documentation/input/
Dmulti-touch-protocol.txt31 Drivers for type A devices separate contact packets by calling
36 Drivers for type B devices separate contact packets by calling
/linux-4.4.14/Documentation/rapidio/
Drapidio.txt76 2.5 Device Drivers
312 4.6 Using Loadable RapidIO Switch Drivers
/linux-4.4.14/Documentation/sound/oss/
DIntroduction1 Introduction Notes on Modular Sound Drivers and Soundcore
39 Modular Sound Drivers:
/linux-4.4.14/Documentation/arm64/
Darm-acpi.txt195 Drivers should determine their probe() type by checking for a null
247 regulation of the use of _DSM than there is of _DSD. Drivers that depend
252 Drivers should look for device properties in the _DSD object ONLY; the _DSD
/linux-4.4.14/Documentation/cpu-freq/
Dcpu-drivers.txt212 Drivers can return '0' from get_intermediate() in case they don't wish to switch
/linux-4.4.14/drivers/mtd/devices/
DKconfig206 comment "Disk-On-Chip Device Drivers"
/linux-4.4.14/Documentation/filesystems/nfs/
Dnfs-rdma.txt123 Device Drivers -> InfiniBand support, update the kernel configuration
/linux-4.4.14/drivers/iommu/
DKconfig286 Warning: Drivers (including userspace drivers of UIO
/linux-4.4.14/Documentation/powerpc/
Dhvcs.txt74 Device Drivers --->
86 Device Drivers --->
/linux-4.4.14/Documentation/watchdog/
Dwatchdog-kernel-api.txt15 WatchDog Timer Drivers that want to use the WatchDog Timer Driver Core
/linux-4.4.14/drivers/base/
DKconfig171 Drivers should "select" this option if they desire to use the
/linux-4.4.14/drivers/usb/host/
DKconfig2 # USB Host Controller Drivers
4 comment "USB Host Controller Drivers"
/linux-4.4.14/Documentation/isdn/
DINTERFACE.CAPI1 Kernel CAPI Interface to Hardware Drivers
DINTERFACE74 its internal purposes. Drivers not supporting sk_buff's should
/linux-4.4.14/Documentation/nfc/
Dnfc-hci.txt175 Included Drivers
/linux-4.4.14/drivers/platform/x86/
DKconfig2 # X86 Platform Specific Drivers
6 bool "X86 Platform Specific Device Drivers"
/linux-4.4.14/Documentation/serial/
Ddriver195 Drivers must not access port->info once this call has completed.
/linux-4.4.14/drivers/staging/unisys/Documentation/
Doverview.txt19 present the virtual busses involved. Drivers in the 'visor*' driver set are
/linux-4.4.14/Documentation/thermal/
Dsysfs-api.txt462 of the framework. Drivers which intend to use the notification mechanism
/linux-4.4.14/drivers/spi/
DKconfig54 comment "SPI Master Controller Drivers"
/linux-4.4.14/Documentation/s390/
Dcds.txt88 Common Device Support (CDS) for Linux/390 Device Drivers
/linux-4.4.14/
DMAINTAINERS1837 W: http://wireless.kernel.org/en/users/Drivers/ath5k
1844 W: http://wireless.kernel.org/en/users/Drivers/ath6kl
1854 W: http://wireless.kernel.org/en/users/Drivers/wil6210
1861 W: http://wireless.kernel.org/en/users/Drivers/carl9170
2083 W: http://wireless.kernel.org/en/users/Drivers/b43
2091 W: http://wireless.kernel.org/en/users/Drivers/b43
5286 IBM Power Virtual SCSI Device Drivers
5293 IBM Power Virtual FC Device Drivers
7950 W: http://wireless.kernel.org/en/users/Drivers/orinoco
7977 W: http://wireless.kernel.org/en/users/Drivers/p54
[all …]
DCREDITS1844 D: Drivers
/linux-4.4.14/drivers/mmc/host/
DKconfig5 comment "MMC/SD/SDIO Host Controller Drivers"
/linux-4.4.14/drivers/hid/
DKconfig62 Say Y here if you want to provide HID I/O Drivers from user-space.
/linux-4.4.14/Documentation/spi/
Dspi-summary511 Drivers may change the defaults provided by board_info, and then
/linux-4.4.14/Documentation/laptops/
Dthinkpad-acpi.txt70 It is located on the menu path: "Device Drivers" -> "X86 Platform
71 Specific Device Drivers" -> "ThinkPad ACPI Laptop Extras".
/linux-4.4.14/drivers/mfd/
DKconfig969 menu "STMicroelectronics STMPE Interface Drivers"
/linux-4.4.14/drivers/watchdog/
DKconfig53 comment "Watchdog Device Drivers"
/linux-4.4.14/arch/arm/
DKconfig118 for larger buffers it just a waste of address space. Drivers which has
/linux-4.4.14/arch/x86/
DKconfig553 and power. Drivers may query the availability of this device to