/linux-4.4.14/drivers/hwmon/pmbus/ |
D | Kconfig | 21 If you say yes here you get hardware monitoring support for generic 33 If you say yes here you get hardware monitoring support for Analog 44 If you say yes here you get hardware monitoring support for National 54 If you say yes here you get hardware monitoring support for Linear 72 If you say yes here you get hardware monitoring support for Maxim 82 If you say yes here you get hardware monitoring support for Maxim 92 If you say yes here you get hardware monitoring support for Maxim 102 If you say yes here you get hardware monitoring support for Maxim 112 If you say yes here you get hardware monitoring support for TI 122 If you say yes here you get hardware monitoring support for TI [all …]
|
/linux-4.4.14/Documentation/hwmon/ |
D | hwmon-kernel-api.txt | 9 This document describes the API that can be used by hardware monitoring 10 drivers that want to use the hardware monitoring framework. 12 This document does not describe what a hardware monitoring (hwmon) Driver or 14 to communicate with a hardware monitoring device. If you want to know this 22 Each hardware monitoring driver must #include <linux/hwmon.h> and, in most 40 hwmon_device_register registers a hardware monitoring device. The parameter 42 This function returns a pointer to the newly created hardware monitoring device 44 monitoring sysfs attributes are expected to have been created and attached to 63 hwmon_device_unregister deregisters a registered hardware monitoring device. 65 monitoring device structure. This function must be called from the driver [all …]
|
D | sch5627 | 16 SMSC SCH5627 Super I/O chips include complete hardware monitoring 19 The SMSC SCH5627 hardware monitoring part also contains an integrated 24 The hardware monitoring part of the SMSC SCH5627 is accessed by talking
|
D | lm63 | 30 The LM63 is a digital temperature sensor with integrated fan monitoring 33 The LM63 is basically an LM86 with fan speed monitoring and control 54 Note that the pin used for fan monitoring is shared with an alert out 56 speed monitoring will or will not be possible. The proper chip configuration 59 for fan monitoring and alert out. On the LM64, monitoring is always enabled;
|
D | emc6w201 | 18 "The EMC6W201 is an environmental monitoring device with automatic fan 20 This ACPI compliant device provides hardware monitoring for up to six 31 The driver currently only supports the monitoring of the voltages,
|
D | smsc47m1 | 34 contain monitoring and PWM control circuitry for two fans. 37 monitoring block' in addition to the fan monitoring and control. The 38 hardware monitoring block is not supported by this driver, use the
|
D | powr1220 | 17 includes voltage monitoring for 14 inputs as well as trim settings 19 monitoring portion of the chip.
|
D | ucd9000 | 24 ADC with a 2.5V internal reference for monitoring up to 13 power supply voltage, 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 | pc87360 | 37 The National Semiconductor PC87360 Super I/O chip contains monitoring and 39 PC87364 chip has monitoring and PWM control for a third fan. 42 hardware monitoring chipsets, not only controlling and monitoring three fans, 43 but also monitoring eleven voltage inputs and two (PC87365) or up to four 183 shouldn't be changed once the monitoring has started, but we ignore that
|
D | smsc47m192 | 11 hardware monitoring. 27 They do also have fan monitoring and control capabilities, but the 29 driver. Use the 'smsc47m1' driver for fan monitoring and control.
|
D | nct7802 | 16 This driver implements support for the Nuvoton NCT7802Y hardware monitoring
|
D | scpi-hwmon | 14 This driver supports hardware monitoring for SoC's based on the ARM
|
D | ina209 | 31 This tries to expose most monitoring features of the hardware via 92 outside the scope of a hardware monitoring driver to enable or disable output
|
D | max31790 | 25 monitoring and control of fan RPM as well as detection of fan failure.
|
D | menf21bmc | 17 This driver gives access to the voltage monitoring feature of the main
|
D | lm83 | 53 health monitoring. They also have voltage and fan rotation speed 67 monitoring chipset. One temperature sensor is used for the motherboard
|
D | via686a | 73 product design but was not interested in its hardware monitoring features, 78 not wired for hardware monitoring.
|
D | sch5636 | 16 hardware monitoring solutions, allowing motherboard manufacturers to create
|
D | w83793 | 50 - If the value is 3, it starts monitoring using a remote termal diode 52 - If the value is 6, it starts monitoring using the temperature sensor
|
D | userspace-tools | 16 setup monitoring limits etc. You can get them on their homepage
|
D | lm85 | 89 The LM85 has four fan speed monitoring modes. The ADM1027 has only two. 125 fan speeds. They use this monitoring capability to alert the system to out 130 EMC6D101 plus additional voltage monitoring and system control features. 220 The number of pulses-per-rev of the fans can be set, Tach monitoring
|
D | dme1737 | 29 * force_start: bool Enables the monitoring of voltage, fan and temp inputs 42 This driver implements support for the hardware monitoring capabilities of the 44 and SCH5127 Super-I/O chips. These chips feature monitoring of 3 temp sensors 58 The hardware monitoring features of the DME1737, A8000, and SCH5027 are only
|
D | it87 | 108 SMBus interface to the hardware monitoring functions. This driver no 123 joysticks and other miscellaneous stuff. For hardware monitoring, they 157 The IT8603E/IT8623E is a custom design, hardware monitoring part is similar to 161 The IT8620E is another custom design, hardware monitoring part is similar to
|
D | pc87427 | 20 monitoring capabilities. It can monitor up to 18 voltages, 8 fans and
|
D | f71882fg | 55 monitoring is concerned. 67 Fintek F718xx/F8000 Super I/O chips include complete hardware monitoring
|
D | lineage-pem | 21 standard PMBus commands are not supported. Specifically, all hardware monitoring
|
D | abituguru3 | 46 This driver supports the hardware monitoring features of the third revision of
|
D | adm1025 | 29 are provided, for monitoring +2.5V, +3.3V, +5V and +12V power supplies and
|
D | max16065 | 54 MAX16070, and MAX16071 also support supply current monitoring.
|
D | abituguru | 75 This driver supports the hardware monitoring features of the first and
|
D | ucd9200 | 28 interface to support configuration, monitoring and management.
|
D | w83627hf | 72 be used to force the base I/O address of the hardware monitoring block.
|
D | lm93 | 60 for dynamic Vccp monitoring and PROCHOT. It is designed to monitor a dual 82 The monitoring intervals for the two #PROCHOT signals is also configurable.
|
D | f71805f | 34 The Fintek F71805F/FG Super I/O chip includes complete hardware monitoring
|
D | nct6775 | 49 The chips support up to 25 temperature monitoring sources. Up to 6 of those are
|
D | vt1211 | 42 The VIA VT1211 Super-I/O chip includes complete hardware monitoring
|
D | pmbus-core | 11 enables programming, control, and real-time monitoring of compliant power
|
D | sysfs-interface | 37 Up to lm-sensors 3.0.0, libsensors looks for hardware monitoring attributes
|
/linux-4.4.14/net/netlink/ |
D | Kconfig | 15 tristate "NETLINK: socket monitoring interface" 18 Support for NETLINK socket monitoring interface used by the ss tool.
|
/linux-4.4.14/sound/pci/mixart/ |
D | mixart.h | 165 int monitoring; /* pipe used for monitoring issue */ member 221 …ipe *snd_mixart_add_ref_pipe(struct snd_mixart *chip, int pcm_number, int capture, int monitoring); 222 int snd_mixart_kill_ref_pipe(struct mixart_mgr *mgr, struct mixart_pipe *pipe, int monitoring);
|
D | mixart.c | 230 int monitoring) in snd_mixart_add_ref_pipe() argument 255 if( (monitoring == 0) && (pipe->references >= stream_count) ) { in snd_mixart_add_ref_pipe() 334 if(monitoring) pipe->monitoring = 1; in snd_mixart_add_ref_pipe() 342 struct mixart_pipe *pipe, int monitoring) in snd_mixart_kill_ref_pipe() argument 349 if(monitoring) in snd_mixart_kill_ref_pipe() 350 pipe->monitoring = 0; in snd_mixart_kill_ref_pipe() 354 if((pipe->references <= 0) && (pipe->monitoring == 0)) { in snd_mixart_kill_ref_pipe()
|
/linux-4.4.14/drivers/staging/gdm724x/ |
D | Kconfig | 11 used for AT commands and DM monitoring applications. 15 GCT-DMx can be used for LTE protocol monitoring
|
/linux-4.4.14/net/packet/ |
D | Kconfig | 19 tristate "Packet: sockets monitoring interface" 23 Support for PF_PACKET sockets monitoring interface used by the ss tool.
|
/linux-4.4.14/Documentation/ABI/testing/ |
D | sysfs-bus-event_source-devices-events | 15 Description: Generic performance monitoring events 17 A collection of performance monitoring events that may be 33 Description: Per-pmu performance monitoring events specific to the running system 37 performance monitoring event supported by the <pmu>. The name
|
D | sysfs-hypervisor-pmu | 6 Describes mode that Xen's performance-monitoring unit (PMU)
|
D | sysfs-class-powercap | 43 power zones provide monitoring and control for a subset of
|
/linux-4.4.14/drivers/hwmon/ |
D | Kconfig | 2 # Hardware monitoring chip drivers configuration 10 Hardware monitoring devices let you monitor the hardware health 43 tristate "AB8500 thermal monitoring" 99 AD7414 temperature monitoring chip. 109 AD7416, AD7417 and AD7418 temperature monitoring chips. 183 ADT7410/ADT7420 temperature monitoring chip drivers. 193 ADT7310 and ADT7320 temperature monitoring chips. 204 ADT7410 and ADT7420 temperature monitoring chips. 214 ADT7411 voltage and temperature monitoring chip. 224 ADT7462 temperature monitoring chips. [all …]
|
/linux-4.4.14/net/unix/ |
D | Kconfig | 23 tristate "UNIX: socket monitoring interface" 27 Support for UNIX socket monitoring interface used by the ss tool.
|
/linux-4.4.14/Documentation/power/ |
D | charger-manager.txt | 5 requires temperature monitoring during suspend-to-RAM state 33 monitoring the battery health and tasks, and user processes that are 60 (in-suspend monitoring), the user should provide charger_global_desc 62 This charger_global_desc data for in-suspend monitoring is global 66 and it will manage in-suspend monitoring for all instances of Charger Manager. 69 in-suspend monitoring: 106 (in-suspend monitoring) results in "normal".
|
D | power_supply_class.txt | 15 power supply, specific monitoring hardware may not be able to provide them 199 Q: Suppose, my battery monitoring chip/firmware does not provides capacity
|
/linux-4.4.14/Documentation/devicetree/bindings/bus/ |
D | ti-gpmc.txt | 67 - gpmc,wait-monitoring-ns: Start of wait monitoring with regard to valid 112 - gpmc,wait-on-read Enables wait monitoring on reads. 113 - gpmc,wait-on-write Enables wait monitoring on writes.
|
/linux-4.4.14/drivers/w1/slaves/ |
D | Kconfig | 88 as the one who is responsible for charging/discharging/monitoring 100 as the one who is responsible for charging/discharging/monitoring 112 as the one who is responsible for charging/discharging/monitoring
|
/linux-4.4.14/Documentation/arm/Samsung-S3C24XX/ |
D | USB-Host.txt | 41 board implements extra power control or over-current monitoring. 68 Called to enable or disable the over-current monitoring.
|
/linux-4.4.14/Documentation/watchdog/ |
D | watchdog-api.txt | 140 Environmental monitoring: 143 some do temperature, fan and power level monitoring, some can tell you 171 External monitoring relay/source 1 was triggered. Controllers intended for 172 real world applications include external monitoring pins that will trigger 177 External monitoring relay/source 2 was triggered
|
D | wdt.txt | 17 A second temperature monitoring interface is available on the WDT501P cards.
|
/linux-4.4.14/fs/notify/inotify/ |
D | Kconfig | 8 associated system calls. Inotify allows monitoring of both files and
|
/linux-4.4.14/Documentation/i2c/busses/ |
D | i2c-ismt | 16 monitoring the bus during debug, thus the need for this module parameter.
|
D | i2c-i801 | 133 hardware monitoring chip), you need to add your board to the list.
|
/linux-4.4.14/Documentation/arm/ |
D | swp_emulation | 23 transaction monitoring block called a global monitor to maintain update
|
/linux-4.4.14/Documentation/devicetree/bindings/power/ |
D | ltc2941.txt | 5 temperature monitoring, and uses a slightly different conversion
|
/linux-4.4.14/Documentation/devicetree/bindings/powerpc/fsl/ |
D | guts.txt | 4 enabling, power-on-reset configuration monitoring, general-purpose
|
/linux-4.4.14/arch/arm/boot/dts/ |
D | omap-gpmc-smsc911x.dtsi | 45 gpmc,wait-monitoring-ns = <0>;
|
D | omap2430-sdp.dts | 67 gpmc,wait-monitoring-ns = <0>;
|
D | omap2420-n8x0-common.dtsi | 74 gpmc,wait-monitoring-ns = <0>;
|
D | omap-zoom-common.dtsi | 47 gpmc,wait-monitoring-ns = <0>;
|
D | omap3-sb-t35.dtsi | 129 gpmc,wait-monitoring-ns = <0>;
|
D | dm8168-evm.dts | 114 gpmc,wait-monitoring-ns = <0>;
|
D | omap3-n950-n9.dtsi | 154 gpmc,wait-monitoring-ns = <0>;
|
D | am335x-chilisom.dtsi | 235 gpmc,wait-monitoring-ns = <0>;
|
D | am335x-igep0033.dtsi | 155 gpmc,wait-monitoring-ns = <0>;
|
D | am335x-phycore-som.dtsi | 193 gpmc,wait-monitoring-ns = <0>;
|
D | omap3-devkit8000-common.dtsi | 291 gpmc,wait-monitoring-ns = <0>;
|
D | omap3-lilly-a83x.dtsi | 373 gpmc,wait-monitoring-ns = <0>;
|
D | omap3-n900.dts | 742 gpmc,wait-monitoring-ns = <0>; 808 gpmc,wait-monitoring-ns = <0>;
|
D | am335x-baltos-ir5221.dts | 269 gpmc,wait-monitoring-ns = <0>;
|
D | am335x-evm.dts | 546 gpmc,wait-monitoring-ns = <0>;
|
D | am43x-epos-evm.dts | 589 gpmc,wait-monitoring-ns = <0>;
|
D | dra72-evm.dts | 520 gpmc,wait-monitoring-ns = <0>;
|
D | dra7-evm.dts | 768 gpmc,wait-monitoring-ns = <0>;
|
D | am437x-gp-evm.dts | 845 gpmc,wait-monitoring-ns = <0>;
|
/linux-4.4.14/drivers/bus/ |
D | Kconfig | 25 Support for PMU events monitoring on the ARM CCI-400 (cache coherent 43 Support for PMU events monitoring on the ARM CCI-500 cache coherent
|
/linux-4.4.14/drivers/net/wireless/ath/wil6210/ |
D | Kconfig | 29 such monitoring impossible.
|
/linux-4.4.14/Documentation/misc-devices/ |
D | isl29003 | 18 I2C multi-function control and monitoring capabilities. The internal ADC
|
/linux-4.4.14/Documentation/devicetree/bindings/power_supply/ab8500/ |
D | fg.txt | 10 main-charger, usb-combo-charger and battery-temperature-monitoring.
|
/linux-4.4.14/Documentation/devicetree/bindings/thermal/ |
D | tegra-soctherm.txt | 4 or interrupt-based thermal monitoring, CPU and GPU throttling based
|
D | thermal.txt | 148 Type: list of used while monitoring the thermal zone.
|
/linux-4.4.14/tools/thermal/tmon/ |
D | README | 49 1. For monitoring only:
|
/linux-4.4.14/Documentation/netlabel/ |
D | introduction.txt | 29 The communication layer exists to allow NetLabel configuration and monitoring
|
/linux-4.4.14/Documentation/i2c/ |
D | summary | 16 and hardware monitoring chips.
|
D | instantiating-devices | 162 to call i2c_new_probed_device(). The typical case is hardware monitoring 166 monitoring chips being used. Fortunately, most of these chips have 179 monitoring chips on a TV adapter.
|
D | writing-clients | 120 monitoring chips on PC motherboards, and thus used to embed some assumptions 194 a given I2C bus. This is for example the case of hardware monitoring 205 a driver for a hardware monitoring chip for which auto-detection is
|
/linux-4.4.14/net/can/ |
D | Kconfig | 35 The Broadcast Manager offers content filtering, timeout monitoring,
|
/linux-4.4.14/Documentation/networking/ |
D | bonding.txt | 25 Additionally, link integrity monitoring may be performed. 274 Specifies the ARP link monitoring frequency in milliseconds. 286 If ARP monitoring is used in an etherchannel compatible mode 292 fail. ARP monitoring should not be used in conjunction with 293 miimon. A value of 0 disables ARP monitoring. The default 298 Specifies the IP addresses to use as ARP monitoring peers when 303 address must be given for ARP monitoring to function. The 310 validated in any mode that supports arp monitoring, or whether 312 monitoring purposes. 520 Specifies the MII link monitoring frequency in milliseconds. [all …]
|
D | ipvs-sysctl.txt | 132 be useful, when user-space monitoring program deletes the
|
D | pktgen.txt | 19 For monitoring and control pktgen creates:
|
D | switchdev.txt | 151 monitoring NETDEV_CHANGEUPPER notifications. For example, a port moved into a
|
D | can.txt | 641 monitoring of received messages. 1158 by monitoring CAN error message frames and do a restart when
|
/linux-4.4.14/Documentation/power/powercap/ |
D | powercap.txt | 19 given zone belongs to. They each contain attributes for monitoring power, as 152 the zones and subzones contain energy monitoring attributes (energy_uj,
|
/linux-4.4.14/tools/perf/Documentation/ |
D | perf-stat.txt | 86 to activate system-wide monitoring. Default is to count on all CPUs. 157 Aggregate counts per monitored threads, when monitoring threads (-t option)
|
/linux-4.4.14/drivers/sbus/char/ |
D | Kconfig | 53 Kernel support for temperature and fan monitoring on Sun SME
|
/linux-4.4.14/drivers/power/ |
D | Kconfig | 5 power supply (batteries, AC, USB) monitoring by userspace 101 as the one who is responsible for charging/discharging/monitoring 229 monitoring as well as alerts for battery over/under voltage and 259 tristate "Battery driver for Samsung ADC based monitoring"
|
/linux-4.4.14/Documentation/thermal/ |
D | nouveau_thermal | 16 cannot access any of the i2c external monitoring chips it may find. If you
|
/linux-4.4.14/Documentation/networking/mac80211_hwsim/ |
D | README | 40 A global monitoring netdev, hwsim#, is created independent of
|
/linux-4.4.14/Documentation/blockdev/ |
D | README.DAC960 | 277 configuration and status monitoring is then to avoid system downtime when disk 278 drives fail and must be replaced. Mylex's online monitoring and configuration 284 The primary interfaces for controller configuration and status monitoring are 290 and the current status as of the last status monitoring query is available in 336 To simplify the monitoring process for custom software, the special file 414 online status monitoring capabilities of the Linux DAC960 Driver. The test 586 online status monitoring capabilities of the Linux DAC960 Driver. The test
|
/linux-4.4.14/net/ipv4/ |
D | Kconfig | 94 bool "IP: verbose route monitoring" 416 tristate "INET: socket monitoring interface" 419 Support for INET (TCP, DCCP, etc) socket monitoring interface used by 432 tristate "UDP: socket monitoring interface" 436 Support for UDP socket monitoring interface used by the ss tool.
|
/linux-4.4.14/fs/proc/ |
D | Kconfig | 68 bool "Enable /proc page monitoring" if EXPERT
|
/linux-4.4.14/Documentation/accounting/ |
D | delay-accounting.txt | 31 exit, ensuring continuous and complete monitoring can be done.
|
/linux-4.4.14/drivers/net/slip/ |
D | Kconfig | 65 RELCOM line fill and keepalive monitoring. Ideal on poor quality
|
/linux-4.4.14/drivers/extcon/ |
D | Kconfig | 5 This allows monitoring external connectors by userspace
|
/linux-4.4.14/arch/s390/ |
D | Kconfig | 798 i.e. enables or disables monitoring on the Linux side. 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/Documentation/input/ |
D | atarikbd.txt | 137 A mode is provided to permit monitoring a single input bit at a high rate. In 259 Set mouse monitoring routines to return cursor motion keycodes instead of 353 disabled). Any valid mouse mode command resumes mouse motion monitoring. (The 382 monitoring process (i.e. the samples are not enqueued for transmission). 470 disabled). Any valid joystick mode command resumes joystick monitoring. (The
|
/linux-4.4.14/arch/powerpc/platforms/ps3/ |
D | Kconfig | 157 If you intend to use the advanced performance monitoring and
|
/linux-4.4.14/Documentation/devicetree/bindings/arm/ |
D | cci.txt | 6 cache coherent interconnect (CCI) that is capable of monitoring bus
|
/linux-4.4.14/Documentation/powerpc/ |
D | pmu-ebb.txt | 29 EBBs can only sensibly be used by programs for self-monitoring.
|
/linux-4.4.14/Documentation/usb/ |
D | hotplug.txt | 22 (triggering some monitoring daemon to invoke a helper program) or
|
D | usbmon.txt | 5 to a packet socket used by network monitoring tools such as tcpdump(1)
|
/linux-4.4.14/Documentation/gpio/ |
D | gpio.txt | 63 On a given board each GPIO is used for one specific purpose like monitoring
|
D | gpio-legacy.txt | 50 On a given board each GPIO is used for one specific purpose like monitoring
|
/linux-4.4.14/Documentation/ |
D | local_ops.txt | 28 and for various performance monitoring counters.
|
D | vme_api.txt | 360 Each block may provide a number of location monitors, monitoring adjacent
|
D | 00-INDEX | 217 - directory with docs on various hardware monitoring drivers.
|
D | devices.txt | 400 182 = /dev/perfctr Performance-monitoring counters 1091 24-hour heart monitoring equipment.
|
/linux-4.4.14/tools/perf/ |
D | design.txt | 215 In future, this will allow sophisticated monitoring programs to supply 311 * NOTE: for obvious reason this only works on self-monitoring
|
/linux-4.4.14/drivers/net/ |
D | Kconfig | 290 tristate "Virtual netlink monitoring device" 292 This option enables a monitoring net device for netlink skbs. The
|
/linux-4.4.14/Documentation/serial/ |
D | moxa-smartio | 442 (Rx/Tx) character count since the time when the monitoring is started. 444 the last 5 seconds) and in average basis (since the time the monitoring
|
/linux-4.4.14/Documentation/cgroups/ |
D | unified-hierarchy.txt | 325 - There is single monitoring point at the root. There's no way to 345 delegating management of subhierarchy - subhierarchy monitoring can 348 there without interfering with monitoring higher in the tree.
|
D | cpusets.txt | 253 This enables batch managers monitoring jobs running in dedicated 278 the system load imposed by a batch scheduler monitoring this
|
/linux-4.4.14/Documentation/scsi/ |
D | advansys.txt | 138 monitoring driver and device performance. It will add to the
|
/linux-4.4.14/Documentation/x86/x86_64/ |
D | boot-options.txt | 31 (e.g. BIOS or hardware monitoring applications), conflicting
|
/linux-4.4.14/drivers/platform/x86/ |
D | Kconfig | 389 Enables monitoring of the built-in console audio output control 711 This driver adds hotkey monitoring support to some Toshiba models
|
/linux-4.4.14/Documentation/vm/ |
D | cleancache.txt | 85 If properly configured, monitoring of cleancache is done via debugfs in
|
D | frontswap.txt | 52 If properly configured, monitoring of frontswap is done via debugfs in
|
/linux-4.4.14/drivers/watchdog/ |
D | Kconfig | 61 A software monitoring watchdog. This will fail to reboot your system 884 A software monitoring watchdog and NMI sourcing driver. This driver 916 during inactivity periods (includes interrupt activity monitoring).
|
/linux-4.4.14/Documentation/laptops/ |
D | thinkpad-acpi.txt | 46 - Fan control and monitoring: fan speed, fan enable/disable 1132 Fan control and monitoring: fan speed, fan enable/disable 1175 monitoring all of the temperature sensor readings and you are ready to
|
/linux-4.4.14/init/ |
D | Kconfig | 999 Provides a simple Resource Controller for monitoring the 1072 bool "Enable perf_event per-cpu per-container group (cgroup) monitoring" 1075 This option extends the per-cpu mode to restrict monitoring to
|
/linux-4.4.14/arch/arm64/ |
D | Kconfig | 621 on an external transaction monitoring block called a global
|
/linux-4.4.14/arch/arm/mm/ |
D | Kconfig | 707 on an external transaction monitoring block called a global
|
/linux-4.4.14/Documentation/networking/dsa/ |
D | dsa.txt | 504 Hardware monitoring
|
/linux-4.4.14/arch/blackfin/ |
D | Kconfig | 685 still be able to read it (such as for performance monitoring), but
|
/linux-4.4.14/drivers/mfd/ |
D | Kconfig | 40 over current monitoring, GPIOs, ADC and a watchdog.
|
/linux-4.4.14/ |
D | CREDITS | 851 D: Several hardware monitoring drivers 1557 D: asb100, lm93 and smsc47b397 hardware monitoring drivers
|
/linux-4.4.14/Documentation/virtual/uml/ |
D | UserModeLinux-HOWTO.txt | 918 monitoring traffic on the host
|