/linux-4.1.27/fs/cachefiles/ |
D | rdwr.c | 27 struct cachefiles_one_read *monitor = in cachefiles_read_waiter() local 28 container_of(wait, struct cachefiles_one_read, monitor); in cachefiles_read_waiter() 36 monitor->netfs_page->index, mode, sync, in cachefiles_read_waiter() 54 ASSERT(monitor->op); in cachefiles_read_waiter() 56 object = container_of(monitor->op->op.object, in cachefiles_read_waiter() 60 list_add_tail(&monitor->op_link, &monitor->op->to_do); in cachefiles_read_waiter() 63 fscache_enqueue_retrieval(monitor->op); in cachefiles_read_waiter() 75 struct cachefiles_one_read *monitor) in cachefiles_read_reissue() argument 78 struct page *backpage = monitor->back_page, *backpage2; in cachefiles_read_reissue() 107 INIT_LIST_HEAD(&monitor->op_link); in cachefiles_read_reissue() [all …]
|
D | internal.h | 98 wait_queue_t monitor; /* link into monitored waitqueue */ member
|
/linux-4.1.27/arch/arm/firmware/ |
D | Kconfig | 12 bool "Trusted Foundations secure monitor support" 17 market) are booted with the Trusted Foundations secure monitor 19 monitor instead of the kernel. 21 This option allows the kernel to invoke the secure monitor whenever
|
/linux-4.1.27/drivers/w1/slaves/ |
D | Kconfig | 82 tristate "Dallas 2760 battery monitor chip (HP iPAQ & others)" 84 If you enable this you will have the DS2760 battery monitor 87 The battery monitor chip is used in many batteries/devices 94 tristate "Dallas 2780 battery monitor chip" 96 If you enable this you will have the DS2780 battery monitor 99 The battery monitor chip is used in many batteries/devices 106 tristate "Dallas 2781 battery monitor chip" 108 If you enable this you will have the DS2781 battery monitor 111 The battery monitor chip is used in many batteries/devices
|
/linux-4.1.27/Documentation/s390/ |
D | monreader.txt | 21 IUCV *MONITOR statement in its user entry. If the monitor DCSS to be used is 26 There are two options for being able to load the monitor DCSS (examples assume 27 that the monitor DCSS begins at 144 MB and ends at 152 MB). You can query the 28 location of the monitor DCSS with the Class E privileged CP command Q NSS MAP 64 to specify the name of the monitor DCSS. If the module is compiled into the 70 Performance Toolkit), the monitor DCSS is already defined and you have to use 72 of the monitor DCSS, if already defined, and the users connected to the 74 Refer to the "z/VM Performance" book (SC24-6109-00) on how to create a monitor 113 This loads the module with the default monitor DCSS (MONDCSS) and creates a 125 Reading from the device provides a 12 Byte monitor control element (MCE), [all …]
|
D | 00-INDEX | 22 - information on accessing the z/VM monitor stream from Linux.
|
/linux-4.1.27/tools/perf/ui/gtk/ |
D | browser.c | 21 int monitor; in perf_gtk__resize_window() local 27 monitor = gdk_screen_get_monitor_at_window(screen, window->window); in perf_gtk__resize_window() 29 gdk_screen_get_monitor_geometry(screen, monitor, &rect); in perf_gtk__resize_window()
|
/linux-4.1.27/drivers/net/wireless/ipw2x00/ |
D | libipw_module.c | 130 struct net_device *alloc_libipw(int sizeof_priv, int monitor) in alloc_libipw() argument 146 if (!monitor) { in alloc_libipw() 204 if (!monitor) in alloc_libipw() 213 void free_libipw(struct net_device *dev, int monitor) in free_libipw() argument 222 if (!monitor) in free_libipw()
|
D | Kconfig | 44 Enables promiscuous/monitor mode support for the ipw2100 driver. 106 Enables promiscuous/monitor mode support for the ipw2200 driver.
|
D | libipw.h | 949 void free_libipw(struct net_device *dev, int monitor); 950 struct net_device *alloc_libipw(int sizeof_priv, int monitor);
|
/linux-4.1.27/arch/avr32/boards/atngw100/ |
D | evklcd10x.c | 51 .monitor = "TCG057VGLAD", 89 .monitor = "TCG057QVLAD", 127 .monitor = "PH320240T",
|
D | mrmt.c | 78 .monitor = "LQ043T3DX02", 121 .monitor = "KWH043GM08",
|
/linux-4.1.27/Documentation/hwmon/ |
D | ina2xx | 40 The INA219 is a high-side current shunt and power monitor with an I2C 44 The INA220 is a high or low side current shunt and power monitor with an I2C 47 The INA226 is a current shunt and power monitor with an I2C interface. 51 with an I2C interface. The chips monitor both a shunt voltage drop and
|
D | userspace-tools | 4 Most mainboards have sensor chips to monitor system health (like temperatures, 38 hardware-monitor
|
D | max6639 | 18 temperature monitor with dual PWM fan speed controller. It can monitor its own
|
D | lm95245 | 21 Management Bus (SMBus) interface and TruTherm technology that can monitor 23 The chips can be used to very accurately monitor the temperature of
|
D | max16065 | 34 monitor and sequence multiple system voltages. The MAX16065/MAX16066 can also 35 accurately monitor (+/-2.5%) one current channel using a dedicated high-side 46 system voltages. The MAX16070/MAX16071 can also accurately monitor (+/-2.5%)
|
D | ucd9000 | 28 system-health monitor. The device integrates a 12-bit ADC for monitoring up to 36 monitor. The device integrates a 12-bit ADC for monitoring up to 10 power-supply 43 system-health monitor. The device integrates a 12-bit ADC for monitoring up to
|
D | adm1025 | 27 monitor for microprocessor-based systems, providing measurement and limit 30 the processor core voltage. The ADM1025 can monitor a sixth power-supply
|
D | wm8350 | 18 monitor a range of system operating parameters, including the voltages
|
D | abx500 | 24 This abx500 is a common layer which can monitor all of the sensors, every
|
D | wm831x | 18 monitor a range of system operating parameters, including the voltages
|
D | sch5627 | 17 capabilities. They can monitor up to 5 voltages, 4 fans and 8 temperatures.
|
D | via686a | 35 The Via 686a southbridge has integrated hardware monitor functionality. 36 It also has an I2C bus, but this driver only supports the hardware monitor.
|
D | nct7904 | 17 The NCT7904D is a hardware monitor supporting up to 20 voltage sensors,
|
D | sch5636 | 24 The Fujitsu Theseus can monitor up to 5 voltages, 8 fans and 16
|
D | vexpress | 23 configuration and control. Theses microcontrollers can also monitor the
|
D | sis5595 | 53 The SiS5595 southbridge has integrated hardware monitor functions. It also 54 has an I2C bus, but this driver only supports the hardware monitor. For the
|
D | lm93 | 49 The LM93 hardware monitor has a two wire digital interface compatible with 60 for dynamic Vccp monitoring and PROCHOT. It is designed to monitor a dual 72 The LM93 can monitor two #PROCHOT signals. The results are found in the 110 The LM93 can monitor two #VRD_HOT signals. The results are found in the 254 The LM93 can monitor the logic level of four dedicated GPIO pins as well as the
|
D | ibmaem | 25 The v1 AEM interface has a simple set of features to monitor energy use. There
|
D | lm95234 | 22 that can very accurately monitor the temperature of two (LM95233)
|
D | pc87427 | 20 monitoring capabilities. It can monitor up to 18 voltages, 8 fans and
|
D | ltc2945 | 17 The LTC2945 is a rail-to-rail system monitor that measures current, voltage,
|
D | f71805f | 35 capabilities. It can monitor up to 9 voltages (counting its own power 57 need external resistors. An exception is in0, which is used to monitor
|
D | ltc2978 | 38 monitor. LTC2977 is a pin compatible replacement for LTC2978. LTC3880 is a dual
|
D | f71882fg | 68 capabilities. They can monitor up to 9 voltages, 4 fans and 3 temperature
|
D | adm9240 | 38 [From ADM9240] The ADM9240 is a complete system hardware monitor for
|
D | vt1211 | 46 programmed to either monitor a voltage or a temperature.
|
D | pc87360 | 122 (voltage level monitor) logical device, not the TMS (temperature
|
D | lm85 | 124 The SMSC EMC6D100 & EMC6D101 monitor external voltages, temperatures, and
|
/linux-4.1.27/tools/power/cpupower/ |
D | ToDo | 7 RAM from HW on Intel SandyBridge -> another monitor? 8 - Add another c1e debug idle monitor
|
/linux-4.1.27/tools/power/cpupower/po/ |
D | de.po | 72 #: utils/idle_monitor/cpupower-monitor.c:66 75 "cpupower monitor: [-h] [ [-t] | [-l] | [-m <mon1>,[<mon2>] ] ] [-i " 79 #: utils/idle_monitor/cpupower-monitor.c:69 82 "cpupower monitor: [-v] [-h] [ [-t] | [-l] | [-m <mon1>,[<mon2>] ] ] [-i " 86 #: utils/idle_monitor/cpupower-monitor.c:71 91 #: utils/idle_monitor/cpupower-monitor.c:73 96 #: utils/idle_monitor/cpupower-monitor.c:74 101 #: utils/idle_monitor/cpupower-monitor.c:75 106 #: utils/idle_monitor/cpupower-monitor.c:76 111 #: utils/idle_monitor/cpupower-monitor.c:77 [all …]
|
D | cs.po | 75 #: utils/idle_monitor/cpupower-monitor.c:66 78 "cpupower monitor: [-h] [ [-t] | [-l] | [-m <mon1>,[<mon2>] ] ] [-i " 82 #: utils/idle_monitor/cpupower-monitor.c:69 85 "cpupower monitor: [-v] [-h] [ [-t] | [-l] | [-m <mon1>,[<mon2>] ] ] [-i " 89 #: utils/idle_monitor/cpupower-monitor.c:71 94 #: utils/idle_monitor/cpupower-monitor.c:73 99 #: utils/idle_monitor/cpupower-monitor.c:74 104 #: utils/idle_monitor/cpupower-monitor.c:75 109 #: utils/idle_monitor/cpupower-monitor.c:76 114 #: utils/idle_monitor/cpupower-monitor.c:77 [all …]
|
D | it.po | 72 #: utils/idle_monitor/cpupower-monitor.c:66 75 "cpupower monitor: [-h] [ [-t] | [-l] | [-m <mon1>,[<mon2>] ] ] [-i " 79 #: utils/idle_monitor/cpupower-monitor.c:69 82 "cpupower monitor: [-v] [-h] [ [-t] | [-l] | [-m <mon1>,[<mon2>] ] ] [-i " 86 #: utils/idle_monitor/cpupower-monitor.c:71 91 #: utils/idle_monitor/cpupower-monitor.c:73 96 #: utils/idle_monitor/cpupower-monitor.c:74 101 #: utils/idle_monitor/cpupower-monitor.c:75 106 #: utils/idle_monitor/cpupower-monitor.c:76 111 #: utils/idle_monitor/cpupower-monitor.c:77 [all …]
|
D | fr.po | 72 #: utils/idle_monitor/cpupower-monitor.c:66 75 "cpupower monitor: [-h] [ [-t] | [-l] | [-m <mon1>,[<mon2>] ] ] [-i " 79 #: utils/idle_monitor/cpupower-monitor.c:69 82 "cpupower monitor: [-v] [-h] [ [-t] | [-l] | [-m <mon1>,[<mon2>] ] ] [-i " 86 #: utils/idle_monitor/cpupower-monitor.c:71 91 #: utils/idle_monitor/cpupower-monitor.c:73 96 #: utils/idle_monitor/cpupower-monitor.c:74 101 #: utils/idle_monitor/cpupower-monitor.c:75 106 #: utils/idle_monitor/cpupower-monitor.c:76 111 #: utils/idle_monitor/cpupower-monitor.c:77 [all …]
|
D | pt.po | 70 #: utils/idle_monitor/cpupower-monitor.c:66 73 "cpupower monitor: [-h] [ [-t] | [-l] | [-m <mon1>,[<mon2>] ] ] [-i " 77 #: utils/idle_monitor/cpupower-monitor.c:69 80 "cpupower monitor: [-v] [-h] [ [-t] | [-l] | [-m <mon1>,[<mon2>] ] ] [-i " 84 #: utils/idle_monitor/cpupower-monitor.c:71 89 #: utils/idle_monitor/cpupower-monitor.c:73 94 #: utils/idle_monitor/cpupower-monitor.c:74 99 #: utils/idle_monitor/cpupower-monitor.c:75 104 #: utils/idle_monitor/cpupower-monitor.c:76 109 #: utils/idle_monitor/cpupower-monitor.c:77 [all …]
|
/linux-4.1.27/Documentation/EDID/ |
D | HOWTO.txt | 8 - The graphics board does not recognize the monitor. 11 - The monitor sends no or bogus EDID data. 12 - A KVM sends its own EDID data instead of querying the connected monitor. 25 individual data for a specific misbehaving monitor, commented sources
|
/linux-4.1.27/Documentation/fb/ |
D | intel810.txt | 42 - Utilizes user-entered monitor specifications to automatically 95 monitor in kHz. If using a fixed frequency monitor, hsync1 must 99 Recommendation: check monitor manual for correct values 103 select the minimum and maximum Vertical Sync Frequency of the monitor 104 in Hz. You can also use this option to lock your monitor's refresh 108 Recommendation: check monitor manual for correct values 146 Useful if the BIOS turns off the VGA port when no monitor is attached. 147 The external VGA monitor can then be attached without rebooting.
|
D | udlfb.txt | 10 monitor with no CPU involvement until a pixel has to change. 60 of the monitor, and set the best common mode between the DisplayLink device 61 and the monitor's capabilities. 131 backup in case reading the actual EDID of the monitor 136 monitor (or last backup value written). This is 137 useful to get the EDID of the attached monitor,
|
D | sstfb.txt | 18 BTW, If you have only one monitor , and you don't feel like playing 41 # If you have only one monitor to play with, once you insmod the 43 plug the monitor to the "normal" video board in order to issue 55 (if you don't have a second monitor, you'll have to plug your monitor 85 vgapass=1 vgapass When enabled, the monitor will get the signal
|
D | matroxfb.txt | 216 (monitor) output. 267 If you know capabilities of your monitor, you can specify some (or all) of 290 your monitor, believe me...). 318 + DDC (monitor detection) is supported through dualhead driver 388 + secondary head always powerups in monitor mode. You have to use fbmatroxset
|
D | tridentfb.txt | 41 crt - assume monitor is present instead of fp
|
D | ep93xx-fb.txt | 6 embedded LCD displays. If you have a standard desktop monitor then you
|
D | framebuffer.txt | 158 A monitor draws an image on the screen by using an electron beam (3 electron 206 Since the monitor doesn't know when a new scanline starts, the graphics board
|
D | uvesafb.txt | 132 EDID-provided values and BIOS defaults. Refer to your monitor's specs to get
|
D | viafb.txt | 168 multi-head since SAMM support multi monitor at driver layers, thus fbcon
|
/linux-4.1.27/Documentation/arm/SA1100/ |
D | Itsy | 21 configuration parameters in the monitor as follows: 32 8-bit data, no parity, 1 stop bit(s), 115200.00 b/s. in the monitor, in the 34 not easily. The monitor parameters are easily changed, the params program
|
/linux-4.1.27/Documentation/arm/ |
D | swp_emulation | 23 transaction monitoring block called a global monitor to maintain update 24 atomicity. If your system does not implement a global monitor, this option can
|
/linux-4.1.27/Documentation/filesystems/ |
D | ceph.txt | 31 (with some minimal coordination from a cluster monitor), making the 73 You only need to specify a single monitor, as the client will get the 74 full list when it connects. (However, if the monitor you specify 76 off if the monitor is using the default. So if the monitor is at 93 address its connection to the monitor originates from.
|
D | proc.txt | 1395 The files in /proc/sys can be used to fine tune and monitor miscellaneous and
|
/linux-4.1.27/arch/arm/mach-omap2/ |
D | sleep34xx.S | 117 smc #1 @ call SMI monitor (smi #1) 449 smc #1 @ call SMI monitor (smi #1) 460 smc #1 @ call SMI monitor (smi #1) 475 smc #1 @ call SMI monitor (smi #1) 485 smc #0 @ Call SMI monitor (smieq) 491 smc #0 @ Call SMI monitor (smieq) 496 smc #0 @ Call SMI monitor (smieq)
|
/linux-4.1.27/drivers/video/fbdev/sis/ |
D | sis_main.c | 402 static bool sisfb_interpret_edid(struct sisfb_monitor *monitor, u8 *buffer) in sisfb_interpret_edid() argument 421 monitor->feature = buffer[0x18]; in sisfb_interpret_edid() 439 monitor->hmin = buffer[j + 7]; in sisfb_interpret_edid() 440 monitor->hmax = buffer[j + 8]; in sisfb_interpret_edid() 441 monitor->vmin = buffer[j + 5]; in sisfb_interpret_edid() 442 monitor->vmax = buffer[j + 6]; in sisfb_interpret_edid() 443 monitor->dclockmax = buffer[j + 9] * 10 * 1000; in sisfb_interpret_edid() 444 monitor->datavalid = true; in sisfb_interpret_edid() 451 if(!monitor->datavalid) { in sisfb_interpret_edid() 457 monitor->hmin = 65535; monitor->hmax = 0; in sisfb_interpret_edid() [all …]
|
/linux-4.1.27/arch/avr32/boards/merisc/ |
D | display.c | 38 .monitor = "TCG075VG2AD",
|
/linux-4.1.27/net/decnet/netfilter/ |
D | Kconfig | 14 unless you just want to monitor routing messages from other nodes.
|
/linux-4.1.27/Documentation/devicetree/bindings/arm/firmware/ |
D | tlm,trusted-foundations.txt | 4 Boards that use the Trusted Foundations secure monitor can signal its
|
/linux-4.1.27/drivers/s390/char/ |
D | Kconfig | 183 prompt "API for reading z/VM monitor service records" 186 Character device driver for reading z/VM monitor service records 190 prompt "API for writing z/VM monitor service records" 193 Character device driver for writing z/VM monitor service records
|
/linux-4.1.27/Documentation/watchdog/ |
D | pcwd-watchdog.txt | 9 the Revision C card allows you to monitor any IO Port to automatically 11 monitor hard drive status, or anything else you need.
|
/linux-4.1.27/Documentation/ABI/testing/ |
D | sysfs-class-power | 7 coloumb counter value inside the battery monitor chip. This 9 A userspace daemon can monitor the battery charging logic
|
D | sysfs-class-mei | 24 registers for BIOS and OS to monitor fw health.
|
/linux-4.1.27/Documentation/devicetree/bindings/arc/ |
D | pct.txt | 3 The ARC700 can be configured with a pipeline performance monitor for counting
|
/linux-4.1.27/drivers/net/ethernet/sfc/ |
D | falcon_boards.c | 716 .monitor = sfe4001_check_hw, 724 .monitor = sfe4002_check_hw, 732 .monitor = sfe4003_check_hw, 740 .monitor = sfn4112f_check_hw,
|
D | Kconfig | 30 hardware monitor device.
|
D | selftest.c | 577 if (efx->type->monitor != NULL) { in efx_wait_for_link() 579 efx->type->monitor(efx); in efx_wait_for_link()
|
D | siena.c | 919 .monitor = siena_monitor, 921 .monitor = NULL,
|
D | nic.h | 179 int (*monitor) (struct efx_nic *nic); member
|
D | falcon.c | 2061 rc = falcon_board(efx)->type->monitor(efx); in falcon_monitor() 2696 .monitor = falcon_monitor, 2797 .monitor = falcon_monitor,
|
D | net_driver.h | 1237 void (*monitor)(struct efx_nic *efx); member
|
D | efx.c | 1760 if (efx->type->monitor != NULL) in efx_start_all() 1917 BUG_ON(efx->type->monitor == NULL); in efx_monitor() 1924 efx->type->monitor(efx); in efx_monitor()
|
/linux-4.1.27/Documentation/devicetree/bindings/thermal/ |
D | thermal.txt | 297 used to monitor the zone 'cpu-thermal' using its sole sensor. A fan 315 requirements, and thus may have their own sensor to monitor or detect internal 415 monitor three sensors. The hardware has been designed so that sensors are 416 placed on different places in the DIE to monitor different temperature 418 other to monitor a DSP thermal zone. 424 monitor CPU thermal zone, <bandgap 1> is used to monitor GPU thermal 425 zone and <bandgap 2> is used to monitor DSP thermal zone. Each zone 594 sensors used to monitor different zones, one of them is composed by several sensors and
|
/linux-4.1.27/Documentation/devicetree/bindings/cpufreq/ |
D | cpufreq-exynos5440.txt | 14 - clock-latency: Clock monitor latency in microsecond.
|
/linux-4.1.27/drivers/staging/iio/ |
D | TODO | 20 - battery voltage monitor (power subsystem related device) 21 - die temperature monitor (thermal management)
|
/linux-4.1.27/drivers/platform/mips/ |
D | Kconfig | 11 extension and hardware monitor drivers. This option itself does
|
/linux-4.1.27/drivers/net/wireless/ |
D | zd1201.c | 323 if (zd->monitor) { in zd1201_usbrx() 675 if (zd->monitor) in zd1201_enable() 687 if (zd->monitor) { in zd1201_disable() 795 if (!zd->mac_enabled || zd->monitor) { in zd1201_hard_start_xmit() 949 short porttype, monitor = 0; in zd1201_set_mode() local 965 monitor = 1; in zd1201_set_mode() 989 if (zd->monitor && !monitor) { in zd1201_set_mode() 998 zd->monitor = monitor; in zd1201_set_mode() 1038 if (zd->monitor) in zd1201_get_mode()
|
D | zd1201.h | 49 int monitor; member
|
/linux-4.1.27/Documentation/devicetree/bindings/arm/ |
D | tegra.txt | 40 Tegra supports the Trusted Foundation secure monitor. See the
|
/linux-4.1.27/drivers/hid/usbhid/ |
D | Kconfig | 13 (UPS) and monitor control devices. 40 devices, like monitor controls and Uninterruptable Power Supplies.
|
/linux-4.1.27/drivers/video/fbdev/via/ |
D | via_aux_edid.c | 57 printk(KERN_DEBUG "EDID: %s %s\n", spec->manufacturer, spec->monitor); in query_edid()
|
/linux-4.1.27/drivers/isdn/hardware/mISDN/ |
D | mISDNipac.c | 326 if (isac->monitor) { in isac_mos_irq() 327 ret = isac->monitor(isac->dch.hw, MONITOR_RX_0, in isac_mos_irq() 344 if (isac->monitor) { in isac_mos_irq() 345 ret = isac->monitor(isac->dch.hw, MONITOR_RX_1, in isac_mos_irq() 365 if (isac->monitor) in isac_mos_irq() 366 ret = isac->monitor(isac->dch.hw, in isac_mos_irq() 376 if (isac->monitor) in isac_mos_irq() 377 ret = isac->monitor(isac->dch.hw, in isac_mos_irq() 398 if (isac->monitor) in isac_mos_irq() 399 ret = isac->monitor(isac->dch.hw, in isac_mos_irq() [all …]
|
D | ipac.h | 37 int (*monitor)(void *, u32, u8 *, int); member
|
/linux-4.1.27/include/linux/lockd/ |
D | xdr.h | 67 u32 monitor; member
|
/linux-4.1.27/drivers/devfreq/event/ |
D | Kconfig | 6 data from devfreq-event device is used to monitor the state of
|
/linux-4.1.27/arch/avr32/boards/atstk1000/ |
D | setup.c | 48 .monitor = "LTV350QV",
|
/linux-4.1.27/Documentation/networking/ |
D | bonding.txt | 239 The ARP monitor works by periodically checking the slave 312 Enabling validation causes the ARP monitor to examine the incoming 335 ARP monitor into considering the links as still up. Use of 336 validation can resolve this, as the ARP monitor will only consider 342 Enabling filtering causes the ARP monitor to only use incoming ARP 354 ARP monitor into considering the links as still up. Use of 363 in order for the ARP monitor to consider a slave as being up. 383 is only valid for the miimon link monitor. The downdelay 415 interferes with the ARP monitor). 427 monitor, devices which assert link up prior to being [all …]
|
D | ieee802154.txt | 87 NOTE: Currently the only monitor device type is supported - it's IEEE 802.15.4
|
D | can.txt | 758 RX_NO_AUTOTIMER: Prevent automatically starting the timeout monitor. 997 to setup, configure and monitor CAN network devices. The user can then
|
/linux-4.1.27/Documentation/devicetree/bindings/arm/tegra/ |
D | nvidia,tegra30-actmon.txt | 3 The activity monitor block collects statistics about the behaviour of other
|
/linux-4.1.27/net/ceph/ |
D | Kconfig | 37 If you say Y here, hostnames (e.g. monitor addresses) will
|
/linux-4.1.27/drivers/vme/bridges/ |
D | vme_ca91cx42.c | 1406 static int ca91cx42_lm_attach(struct vme_lm_resource *lm, int monitor, in ca91cx42_lm_attach() argument 1427 if (bridge->lm_callback[monitor] != NULL) { in ca91cx42_lm_attach() 1434 bridge->lm_callback[monitor] = callback; in ca91cx42_lm_attach() 1438 tmp |= CA91CX42_LINT_LM[monitor]; in ca91cx42_lm_attach() 1455 static int ca91cx42_lm_detach(struct vme_lm_resource *lm, int monitor) in ca91cx42_lm_detach() argument 1466 tmp &= ~CA91CX42_LINT_LM[monitor]; in ca91cx42_lm_detach() 1469 iowrite32(CA91CX42_LINT_LM[monitor], in ca91cx42_lm_detach() 1473 bridge->lm_callback[monitor] = NULL; in ca91cx42_lm_detach()
|
D | vme_tsi148.c | 2117 static int tsi148_lm_attach(struct vme_lm_resource *lm, int monitor, in tsi148_lm_attach() argument 2140 if (bridge->lm_callback[monitor] != NULL) { in tsi148_lm_attach() 2147 bridge->lm_callback[monitor] = callback; in tsi148_lm_attach() 2151 tmp |= TSI148_LCSR_INTEN_LMEN[monitor]; in tsi148_lm_attach() 2155 tmp |= TSI148_LCSR_INTEO_LMEO[monitor]; in tsi148_lm_attach() 2172 static int tsi148_lm_detach(struct vme_lm_resource *lm, int monitor) in tsi148_lm_detach() argument 2183 lm_en &= ~TSI148_LCSR_INTEN_LMEN[monitor]; in tsi148_lm_detach() 2187 tmp &= ~TSI148_LCSR_INTEO_LMEO[monitor]; in tsi148_lm_detach() 2190 iowrite32be(TSI148_LCSR_INTC_LMC[monitor], in tsi148_lm_detach() 2194 bridge->lm_callback[monitor] = NULL; in tsi148_lm_detach()
|
/linux-4.1.27/drivers/net/wireless/ath/wil6210/ |
D | Kconfig | 25 For ISR debug, use W1C (say n); is allows to monitor ISR
|
/linux-4.1.27/drivers/video/console/ |
D | Kconfig | 85 monitor. 95 monitor.
|
/linux-4.1.27/arch/arm/kvm/ |
D | interrupts.S | 153 clrex @ Clear exclusive monitor 210 clrex @ Clear exclusive monitor
|
/linux-4.1.27/arch/avr32/boards/hammerhead/ |
D | setup.c | 70 .monitor = "HDA350T-LV",
|
/linux-4.1.27/drivers/media/dvb-frontends/ |
D | mt312.c | 180 u16 monitor; in mt312_get_symbol_rate() local 197 monitor = (buf[0] << 8) | buf[1]; in mt312_get_symbol_rate() 200 mt312_div(monitor * 15625, 4)); in mt312_get_symbol_rate()
|
/linux-4.1.27/Documentation/ |
D | vme_api.txt | 341 monitor. 365 are provided to configure the location and mode of the location monitor: 378 location monitor location. Each location monitor can monitor a number of
|
D | gdb-kernel-debugging.txt | 42 - during runtime by issuing "gdbserver" from the QEMU monitor
|
D | svga.txt | 90 strange noises will be heard from inside the monitor and so on and then, really 92 `ghost modes'). If you are afraid this could damage your monitor, don't use this
|
D | rtc.txt | 66 A user process can monitor these interrupts by doing a read(2) or a
|
D | IPMI.txt | 9 standard for controlling intelligent devices that monitor a system. 11 ability to monitor the sensors and be informed when the sensor's
|
D | devices.txt | 383 165 = /dev/vmmon VMware virtual machine monitor 965 255 = /dev/isdninfo ISDN monitor interface 2320 2 = /dev/etherd/raw Raw AoE packet monitor 2713 5 = /dev/vx/taskmon Volume tasks monitor daemon 3271 monitor. Virtual consoles are named /dev/tty#, with numbering
|
D | md.txt | 489 a text file that can be used to monitor and control the rebuild
|
/linux-4.1.27/drivers/staging/i2o/ |
D | Kconfig | 93 by the SCSI OSM driver, for example to monitor the disks. 105 But you could use the SCSI OSM driver to monitor the single disks.
|
/linux-4.1.27/arch/avr32/boards/mimc200/ |
D | setup.c | 64 .monitor = "PT0434827-A401",
|
/linux-4.1.27/drivers/platform/x86/ |
D | intel_ips.c | 299 struct task_struct *monitor; member 1650 ips->monitor = kthread_run(ips_monitor, ips, "ips-monitor"); in ips_probe() 1651 if (IS_ERR(ips->monitor)) { in ips_probe() 1714 if (ips->monitor) in ips_remove() 1715 kthread_stop(ips->monitor); in ips_remove()
|
/linux-4.1.27/tools/perf/Documentation/ |
D | perf-stat.txt | 100 monitor only in the container (cgroup) called "name". This option is available only 105 an empty cgroup (monitor all the time) using, e.g., -G foo,,bar. Cgroups must have
|
D | perf-record.txt | 172 the thread executes on the designated CPUs. Default is to monitor all CPUs. 182 monitor only in the container (cgroup) called "name". This option is available only 187 an empty cgroup (monitor all the time) using, e.g., -G foo,,bar. Cgroups must have
|
D | perf-trace.txt | 80 the thread executes on the designated CPUs. Default is to monitor all CPUs.
|
D | perf-top.txt | 32 Default is to monitor all CPUS.
|
/linux-4.1.27/arch/s390/ |
D | Kconfig | 698 allows an external monitor to balance memory of many systems. 716 monitor records. The monitor records are updated at certain time 734 APPLDATA monitor record, i.e. enables or disables monitoring this record 751 APPLDATA monitor record, i.e. enables or disables monitoring this record 767 APPLDATA monitor record, i.e. enables or disables monitoring this record
|
/linux-4.1.27/drivers/power/ |
D | Kconfig | 76 Say Y here to enable battery monitor for Marvell 88PM860x chip. 100 The battery monitor chip is used in many batteries/devices 144 Choose this option if you want to monitor battery status on 344 system. The charger-manager also can monitor charging status in
|
/linux-4.1.27/Documentation/w1/masters/ |
D | omap-hdq | 21 monitor (gas gauge) integrated circuits.
|
/linux-4.1.27/fs/lockd/ |
D | svc4proc.c | 36 || (argp->monitor && nsm_monitor(host) < 0)) in nlm4svc_retrieve_args() 386 argp->monitor = 0; /* just clean the monitor flag */ in nlm4svc_proc_nm_lock()
|
D | svcproc.c | 65 || (argp->monitor && nsm_monitor(host) < 0)) in nlmsvc_retrieve_args() 429 argp->monitor = 0; /* just clean the monitor flag */ in nlmsvc_proc_nm_lock()
|
D | xdr4.c | 221 argp->monitor = 1; /* monitor client by default */ in nlm4svc_decode_lockargs()
|
D | xdr.c | 224 argp->monitor = 1; /* monitor client by default */ in nlmsvc_decode_lockargs()
|
/linux-4.1.27/arch/arm/kernel/ |
D | entry-header.S | 298 strex r2, r1, [sp, #S_LR] @ clear the exclusive monitor 347 strex r1, r2, [sp] @ clear the exclusive monitor
|
/linux-4.1.27/arch/avr32/boards/favr-32/ |
D | setup.c | 123 .monitor = "LB104V03",
|
/linux-4.1.27/Documentation/ABI/stable/ |
D | sysfs-firmware-opal-elog | 23 Typically, a user space daemon will monitor for new
|
/linux-4.1.27/Documentation/devicetree/bindings/soc/ti/ |
D | keystone-navigator-qmss.txt | 67 channels can be configured to monitor 32 contiguous 83 monitor upto 32 queues starting at the base queue #.
|
/linux-4.1.27/drivers/vme/ |
D | vme.c | 1234 int vme_lm_attach(struct vme_resource *resource, int monitor, in vme_lm_attach() argument 1252 return bridge->lm_attach(lm, monitor, callback); in vme_lm_attach() 1256 int vme_lm_detach(struct vme_resource *resource, int monitor) in vme_lm_detach() argument 1273 return bridge->lm_detach(lm, monitor); in vme_lm_detach()
|
/linux-4.1.27/Documentation/ide/ |
D | ChangeLog.ide-floppy.1996-2002 | 40 * monitor the dsc bit in the status register.
|
/linux-4.1.27/Documentation/networking/mac80211_hwsim/ |
D | README | 41 mac80211. This interface can be used to monitor all transmitted frames
|
/linux-4.1.27/fs/proc/ |
D | Kconfig | 70 Various /proc files exist to monitor process memory utilization:
|
/linux-4.1.27/Documentation/sound/alsa/soc/ |
D | jack.txt | 51 Actual jack detection is done by code which is able to monitor some
|
/linux-4.1.27/arch/arm/boot/dts/ |
D | omap3-igep0020-common.dtsi | 197 * Display monitor features are burnt in the EEPROM
|
D | omap4-panda-common.dtsi | 411 * Display monitor features are burnt in their EEPROM as EDID data.
|
D | atlas6.dtsi | 104 memc-monitor {
|
D | prima2.dtsi | 115 memc-monitor {
|
/linux-4.1.27/arch/um/ |
D | Kconfig.net | 164 UML act as a network monitor for the host. You must have libcap 171 If you intend to use UML as a network monitor for the host, say
|
/linux-4.1.27/arch/parisc/kernel/ |
D | perf_asm.S | 57 pmenb ; enable performance monitor 83 pmdis ; disable performance monitor
|
/linux-4.1.27/Documentation/parisc/ |
D | registers | 66 F (performance monitor) 0
|
/linux-4.1.27/Documentation/m68k/ |
D | kernel-options.txt | 504 This describes the capabilities of a multisync monitor. Don't use it 505 with a fixed-frequency monitor! For now, only the Falcon frame buffer 509 your monitor can work with, in Hz. <hmin> and <hmax> are the same for 754 This describes the capabilities of a multisync monitor. For now, only 758 your monitor can work with, in Hz. <hmin> and <hmax> are the same for 761 The defaults are 50;90;15;38 (Generic Amiga multisync monitor).
|
D | README.buddha | 195 multisync monitor, or a graphics card, and your internal
|
/linux-4.1.27/arch/powerpc/platforms/ps3/ |
D | Kconfig | 154 This support is required to use the logical performance monitor
|
/linux-4.1.27/drivers/net/wireless/ath/ath10k/ |
D | core.h | 596 bool monitor; member
|
D | mac.c | 775 should_start = ar->monitor || in ath10k_monitor_recalc() 2763 ar->monitor = false; in ath10k_halt() 3174 ar->monitor = conf->flags & IEEE80211_CONF_MONITOR; in ath10k_config()
|
/linux-4.1.27/Documentation/input/ |
D | input.txt | 109 However, USB uses HID also for monitor controls, speaker controls, UPSs, 112 The monitor and speaker controls should be easy to add to the hid/input
|
D | atarikbd.txt | 416 Sets the ikbd to do nothing but monitor the serial command line, maintain the 417 time-of-day clock, and monitor the joystick. The rate sets the interval 429 Set the ikbd to do nothing but monitor the serial command line, maintain the 430 time-of-day clock, and monitor the fire button on Joystick 1. The fire button
|
/linux-4.1.27/Documentation/power/regulator/ |
D | overview.txt | 168 userspace via sysfs. This could be used to help monitor device power
|
/linux-4.1.27/drivers/input/ |
D | Kconfig | 17 Say N here if you have a headless (no monitor, no keyboard) system.
|
/linux-4.1.27/drivers/gpu/drm/ |
D | Kconfig | 50 monitor are unable to provide appropriate EDID data. Since this
|
/linux-4.1.27/drivers/usb/host/ |
D | u132-hcd.c | 202 struct delayed_work monitor; member 409 if (queue_delayed_work(workqueue, &u132->monitor, delta)) in u132_monitor_queue_work() 415 if (!queue_delayed_work(workqueue, &u132->monitor, delta)) in u132_monitor_requeue_work() 421 if (cancel_delayed_work(&u132->monitor)) in u132_monitor_cancel_work() 480 struct u132 *u132 = container_of(work, struct u132, monitor.work); in u132_hcd_monitor_work() 3053 INIT_DELAYED_WORK(&u132->monitor, u132_hcd_monitor_work); in u132_initialise()
|
/linux-4.1.27/drivers/atm/ |
D | fore200e.c | 2436 struct cp_monitor __iomem * monitor = fore200e->cp_monitor; in fore200e_monitor_putc() local 2441 fore200e->bus->write(((u32) c) | FORE200E_CP_MONITOR_UART_AVAIL, &monitor->soft_uart.send); in fore200e_monitor_putc() 2447 struct cp_monitor __iomem * monitor = fore200e->cp_monitor; in fore200e_monitor_getc() local 2453 c = (int) fore200e->bus->read(&monitor->soft_uart.recv); in fore200e_monitor_getc() 2457 fore200e->bus->write(FORE200E_CP_MONITOR_UART_FREE, &monitor->soft_uart.recv); in fore200e_monitor_getc()
|
/linux-4.1.27/Documentation/cgroups/ |
D | unified-hierarchy.txt | 276 which can be used to monitor whether the cgroup's subhierarchy has 284 in the subhierarchy and monitor events that it's interested in from 373 lead to gradual performance degradation. The user can monitor this
|
D | memory.txt | 776 The pressure level notifications can be used to monitor the memory
|
D | cpusets.txt | 265 to monitor a cpuset for signs of memory pressure. It's up to the
|
/linux-4.1.27/Documentation/dvb/ |
D | faq.txt | 97 DVB sniffer program to monitor, analyze, debug, dump
|
D | avermedia.txt | 49 displayed on the video monitor screen. Some Analogue TV cards
|
/linux-4.1.27/Documentation/laptops/ |
D | sonypi.txt | 127 external monitor on/off. There is no workaround yet, since this
|
D | asus-laptop.txt | 59 "acpi_genl monitor" (part of the acpica project).
|
/linux-4.1.27/Documentation/filesystems/caching/ |
D | operations.txt | 172 operation with FSCACHE_OP_MYTHREAD, then it should monitor
|
D | cachefiles.txt | 244 The daemon uses dnotify to monitor the graveyard directory, and will delete
|
/linux-4.1.27/Documentation/device-mapper/ |
D | snapshot.txt | 40 useless and be disabled, returning errors. So it is important to monitor
|
/linux-4.1.27/Documentation/sound/alsa/ |
D | README.maya44 | 26 - analogue monitor a.k.a bypass
|
/linux-4.1.27/arch/ia64/ |
D | Kconfig | 490 bool "Performance monitor support" 492 Selects whether support for the IA-64 performance monitor hardware
|
/linux-4.1.27/drivers/usb/storage/ |
D | Kconfig | 181 to use tools to tune and monitor your drive (like hdparm or smartctl).
|
/linux-4.1.27/drivers/video/fbdev/core/ |
D | fbmon.c | 972 copy_string(block, specs->monitor); in fb_edid_to_monspecs() 973 DPRINTK(" Monitor Name: %s\n", specs->monitor); in fb_edid_to_monspecs()
|
/linux-4.1.27/Documentation/isdn/ |
D | README.x25 | 181 used to monitor X.25 packets received by the network interfaces.
|
D | README.HiSax | 266 programs and for identification when using a line monitor 394 0x0200 ISAC monitor debug
|
/linux-4.1.27/include/linux/ |
D | fb.h | 66 __u8 monitor[14]; /* Monitor String */ member
|
/linux-4.1.27/Documentation/power/ |
D | charger-manager.txt | 30 we may need to monitor the battery health by looking at the ambient or
|
/linux-4.1.27/Documentation/hid/ |
D | hiddev.txt | 9 supplies) and monitor control on higher end monitors.
|
/linux-4.1.27/drivers/video/fbdev/ |
D | fsl-diu-fb.c | 1990 module_param_named(monitor, monitor_string, charp, 0); 1991 MODULE_PARM_DESC(monitor, "Specify the monitor port "
|
D | Kconfig | 1140 monitor is recommended, but can still work with non-compliant ones. 1265 The driver starts in monitor mode. You must use the matroxset tool 1290 You can say Y or M here if you want to experiment with monitor 1315 The driver starts in monitor mode and you must use the matroxset
|
/linux-4.1.27/arch/arm64/ |
D | Kconfig | 641 monitor to maintain update atomicity. If your system does not 642 implement a global monitor, this option can cause programs that
|
/linux-4.1.27/Documentation/vm/ |
D | transhuge.txt | 197 monitor how successfully the system is providing huge pages for use. 229 monitor this overhead.
|
/linux-4.1.27/Documentation/arm64/ |
D | booting.txt | 17 is passed to the Linux kernel. This may include secure monitor and
|
/linux-4.1.27/Documentation/devicetree/bindings/powerpc/fsl/ |
D | dcsr.txt | 75 monitor interrupt signal based on either counter overflow or value
|
/linux-4.1.27/arch/powerpc/ |
D | Kconfig.debug | 77 Include in-kernel hooks for the xmon kernel monitor/debugger.
|
/linux-4.1.27/sound/aoa/codecs/ |
D | tas.c | 384 MIXER_CONTROL(monitor, "Monitor", 2);
|
/linux-4.1.27/Documentation/sysctl/ |
D | fs.txt | 12 The files in this directory can be used to tune and monitor
|
D | kernel.txt | 12 The files in this directory can be used to tune and monitor 602 0: disable the mechanism. Do not monitor or correct perf's
|
/linux-4.1.27/Documentation/thermal/ |
D | intel_powerclamp.txt | 90 kidle_inject/cpu. During idle injection, it runs monitor/mwait idle
|
/linux-4.1.27/Documentation/devicetree/bindings/crypto/ |
D | fsl-sec4.txt | 188 calculated, these addresses are checked by HW to monitor any
|
/linux-4.1.27/drivers/mtd/ |
D | Kconfig | 29 RedBoot is a ROM monitor and bootloader which deals with multiple
|
/linux-4.1.27/tools/testing/ktest/ |
D | ktest.pl | 1923 sub monitor { subroutine 2199 return monitor;
|
/linux-4.1.27/drivers/hwmon/ |
D | Kconfig | 10 Hardware monitoring devices let you monitor the hardware health 1105 interpretation. The driver can also monitor the temperature and 1437 voltage / current / power monitor I2C interface. 1447 INA230, and INA231 power monitor chips.
|
/linux-4.1.27/arch/arm/mm/ |
D | Kconfig | 692 monitor to maintain update atomicity. If your system does not 693 implement a global monitor, this option can cause programs that
|
/linux-4.1.27/Documentation/scsi/ |
D | arcmsr_spec.txt | 235 ** GUI_GET_HW_MONITOR : Get HW monitor data
|
/linux-4.1.27/drivers/watchdog/ |
D | Kconfig | 24 also monitor NFS connections and can reboot the machine when the process 1508 time. The card can also monitor the internal temperature of the PC. 1546 time. The card can also monitor the internal temperature of the PC.
|
/linux-4.1.27/drivers/misc/ |
D | Kconfig | 412 monitor, freeing up the underlying machine pages so they can
|
/linux-4.1.27/drivers/tty/ |
D | Kconfig | 36 of your keyboard and monitor. Therefore, only people configuring an
|
/linux-4.1.27/drivers/hid/ |
D | Kconfig | 44 devices, like monitor controls and Uninterruptable Power Supplies.
|
/linux-4.1.27/Documentation/spi/ |
D | spi-summary | 154 or monitor temperature and voltage levels during industrial processing.
|
/linux-4.1.27/arch/x86/ |
D | Kconfig | 962 the thermal monitor. 1486 during events such as suspend/resume or monitor cable 2194 do with your VESA-compliant power-saving monitor. Further, this
|
/linux-4.1.27/Documentation/video4linux/ |
D | vivid.txt | 599 then the width and height of the square on the monitor should be
|
/linux-4.1.27/lib/ |
D | Kconfig.debug | 1654 With remote DMA, you can monitor the printk buffer remotely using
|
/linux-4.1.27/arch/x86/kvm/ |
D | emulate.c | 3774 DI(SrcNone | Priv, monitor),
|
/linux-4.1.27/ |
D | CREDITS | 2241 D: Original dual-monitor patches
|