Home
last modified time | relevance | path

Searched refs:monitor (Results 1 – 200 of 209) sorted by relevance

12

/linux-4.4.14/fs/cachefiles/
Drdwr.c27 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 …]
Dinternal.h97 wait_queue_t monitor; /* link into monitored waitqueue */ member
/linux-4.4.14/arch/arm/firmware/
DKconfig12 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.4.14/drivers/w1/slaves/
DKconfig82 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.4.14/Documentation/s390/
Dmonreader.txt21 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 …]
D00-INDEX20 - information on accessing the z/VM monitor stream from Linux.
/linux-4.4.14/tools/perf/ui/gtk/
Dbrowser.c21 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.4.14/drivers/net/wireless/ipw2x00/
Dlibipw_module.c130 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()
DKconfig44 Enables promiscuous/monitor mode support for the ipw2100 driver.
106 Enables promiscuous/monitor mode support for the ipw2200 driver.
Dlibipw.h949 void free_libipw(struct net_device *dev, int monitor);
950 struct net_device *alloc_libipw(int sizeof_priv, int monitor);
/linux-4.4.14/arch/avr32/boards/atngw100/
Devklcd10x.c51 .monitor = "TCG057VGLAD",
89 .monitor = "TCG057QVLAD",
127 .monitor = "PH320240T",
Dmrmt.c77 .monitor = "LQ043T3DX02",
120 .monitor = "KWH043GM08",
/linux-4.4.14/Documentation/hwmon/
Dina2xx40 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
Dmax663918 temperature monitor with dual PWM fan speed controller. It can monitor its own
Duserspace-tools4 Most mainboards have sensor chips to monitor system health (like temperatures,
38 hardware-monitor
Dlm9524521 Management Bus (SMBus) interface and TruTherm technology that can monitor
23 The chips can be used to very accurately monitor the temperature of
Dmax1606534 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%)
Ducd900028 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
Dadm102527 monitor for microprocessor-based systems, providing measurement and limit
30 the processor core voltage. The ADM1025 can monitor a sixth power-supply
Dwm835018 monitor a range of system operating parameters, including the voltages
Dsch562717 capabilities. They can monitor up to 5 voltages, 4 fans and 8 temperatures.
Dwm831x18 monitor a range of system operating parameters, including the voltages
Dabx50024 This abx500 is a common layer which can monitor all of the sensors, every
Dmax3179024 Tachometer inputs monitor fan tachometer logic outputs for precise (+/-1%)
Dvia686a35 The Via 686a southbridge has integrated hardware monitor functionality.
36 It also has an I2C bus, but this driver only supports the hardware monitor.
Dnct790417 The NCT7904D is a hardware monitor supporting up to 20 voltage sensors,
Dsch563624 The Fujitsu Theseus can monitor up to 5 voltages, 8 fans and 16
Dvexpress23 configuration and control. Theses microcontrollers can also monitor the
Dsis559553 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
Dlm9349 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
Dibmaem25 The v1 AEM interface has a simple set of features to monitor energy use. There
Dlm9523422 that can very accurately monitor the temperature of two (LM95233)
Dpc8742720 monitoring capabilities. It can monitor up to 18 voltages, 8 fans and
Dltc294517 The LTC2945 is a rail-to-rail system monitor that measures current, voltage,
Df71805f35 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
Df71882fg68 capabilities. They can monitor up to 9 voltages, 4 fans and 3 temperature
Dltc297866 LTC2978 is an octal power supply monitor.
Dadm924038 [From ADM9240] The ADM9240 is a complete system hardware monitor for
Dpc87360122 (voltage level monitor) logical device, not the TMS (temperature
Dvt121146 programmed to either monitor a voltage or a temperature.
Dlm85124 The SMSC EMC6D100 & EMC6D101 monitor external voltages, temperatures, and
/linux-4.4.14/tools/power/cpupower/
DToDo7 RAM from HW on Intel SandyBridge -> another monitor?
8 - Add another c1e debug idle monitor
/linux-4.4.14/tools/power/cpupower/po/
Dde.po72 #: 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 …]
Dit.po72 #: 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 …]
Dcs.po75 #: 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 …]
Dfr.po72 #: 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 …]
Dpt.po70 #: 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.4.14/Documentation/EDID/
DHOWTO.txt8 - 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.4.14/Documentation/fb/
Dintel810.txt42 - 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.
Dudlfb.txt10 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,
Dsstfb.txt18 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
Dmatroxfb.txt216 (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
Dtridentfb.txt41 crt - assume monitor is present instead of fp
Dep93xx-fb.txt6 embedded LCD displays. If you have a standard desktop monitor then you
Dframebuffer.txt158 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
Duvesafb.txt132 EDID-provided values and BIOS defaults. Refer to your monitor's specs to get
Dviafb.txt168 multi-head since SAMM support multi monitor at driver layers, thus fbcon
/linux-4.4.14/drivers/gpu/drm/nouveau/nvkm/subdev/i2c/
Daux.c84 nvkm_i2c_aux_monitor(struct nvkm_i2c_aux *aux, bool monitor) in nvkm_i2c_aux_monitor() argument
87 AUX_TRACE(aux, "monitor: %s", monitor ? "yes" : "no"); in nvkm_i2c_aux_monitor()
88 if (monitor) in nvkm_i2c_aux_monitor()
/linux-4.4.14/Documentation/arm/SA1100/
DItsy21 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.4.14/Documentation/arm/
Dswp_emulation23 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.4.14/Documentation/filesystems/
Dceph.txt31 (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.
/linux-4.4.14/arch/arm/mach-omap2/
Dsleep34xx.S117 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.4.14/drivers/video/fbdev/sis/
Dsis_main.c399 static bool sisfb_interpret_edid(struct sisfb_monitor *monitor, u8 *buffer) in sisfb_interpret_edid() argument
418 monitor->feature = buffer[0x18]; in sisfb_interpret_edid()
436 monitor->hmin = buffer[j + 7]; in sisfb_interpret_edid()
437 monitor->hmax = buffer[j + 8]; in sisfb_interpret_edid()
438 monitor->vmin = buffer[j + 5]; in sisfb_interpret_edid()
439 monitor->vmax = buffer[j + 6]; in sisfb_interpret_edid()
440 monitor->dclockmax = buffer[j + 9] * 10 * 1000; in sisfb_interpret_edid()
441 monitor->datavalid = true; in sisfb_interpret_edid()
448 if(!monitor->datavalid) { in sisfb_interpret_edid()
454 monitor->hmin = 65535; monitor->hmax = 0; in sisfb_interpret_edid()
[all …]
/linux-4.4.14/drivers/perf/
DKconfig5 menu "Performance monitor support"
/linux-4.4.14/arch/avr32/boards/merisc/
Ddisplay.c38 .monitor = "TCG075VG2AD",
/linux-4.4.14/Documentation/devicetree/bindings/arc/
Darchs-pct.txt3 The ARC HS can be configured with a pipeline performance monitor for counting
Dpct.txt3 The ARC700 can be configured with a pipeline performance monitor for counting
/linux-4.4.14/net/decnet/netfilter/
DKconfig14 unless you just want to monitor routing messages from other nodes.
/linux-4.4.14/Documentation/devicetree/bindings/arm/firmware/
Dtlm,trusted-foundations.txt4 Boards that use the Trusted Foundations secure monitor can signal its
/linux-4.4.14/drivers/s390/char/
DKconfig183 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.4.14/Documentation/watchdog/
Dpcwd-watchdog.txt9 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.4.14/drivers/net/ethernet/sfc/
Dfalcon_boards.c716 .monitor = sfe4001_check_hw,
724 .monitor = sfe4002_check_hw,
732 .monitor = sfe4003_check_hw,
740 .monitor = sfn4112f_check_hw,
DKconfig30 hardware monitor device.
Dselftest.c586 if (efx->type->monitor != NULL) { in efx_wait_for_link()
588 efx->type->monitor(efx); in efx_wait_for_link()
Dsiena.c930 .monitor = siena_monitor,
932 .monitor = NULL,
Dnic.h179 int (*monitor) (struct efx_nic *nic); member
Dfalcon.c2074 rc = falcon_board(efx)->type->monitor(efx); in falcon_monitor()
2712 .monitor = falcon_monitor,
2810 .monitor = falcon_monitor,
Dnet_driver.h1229 void (*monitor)(struct efx_nic *efx); member
Defx.c1847 if (efx->type->monitor != NULL) in efx_start_all()
2007 BUG_ON(efx->type->monitor == NULL); in efx_monitor()
2014 efx->type->monitor(efx); in efx_monitor()
/linux-4.4.14/Documentation/devicetree/bindings/thermal/
Dthermal.txt305 used to monitor the zone 'cpu-thermal' using its sole sensor. A fan
323 requirements, and thus may have their own sensor to monitor or detect internal
423 monitor three sensors. The hardware has been designed so that sensors are
424 placed on different places in the DIE to monitor different temperature
426 other to monitor a DSP thermal zone.
432 monitor CPU thermal zone, <bandgap 1> is used to monitor GPU thermal
433 zone and <bandgap 2> is used to monitor DSP thermal zone. Each zone
604 sensors used to monitor different zones, one of them is composed by several sensors and
/linux-4.4.14/Documentation/devicetree/bindings/cpufreq/
Dcpufreq-exynos5440.txt14 - clock-latency: Clock monitor latency in microsecond.
/linux-4.4.14/drivers/staging/iio/
DTODO20 - battery voltage monitor (power subsystem related device)
21 - die temperature monitor (thermal management)
/linux-4.4.14/drivers/platform/mips/
DKconfig11 extension and hardware monitor drivers. This option itself does
/linux-4.4.14/drivers/net/wireless/
Dzd1201.c323 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()
Dzd1201.h49 int monitor; member
/linux-4.4.14/Documentation/devicetree/bindings/arm/
Dtegra.txt40 Tegra supports the Trusted Foundation secure monitor. See the
/linux-4.4.14/drivers/hid/usbhid/
DKconfig13 (UPS) and monitor control devices.
40 devices, like monitor controls and Uninterruptable Power Supplies.
/linux-4.4.14/drivers/video/fbdev/via/
Dvia_aux_edid.c57 printk(KERN_DEBUG "EDID: %s %s\n", spec->manufacturer, spec->monitor); in query_edid()
/linux-4.4.14/drivers/isdn/hardware/mISDN/
DmISDNipac.c326 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 …]
Dipac.h37 int (*monitor)(void *, u32, u8 *, int); member
/linux-4.4.14/include/linux/lockd/
Dxdr.h67 u32 monitor; member
/linux-4.4.14/Documentation/arm/keystone/
Dknav-qmss.txt31 The QMSS PDSP firmware support accumulator channel that can monitor a single
34 accumulator channels defined in DTS (example in DT documentation) to monitor
/linux-4.4.14/Documentation/ABI/testing/
Dsysfs-class-mei24 registers for BIOS and OS to monitor fw health.
Dsysfs-class-power7 coloumb counter value inside the battery monitor chip. This
9 A userspace daemon can monitor the battery charging logic
/linux-4.4.14/drivers/devfreq/event/
DKconfig6 data from devfreq-event device is used to monitor the state of
/linux-4.4.14/arch/avr32/boards/atstk1000/
Dsetup.c48 .monitor = "LTV350QV",
/linux-4.4.14/Documentation/networking/
Dbonding.txt276 The ARP monitor works by periodically checking the slave
349 Enabling validation causes the ARP monitor to examine the incoming
372 ARP monitor into considering the links as still up. Use of
373 validation can resolve this, as the ARP monitor will only consider
379 Enabling filtering causes the ARP monitor to only use incoming ARP
391 ARP monitor into considering the links as still up. Use of
400 in order for the ARP monitor to consider a slave as being up.
420 is only valid for the miimon link monitor. The downdelay
452 interferes with the ARP monitor).
464 monitor, devices which assert link up prior to being
[all …]
Dieee802154.txt76 NOTE: Currently the only monitor device type is supported - it's IEEE 802.15.4
Dswitchdev.txt248 garbage collection timer to monitor FBD entries. Expired entries will be
372 The driver can monitor for updates to arp_tbl using the netevent notifier
Dcan.txt761 RX_NO_AUTOTIMER: Prevent automatically starting the timeout monitor.
1000 to setup, configure and monitor CAN network devices. The user can then
/linux-4.4.14/net/ceph/
DKconfig37 If you say Y here, hostnames (e.g. monitor addresses) will
/linux-4.4.14/Documentation/devicetree/bindings/arm/tegra/
Dnvidia,tegra30-actmon.txt3 The activity monitor block collects statistics about the behaviour of other
/linux-4.4.14/drivers/vme/bridges/
Dvme_ca91cx42.c1417 static int ca91cx42_lm_attach(struct vme_lm_resource *lm, int monitor, in ca91cx42_lm_attach() argument
1438 if (bridge->lm_callback[monitor] != NULL) { in ca91cx42_lm_attach()
1445 bridge->lm_callback[monitor] = callback; in ca91cx42_lm_attach()
1449 tmp |= CA91CX42_LINT_LM[monitor]; in ca91cx42_lm_attach()
1466 static int ca91cx42_lm_detach(struct vme_lm_resource *lm, int monitor) in ca91cx42_lm_detach() argument
1477 tmp &= ~CA91CX42_LINT_LM[monitor]; in ca91cx42_lm_detach()
1480 iowrite32(CA91CX42_LINT_LM[monitor], in ca91cx42_lm_detach()
1484 bridge->lm_callback[monitor] = NULL; in ca91cx42_lm_detach()
Dvme_tsi148.c2053 static int tsi148_lm_attach(struct vme_lm_resource *lm, int monitor, in tsi148_lm_attach() argument
2076 if (bridge->lm_callback[monitor] != NULL) { in tsi148_lm_attach()
2083 bridge->lm_callback[monitor] = callback; in tsi148_lm_attach()
2087 tmp |= TSI148_LCSR_INTEN_LMEN[monitor]; in tsi148_lm_attach()
2091 tmp |= TSI148_LCSR_INTEO_LMEO[monitor]; in tsi148_lm_attach()
2108 static int tsi148_lm_detach(struct vme_lm_resource *lm, int monitor) in tsi148_lm_detach() argument
2119 lm_en &= ~TSI148_LCSR_INTEN_LMEN[monitor]; in tsi148_lm_detach()
2123 tmp &= ~TSI148_LCSR_INTEO_LMEO[monitor]; in tsi148_lm_detach()
2126 iowrite32be(TSI148_LCSR_INTC_LMC[monitor], in tsi148_lm_detach()
2130 bridge->lm_callback[monitor] = NULL; in tsi148_lm_detach()
/linux-4.4.14/drivers/net/wireless/ath/wil6210/
DKconfig26 For ISR debug, use W1C (say n); is allows to monitor ISR
/linux-4.4.14/drivers/video/console/
DKconfig85 monitor.
95 monitor.
/linux-4.4.14/arch/arm/kvm/
Dinterrupts.S153 clrex @ Clear exclusive monitor
210 clrex @ Clear exclusive monitor
/linux-4.4.14/arch/avr32/boards/hammerhead/
Dsetup.c70 .monitor = "HDA350T-LV",
/linux-4.4.14/drivers/media/dvb-frontends/
Dmt312.c180 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.4.14/Documentation/
Dvme_api.txt347 monitor.
371 are provided to configure the location and mode of the location monitor:
384 location monitor location. Each location monitor can monitor a number of
Dgdb-kernel-debugging.txt42 - during runtime by issuing "gdbserver" from the QEMU monitor
Dsvga.txt90 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
Drtc.txt66 A user process can monitor these interrupts by doing a read(2) or a
DIPMI.txt9 standard for controlling intelligent devices that monitor a system.
11 ability to monitor the sensors and be informed when the sensor's
Ddevices.txt383 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
Dmd.txt489 a text file that can be used to monitor and control the rebuild
/linux-4.4.14/arch/avr32/boards/mimc200/
Dsetup.c64 .monitor = "PT0434827-A401",
/linux-4.4.14/drivers/gpu/drm/nouveau/include/nvkm/subdev/
Di2c.h63 void nvkm_i2c_aux_monitor(struct nvkm_i2c_aux *, bool monitor);
/linux-4.4.14/drivers/platform/x86/
Dintel_ips.c299 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.4.14/arch/arm/kernel/
Dentry-header.S315 @ monitor is part of the exception entry and exit sequence.
330 strex r1, r2, [sp] @ clear the exclusive monitor
/linux-4.4.14/fs/lockd/
Dsvc4proc.c36 || (argp->monitor && nsm_monitor(host) < 0)) in nlm4svc_retrieve_args()
386 argp->monitor = 0; /* just clean the monitor flag */ in nlm4svc_proc_nm_lock()
Dsvcproc.c65 || (argp->monitor && nsm_monitor(host) < 0)) in nlmsvc_retrieve_args()
429 argp->monitor = 0; /* just clean the monitor flag */ in nlmsvc_proc_nm_lock()
Dxdr.c224 argp->monitor = 1; /* monitor client by default */ in nlmsvc_decode_lockargs()
Dxdr4.c221 argp->monitor = 1; /* monitor client by default */ in nlm4svc_decode_lockargs()
/linux-4.4.14/arch/s390/
DKconfig777 allows an external monitor to balance memory of many systems.
795 monitor records. The monitor records are updated at certain time
813 APPLDATA monitor record, i.e. enables or disables monitoring this record
830 APPLDATA monitor record, i.e. enables or disables monitoring this record
846 APPLDATA monitor record, i.e. enables or disables monitoring this record
/linux-4.4.14/tools/perf/Documentation/
Dperf-stat.txt108 monitor only in the container (cgroup) called "name". This option is available only
113 an empty cgroup (monitor all the time) using, e.g., -G foo,,bar. Cgroups must have
Dperf-record.txt208 the thread executes on the designated CPUs. Default is to monitor all CPUs.
218 monitor only in the container (cgroup) called "name". This option is available only
223 an empty cgroup (monitor all the time) using, e.g., -G foo,,bar. Cgroups must have
Dperf-trace.txt79 the thread executes on the designated CPUs. Default is to monitor all CPUs.
Dperf-top.txt32 Default is to monitor all CPUS.
/linux-4.4.14/Documentation/ABI/stable/
Dsysfs-firmware-opal-elog23 Typically, a user space daemon will monitor for new
/linux-4.4.14/Documentation/w1/masters/
Domap-hdq21 monitor (gas gauge) integrated circuits.
/linux-4.4.14/arch/avr32/boards/favr-32/
Dsetup.c123 .monitor = "LB104V03",
/linux-4.4.14/Documentation/devicetree/bindings/soc/ti/
Dkeystone-navigator-qmss.txt67 channels can be configured to monitor 32 contiguous
83 monitor upto 32 queues starting at the base queue #.
/linux-4.4.14/drivers/power/
DKconfig76 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
360 system. The charger-manager also can monitor charging status in
/linux-4.4.14/drivers/vme/
Dvme.c1323 int vme_lm_attach(struct vme_resource *resource, int monitor, in vme_lm_attach() argument
1341 return bridge->lm_attach(lm, monitor, callback); in vme_lm_attach()
1345 int vme_lm_detach(struct vme_resource *resource, int monitor) in vme_lm_detach() argument
1362 return bridge->lm_detach(lm, monitor); in vme_lm_detach()
/linux-4.4.14/Documentation/ide/
DChangeLog.ide-floppy.1996-200240 * monitor the dsc bit in the status register.
/linux-4.4.14/Documentation/networking/mac80211_hwsim/
DREADME41 mac80211. This interface can be used to monitor all transmitted frames
/linux-4.4.14/Documentation/sound/alsa/soc/
Djack.txt51 Actual jack detection is done by code which is able to monitor some
/linux-4.4.14/fs/proc/
DKconfig70 Various /proc files exist to monitor process memory utilization:
/linux-4.4.14/arch/parisc/kernel/
Dperf_asm.S57 pmenb ; enable performance monitor
83 pmdis ; disable performance monitor
/linux-4.4.14/arch/um/
DKconfig.net164 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.4.14/arch/arm/boot/dts/
Domap3-igep0020-common.dtsi203 * Display monitor features are burnt in the EEPROM
Domap4-panda-common.dtsi411 * Display monitor features are burnt in their EEPROM as EDID data.
Datlas6.dtsi104 memc-monitor {
Dprima2.dtsi115 memc-monitor {
/linux-4.4.14/Documentation/parisc/
Dregisters66 F (performance monitor) 0
/linux-4.4.14/Documentation/m68k/
Dkernel-options.txt504 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).
DREADME.buddha195 multisync monitor, or a graphics card, and your internal
/linux-4.4.14/Documentation/input/
Dinput.txt109 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
Datarikbd.txt416 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.4.14/arch/powerpc/platforms/ps3/
DKconfig154 This support is required to use the logical performance monitor
/linux-4.4.14/Documentation/power/regulator/
Doverview.txt168 userspace via sysfs. This could be used to help monitor device power
/linux-4.4.14/Documentation/DocBook/
D80211.xml.db37 API-enum-monitor-flags
Dgpu.xml.db423 API-drm-detect-hdmi-monitor
424 API-drm-detect-monitor-audio
/linux-4.4.14/drivers/net/wireless/ath/ath10k/
Dcore.h737 bool monitor; member
Dmac.c1071 return ar->monitor || in ath10k_mac_monitor_vdev_is_needed()
3713 ar->monitor = false; in ath10k_halt()
4216 ar->monitor = conf->flags & IEEE80211_CONF_MONITOR; in ath10k_config()
/linux-4.4.14/drivers/usb/host/
Du132-hcd.c202 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()
3035 INIT_DELAYED_WORK(&u132->monitor, u132_hcd_monitor_work); in u132_initialise()
/linux-4.4.14/drivers/atm/
Dfore200e.c2436 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.4.14/Documentation/filesystems/caching/
Doperations.txt172 operation with FSCACHE_OP_MYTHREAD, then it should monitor
Dcachefiles.txt244 The daemon uses dnotify to monitor the graveyard directory, and will delete
/linux-4.4.14/Documentation/sound/alsa/
DREADME.maya4426 - analogue monitor a.k.a bypass
/linux-4.4.14/Documentation/dvb/
Dfaq.txt97 DVB sniffer program to monitor, analyze, debug, dump
Davermedia.txt49 displayed on the video monitor screen. Some Analogue TV cards
/linux-4.4.14/Documentation/laptops/
Dsonypi.txt127 external monitor on/off. There is no workaround yet, since this
Dasus-laptop.txt59 "acpi_genl monitor" (part of the acpica project).
/linux-4.4.14/drivers/input/
DKconfig17 Say N here if you have a headless (no monitor, no keyboard) system.
/linux-4.4.14/Documentation/device-mapper/
Dsnapshot.txt40 useless and be disabled, returning errors. So it is important to monitor
/linux-4.4.14/arch/ia64/
DKconfig467 bool "Performance monitor support"
469 Selects whether support for the IA-64 performance monitor hardware
/linux-4.4.14/drivers/usb/storage/
DKconfig181 to use tools to tune and monitor your drive (like hdparm or smartctl).
/linux-4.4.14/drivers/gpu/drm/
DKconfig70 monitor are unable to provide appropriate EDID data. Since this
/linux-4.4.14/drivers/video/fbdev/core/
Dfbmon.c972 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.4.14/include/linux/
Dfb.h66 __u8 monitor[14]; /* Monitor String */ member
/linux-4.4.14/Documentation/isdn/
DREADME.x25181 used to monitor X.25 packets received by the network interfaces.
DREADME.HiSax266 programs and for identification when using a line monitor
394 0x0200 ISAC monitor debug
/linux-4.4.14/Documentation/cgroups/
Dunified-hierarchy.txt339 interface file which can be used to monitor whether the cgroup's
347 in the subhierarchy and monitor events that it's interested in from
559 lead to gradual performance degradation. The user can monitor this
/linux-4.4.14/Documentation/hid/
Dhiddev.txt9 supplies) and monitor control on higher end monitors.
/linux-4.4.14/Documentation/power/
Dcharger-manager.txt30 we may need to monitor the battery health by looking at the ambient or
/linux-4.4.14/Documentation/vm/
Dtranshuge.txt207 monitor how successfully the system is providing huge pages for use.
239 monitor this overhead.
/linux-4.4.14/sound/aoa/codecs/
Dtas.c384 MIXER_CONTROL(monitor, "Monitor", 2);
/linux-4.4.14/Documentation/devicetree/bindings/powerpc/fsl/
Ddcsr.txt75 monitor interrupt signal based on either counter overflow or value
/linux-4.4.14/drivers/video/fbdev/
Dfsl-diu-fb.c2008 module_param_named(monitor, monitor_string, charp, 0);
2009 MODULE_PARM_DESC(monitor, "Specify the monitor port "
DKconfig1140 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.4.14/arch/arm64/
DKconfig622 monitor to maintain update atomicity. If your system does not
623 implement a global monitor, this option can cause programs that
/linux-4.4.14/arch/powerpc/
DKconfig.debug85 Include in-kernel hooks for the xmon kernel monitor/debugger.
/linux-4.4.14/Documentation/arm64/
Dbooting.txt17 is passed to the Linux kernel. This may include secure monitor and
/linux-4.4.14/Documentation/thermal/
Dintel_powerclamp.txt90 kidle_inject/cpu. During idle injection, it runs monitor/mwait idle
/linux-4.4.14/Documentation/sysctl/
Dfs.txt12 The files in this directory can be used to tune and monitor
Dkernel.txt12 The files in this directory can be used to tune and monitor
614 0: disable the mechanism. Do not monitor or correct perf's
/linux-4.4.14/drivers/mtd/
DKconfig29 RedBoot is a ROM monitor and bootloader which deals with multiple
/linux-4.4.14/tools/testing/ktest/
Dktest.pl1923 sub monitor { subroutine
2199 return monitor;
/linux-4.4.14/arch/arm/mm/
DKconfig708 monitor to maintain update atomicity. If your system does not
709 implement a global monitor, this option can cause programs that
/linux-4.4.14/drivers/hwmon/
DKconfig10 Hardware monitoring devices let you monitor the hardware health
1135 interpretation. The driver can also monitor the temperature and
1468 voltage / current / power monitor I2C interface.
1479 INA230, and INA231 power monitor chips.
/linux-4.4.14/Documentation/devicetree/bindings/crypto/
Dfsl-sec4.txt205 calculated, these addresses are checked by HW to monitor any
/linux-4.4.14/Documentation/scsi/
Darcmsr_spec.txt235 ** GUI_GET_HW_MONITOR : Get HW monitor data
/linux-4.4.14/drivers/net/wireless/iwlwifi/pcie/
Dtrans.c915 goto monitor; in iwl_pcie_apply_destination()
925 monitor: in iwl_pcie_apply_destination()
/linux-4.4.14/drivers/watchdog/
DKconfig25 also monitor NFS connections and can reboot the machine when the process
1582 time. The card can also monitor the internal temperature of the PC.
1620 time. The card can also monitor the internal temperature of the PC.
/linux-4.4.14/drivers/tty/
DKconfig36 of your keyboard and monitor. Therefore, only people configuring an
/linux-4.4.14/drivers/misc/
DKconfig422 monitor, freeing up the underlying machine pages so they can
/linux-4.4.14/drivers/hid/
DKconfig44 devices, like monitor controls and Uninterruptable Power Supplies.
/linux-4.4.14/Documentation/spi/
Dspi-summary154 or monitor temperature and voltage levels during industrial processing.

12