/drivers/char/ |
D | mmtimer.c | 262 int nodeid = n->timer->it.mmtimer.node; in mmtimer_add_list() 263 unsigned long expires = n->timer->it.mmtimer.expires; in mmtimer_add_list() 275 if (expires < x->timer->it.mmtimer.expires) in mmtimer_add_list() 289 struct mmtimer, list)->timer->it.mmtimer.expires) in mmtimer_add_list() 311 if (!t->it.mmtimer.incr) { in mmtimer_set_next_timer() 314 t->it.mmtimer.expires, in mmtimer_set_next_timer() 324 expires = exp = t->it.mmtimer.expires; in mmtimer_set_next_timer() 333 to = ((u64)(expires - exp) / t->it.mmtimer.incr); in mmtimer_set_next_timer() 336 t->it.mmtimer.expires += t->it.mmtimer.incr * to; in mmtimer_set_next_timer() 337 exp = t->it.mmtimer.expires; in mmtimer_set_next_timer() [all …]
|
/drivers/staging/speakup/ |
D | Kconfig | 7 This is the Speakup screen reader. Think of it as a 9 kernel, it can speak everything on the text console from 48 synthesizer. You can say y to build it into the kernel, 49 or m to build it as a module. See the configuration 56 synthesizer. You can say y to build it into the kernel, 57 or m to build it as a module. See the configuration 64 synthesizer. You can say y to build it into the kernel, 65 or m to build it as a module. See the configuration 72 You can say y to build it into the kernel, or m to 73 build it as a module. See the configuration help on the [all …]
|
/drivers/net/wireless/rtlwifi/ |
D | Kconfig | 10 If you choose to build as a module, it'll be called rtlwifi. 29 If you choose to build it as a module, it will be called rtl8192ce 38 If you choose to build it as a module, it will be called rtl8192se 47 If you choose to build it as a module, it will be called rtl8192de 56 If you choose to build it as a module, it will be called rtl8723ae 65 If you choose to build it as a module, it will be called rtl8188ee 75 If you choose to build it as a module, it will be called rtl8192cu
|
/drivers/staging/asus_oled/ |
D | README | 12 but I don't guarantee that it won't do anything wrong :) 15 in my case, and I hope others will find it useful too! 27 It will build (hopefully) the module and install it in 30 To load it just use: 33 You can check if it has detected your OLED display by looking into dmesg output. 37 If it doesn't find your display, you can try removing usbhid module. 39 before usbhid, it will work even when usbhid is present. 41 If it still doesn't detect your hardware, check lsusb output. 45 If you don't see any lines with '0b05:1726' it means that you have different 46 type of hardware that is not detected (it may or may not work, but the driver [all …]
|
/drivers/net/wireless/mwifiex/ |
D | Kconfig | 8 If you choose to build it as a module, it will be called 19 If you choose to build it as a module, it will be called 30 If you choose to build it as a module, it will be called 41 If you choose to build it as a module, it will be called
|
/drivers/staging/iio/Documentation/ |
D | sysfs-bus-iio-light | 34 it comes back in SI units, it should also include _input else it 35 should include _raw to signify it is not in SI units. 54 value is returned in SI units, it should also include _input 55 but if it is not, then it should include _raw. 64 value is not in SI units, then it should include _raw. 96 value is not in SI units (irradiance, uW/mm^2), then it should 104 light sensor. If it comes back in SI units, it should also 105 include _input else it should include _raw to signify it is not
|
/drivers/staging/comedi/ |
D | range.c | 65 struct comedi_rangeinfo it; in do_rangeinfo_ioctl() local 70 if (copy_from_user(&it, arg, sizeof(struct comedi_rangeinfo))) in do_rangeinfo_ioctl() 72 subd = (it.range_type >> 24) & 0xf; in do_rangeinfo_ioctl() 73 chan = (it.range_type >> 16) & 0xff; in do_rangeinfo_ioctl() 90 if (RANGE_LENGTH(it.range_type) != lr->length) { in do_rangeinfo_ioctl() 92 RANGE_LENGTH(it.range_type), lr->length, it.range_type); in do_rangeinfo_ioctl() 96 if (copy_to_user(it.range_ptr, lr->range, in do_rangeinfo_ioctl()
|
/drivers/staging/comedi/drivers/ |
D | rti800.c | 290 static int rti800_attach(struct comedi_device *dev, struct comedi_devconfig *it) in rti800_attach() argument 297 ret = comedi_request_region(dev, it->options[0], RTI800_IOSIZE); in rti800_attach() 310 devpriv->adc_2comp = (it->options[4] == 0); in rti800_attach() 311 devpriv->dac_2comp[0] = (it->options[6] == 0); in rti800_attach() 312 devpriv->dac_2comp[1] = (it->options[8] == 0); in rti800_attach() 324 s->n_chan = (it->options[2] ? 16 : 8); in rti800_attach() 327 s->range_table = (it->options[3] < ARRAY_SIZE(rti800_ai_ranges)) in rti800_attach() 328 ? rti800_ai_ranges[it->options[3]] in rti800_attach() 342 (it->options[5] < ARRAY_SIZE(rti800_ao_ranges)) in rti800_attach() 343 ? rti800_ao_ranges[it->options[5]] in rti800_attach() [all …]
|
D | pcl724.c | 99 static int pcl724_attach(struct comedi_device *dev, struct comedi_devconfig *it) in pcl724_attach() argument 111 ((it->options[1] == 1) || (it->options[1] == 96))) in pcl724_attach() 113 ret = comedi_request_region(dev, it->options[0], iorange); in pcl724_attach() 120 irq = it->options[1]; in pcl724_attach() 147 if ((board->can_have96) && ((it->options[1] == 1) in pcl724_attach() 148 || (it->options[1] == 96))) in pcl724_attach()
|
D | dt2815.c | 157 static int dt2815_attach(struct comedi_device *dev, struct comedi_devconfig *it) in dt2815_attach() argument 165 ret = comedi_request_region(dev, it->options[0], DT2815_SIZE); in dt2815_attach() 188 current_range_type = (it->options[3]) in dt2815_attach() 190 voltage_range_type = (it->options[2]) in dt2815_attach() 193 devpriv->range_type_list[i] = (it->options[5 + i]) in dt2815_attach() 207 program = (it->options[4] & 0x3) << 3 | 0x7; in dt2815_attach()
|
D | das16.c | 996 static int das16_probe(struct comedi_device *dev, struct comedi_devconfig *it) in das16_probe() argument 1077 static int das16_attach(struct comedi_device *dev, struct comedi_devconfig *it) in das16_attach() argument 1090 irq = it->options[1]; in das16_attach() 1091 timer_mode = it->options[8]; in das16_attach() 1101 if (it->options[3]) { in das16_attach() 1102 if (it->options[3] != 0 && in das16_attach() 1103 it->options[3] != 1 && it->options[3] != 10) { in das16_attach() 1117 ret = comedi_request_region(dev, it->options[0], board->size); in das16_attach() 1121 ret = comedi_request_region(dev, it->options[0], 0x10); in das16_attach() 1133 if (das16_probe(dev, it)) { in das16_attach() [all …]
|
/drivers/net/wireless/ath/ath6kl/ |
D | Kconfig | 12 choose to build it as a module, it will be called ath6kl_sdio. 24 implementation and it isn't functional. If you choose to 25 build it as a module, it will be called ath6kl_usb. 40 If unsure, say Y to make it easier to debug problems. 47 Enabling this makes it possible to change the regdomain in
|
/drivers/bluetooth/ |
D | Kconfig | 14 kernel or say M to compile it as module (btusb). 25 kernel or say M to compile it as module (btsdio). 38 kernel or say M to compile it as module (hci_uart). 89 The HCI Three-wire UART Transport Layer makes it possible to 107 kernel or say M to compile it as module (bcm203x). 118 kernel or say M to compile it as module (bpa10x). 131 kernel or say M to compile it as module (bfusb). 144 kernel or say M to compile it as module (dtl1_cs). 158 kernel or say M to compile it as module (bt3c_cs). 171 kernel or say M to compile it as module (bluecard_cs). [all …]
|
/drivers/isdn/hisax/ |
D | Kconfig | 96 See <file:Documentation/isdn/README.HiSax> on how to configure it 106 See <file:Documentation/isdn/README.HiSax> on how to configure it 115 See <file:Documentation/isdn/README.HiSax> on how to configure it. 122 configure it. 130 See <file:Documentation/isdn/README.HiSax> on how to configure it 139 See <file:Documentation/isdn/README.HiSax> on how to configure it. 145 See <file:Documentation/isdn/README.HiSax> on how to configure it. 153 See <file:Documentation/isdn/README.HiSax> on how to configure it 163 See <file:Documentation/isdn/README.HiSax> on how to configure it 173 See <file:Documentation/isdn/README.HiSax> on how to configure it [all …]
|
/drivers/staging/rtl8192e/ |
D | license | 14 document, but changing it is not allowed. 19 share and change it. By contrast, the GNU General Public License is intended 23 whose authors commit to using it. (Some other Free Software Foundation 25 can apply it to your programs, too. 30 wish), that you receive source code or can get it if you want it, that you 31 can change the software or use pieces of it in new free programs; and that 37 copies of the software, or if you modify it. 58 proprietary. To prevent this, we have made it clear that any patent must be 67 placed by the copyright holder saying it may be distributed under the 71 work containing the Program or a portion of it, either verbatim or with [all …]
|
/drivers/staging/usbip/userspace/ |
D | COPYING | 7 of this license document, but changing it is not allowed. 12 freedom to share and change it. By contrast, the GNU General Public 17 using it. (Some other Free Software Foundation software is covered by 18 the GNU Library General Public License instead.) You can apply it to 24 this service if you wish), that you receive source code or can get it 25 if you want it, that you can change the software or use pieces of it 31 distribute copies of the software, or if you modify it. 53 program proprietary. To prevent this, we have made it clear that any 63 a notice placed by the copyright holder saying it may be distributed 67 that is to say, a work containing the Program or a portion of it, [all …]
|
D | INSTALL | 8 unlimited permission to copy, distribute and modify it. 22 definitions. Finally, it creates a shell script `config.status' that 38 may remove or edit it. 42 you want to change it or regenerate `configure' using a newer version 50 Running `configure' might take a while. While running, it prints 51 some messages telling which features it is checking for. 66 for the package's developers. If you use it, you may have to get 98 With a non-GNU `make', it is safer to compile the package for one 122 If the package supports it, you can cause programs to be installed 137 find the X include and library files automatically, but if it doesn't, [all …]
|
/drivers/staging/rtl8192u/ |
D | copying | 7 of this license document, but changing it is not allowed. 12 freedom to share and change it. By contrast, the GNU General Public 17 using it. (Some other Free Software Foundation software is covered by 18 the GNU Library General Public License instead.) You can apply it to 24 this service if you wish), that you receive source code or can get it 25 if you want it, that you can change the software or use pieces of it 31 distribute copies of the software, or if you modify it. 53 program proprietary. To prevent this, we have made it clear that any 63 a notice placed by the copyright holder saying it may be distributed 67 that is to say, a work containing the Program or a portion of it, [all …]
|
/drivers/net/irda/ |
D | Kconfig | 11 discipline. To compile it as a module, choose M here: the module 12 will be called irtty-sir. IrTTY makes it possible to use Linux's 31 Saying M, it will be built as a module named bfin_sir. 94 JetEye PC dongle. To compile it as a module, choose M here. The ESI 105 IR220L+ dongles. To compile it as a module, choose M here. The 116 dongle. To compile it as a module, choose M here. The Tekram dongle 128 To compile it as a module, choose M here. 135 dongle. To compile it as a module, choose M here. The Parallax 146 dongle. To compile it as a module, choose M here. The MA600 dongle 159 dongle. If you want to compile it as a module, choose M here. [all …]
|
/drivers/usb/storage/ |
D | Kconfig | 40 If this driver is compiled as a module, it will be named ums-realtek. 54 If this driver is compiled as a module, it will be named ums-datafab. 63 If this driver is compiled as a module, it will be named ums-freecom. 81 If this driver is compiled as a module, it will be named ums-isd200. 104 If this driver is compiled as a module, it will be named ums-usbat. 114 If this driver is compiled as a module, it will be named ums-sddr09. 123 If this driver is compiled as a module, it will be named ums-sddr55. 132 If this driver is compiled as a module, it will be named ums-jumpshot. 144 If this driver is compiled as a module, it will be named ums-alauda. 159 If this driver is compiled as a module, it will be named ums-onetouch. [all …]
|
/drivers/media/usb/pwc/ |
D | philips.txt | 40 the latter, since it makes troubleshooting a lot easier. The built-in 45 don't know how to set it properly in the driver. The options are: 59 the cam is a bit slow or momentarily busy. However, on slow machines it 61 reasonable. You can set it between 2 and 5. 71 However, it doesn't really buffer images, it just gives you a bit more 75 The absolute maximum is 10, but don't set it too high! Every buffer takes 100 High compression takes less bandwidth of course, but it could also 120 the LED never goes on, making it suitable for silent surveillance. 134 never know what device a camera gets assigned; it depends on module load 136 and the phase of the moon (i.e. it can be random). With this option you [all …]
|
/drivers/watchdog/ |
D | Kconfig | 11 subsequently opening the file and then failing to write to it for 43 to stop the timer if the process managing it closes the file 46 it has been started. 62 from. Equally it's a lot cheaper to install. 145 "If in doubt, leave it out" - say N. 389 this driver is essential and you should enable it. 430 simply watches your kernel to make sure it doesn't freeze, and if 431 it does, it reboots your computer after a certain amount of time. 479 it as a module. The module will be called f71808e_wdt. 500 it doesn't freeze, and if it does, it reboots your computer after [all …]
|
/drivers/char/tpm/ |
D | Kconfig | 12 say Yes and it will be accessible from within Linux. For 32 TCG TIS 1.2 TPM specification say Yes and it will be accessible 42 Specification 0.20 say Yes and it will be accessible from within 52 say Yes and it will be accessible from within Linux. To 60 If you have a TPM security chip from Atmel say Yes and it 69 (either SLD 9630 TT 1.1 or SLB 9635 TT 1.2) say Yes and it 80 If you have IBM virtual TPM (VTPM) support say Yes and it 90 an I2C bus say Yes and it will be accessible from within Linux.
|
/drivers/staging/media/dt3155v4l/ |
D | Kconfig | 19 Select it for CCIR/50Hz (European region), 20 or leave it unselected for RS-170/60Hz (North America). 27 Select it if you want to use streaming of memory mapped buffers 28 or leave it unselected if you want to use read method (one copy more).
|
/drivers/net/wireless/ath/wil6210/ |
D | Kconfig | 13 If you choose to build it as a module, it will be called 24 it saves extra target transaction; 27 self-clear when accessed for debug purposes, it makes
|