Home
last modified time | relevance | path

Searched refs:drivers (Results 1 – 200 of 1076) sorted by relevance

123456

/linux-4.1.27/drivers/
DKconfig3 source "drivers/amba/Kconfig"
5 source "drivers/base/Kconfig"
7 source "drivers/bus/Kconfig"
9 source "drivers/connector/Kconfig"
11 source "drivers/mtd/Kconfig"
13 source "drivers/of/Kconfig"
15 source "drivers/parport/Kconfig"
17 source "drivers/pnp/Kconfig"
19 source "drivers/block/Kconfig"
23 source "drivers/misc/Kconfig"
[all …]
/linux-4.1.27/Documentation/DocBook/
D.drm.xml.cmd2 …drivers/gpu/drm/drm_pci.c drivers/gpu/drm/drm_platform.c drivers/gpu/drm/drm_drv.c drivers/gpu/drm…
D.device-drivers.xml.cmd1 …cBook/device-drivers.xml := SRCTREE=./ ./scripts/docproc doc Documentation/DocBook/device-drivers.…
2 …drivers.xml: Documentation/DocBook/device-drivers.tmpl include/linux/init.h arch/x86/include/asm/a…
D.scsi.xml.cmd2 …drivers/scsi/scsi.c drivers/scsi/scsicam.c drivers/scsi/scsi_error.c drivers/scsi/scsi_devinfo.c d…
D.s390-drivers.xml.cmd1 …n/DocBook/s390-drivers.xml := SRCTREE=./ ./scripts/docproc doc Documentation/DocBook/s390-drivers.…
2 …drivers.xml: Documentation/DocBook/s390-drivers.tmpl arch/s390/include/asm/cio.h arch/s390/include…
D.kernel-api.xml.cmd2 …drivers/pci/pci.c drivers/pci/pci-driver.c drivers/pci/remove.c drivers/pci/search.c drivers/pci/m…
D.usb.xml.cmd2 …drivers/usb/core/urb.c drivers/usb/core/message.c drivers/usb/core/file.c drivers/usb/core/driver.…
D.w1.xml.cmd2 …l drivers/w1/w1.h drivers/w1/w1.c drivers/w1/w1_family.h drivers/w1/w1_family.c drivers/w1/w1_int.…
D.gadget.xml.cmd2 …drivers/usb/gadget/usbstring.c drivers/usb/gadget/config.c include/linux/usb/composite.h drivers/u…
D.rapidio.xml.cmd2 …drivers/rapidio/rio-driver.c drivers/rapidio/rio.c include/linux/rio.h drivers/rapidio/rio-scan.c …
D.libata.xml.cmd2 …ata.tmpl drivers/ata/libata-core.c drivers/ata/libata-core.c drivers/ata/libata-scsi.c drivers/ata…
D.mtdnand.xml.cmd2 …inux/mtd/nand.h drivers/mtd/nand/nand_base.c drivers/mtd/nand/nand_bbt.c drivers/mtd/nand/nand_ecc…
D.networking.xml.cmd2 …evice.h drivers/net/phy/phy.c drivers/net/phy/phy.c drivers/net/phy/phy_device.c drivers/net/phy/p…
D.z8530book.xml.cmd2 …DocBook/z8530book.xml: Documentation/DocBook/z8530book.tmpl drivers/net/wan/z85230.c drivers/net/w…
D.sh.xml.cmd2 …ch-dreamcast/rtc.c arch/sh/boards/mach-x3proto/ilsel.c drivers/sh/superhyway/superhyway.c drivers/…
/linux-4.1.27/drivers/staging/
DKconfig2 bool "Staging drivers"
5 This option allows you to select a number of drivers that are
6 not of the "normal" Linux kernel quality level. These drivers
8 them. Please note that these drivers are under heavy
13 Using any of these drivers will taint your kernel which might
17 If you wish to work on these drivers, to help improve them, or
19 driver_name.README file in the drivers/staging/ directory to
27 source "drivers/staging/slicoss/Kconfig"
29 source "drivers/staging/wlan-ng/Kconfig"
31 source "drivers/staging/comedi/Kconfig"
[all …]
/linux-4.1.27/drivers/net/ethernet/
DKconfig10 This section contains all the Ethernet device drivers.
20 source "drivers/net/ethernet/3com/Kconfig"
21 source "drivers/net/ethernet/adaptec/Kconfig"
22 source "drivers/net/ethernet/aeroflex/Kconfig"
23 source "drivers/net/ethernet/agere/Kconfig"
24 source "drivers/net/ethernet/allwinner/Kconfig"
25 source "drivers/net/ethernet/alteon/Kconfig"
26 source "drivers/net/ethernet/altera/Kconfig"
27 source "drivers/net/ethernet/amd/Kconfig"
28 source "drivers/net/ethernet/apm/Kconfig"
[all …]
/linux-4.1.27/drivers/media/pci/
DKconfig6 Enable media drivers for PCI/PCIe bus.
13 source "drivers/media/pci/meye/Kconfig"
14 source "drivers/media/pci/sta2x11/Kconfig"
19 source "drivers/media/pci/ivtv/Kconfig"
20 source "drivers/media/pci/zoran/Kconfig"
21 source "drivers/media/pci/saa7146/Kconfig"
22 source "drivers/media/pci/solo6x10/Kconfig"
23 source "drivers/media/pci/tw68/Kconfig"
28 source "drivers/media/pci/cx18/Kconfig"
29 source "drivers/media/pci/cx23885/Kconfig"
[all …]
/linux-4.1.27/drivers/media/usb/
DKconfig6 Enable media drivers for USB bus.
13 source "drivers/media/usb/uvc/Kconfig"
14 source "drivers/media/usb/gspca/Kconfig"
15 source "drivers/media/usb/pwc/Kconfig"
16 source "drivers/media/usb/cpia2/Kconfig"
17 source "drivers/media/usb/zr364xx/Kconfig"
18 source "drivers/media/usb/stkwebcam/Kconfig"
19 source "drivers/media/usb/s2255/Kconfig"
20 source "drivers/media/usb/usbtv/Kconfig"
25 source "drivers/media/usb/pvrusb2/Kconfig"
[all …]
/linux-4.1.27/Documentation/zh_CN/
Dmagic-number.txt65 MKISS_DRIVER_MAGIC 0x04bf mkiss_channel drivers/net/mkiss.h
66 HDLC_MAGIC 0x239e n_hdlc drivers/char/n_hdlc.c
69 DB_MAGIC 0x4442 fc_info drivers/net/iph5526_novram.c
70 DL_MAGIC 0x444d fc_info drivers/net/iph5526_novram.c
72 FF_MAGIC 0x4646 fc_info drivers/net/iph5526_novram.c
74 PTY_MAGIC 0x5001 drivers/char/pty.c
78 SLIP_MAGIC 0x5302 slip drivers/net/slip.h
79 STRIP_MAGIC 0x5303 strip drivers/net/strip.c
80 X25_ASY_MAGIC 0x5303 x25_asy drivers/net/x25_asy.h
81 SIXPACK_MAGIC 0x5304 sixpack drivers/net/hamradio/6pack.h
[all …]
/linux-4.1.27/Documentation/
Dmagic-number.txt65 MKISS_DRIVER_MAGIC 0x04bf mkiss_channel drivers/net/mkiss.h
66 HDLC_MAGIC 0x239e n_hdlc drivers/char/n_hdlc.c
69 DB_MAGIC 0x4442 fc_info drivers/net/iph5526_novram.c
70 DL_MAGIC 0x444d fc_info drivers/net/iph5526_novram.c
72 FF_MAGIC 0x4646 fc_info drivers/net/iph5526_novram.c
74 PTY_MAGIC 0x5001 drivers/char/pty.c
78 SLIP_MAGIC 0x5302 slip drivers/net/slip.h
79 STRIP_MAGIC 0x5303 strip drivers/net/strip.c
80 X25_ASY_MAGIC 0x5303 x25_asy drivers/net/x25_asy.h
81 SIXPACK_MAGIC 0x5304 sixpack drivers/net/hamradio/6pack.h
[all …]
DSM501.txt14 The core driver in drivers/mfd provides common services for the
15 drivers which manage the specific hardware blocks. These services
19 The core registers drivers for both PCI and generic bus based
24 peripheral set as platform devices for the specific drivers.
27 system provides enough features to support the drivers without the
59 configurations through to the core and the subsidiary drivers
Drfkill.txt38 * the rfkill drivers.
40 The rfkill core provides API for kernel drivers to register their radio
51 block, but drivers can ignore the method call since they can use the return
53 instead of keeping track of calls to set_block(). In fact, drivers should
63 Platform drivers might implement input devices if the rfkill button is just
82 rfkill drivers that control devices that can be hard-blocked unless they also
101 system. Also, it is possible to switch all rfkill drivers (or all drivers of
DSubmittingDrivers4 This document is intended to explain how to submit device drivers to the
5 various kernel trees. Note that if you are interested in video card drivers
30 No new drivers are accepted for this kernel tree.
33 No new drivers are accepted for this kernel tree.
64 other drivers in the same class it will be much more likely
67 drivers do it in userspace.
79 careful thought. Pure x86 drivers generally are not popular.
100 Documentation/power/drivers-testing.txt and for a relatively
102 drivers see Documentation/power/devices.txt .
146 Porting drivers from prior kernels to 2.6:
Dpnp.txt12 services to compatible drivers.
19 for legacy and user level drivers that do not support Linux Plug and Play. The
95 All Plug and Play drivers, protocols, and services meet at a central location
97 information between PnP drivers and PnP protocols. Thus it automatically
98 forwards commands to the proper protocol. This makes writing PnP drivers
164 /drivers/pnp/pnpbios/core.c.
212 consult /drivers/serial/8250_pnp.c for more information.
239 ISAPNP drivers. They should serve as a temporary solution only.
Dhsi.txt41 The hsi subsystem contains drivers for hsi controllers including support for
44 It also contains HSI client drivers, which make use of the generic API to
45 implement a protocol used on the HSI interface. These client drivers can
Dmedia-framework.txt102 although drivers can allocate entities directly.
115 dynamically but is managed by the entity driver. Most drivers will embed the
166 drivers.
168 Media device drivers should define groups if several entities are logically
226 To iterate over all entities belonging to a media device, drivers can use the
276 Due to the wide differences between drivers regarding power management needs,
278 media_entity structure includes a use_count field that media drivers can use to
281 The use_count field is owned by media drivers and must not be touched by entity
282 drivers. Access to the field must be protected by the media device graph_mutex
303 Media device drivers can be notified of link setup operations by setting the
[all …]
Deisa.txt3 This document groups random notes about porting EISA drivers to the
9 abstractions to manage busses, devices and drivers.
12 drivers to the new infrastructure is not an easy task (mostly because
14 most EISA drivers are among the oldest Linux drivers so, as you can
182 drivers share their probing routine between ISA, and EISA. Special
190 Unfortunately, most drivers are doing the probing by themselves, and
/linux-4.1.27/drivers/staging/iio/
DKconfig4 menu "IIO staging drivers"
7 source "drivers/staging/iio/accel/Kconfig"
8 source "drivers/staging/iio/adc/Kconfig"
9 source "drivers/staging/iio/addac/Kconfig"
10 source "drivers/staging/iio/cdc/Kconfig"
11 source "drivers/staging/iio/frequency/Kconfig"
12 source "drivers/staging/iio/gyro/Kconfig"
13 source "drivers/staging/iio/impedance-analyzer/Kconfig"
14 source "drivers/staging/iio/light/Kconfig"
15 source "drivers/staging/iio/magnetometer/Kconfig"
[all …]
/linux-4.1.27/drivers/infiniband/
DKconfig10 any protocols you wish to use as well as drivers for your
57 source "drivers/infiniband/hw/mthca/Kconfig"
58 source "drivers/infiniband/hw/ipath/Kconfig"
59 source "drivers/infiniband/hw/qib/Kconfig"
60 source "drivers/infiniband/hw/ehca/Kconfig"
61 source "drivers/infiniband/hw/amso1100/Kconfig"
62 source "drivers/infiniband/hw/cxgb3/Kconfig"
63 source "drivers/infiniband/hw/cxgb4/Kconfig"
64 source "drivers/infiniband/hw/mlx4/Kconfig"
65 source "drivers/infiniband/hw/mlx5/Kconfig"
[all …]
/linux-4.1.27/drivers/iio/
DKconfig10 drivers for many different types of embedded sensors using a
26 Should be selected by any drivers that do in-kernel push
61 source "drivers/iio/accel/Kconfig"
62 source "drivers/iio/adc/Kconfig"
63 source "drivers/iio/amplifiers/Kconfig"
64 source "drivers/iio/common/Kconfig"
65 source "drivers/iio/dac/Kconfig"
66 source "drivers/iio/frequency/Kconfig"
67 source "drivers/iio/gyro/Kconfig"
68 source "drivers/iio/humidity/Kconfig"
[all …]
/linux-4.1.27/drivers/staging/fbtft/
DREADME4 Linux Framebuffer drivers for small TFT LCD display modules.
5 The module 'fbtft' makes writing drivers for some of these displays very easy.
13 cd drivers/video/fbdev/fbtft
16 Add to drivers/video/fbdev/Kconfig: source "drivers/video/fbdev/fbtft/Kconfig"
17 Add to drivers/video/fbdev/Makefile: obj-y += fbtft/
20 cd drivers/video
23 Add to drivers/video/Kconfig: source "drivers/video/fbtft/Kconfig"
24 Add to drivers/video/Makefile: obj-y += fbtft/
/linux-4.1.27/drivers/video/
DKconfig18 source "drivers/char/agp/Kconfig"
20 source "drivers/gpu/vga/Kconfig"
22 source "drivers/gpu/host1x/Kconfig"
23 source "drivers/gpu/ipu-v3/Kconfig"
26 source "drivers/gpu/drm/Kconfig"
30 source "drivers/video/fbdev/Kconfig"
33 source "drivers/video/backlight/Kconfig"
46 source "drivers/video/console/Kconfig"
50 source "drivers/video/logo/Kconfig"
/linux-4.1.27/drivers/staging/media/
DKconfig2 bool "Media staging drivers"
5 This option allows you to select a number of media drivers that
12 If you wish to work on these drivers, to help improve them, or
22 source "drivers/staging/media/bcm2048/Kconfig"
24 source "drivers/staging/media/cxd2099/Kconfig"
26 source "drivers/staging/media/davinci_vpfe/Kconfig"
28 source "drivers/staging/media/dt3155v4l/Kconfig"
30 source "drivers/staging/media/mn88472/Kconfig"
32 source "drivers/staging/media/mn88473/Kconfig"
34 source "drivers/staging/media/omap4iss/Kconfig"
[all …]
/linux-4.1.27/drivers/net/wireless/ath/
DKconfig8 This will enable the support for the Atheros wireless drivers.
9 ath5k, ath9k, ath9k_htc and ar9170 drivers share some common code, this option
16 For information on all Atheros wireless drivers visit:
25 Say Y, if you want to debug atheros wireless drivers.
33 This option enables tracepoints for atheros wireless drivers.
53 source "drivers/net/wireless/ath/ath5k/Kconfig"
54 source "drivers/net/wireless/ath/ath9k/Kconfig"
55 source "drivers/net/wireless/ath/carl9170/Kconfig"
56 source "drivers/net/wireless/ath/ath6kl/Kconfig"
57 source "drivers/net/wireless/ath/ar5523/Kconfig"
[all …]
/linux-4.1.27/drivers/gpu/drm/
DKconfig32 CRTC helpers for KMS drivers.
41 FBDEV helpers for KMS drivers.
80 source "drivers/gpu/drm/i2c/Kconfig"
82 source "drivers/gpu/drm/bridge/Kconfig"
121 source "drivers/gpu/drm/radeon/Kconfig"
123 source "drivers/gpu/drm/nouveau/Kconfig"
134 source "drivers/gpu/drm/i915/Kconfig"
177 source "drivers/gpu/drm/exynos/Kconfig"
179 source "drivers/gpu/drm/rockchip/Kconfig"
181 source "drivers/gpu/drm/vmwgfx/Kconfig"
[all …]
/linux-4.1.27/
DMAINTAINERS14 important for device drivers, because often that's the only way
92 F: drivers/net/ all files in and below drivers/net
93 F: drivers/net/* all files in drivers/net, but not below
132 F: drivers/net/ethernet/3com/3c59x.c
138 F: drivers/net/ethernet/3com/typhoon*
145 F: drivers/scsi/3w-*
151 F: drivers/scsi/53c700*
166 F: drivers/net/hamradio/6pack.c
172 F: drivers/net/ethernet/realtek/r8169.c
180 F: drivers/tty/serial/8250*
[all …]
/linux-4.1.27/drivers/staging/unisys/
DKconfig8 Support for the Unisys SPAR drivers
12 source "drivers/staging/unisys/visorutil/Kconfig"
13 source "drivers/staging/unisys/visorchannel/Kconfig"
14 source "drivers/staging/unisys/visorchipset/Kconfig"
15 source "drivers/staging/unisys/uislib/Kconfig"
16 source "drivers/staging/unisys/virtpci/Kconfig"
17 source "drivers/staging/unisys/virthba/Kconfig"
DMAINTAINERS1 Unisys s-Par drivers
6 F: drivers/staging/unisys/
DTODO5 -add other drivers needed for full functionality:
15 -move individual drivers into proper driver subsystems
/linux-4.1.27/drivers/usb/
DKconfig28 You will also need drivers from the following menu to make use of it.
69 After choosing your HCD, then select drivers for the USB peripherals
79 source "drivers/usb/core/Kconfig"
81 source "drivers/usb/mon/Kconfig"
83 source "drivers/usb/wusbcore/Kconfig"
85 source "drivers/usb/host/Kconfig"
87 source "drivers/usb/renesas_usbhs/Kconfig"
89 source "drivers/usb/class/Kconfig"
91 source "drivers/usb/storage/Kconfig"
93 source "drivers/usb/image/Kconfig"
[all …]
DREADME29 host/ - This is for USB host controller drivers. This
33 gadget/ - This is for USB peripheral controller drivers and
34 the various gadget drivers which talk to them.
40 image/ - This is for still image drivers, like scanners or
44 ../media/ - This is for multimedia drivers, like video cameras,
45 radios, and any other drivers that talk to the v4l
47 ../net/ - This is for network drivers.
48 serial/ - This is for USB to serial drivers.
49 storage/ - This is for USB mass-storage drivers.
50 class/ - This is for all USB device drivers that do not fit
[all …]
/linux-4.1.27/Documentation/scsi/
Dscsi-parameters.txt16 See header of drivers/scsi/advansys.c.
33 See drivers/scsi/BusLogic.c, comment before function
41 See header of drivers/scsi/fdomain.c.
44 See header of drivers/scsi/gdth.c.
49 See header of drivers/scsi/in2000.c.
52 See header of drivers/scsi/ips.c.
65 See header of drivers/scsi/NCR_D700.c.
84 See header of drivers/scsi/pas16.c.
87 See drivers/scsi/scsi_debug.c.
98 See drivers/scsi/scsi_logging.h for bits. Also
[all …]
Dmegaraid.txt11 interfaces with the applications on one side and all the low level drivers
16 i. Avoid duplicate code from the low level drivers.
17 ii. Unburden the low level drivers from having to export the
21 multiple low level drivers.
53 module acts as a registry for low level hba drivers. The low level drivers
59 The lower level drivers now understand only a new improved ioctl packet called
Dscsi.txt17 support. Without it you can do nothing with any of the other scsi drivers.
25 The individual upper and lower level drivers can be loaded in any order
29 level drivers to support the various assorted devices which can be
34 The lower level drivers are the ones that support the individual cards that
38 Adaptec. Almost all lower level drivers can be built either as modules or
Dbfa.txt36 http://www.brocade.com/services-support/drivers-downloads/adapters/Linux.page
51 http://www.brocade.com/services-support/drivers-downloads/adapters/Linux.page
67 http://www.brocade.com/services-support/drivers-downloads/adapters/Linux.page
/linux-4.1.27/drivers/media/
DKconfig85 # Selectable only for webcam/grabbers, as other drivers don't use it
126 source "drivers/media/v4l2-core/Kconfig"
153 # This Kconfig option is used by both PCI and USB drivers
159 source "drivers/media/dvb-core/Kconfig"
161 comment "Media drivers"
162 source "drivers/media/rc/Kconfig"
165 # V4L platform/mem2mem drivers
168 source "drivers/media/usb/Kconfig"
169 source "drivers/media/pci/Kconfig"
170 source "drivers/media/platform/Kconfig"
[all …]
/linux-4.1.27/Documentation/PCI/
DPCIEBUS-HOWTO.txt8 and provides information on how to enable the service drivers to
31 and handled by corresponding service drivers.
40 service drivers will compete for a single PCI-PCI Bridge device.
43 kernel therefore does not load other service drivers for that Root
45 drivers load and run on a PCI-PCI Bridge device simultaneously
48 To enable multiple service drivers running simultaneously requires
51 to the corresponding service drivers as required. Some key
54 - Allow multiple service drivers to run simultaneously on
57 - Allow service drivers implemented in an independent
64 device to requested service drivers.
[all …]
Dpci-error-recovery.txt23 between the affected device drivers and the PCI controller chip.
24 This document describes a generic API for notifying device drivers
30 is reported as soon as possible to all affected device drivers,
32 cards. This allows device drivers to avoid deadlocking in spinloops,
34 It also gives the drivers a chance to defer incoming I/O as
39 devices that have multiple device drivers associated with them.
46 After a reset and/or a re-enabling of I/O, all drivers are
60 device drivers already handle very similar recovery procedures;
137 All drivers participating in this system must implement this call.
151 drivers.
[all …]
Dpci.txt13 PCI device drivers.
29 0. Structure of PCI drivers
31 PCI drivers "discover" PCI devices in a system via pci_register_driver().
70 lots of ifdefs in the drivers.
77 PCI device drivers call pci_register_driver() during their
84 interested in. Most drivers should export this
91 "owned" by the other drivers yet. This function gets
120 e.g. drivers/net/e100.c.
139 Most drivers do not need to specify class/class_mask
143 See drivers/scsi/sym53c8xx_2/ for example of usage.
[all …]
/linux-4.1.27/Documentation/target/
Dtcm_mod_builder.txt13 This script will create a new drivers/target/$TCM_NEW_MOD/, and will do the following
15 *) Generate new API callers for drivers/target/target_core_fabric_configs.c logic
23 using drivers/target/target_core_fabric_lib.c logic.
34 /mnt/sdb/lio-core-2.6.git/Documentation/target/../../drivers/target/tcm_nab5000
37 /mnt/sdb/lio-core-2.6.git/Documentation/target/../../drivers/target/tcm_nab5000
39 /mnt/sdb/lio-core-2.6.git/Documentation/target/../../drivers/target/tcm_nab5000/tcm_nab5000_base.h
43 /mnt/sdb/lio-core-2.6.git/Documentation/target/../../drivers/target/tcm_nab5000/tcm_nab5000_fabric.c
45 /mnt/sdb/lio-core-2.6.git/Documentation/target/../../drivers/target/tcm_nab5000/tcm_nab5000_fabric.h
47 /mnt/sdb/lio-core-2.6.git/Documentation/target/../../drivers/target/tcm_nab5000/tcm_nab5000_configf…
49 /mnt/sdb/lio-core-2.6.git/Documentation/target/../../drivers/target/tcm_nab5000/Kbuild
[all …]
/linux-4.1.27/drivers/isdn/hardware/
DKconfig2 # ISDN hardware drivers
4 comment "CAPI hardware drivers"
6 source "drivers/isdn/hardware/avm/Kconfig"
8 source "drivers/isdn/hardware/eicon/Kconfig"
/linux-4.1.27/drivers/media/pci/saa7134/
DMakefile14 ccflags-y += -I$(srctree)/drivers/media/i2c
15 ccflags-y += -I$(srctree)/drivers/media/tuners
16 ccflags-y += -I$(srctree)/drivers/media/dvb-core
17 ccflags-y += -I$(srctree)/drivers/media/dvb-frontends
18 ccflags-y += -I$(srctree)/drivers/media/usb/go7007
/linux-4.1.27/Documentation/ioctl/
Dioctl-number.txt21 or number from the table below. Because of the large number of drivers,
22 many drivers share a partial letter with other drivers.
60 most drivers up to 2.6.31, but I know I am missing some. There has been
61 no attempt to list non-X86 architectures or ioctls from drivers/staging/.
74 0x10 00-0F drivers/char/s390/vmcp.h
80 0x20 all drivers/cdrom/cm206.h
84 '&' 00-07 drivers/firewire/nosy-user.h
88 '3' 00-0F drivers/s390/char/raw3270.h conflict!
95 '@' 00-0F drivers/video/aty/aty128fb.c conflict!
98 and drivers/char/agp/compat_ioctl.h
[all …]
/linux-4.1.27/drivers/soc/
DKconfig3 source "drivers/soc/mediatek/Kconfig"
4 source "drivers/soc/qcom/Kconfig"
5 source "drivers/soc/ti/Kconfig"
6 source "drivers/soc/versatile/Kconfig"
/linux-4.1.27/Documentation/video4linux/
DREADME.davinci-vpbe8 drivers/media/platform/davinci/vpbe_display.c
9 drivers/media/platform/davinci/vpbe_display.h
12 drivers/media/platform/davinci/vpbe.c
13 drivers/media/platform/davinci/vpbe.h
16 drivers/media/platform/davinci/vpbe_venc.c
17 drivers/media/platform/davinci/vpbe_venc.h
18 drivers/media/platform/davinci/vpbe_venc_regs.h
21 drivers/media/platform/davinci/vpbe_osd.c
22 drivers/media/platform/davinci/vpbe_osd.h
23 drivers/media/platform/davinci/vpbe_osd_regs.h
[all …]
Dsoc-camera.txt22 drivers and camera sensor drivers. Later the soc-camera sensor API has been
28 method is supported by host drivers. However, the soc-camera core also provides
35 Existing drivers
38 As of 3.7 there are seven host drivers in the mainline: atmel-isi.c,
41 drivers under drivers/media/i2c/soc_camera/.
88 Sensor drivers can use struct soc_camera_link, typically provided by the
96 using the V4L2 subdev API. Additionally soc-camera camera drivers can use
128 Camera drivers are interfaced to the soc-camera core and to host drivers over
130 Therefore all camera drivers shall reply to .g_fmt() requests with their current
133 factors have to be maintained by camera drivers internally. According to the
[all …]
Dvideobuf44 shows up occasionally in system-on-chip drivers where the performance
113 /* Scatter/gather drivers */
118 /* vmalloc drivers */
121 /* Contiguous drivers */
178 V4L2 capture drivers can be written to support either of two APIs: the
213 V4L2 drivers, the often-complex mmap() implementation simplifies to a
255 boilerplate in a lot of V4L2 drivers.
289 same is normally true of contiguous-DMA drivers as well; videobuf will
291 means that these drivers may be trying to do high-order allocations at any
292 time, an operation which is not always guaranteed to work. Some drivers
[all …]
Dfimc.txt13 drivers/media/platform/exynos4-is directory.
39 drivers/media/platform/exynos4-is/media-dev.[ch]
42 drivers/media/platform/exynos4-is/fimc-capture.c
45 drivers/media/platform/exynos4-is/mipi-csis.[ch]
48 drivers/media/platform/exynos4-is/fimc-core.c
51 drivers/media/platform/exynos4-is/fimc-core.h
52 drivers/media/platform/exynos4-is/fimc-reg.h
53 drivers/media/platform/exynos4-is/regs-fimc.h
/linux-4.1.27/drivers/platform/
DKconfig2 source "drivers/platform/x86/Kconfig"
5 source "drivers/platform/mips/Kconfig"
8 source "drivers/platform/goldfish/Kconfig"
11 source "drivers/platform/chrome/Kconfig"
/linux-4.1.27/Documentation/isdn/
DHiSax.cert35 Please send any questions regarding this drivers or approval abouts to
54 "drivers/isdn/hisax/md5sums.asc" match, is the certification valid; a
59 drivers/isdn/hisax/isac.c
60 drivers/isdn/hisax/isdnl1.c
61 drivers/isdn/hisax/isdnl2.c
62 drivers/isdn/hisax/isdnl3.c
63 drivers/isdn/hisax/tei.c
64 drivers/isdn/hisax/callc.c
65 drivers/isdn/hisax/l3dss1.c
66 drivers/isdn/hisax/l3_1tr6.c
[all …]
/linux-4.1.27/drivers/net/wireless/ti/
DKconfig4 This section contains support for all the wireless drivers
9 source "drivers/net/wireless/ti/wl1251/Kconfig"
10 source "drivers/net/wireless/ti/wl12xx/Kconfig"
11 source "drivers/net/wireless/ti/wl18xx/Kconfig"
14 source "drivers/net/wireless/ti/wlcore/Kconfig"
/linux-4.1.27/Documentation/hid/
Dhid-transport.txt6 provided new transport drivers. The kernel includes at least support for USB,
7 Bluetooth, I2C and user-space I/O drivers.
14 drivers on top of it. The transport drivers are responsible of raw data
49 interest to HID device drivers. Transport drivers do not need to know the
55 I/O drivers normally provide hotplug detection or device enumeration APIs to the
56 transport drivers. Transport drivers use this to find any suitable HID device.
58 drivers are not required to register themselves with HID core. HID core is never
59 aware of which transport drivers are available and is not interested in it. It
62 Transport drivers attach a constant "struct hid_ll_driver" object with each
66 Transport drivers are responsible of detecting device failures and unplugging.
[all …]
/linux-4.1.27/drivers/pinctrl/
DKconfig2 # PINCTRL infrastructure and drivers
213 source "drivers/pinctrl/bcm/Kconfig"
214 source "drivers/pinctrl/berlin/Kconfig"
215 source "drivers/pinctrl/freescale/Kconfig"
216 source "drivers/pinctrl/intel/Kconfig"
217 source "drivers/pinctrl/mvebu/Kconfig"
218 source "drivers/pinctrl/nomadik/Kconfig"
219 source "drivers/pinctrl/qcom/Kconfig"
220 source "drivers/pinctrl/samsung/Kconfig"
221 source "drivers/pinctrl/sh-pfc/Kconfig"
[all …]
/linux-4.1.27/drivers/media/common/
DKconfig1 # Used by common drivers, when they need to ask questions
19 source "drivers/media/common/b2c2/Kconfig"
20 source "drivers/media/common/saa7146/Kconfig"
21 source "drivers/media/common/siano/Kconfig"
/linux-4.1.27/drivers/media/v4l2-core/
DKconfig12 bool "Enable advanced debug functionality on V4L2 drivers"
20 bool "Enable old-style fixed minor ranges on drivers/video devices"
35 when developing new drivers.
37 # Used by drivers that need tuner.ko
42 # Used by drivers that need v4l2-mem2mem.ko
47 # Used by drivers that need Videobuf modules
69 # Used by drivers that need Videobuf2 modules
DMakefile38 ccflags-y += -I$(srctree)/drivers/media/dvb-core
39 ccflags-y += -I$(srctree)/drivers/media/dvb-frontends
40 ccflags-y += -I$(srctree)/drivers/media/tuners
/linux-4.1.27/drivers/net/wireless/
DKconfig13 device drivers. For a complete list of drivers and documentation
217 source "drivers/net/wireless/rtl818x/Kconfig"
268 source "drivers/net/wireless/ath/Kconfig"
269 source "drivers/net/wireless/b43/Kconfig"
270 source "drivers/net/wireless/b43legacy/Kconfig"
271 source "drivers/net/wireless/brcm80211/Kconfig"
272 source "drivers/net/wireless/hostap/Kconfig"
273 source "drivers/net/wireless/ipw2x00/Kconfig"
274 source "drivers/net/wireless/iwlwifi/Kconfig"
275 source "drivers/net/wireless/iwlegacy/Kconfig"
[all …]
/linux-4.1.27/drivers/media/pci/saa7164/
DMakefile7 ccflags-y += -I$(srctree)/drivers/media/i2c
8 ccflags-y += -I$(srctree)/drivers/media/tuners
9 ccflags-y += -I$(srctree)/drivers/media/dvb-core
10 ccflags-y += -I$(srctree)/drivers/media/dvb-frontends
/linux-4.1.27/Documentation/sound/alsa/soc/
Doverview.txt10 * Codec drivers were often tightly coupled to the underlying SoC
12 Linux had different wm8731 drivers for 4 different SoC platforms.
32 * Codec independence. Allows reuse of codec drivers on other platforms
53 multiple re-usable component drivers :-
55 * Codec class drivers: The codec class driver is platform independent and
58 ICs if required. Codec class drivers should be generic code that can run
61 * Platform class drivers: The platform class driver includes the audio DMA
62 engine driver, digital audio interface (DAI) drivers (e.g. I2S, AC97, PCM)
63 and any audio DSP drivers for that platform.
66 decribes and binds the other component drivers together to form an ALSA
[all …]
Dplatform.txt4 An ASoC platform driver class can be divided into audio DMA drivers, SoC DAI
5 drivers and DSP drivers. The platform drivers only target the SoC CPU and must
/linux-4.1.27/drivers/media/platform/
DKconfig2 # Platform drivers
3 # All drivers here are currently for webcam support
10 Say Y here to enable support for platform-specific V4L drivers.
14 source "drivers/media/platform/marvell-ccic/Kconfig"
30 source "drivers/media/platform/davinci/Kconfig"
32 source "drivers/media/platform/omap/Kconfig"
34 source "drivers/media/platform/blackfin/Kconfig"
117 source "drivers/media/platform/soc_camera/Kconfig"
118 source "drivers/media/platform/exynos4-is/Kconfig"
119 source "drivers/media/platform/s5p-tv/Kconfig"
[all …]
/linux-4.1.27/Documentation/sound/alsa/
DJoystick.txt13 The joystick support of ALSA drivers is different between ISA and PCI
15 independent module (ns558). Meanwhile, the ALSA PCI drivers have the
29 option is specified. Some drivers don't need options, and the
35 The following PCI drivers support the joystick natively.
62 The following drivers don't support gameport natively, but there are
72 Note: the "pcigame" and "cs461x" modules are for the OSS drivers only.
73 These ALSA drivers (cs46xx, trident and au88x0) have the
76 As mentioned above, ALSA PCI drivers have the built-in gameport
84 ALSA ISA drivers don't have the built-in gameport support.
/linux-4.1.27/Documentation/driver-model/
Dclass.txt14 that devices of that class adhere to. Device drivers are the
41 can be used by drivers, extensions and interfaces.
51 As devices are bound to drivers, they are added to the device class
68 drivers of that particular class. To access all of the devices in the
74 Device drivers are added to device classes when they are registered
89 `-- drivers
92 Drivers registered with the class get a symlink in the drivers/ directory
98 `-- drivers
99 `-- usb:usb_mouse -> ../../../bus/drivers/usb_mouse/
109 `-- drivers
[all …]
Dplatform.txt33 Platform drivers
35 Platform drivers follow the standard driver model convention, where
36 discovery/enumeration is handled outside the drivers, and drivers
55 Platform drivers register themselves the normal way:
101 Some drivers are not fully converted to the driver model, because they take
103 leaving that for system infrastructure. Such drivers can't be hotplugged
117 outside the driver. This will usually be cleanup, since such drivers
121 None the less, there are some APIs to support such legacy drivers. Avoid
122 using these calls except with such hotplug-deficient drivers.
159 - Whenever a device is registered, the drivers for that bus are
[all …]
Dbus.txt23 The structure should be exported to drivers in a header file:
63 The lists of devices and drivers are intended to replace the local
65 struct device_drivers, respectively. Bus drivers are free to use the
94 `-- drivers
96 Drivers registered with the bus get a directory in the bus's drivers
101 `-- drivers
116 `-- drivers
127 Bus drivers can export attributes using the BUS_ATTR macro that works
Dporting.txt14 Most of the work of porting devices drivers to the new model happens
16 negative effect on kernel drivers, and to allow a gradual transition
17 of bus drivers.
80 subdirectories: 'devices' and 'drivers'.
85 `-- drivers
271 /sys/bus/pci/drivers/
283 operations the bus already defines for drivers, but taking different
287 simultaneously convert their drivers to generic format. Instead, the
289 forward call to the bus-specific drivers. For instance:
322 already set. This allows the drivers to implement their own generic
[all …]
Ddriver.txt10 Device drivers are statically allocated structures. Though there may
41 Most drivers will not be able to be converted completely to the new
51 Bus-specific drivers should include a generic struct device_driver in
82 The driver registers the structure on startup. For drivers that have
87 Most drivers, however, will have a bus-specific structure and will
90 It is important that drivers register their driver structure as early as
104 callbacks of the drivers.
107 information in the driver, the drivers must be modified anyway. Since
108 converting drivers to the new model should reduce some infrastructural
198 Device drivers can export attributes via their sysfs directories.
Dbinding.txt5 driver that can control it. Bus drivers have typically handled this
7 devices and the drivers. With generic device and device driver
17 list of all drivers of that bus type. When driver_register is called
25 When a new device is added, the bus's list of drivers is iterated over
45 the class to which it belongs. Device drivers belong to one and only one
/linux-4.1.27/Documentation/ABI/stable/
Dsysfs-driver-usb-usbtmc1 What: /sys/bus/usb/drivers/usbtmc/*/interface_capabilities
2 What: /sys/bus/usb/drivers/usbtmc/*/device_capabilities
15 What: /sys/bus/usb/drivers/usbtmc/*/usb488_interface_capabilities
16 What: /sys/bus/usb/drivers/usbtmc/*/usb488_device_capabilities
30 What: /sys/bus/usb/drivers/usbtmc/*/TermChar
43 What: /sys/bus/usb/drivers/usbtmc/*/TermCharEnabled
54 What: /sys/bus/usb/drivers/usbtmc/*/auto_abort
/linux-4.1.27/drivers/iio/common/
DKconfig5 source "drivers/iio/common/hid-sensors/Kconfig"
6 source "drivers/iio/common/ssp_sensors/Kconfig"
7 source "drivers/iio/common/st_sensors/Kconfig"
/linux-4.1.27/drivers/media/pci/ivtv/
DMakefile12 ccflags-y += -I$(srctree)/drivers/media/i2c
13 ccflags-y += -I$(srctree)/drivers/media/tuners
14 ccflags-y += -I$(srctree)/drivers/media/dvb-core
15 ccflags-y += -I$(srctree)/drivers/media/dvb-frontends
/linux-4.1.27/drivers/video/fbdev/omap2/
DKconfig6 source "drivers/video/fbdev/omap2/dss/Kconfig"
7 source "drivers/video/fbdev/omap2/omapfb/Kconfig"
8 source "drivers/video/fbdev/omap2/displays-new/Kconfig"
/linux-4.1.27/drivers/input/
DKconfig46 option is only useful for out-of-tree drivers since
47 in-tree drivers select it automatically.
59 useful for out-of-tree drivers since in-tree drivers
72 useful for out-of-tree drivers since in-tree drivers
179 source "drivers/input/keyboard/Kconfig"
181 source "drivers/input/mouse/Kconfig"
183 source "drivers/input/joystick/Kconfig"
185 source "drivers/input/tablet/Kconfig"
187 source "drivers/input/touchscreen/Kconfig"
189 source "drivers/input/misc/Kconfig"
[all …]
/linux-4.1.27/Documentation/power/
Dnotifiers.txt4 There are some operations that subsystems or drivers may want to carry out
6 to be fully functional, so the drivers' and subsystems' .suspend() and .resume()
8 For example, device drivers may want to upload firmware to their devices after
15 The subsystems or drivers having such needs can register suspend notifiers that
21 and drivers freezing.
25 hibernation. Device drivers' restore callbacks have
33 Device drivers' restore callbacks have been executed
39 suspend. Device drivers' resume callbacks have been
D00-INDEX10 - How drivers interact with system-wide power management
11 drivers-testing.txt
12 - Testing suspend and resume support in device drivers
18 - Registering suspend notifiers in device drivers
/linux-4.1.27/drivers/net/can/
DKconfig33 tristate "Platform CAN drivers with Netlink support"
36 Enables the common framework for platform CAN drivers with Netlink
37 support. This is the standard library for CAN drivers.
56 bool "Enable LED triggers for Netlink based drivers"
140 source "drivers/net/can/mscan/Kconfig"
142 source "drivers/net/can/sja1000/Kconfig"
144 source "drivers/net/can/c_can/Kconfig"
146 source "drivers/net/can/m_can/Kconfig"
148 source "drivers/net/can/cc770/Kconfig"
150 source "drivers/net/can/spi/Kconfig"
[all …]
/linux-4.1.27/drivers/net/wimax/
DKconfig2 # WiMAX LAN device drivers configuration
6 comment "Enable WiMAX (Networking options) to see the WiMAX drivers"
13 source "drivers/net/wimax/i2400m/Kconfig"
/linux-4.1.27/drivers/virt/
DKconfig2 # Virtualization support drivers
6 bool "Virtualization drivers"
8 Say Y here to get to see options for device drivers that support
21 to drivers and applications related to the Freescale hypervisor:
/linux-4.1.27/drivers/video/fbdev/mmp/
DKconfig8 source "drivers/video/fbdev/mmp/hw/Kconfig"
9 source "drivers/video/fbdev/mmp/panel/Kconfig"
10 source "drivers/video/fbdev/mmp/fb/Kconfig"
/linux-4.1.27/drivers/vme/
DKconfig13 source "drivers/vme/bridges/Kconfig"
15 source "drivers/vme/boards/Kconfig"
17 source "drivers/staging/vme/devices/Kconfig"
/linux-4.1.27/Documentation/fmc/
D00-INDEX29 - about drivers/fmc/fmc-fakedev.ko
32 - about drivers/fmc/fmc-trivial.ko
35 - about drivers/fmc/fmc-write-eeprom.ko
38 - about drivers/fmc/fmc-chardev.ko
/linux-4.1.27/drivers/dma/
DTODO3 1. Move remaining drivers to use new slave interface
5 3. Make issue_pending to start the transaction in below drivers
11 4. Check other subsystems for dma drivers and merge/move to dmaengine
/linux-4.1.27/arch/ia64/
DMakefile57 drivers-$(CONFIG_PCI) += arch/ia64/pci/
58 drivers-$(CONFIG_IA64_HP_SIM) += arch/ia64/hp/sim/
59 drivers-$(CONFIG_IA64_HP_ZX1) += arch/ia64/hp/common/ arch/ia64/hp/zx1/
60 drivers-$(CONFIG_IA64_HP_ZX1_SWIOTLB) += arch/ia64/hp/common/ arch/ia64/hp/zx1/
61 drivers-$(CONFIG_IA64_GENERIC) += arch/ia64/hp/common/ arch/ia64/hp/zx1/ arch/ia64/hp/sim/ arch/ia6…
62 drivers-$(CONFIG_OPROFILE) += arch/ia64/oprofile/
/linux-4.1.27/Documentation/ABI/testing/
Dsysfs-wusb_cbaf1 What: /sys/bus/usb/drivers/wusb_cbaf/.../wusb_*
52 What: /sys/bus/usb/drivers/wusb_cbaf/.../wusb_chid
63 What: /sys/bus/usb/drivers/wusb_cbaf/.../wusb_host_name
70 What: /sys/bus/usb/drivers/wusb_cbaf/.../wusb_host_band_groups
78 What: /sys/bus/usb/drivers/wusb_cbaf/.../wusb_device_band_groups
86 What: /sys/bus/usb/drivers/wusb_cbaf/.../wusb_cdid
94 What: /sys/bus/usb/drivers/wusb_cbaf/.../wusb_ck
Dsysfs-driver-hid-wiimote1 What: /sys/bus/hid/drivers/wiimote/<dev>/led1
2 What: /sys/bus/hid/drivers/wiimote/<dev>/led2
3 What: /sys/bus/hid/drivers/wiimote/<dev>/led3
4 What: /sys/bus/hid/drivers/wiimote/<dev>/led4
12 What: /sys/bus/hid/drivers/wiimote/<dev>/extension
28 What: /sys/bus/hid/drivers/wiimote/<dev>/devtype
46 What: /sys/bus/hid/drivers/wiimote/<dev>/bboard_calib
61 What: /sys/bus/hid/drivers/wiimote/<dev>/pro_calib
Dsysfs-driver-hid-prodikeys1 What: /sys/bus/hid/drivers/prodikeys/.../channel
10 What: /sys/bus/hid/drivers/prodikeys/.../sustain
20 What: /sys/bus/hid/drivers/prodikeys/.../octave
Dsysfs-bus-usb7 drivers, non-authorized one are not. By default, wired
44 What: /sys/bus/usb/drivers/.../new_id
60 # echo "8086 10f5" > /sys/bus/usb/drivers/foo/new_id
64 # echo "0458 7045 0 0458 704c" > /sys/bus/usb/drivers/foo/new_id
69 # cat /sys/bus/usb/drivers/foo/new_id
77 What: /sys/bus/usb-serial/drivers/.../new_id
81 For serial USB drivers, this attribute appears under the
84 "/sys/bus/usb/drivers/.../new_id" apply.
86 What: /sys/bus/usb/drivers/.../remove_id
97 # echo "046d c315" > /sys/bus/usb/drivers/foo/remove_id
[all …]
Dsysfs-class-backlight-driver-adp88709 Contact: device-drivers-devel@blackfin.uclinux.org
23 Contact: device-drivers-devel@blackfin.uclinux.org
34 Contact: device-drivers-devel@blackfin.uclinux.org
44 Contact: device-drivers-devel@blackfin.uclinux.org
Dsysfs-class-iommu6 IOMMU drivers are able to link devices managed by a
15 IOMMU drivers are able to link the IOMMU for a
Dsysfs-module1 What: /sys/module/pch_phub/drivers/.../pch_mac
7 What: /sys/module/pch_phub/drivers/.../pch_firmware
14 What: /sys/module/ehci_hcd/drivers/.../uframe_periodic_max
Dsysfs-driver-pciback1 What: /sys/bus/pci/drivers/pciback/quirks
11 #echo 00:19.0-E0:2:FF > /sys/bus/pci/drivers/pciback/quirks
Dsysfs-driver-hid-logitech-lg4ff1 What: /sys/module/hid_logitech/drivers/hid:logitech/<dev>/range.
9 What: /sys/bus/hid/drivers/logitech/<dev>/alternate_modes
45 What: /sys/bus/hid/drivers/logitech/<dev>/real_id
/linux-4.1.27/Documentation/pti/
Dpti_intel_mid.txt7 ./drivers/.../n_tracesink.h
8 ./drivers/.../n_tracerouter.c
9 ./drivers/.../n_tracesink.c
10 ./drivers/.../pti.c
33 *Use mipi_* Kernel Driver API in other device drivers for
40 privileges to successfully manipulate the ldisc drivers
43 and n_tracesink line discpline drivers but is a generic
58 // these two vars used to grab LDISC values from loaded ldisc drivers
/linux-4.1.27/Documentation/usb/
Dgadget_multi.txt20 * Host drivers
26 ** Linux host drivers
29 to Linux host it does not need any additional drivers on Linux host
30 side. All the functions are handled by respective drivers developed
37 ** Windows host drivers
46 tries to much drivers for each individual interface (sort of, don't
56 *** Installing drivers for each function
58 The other, trickier thing is making Windows install drivers for each
68 To make Windows select RNDIS drivers for the first function in the
97 some drivers information (changing USB port may sometimes help plus
[all …]
Dhotplug.txt8 loading a kernel module; newer drivers can use module-init-tools
29 Because some of those actions rely on information about drivers (metadata)
30 that is currently available only when the drivers are dynamically linked,
77 Currently available policy agent implementations can load drivers for
79 leverage USB module-init-tools support. Later agents might unload drivers.
90 at existing drivers. Each table entry describes one or more criteria to
116 Most USB device drivers should pass these tables to the USB subsystem as
140 choosing drivers to probe(). The thread doing new device processing checks
141 drivers' device ID entries from the MODULE_DEVICE_TABLE against interface and
Ddma.txt1 In Linux 2.5 kernels (and later), USB device drivers have additional control
8 The big picture is that USB drivers can continue to ignore most DMA issues,
15 - New calls enable DMA-aware drivers, letting them allocate dma buffers and
20 drivers must not use it.)
27 drivers. Never use dma_set_mask() on any USB interface or device; that
52 Most drivers should *NOT* be using these primitives; they don't need
109 - Some drivers may prefer to work with the model that they're mapping large
/linux-4.1.27/Documentation/console/
Dconsole.txt4 The linux kernel has 2 general types of console drivers. The first type is
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
20 Modular drivers, from the programmer's point of view, has to call:
80 console drivers
110 console drivers must follow these guidelines:
112 1. All drivers, except system drivers, must call either do_register_con_driver()
136 with the framebuffer console that suddenly lost all of its drivers.
138 The current crop of console drivers should still work correctly, but binding
[all …]
/linux-4.1.27/Documentation/power/regulator/
Dconsumer.txt4 This text describes the regulator interface for consumer device drivers.
8 1. Consumer Regulator Access (static & dynamic drivers)
31 usually be called in your device drivers probe() and remove() respectively.
34 2. Regulator Output Enable & Disable (static & dynamic drivers)
67 3. Regulator Voltage Control & Status (dynamic drivers)
70 Some consumer drivers need to be able to dynamically change their supply
71 voltage to match system operating points. e.g. CPUfreq drivers can scale
72 voltage along with frequency to save power, SD drivers may need to select the
97 4. Regulator Current Limit Control & Status (dynamic drivers)
100 Some consumer drivers need to be able to dynamically change their supply
[all …]
Dregulator.txt5 regulator drivers to register their services with the core framework.
27 consumer drivers by calling :-
/linux-4.1.27/drivers/nfc/
DKconfig71 source "drivers/nfc/pn544/Kconfig"
72 source "drivers/nfc/microread/Kconfig"
73 source "drivers/nfc/nfcmrvl/Kconfig"
74 source "drivers/nfc/st21nfca/Kconfig"
75 source "drivers/nfc/st21nfcb/Kconfig"
76 source "drivers/nfc/nxp-nci/Kconfig"
/linux-4.1.27/drivers/usb/host/
Dfsl-mph-dr-of.c23 char *drivers[3]; /* drivers to instantiate for this mode */ member
30 .drivers = { "fsl-ehci", NULL, NULL, },
35 .drivers = { "fsl-usb2-otg", "fsl-ehci", "fsl-usb2-udc", },
40 .drivers = { "fsl-usb2-udc", NULL, NULL, },
216 for (i = 0; i < ARRAY_SIZE(dev_data->drivers); i++) { in fsl_usb2_mph_dr_of_probe()
217 if (!dev_data->drivers[i]) in fsl_usb2_mph_dr_of_probe()
220 dev_data->drivers[i], idx); in fsl_usb2_mph_dr_of_probe()
/linux-4.1.27/drivers/misc/ti-st/
DKconfig3 # drivers (BT, FM and GPS)
12 BT / FM and GPS combo chips. This enables protocol drivers
14 are returned to relevant protocol drivers based on their
/linux-4.1.27/Documentation/dvb/
Dbt8xx.txt12 a.)"Device drivers" => "Multimedia devices" => "Video For Linux" => "Enable Video for Linux API 1 (…
13 b.)"Device drivers" => "Multimedia devices" => "Video For Linux" => "Video Capture Adapters" => "BT…
14 c.)"Device drivers" => "Multimedia devices" => "Digital Video Broadcasting Devices" => "DVB for Lin…
16 Please use the following options with care as deselection of drivers which are in fact necessary
20 First please remove the static dependency of DVB card drivers on all frontend modules for all possi…
21 d.) "Device drivers" => "Multimedia devices" => "Digital Video Broadcasting Devices"
25 e.)"Device drivers" => "Multimedia devices" => "Digital Video Broadcasting Devices"
88 /sys/bus/pci/drivers/bt878/new_id
Dlmedm04.txt7 The Sharp 7395 driver can be found in windows/system32/drivers
47 only found in windows/system32/drivers
58 The Sharp 0194 tuner driver can be found in windows/system32/drivers
71 The m88rs2000 tuner driver can be found in windows/system32/drivers
/linux-4.1.27/drivers/video/fbdev/via/
Dvia_aux.c40 INIT_LIST_HEAD(&bus->drivers); in via_aux_probe()
62 list_for_each_entry_safe(pos, n, &bus->drivers, chain) { in via_aux_free()
82 list_for_each_entry(pos, &bus->drivers, chain) { in via_aux_get_preferred_mode()
Dvia_aux.h35 struct list_head drivers; /* drivers for devices on this bus */ member
66 list_add_tail(&data->chain, &data->bus->drivers); in via_aux_add()
/linux-4.1.27/drivers/staging/media/lirc/
DTODO1 - All drivers should either be ported to ir-core, or dropped entirely
2 (see drivers/media/IR/mceusb.c vs. lirc_mceusb.c in lirc cvs for an
8 coordinated with the other drivers.
DKconfig5 bool "Linux Infrared Remote Control IR receiver/transmitter drivers"
9 RF receiver and transmitter drivers will be displayed. When paired
10 with a remote control and the lirc daemon, the receiver drivers
/linux-4.1.27/drivers/isdn/
DKconfig42 source "drivers/isdn/i4l/Kconfig"
61 source "drivers/isdn/capi/Kconfig"
63 source "drivers/isdn/hardware/Kconfig"
67 source "drivers/isdn/gigaset/Kconfig"
69 source "drivers/isdn/hysdn/Kconfig"
71 source "drivers/isdn/mISDN/Kconfig"
/linux-4.1.27/drivers/vfio/
DKconfig29 VFIO provides a framework for secure userspace device drivers.
34 source "drivers/vfio/pci/Kconfig"
35 source "drivers/vfio/platform/Kconfig"
/linux-4.1.27/drivers/mmc/
DKconfig24 source "drivers/mmc/core/Kconfig"
26 source "drivers/mmc/card/Kconfig"
28 source "drivers/mmc/host/Kconfig"
/linux-4.1.27/Documentation/blockdev/
Dparide.txt56 high-level drivers for each of the different types of supported devices:
66 The high-level drivers function according to the relevant standards.
67 The third component of PARIDE is a set of low-level protocol drivers
91 the PARIDE drivers into your kernel, or to build them as modules.
94 as well as at least one of the high-level drivers and at least one
106 and high-level drivers that you would use:
123 2.1 Configuring built-in drivers
125 We recommend that you get to know how the drivers work and how to
127 kernel with the drivers built-in.
135 The high-level drivers accept a number of command line parameters, all
[all …]
/linux-4.1.27/drivers/media/usb/dvb-usb-v2/
DMakefile43 ccflags-y += -I$(srctree)/drivers/media/dvb-core
44 ccflags-y += -I$(srctree)/drivers/media/dvb-frontends
45 ccflags-y += -I$(srctree)/drivers/media/tuners
46 ccflags-y += -I$(srctree)/drivers/media/common
/linux-4.1.27/drivers/target/
DKconfig42 source "drivers/target/loopback/Kconfig"
43 source "drivers/target/tcm_fc/Kconfig"
44 source "drivers/target/iscsi/Kconfig"
45 source "drivers/target/sbp/Kconfig"
/linux-4.1.27/Documentation/pcmcia/
Ddriver-changes.txt21 Instead of win_req_t, drivers are now requested to fill out
28 Instead of io_req_t, drivers are now requested to fill out
36 in PCMCIA device drivers. Also, do not include pcmcia/cs_types.h, as
43 Instead of the old pcmcia_request_irq() interface, drivers may now
49 - drivers still not capable of IRQF_SHARED (or not telling us so) may
96 PCMCIA devices and their correct drivers can now be matched in
105 ioaddr_t should be replaced by unsigned int in PCMCIA card drivers.
109 PCMCIA card drivers. Instead, it is the job of the PCMCIA core to
118 PCMCIA card drivers
122 because they are unused by all in-kernel drivers, and no external
[all …]
Ddriver.txt13 /sys/bus/pcmcia/drivers/{driver}/new_id
28 /sys/bus/pcmcia/drivers/{driver}/new_id
/linux-4.1.27/Documentation/networking/
Dbaycom.txt5 !!NEW!! (04/98) The drivers for the baycom modems have been split into
6 separate drivers as they did not share any code, and the driver
12 The following drivers are available:
78 The Interface of the drivers
80 Unlike previous drivers, these drivers are no longer character devices,
142 The serial driver and the baycom serial drivers compete
145 startup time. Therefore the baycom drivers subsequently won't be able to
148 # is the number of the interface. The baycom drivers do not reserve any
150 method to solve the problem is to compile all drivers as modules and
153 The parallel port drivers (baycom_par, baycom_epp) now use the parport subsystem
[all …]
Dieee802154.txt22 - PHY - represents device drivers
78 We provide an example of simple HardMAC driver at drivers/ieee802154/fakehard.c
85 provides interface for drivers registration and management of slave interfaces.
92 See header include/net/mac802154.h and several drivers in drivers/ieee802154/.
95 Device drivers API
114 Fake drivers
117 In addition there are two drivers available which simulate real devices with
122 See sources in drivers/ieee802154 folder for more details.
Dregulatory.txt70 If drivers determine they need a specific regulatory domain
77 *Most* drivers will rely on the first mechanism of providing a
78 regulatory hint with an alpha2. For these drivers there is an additional
80 regulatory data. This additional check can be used by drivers by
85 internal EEPROM data. Devices drivers wishing to be capable of world
89 Device drivers who provide their own built regulatory domain
94 Example code - drivers hinting an alpha2:
136 Example code - drivers providing a built in regulatory domain:
/linux-4.1.27/drivers/clk/
DKconfig34 source "drivers/clk/versatile/Kconfig"
120 tristate "Clock drivers for Keystone based SOCs"
123 Supports clock drivers for Keystone based SOCs. These SOCs have local
153 source "drivers/clk/qcom/Kconfig"
157 source "drivers/clk/bcm/Kconfig"
158 source "drivers/clk/mvebu/Kconfig"
160 source "drivers/clk/samsung/Kconfig"
/linux-4.1.27/drivers/staging/lustre/
DKconfig1 source "drivers/staging/lustre/lustre/Kconfig"
3 source "drivers/staging/lustre/lnet/Kconfig"
/linux-4.1.27/drivers/s390/
DMakefile7 drivers-y += drivers/s390/built-in.o
/linux-4.1.27/drivers/scsi/cxgbi/
DKconfig1 source "drivers/scsi/cxgbi/cxgb3i/Kconfig"
2 source "drivers/scsi/cxgbi/cxgb4i/Kconfig"
/linux-4.1.27/drivers/iio/common/hid-sensors/
DKconfig7 tristate "Common modules for all HID Sensor IIO drivers"
14 HID sensor drivers, this module contains processing for those
18 tristate "Common module (trigger) for all HID Sensor IIO drivers"
/linux-4.1.27/drivers/net/
DKconfig36 networking core drivers (i.e. VLAN, bridging, bonding, etc.)
119 source "drivers/net/team/Kconfig"
277 source "drivers/net/arcnet/Kconfig"
279 source "drivers/atm/Kconfig"
281 source "drivers/net/caif/Kconfig"
283 source "drivers/net/dsa/Kconfig"
285 source "drivers/net/ethernet/Kconfig"
287 source "drivers/net/fddi/Kconfig"
289 source "drivers/net/hippi/Kconfig"
315 source "drivers/net/phy/Kconfig"
[all …]
/linux-4.1.27/drivers/i2c/
DKconfig71 source drivers/i2c/muxes/Kconfig
77 Some I2C bus drivers require so-called "I2C algorithm" modules
83 modules, for example for use with external I2C bus drivers.
97 source drivers/i2c/algos/Kconfig
98 source drivers/i2c/busses/Kconfig
105 This module may be useful to developers of SMBus client drivers,
133 Say Y here if you want the I2C algorithm drivers to produce a bunch
142 Say Y here if you want the I2C bus drivers to produce a bunch of
/linux-4.1.27/Documentation/input/
Dcs461x.txt5 Vortex/Solo drivers as an example of decoration style, and ALSA
6 0.5.8a kernel drivers as an chipset documentation and samples.
30 The driver works with ALSA drivers simultaneously. For example, the xracer
35 without ALSA drivers. The ALSA drivers are not needed to compile or
/linux-4.1.27/drivers/media/dvb-frontends/drx39xyj/
DMakefile5 ccflags-y += -I$(srctree)/drivers/media/dvb-core/
6 ccflags-y += -I$(srctree)/drivers/media/tuners/
/linux-4.1.27/Documentation/fb/
Dfbcon.txt26 required, so choose from any of the numerous drivers available. For x86
83 Note, not all drivers can handle font with widths not divisible by 8,
108 the number of loaded fb drivers. For example, if only one driver is
167 because fbcon is an intermediate layer between the console and the drivers:
169 console ---> fbcon ---> fbdev drivers ---> hardware
171 The fbdev drivers cannot be unloaded if it's bound to fbcon, and fbcon cannot
174 So to unload the fbdev drivers, one must first unbind fbcon from the console,
175 then unbind the fbdev drivers from fbcon. Fortunately, unbinding fbcon from
176 the console layer will automatically unbind framebuffer drivers from
177 fbcon. Thus, there is no need to explicitly unbind the fbdev drivers from
[all …]
/linux-4.1.27/drivers/cpuidle/
DKconfig33 source "drivers/cpuidle/Kconfig.arm"
38 source "drivers/cpuidle/Kconfig.mips"
43 source "drivers/cpuidle/Kconfig.powerpc"
/linux-4.1.27/drivers/usb/gadget/legacy/
DMakefile5 ccflags-y := -I$(srctree)/drivers/usb/gadget/
6 ccflags-y += -I$(srctree)/drivers/usb/gadget/udc/
7 ccflags-y += -I$(srctree)/drivers/usb/gadget/function/
/linux-4.1.27/sound/soc/fsl/
DKconfig12 This option is only useful for out-of-tree drivers since
13 in-tree drivers select it automatically.
23 This option is only useful for out-of-tree drivers since
24 in-tree drivers select it automatically.
34 This option is only useful for out-of-tree drivers since
35 in-tree drivers select it automatically.
45 This option is only useful for out-of-tree drivers since
46 in-tree drivers select it automatically.
55 This option is only useful for out-of-tree drivers since
56 in-tree drivers select it automatically.
[all …]
/linux-4.1.27/Documentation/watchdog/
Dwatchdog-api.txt29 drivers implement different, and sometimes incompatible, parts of it.
35 All drivers support the basic mode of operation, where the watchdog
49 drivers support the configuration option "Disable watchdog shutdown on
69 All conforming drivers also support an ioctl API.
73 All drivers that have an ioctl interface support at least one ioctl,
87 For some drivers it is possible to modify the watchdog timeout on the
88 fly with the SETTIMEOUT ioctl, those drivers have the WDIOF_SETTIMEOUT
129 Not all watchdog drivers will support a pretimeout.
133 Some watchdog drivers have the ability to report the remaining time
142 All watchdog drivers are required return more information about the system,
[all …]
Dconvert_drivers_to_kernel_api.txt1 Converting old watchdog drivers to the watchdog framework
7 components, those drivers can be lightened making it a user of the framework.
15 Old drivers define their own file_operations for actions like open(), write(),
23 driver specific start-function. Note that for some drivers, the start-function
67 intended for porting old drivers; new drivers should not invent private IOCTLs.
156 watchdog_info struct and the newly created watchdog_ops. Often, old drivers
159 watchdog_device. Note that the timeout values are unsigned int. Some drivers
173 A few drivers use nowayout statically, i.e. there is no module parameter for it
180 Most drivers, however, also allow runtime configuration of nowayout, usually
/linux-4.1.27/drivers/media/platform/s5p-tv/
DKconfig1 # drivers/media/platform/s5p-tv/Kconfig
30 subdev for use by other drivers. This driver requires
48 subdev for use by other drivers.
58 subdev for use by other drivers.
68 subdev for use by other drivers. This driver requires
/linux-4.1.27/Documentation/ptp/
Dptp.txt11 drivers and a user space interface. The infrastructure supports a
35 The class driver supports multiple PTP clock drivers. In normal use
55 ** Writing clock drivers
57 Clock drivers include include/linux/ptp_clock_kernel.h and register
59 registration method. Clock drivers must implement all of the
66 as a 64 bit integer accessed as two 32 bit registers, drivers
/linux-4.1.27/arch/arm/oprofile/
DMakefile3 DRIVER_OBJS = $(addprefix ../../../drivers/oprofile/, \
10 DRIVER_OBJS += $(addprefix ../../../drivers/oprofile/, oprofile_perf.o)
/linux-4.1.27/drivers/staging/comedi/
DMakefile3 comedi-y := comedi_fops.o range.o drivers.o \
15 obj-$(CONFIG_COMEDI) += drivers/
/linux-4.1.27/arch/sh/oprofile/
DMakefile5 DRIVER_OBJS = $(addprefix ../../../drivers/oprofile/, \
12 DRIVER_OBJS += $(addprefix ../../../drivers/oprofile/, oprofile_perf.o)
/linux-4.1.27/drivers/hsi/
DKconfig17 source "drivers/hsi/controllers/Kconfig"
18 source "drivers/hsi/clients/Kconfig"
/linux-4.1.27/drivers/usb/mon/
DKconfig9 between peripheral-specific drivers and HC drivers will be built.
/linux-4.1.27/drivers/staging/unisys/Documentation/
Doverview.txt8 partitions. s-Par provides a set of para-virtualized device drivers to
15 drivers provide support interfaces for communicating with s-Par
22 drivers. The bus modules provide organization for the device driver
25 These drivers are for the Unisys virtual PCI hardware model where the
27 in the interactions between the client drivers and the virtual adapter
42 controlling registration of shared device drivers with the s-Par
45 for shared device drivers to function properly. Visorchipset also
94 drivers except visorserial, visordiag, virthba, and virtnic. It
171 The drivers required to boot a Linux guest are visorchipset, visorbus,
173 visorchannel, and visorutil. The other drivers are required by the
/linux-4.1.27/drivers/usb/gadget/
DKconfig36 your peripheral protocol. (If you use modular gadget drivers,
39 If in doubt, say "N" and don't enable these drivers; most people
51 Many controller and gadget drivers will print some debugging
55 debugging such a driver. Many drivers will emit so many
65 Many controller and gadget drivers will print verbose debugging
69 debugging such a driver. Many drivers will emit so many
79 Some of the drivers in the "gadget" framework can expose
90 Some of the drivers in the "gadget" framework can expose
112 drivers that have more specific information.
130 source "drivers/usb/gadget/udc/Kconfig"
[all …]
/linux-4.1.27/drivers/usb/gadget/udc/
DKconfig43 gadget drivers to also be dynamically linked.
54 gadget drivers to also be dynamically linked.
87 all gadget drivers to also be dynamically linked.
126 gadget drivers to also be dynamically linked.
141 gadget drivers to also be dynamically linked.
163 gadget drivers to also be dynamically linked.
175 gadget drivers to also be dynamically linked.
188 gadget drivers to also be dynamically linked.
243 gadget drivers to also be dynamically linked.
245 source "drivers/usb/gadget/udc/bdc/Kconfig"
[all …]
/linux-4.1.27/drivers/mfd/
DKconfig6 menu "Multifunction device drivers"
59 additional drivers must be enabled in order to use the
70 additional drivers must be enabled in order to use the
155 for accessing the device, additional drivers must be enabled in
167 for accessing the device, additional drivers must be enabled in
180 Additional drivers must be enabled in order to use the functionality
195 Additional drivers must be enabled in order to use the functionality
207 Additional drivers must be enabled in order to use the specific
216 DLN-2. Additional drivers such as I2C_DLN2, GPIO_DLN2,
228 additional drivers must be enabled in order to use the
[all …]
/linux-4.1.27/Documentation/devicetree/bindings/mmc/
Dtmio_mmc.txt4 devices is managed by either MFD drivers or by the sh_mobile_sdhi platform
5 driver. Those drivers supply the tmio-mmc driver with platform data, that either
8 compulsory and any optional properties, common to all SD/MMC drivers, as
/linux-4.1.27/tools/virtio/
DMakefile7 vpath %.c ../../drivers/virtio ../../drivers/vhost
/linux-4.1.27/drivers/message/fusion/
DKconfig7 Passing Technology (MPT) drivers.
15 tristate "Fusion MPT ScsiHost drivers for SPI"
30 tristate "Fusion MPT ScsiHost drivers for FC"
49 tristate "Fusion MPT ScsiHost drivers for SAS"
121 file:drivers/message/fusion/mptdebug.h
/linux-4.1.27/drivers/media/usb/b2c2/
DKconfig10 bool "Enable debug for the B2C2 FlexCop drivers"
15 of all B2C2 FlexCop drivers.
/linux-4.1.27/drivers/media/pci/b2c2/
DKconfig10 bool "Enable debug for the B2C2 FlexCop drivers"
15 of all B2C2 FlexCop drivers.
/linux-4.1.27/drivers/pnp/
DKconfig41 source "drivers/pnp/isapnp/Kconfig"
43 source "drivers/pnp/pnpbios/Kconfig"
45 source "drivers/pnp/pnpacpi/Kconfig"
/linux-4.1.27/drivers/staging/android/
DKconfig38 drivers. Sync implementations can take advantage of hardware
57 drivers from userspace.
59 source "drivers/staging/android/ion/Kconfig"
/linux-4.1.27/drivers/memstick/
DKconfig22 source "drivers/memstick/core/Kconfig"
24 source "drivers/memstick/host/Kconfig"
/linux-4.1.27/drivers/ipack/
DKconfig20 source "drivers/ipack/carriers/Kconfig"
22 source "drivers/ipack/devices/Kconfig"
/linux-4.1.27/Documentation/powerpc/
Deeh-pci-error-recovery.txt116 so that individual device drivers do not need to be modified to support
125 drivers/pci/hotplug/pSeries_pci.c calling in to the eeh.c code.
155 drivers, or other parts of the kernel, can use
173 drivers/pci/hotplug/pSeries_pci.c, called handle_eeh_events().
199 pci_remove_bus_device (struct pci_dev *) // in /drivers/pci/remove.c
205 device_unregister (&dev->dev) // in /drivers/base/core.c
211 bus_remove_device() // in /drivers/base/bus.c
218 pci_device_remove() // in /drivers/pci/pci_driver.c
222 pcnet32_remove_one() // in /drivers/net/pcnet32.c
244 in drivers/pci/pci_driver.c,
[all …]
/linux-4.1.27/drivers/net/caif/
DKconfig2 # CAIF physical drivers
5 comment "CAIF transport drivers"
55 source "drivers/vhost/Kconfig"
/linux-4.1.27/drivers/staging/media/davinci_vpfe/
DTODO30 - copy vpfe.h from drivers/staging/media/davinci_vpfe/ to
32 - copy davinci_vpfe_user.h from drivers/staging/media/davinci_vpfe/ to
35 - copy dm365_ipipeif_user.h from drivers/staging/media/davinci_vpfe/ to
/linux-4.1.27/firmware/
DREADME.AddingFirmware6 device drivers which predate the common use of request_firmware().
8 As we update those drivers to use request_firmware() and keep a clean
18 extracted from older drivers, as well various new firmware images which
/linux-4.1.27/sound/soc/tegra/
DKconfig19 machine drivers to support below.
26 You will also need to select the individual machine drivers to
36 machine drivers to support below.
44 You will also need to select the individual machine drivers to support
52 You will also need to select the individual machine drivers to
62 machine drivers to support below.
/linux-4.1.27/drivers/misc/
DKconfig60 these blocks by different drivers despite processor differences.
148 necessary infrastructure for other drivers to utilize.
162 You will also have to select some flash card format drivers. MMC/SD
177 flash card format drivers, as outlined in the TIFM_CORE Help.
233 drivers that need timers. MFGPTs are available in the CS5535 and
237 You probably don't want to enable this manually; other drivers that
518 source "drivers/misc/c2port/Kconfig"
519 source "drivers/misc/eeprom/Kconfig"
520 source "drivers/misc/cb710/Kconfig"
521 source "drivers/misc/ti-st/Kconfig"
[all …]
/linux-4.1.27/lib/fonts/
DKconfig47 bool "Mac console 6x11 font (not supported by all drivers)" if FONTS
52 framebuffer drivers don't support this one at all.
55 bool "console 7x14 font (not supported by all drivers)" if FONTS
97 bool "Sparc console 12x22 font (not supported by all drivers)"
105 bool "console 10x18 font (not supported by all drivers)" if FONTS
/linux-4.1.27/Documentation/block/
Dwriteback_cache_control.txt50 Implementation details for make_request_fn based block drivers
53 These drivers will always see the REQ_FLUSH and REQ_FUA bits as they sit
54 directly below the submit_bio interface. For remapping drivers the REQ_FUA
57 drivers that do not have a volatile cache the REQ_FLUSH and REQ_FUA bits
64 Implementation details for request_fn based block drivers
/linux-4.1.27/Documentation/cpu-freq/
Dcore.txt28 The CPUFreq core code is located in drivers/cpufreq/cpufreq.c. This
30 architecture drivers (those pieces of code that do actual
32 drivers or other part of the kernel that need to be informed of
35 speed limits (like LCD drivers on ARM architecture). Additionally, the
68 - if two hardware drivers failed to agree on a new policy before this
/linux-4.1.27/Documentation/mips/
DAU1xxx_IDE.README5 This file describes the 'drivers/ide/au1xxx-ide.c', related files and the
52 b) 'drivers/ide/mips/au1xxx-ide.c'
91 Also define 'IDE_AU1XXX_BURSTMODE' in 'drivers/ide/mips/au1xxx-ide.c' to enable
108 Also undefine 'IDE_AU1XXX_BURSTMODE' in 'drivers/ide/mips/au1xxx-ide.c' to
115 These drivers wouldn't have been done without the base of kernel 2.4.x AU1XXX
/linux-4.1.27/drivers/platform/mips/
DKconfig9 Say Y here to get to see options for device drivers of various
11 extension and hardware monitor drivers. This option itself does
/linux-4.1.27/drivers/iio/common/ssp_sensors/
DKconfig2 # SSP sensor drivers and commons configuration
7 tristate "Commons for all SSP Sensor IIO drivers"
/linux-4.1.27/drivers/thermal/
DKconfig2 # Generic thermal sysfs drivers configuration
94 used for fans without throttling. Some fan drivers depend on this
109 (drivers/acpi/processor_thermal.c).
265 tristate "ACPI INT340X thermal drivers"
288 menu "Texas Instruments thermal drivers"
289 source "drivers/thermal/ti-soc-thermal/Kconfig"
292 menu "Samsung thermal drivers"
294 source "drivers/thermal/samsung/Kconfig"
297 menu "STMicroelectronics thermal drivers"
299 source "drivers/thermal/st/Kconfig"
/linux-4.1.27/drivers/xen/
DKconfig100 Support for backend device drivers that provide I/O services
154 to other domains. This can be used to implement frontend drivers
187 from the default device drivers. The argument is the list of PCI BDFs:
207 bool "Xen stub drivers"
211 Allow kernel to install stub drivers, to reserve space for Xen drivers,
212 i.e. memory hotplug and cpu hotplug, and to block native drivers loaded,
213 so that real Xen drivers can be modular.
251 SMM so that other drivers (such as ACPI cpufreq scaling driver) will
256 M here. If the CPUFREQ drivers are built in, select Y here.
/linux-4.1.27/sound/soc/ux500/
DKconfig31 This will enable platform-drivers for: Ux500
32 This will enable codec-drivers for: AB8500
/linux-4.1.27/sound/mips/
DKconfig1 # ALSA MIPS drivers
35 Newer drivers for ASoC are available, please do not use
/linux-4.1.27/drivers/net/ethernet/mellanox/
DKconfig21 source "drivers/net/ethernet/mellanox/mlx4/Kconfig"
22 source "drivers/net/ethernet/mellanox/mlx5/core/Kconfig"
/linux-4.1.27/drivers/media/usb/dvb-usb/
DMakefile79 ccflags-y += -I$(srctree)/drivers/media/dvb-core
80 ccflags-y += -I$(srctree)/drivers/media/dvb-frontends/
82 ccflags-y += -I$(srctree)/drivers/media/tuners
83 ccflags-y += -I$(srctree)/drivers/media/pci/ttpci
/linux-4.1.27/Documentation/mtd/
Dspi-nor.txt7 SPI bus controllers (drivers/spi/) only deal with streams of bytes; the bus
56 Part III - How can drivers use the framework?
61 drivers/mtd/spi-nor/spi-nor.c for detail. Please also refer to fsl-quadspi.c
/linux-4.1.27/drivers/isdn/i4l/
DKconfig122 comment "ISDN4Linux hardware drivers"
124 source "drivers/isdn/hisax/Kconfig"
129 source "drivers/isdn/icn/Kconfig"
131 source "drivers/isdn/pcbit/Kconfig"
133 source "drivers/isdn/sc/Kconfig"
135 source "drivers/isdn/act2000/Kconfig"
/linux-4.1.27/drivers/vfio/pci/
DKconfig7 use of PCI drivers using the VFIO framework.
17 BIOS and generic video drivers.
/linux-4.1.27/Documentation/devicetree/bindings/mailbox/
Dmailbox.txt3 Generic binding to provide a way for Mailbox controller drivers to
4 assign appropriate mailbox channel to client drivers.
/linux-4.1.27/Documentation/cpuidle/
Dcore.txt13 governors and drivers.
15 cpuidle resides under drivers/cpuidle.
/linux-4.1.27/drivers/dma/bestcomm/
DKconfig13 optional for some drivers (like ATA), but required for
16 If you want to use drivers that require DMA operations,
/linux-4.1.27/drivers/soc/ti/
DKconfig2 # TI SOC drivers
5 bool "TI SOC drivers support"
/linux-4.1.27/arch/s390/
DMakefile101 drivers-y += drivers/s390/
104 drivers-$(CONFIG_OPROFILE) += arch/s390/oprofile/
/linux-4.1.27/Documentation/arm/Samsung-S3C24XX/
DS3C2412.txt15 The core clock code provides a set of clocks to the drivers, and allows
42 s3c2410 driver in the drivers/serial directory.
49 s3c2410 driver in the drivers/mtd/nand directory.
/linux-4.1.27/drivers/net/wireless/iwlegacy/
DKconfig67 bool "Enable full debugging output in iwlegacy (iwl 3945/4965) drivers"
71 drivers.
86 drivers/net/wireless/iwlegacy/common.h
96 Enable creation of debugfs files for the iwlegacy drivers. This
/linux-4.1.27/arch/x86/
DMakefile201 drivers-$(CONFIG_MATH_EMULATION) += arch/x86/math-emu/
202 drivers-$(CONFIG_PCI) += arch/x86/pci/
205 drivers-$(CONFIG_OPROFILE) += arch/x86/oprofile/
208 drivers-$(CONFIG_PM) += arch/x86/power/
210 drivers-$(CONFIG_FB) += arch/x86/video/
/linux-4.1.27/Documentation/devicetree/
Dof_unittest.txt20 most of the device drivers in various use cases.
25 The Device Tree Source file (drivers/of/unittest-data/testcases.dts) contains
27 drivers/of/unittest.c. Currently, following Device Tree Source Include files
30 drivers/of/unittest-data/tests-interrupts.dtsi
31 drivers/of/unittest-data/tests-platform.dtsi
32 drivers/of/unittest-data/tests-phandle.dtsi
33 drivers/of/unittest-data/tests-match.dtsi
/linux-4.1.27/Documentation/devicetree/bindings/powerpc/fsl/cpm_qe/qe/
Dfirmware.txt6 device drivers may need.
11 Device drivers can search this string to determine if the
/linux-4.1.27/drivers/net/wireless/rsi/
DKconfig21 This option enables the SDIO bus support in rsi drivers.
29 This option enables the USB bus support in rsi drivers.
/linux-4.1.27/Documentation/wimax/
DREADME.i2400m26 2.1. Compilation of the drivers included in the kernel
28 Configure the kernel; to enable the WiMAX drivers select Drivers >
33 to build the i2400m USB or SDIO drivers will not show. Enable said
34 subsystems and go back to the WiMAX menu to enable the drivers.
38 2.2. Compilation of the drivers distributed as an standalone module
88 generic driver and the bus-specific drivers. The bus generic driver
90 use to connect to the device. The bus specific drivers are just the
92 USB and SDIO are supported. See drivers/net/wimax/i2400m/i2400m.h for
99 easily reuse the hardware-glue to write drivers for other OSes; note
227 to the host. See drivers/net/wimax/i2400m/tx.c.
/linux-4.1.27/drivers/w1/
DKconfig28 source drivers/w1/masters/Kconfig
29 source drivers/w1/slaves/Kconfig
/linux-4.1.27/drivers/pinctrl/spear/
DKconfig2 # ST Microelectronics SPEAr PINCTRL drivers
12 This enables pin control drivers for SPEAr Platform

123456