Searched refs:monitoring (Results 1 – 25 of 191) sorted by relevance
12345678
| /Linux-v5.4/drivers/hwmon/pmbus/ |
| D | Kconfig | 21 If you say yes here you get hardware monitoring support for generic
32 If you say yes here you get hardware monitoring support for Analog
43 If you say yes here you get hardware monitoring support for the IBM
52 If you say yes here you get hardware monitoring support for the INSPUR
61 If you say yes here you get hardware monitoring support for the
70 If you say yes here you get hardware monitoring support for Infineon
79 If you say yes here you get hardware monitoring support for the
88 If you say yes here you get hardware monitoring support for Intersil
97 If you say yes here you get hardware monitoring support for National
106 If you say yes here you get hardware monitoring support for Linear
[all …]
|
| /Linux-v5.4/Documentation/admin-guide/ |
| D | perf-security.rst | 14 depends on the nature of data that perf_events performance monitoring
21 its topology, used kernel and Perf versions, performance monitoring
43 sensitive process data. If PMUs in some monitoring modes capture values
45 to such monitoring capabilities requires to be ordered and secured
46 properly. So, perf_events/Perf performance monitoring is the subject for
57 monitoring is fully available to privileged processes without access,
71 monitoring and bypass *scope* permissions checks in the kernel.
75 outcome determines whether monitoring is permitted. So unprivileged
91 performance monitoring without scope limits. The following steps can be
111 enable members of perf_users group with performance monitoring
[all …]
|
| /Linux-v5.4/Documentation/hwmon/ |
| D | hwmon-kernel-api.rst | 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
53 hwmon_device_register_with_groups registers a hardware monitoring device.
64 This function returns a pointer to the newly created hardware monitoring device
72 to register a hardware monitoring device. It creates the standard sysfs
73 attributes in the hardware monitoring core, letting the driver focus on reading
82 hwmon_device_unregister deregisters a registered hardware monitoring device.
[all …]
|
| D | sch5627.rst | 20 SMSC SCH5627 Super I/O chips include complete hardware monitoring
23 The SMSC SCH5627 hardware monitoring part also contains an integrated
28 The hardware monitoring part of the SMSC SCH5627 is accessed by talking
|
| D | lm63.rst | 47 The LM63 is a digital temperature sensor with integrated fan monitoring
50 The LM63 is basically an LM86 with fan speed monitoring and control
72 Note that the pin used for fan monitoring is shared with an alert out
74 speed monitoring will or will not be possible. The proper chip configuration
77 for fan monitoring and alert out. On the LM64, monitoring is always enabled;
|
| D | emc6w201.rst | 22 "The EMC6W201 is an environmental monitoring device with automatic fan
24 This ACPI compliant device provides hardware monitoring for up to six
35 The driver currently only supports the monitoring of the voltages,
|
| D | smsc47m1.rst | 57 contain monitoring and PWM control circuitry for two fans.
60 monitoring block' in addition to the fan monitoring and control. The
61 hardware monitoring block is not supported by this driver, use the
|
| D | ucd9000.rst | 30 ADC with a 2.5V internal reference for monitoring up to 13 power supply voltage,
34 system-health monitor. The device integrates a 12-bit ADC for monitoring up to
42 monitor. The device integrates a 12-bit ADC for monitoring up to 16 power-supply
49 monitor. The device integrates a 12-bit ADC for monitoring up to 10 power-supply
56 system-health monitor. The device integrates a 12-bit ADC for monitoring up to
|
| D | powr1220.rst | 22 includes voltage monitoring for 14 inputs as well as trim settings
24 monitoring portion of the chip.
|
| D | pc87360.rst | 44 The National Semiconductor PC87360 Super I/O chip contains monitoring and
46 PC87364 chip has monitoring and PWM control for a third fan.
49 hardware monitoring chipsets, not only controlling and monitoring three fans,
50 but also monitoring eleven voltage inputs and two (PC87365) or up to four
197 shouldn't be changed once the monitoring has started, but we ignore that
|
| /Linux-v5.4/arch/x86/events/ |
| D | Kconfig | 2 menu "Performance monitoring"
18 monitoring on modern processors.
26 monitoring on modern processors.
|
| /Linux-v5.4/net/netlink/ |
| D | Kconfig | 7 tristate "NETLINK: socket monitoring interface"
10 Support for NETLINK socket monitoring interface used by the ss tool.
|
| /Linux-v5.4/sound/pci/mixart/ |
| D | mixart.h | 148 int monitoring; /* pipe used for monitoring issue */ member
204 …ipe *snd_mixart_add_ref_pipe(struct snd_mixart *chip, int pcm_number, int capture, int monitoring);
205 int snd_mixart_kill_ref_pipe(struct mixart_mgr *mgr, struct mixart_pipe *pipe, int monitoring);
|
| /Linux-v5.4/net/xdp/ |
| D | Kconfig | 11 tristate "XDP sockets: monitoring interface"
15 Support for PF_XDP sockets monitoring interface used by the ss tool.
|
| /Linux-v5.4/drivers/staging/gdm724x/ |
| D | Kconfig | 12 used for AT commands and DM monitoring applications.
16 GCT-DMx can be used for LTE protocol monitoring
|
| /Linux-v5.4/drivers/perf/ |
| D | Kconfig | 14 Support for PMU events monitoring on the ARM CCI (Cache Coherent
61 Groups (PMCG), which provide monitoring of transactions passing
86 Support for HiSilicon SoC uncore performance monitoring
96 monitoring L2 cache events.
106 monitoring L3 cache events.
|
| /Linux-v5.4/net/smc/ |
| D | Kconfig | 15 tristate "SMC: socket monitoring interface"
18 Support for SMC socket monitoring interface used by tools such as
|
| /Linux-v5.4/net/packet/ |
| D | Kconfig | 20 tristate "Packet: sockets monitoring interface"
24 Support for PF_PACKET sockets monitoring interface used by the ss tool.
|
| /Linux-v5.4/drivers/hwmon/ |
| D | Kconfig | 3 # Hardware monitoring chip drivers configuration
11 Hardware monitoring devices let you monitor the hardware health
42 tristate "AB8500 thermal monitoring"
97 AD7414 temperature monitoring chip.
107 AD7416, AD7417 and AD7418 temperature monitoring chips.
181 ADT7410/ADT7420 temperature monitoring chip drivers.
191 ADT7310 and ADT7320 temperature monitoring chips.
202 ADT7410 and ADT7420 temperature monitoring chips.
212 ADT7411 voltage and temperature monitoring chip.
222 ADT7462 temperature monitoring chips.
[all …]
|
| /Linux-v5.4/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
|
| /Linux-v5.4/net/unix/ |
| D | Kconfig | 29 tristate "UNIX: socket monitoring interface"
33 Support for UNIX socket monitoring interface used by the ss tool.
|
| /Linux-v5.4/Documentation/devicetree/bindings/power/supply/ |
| D | ltc2941.txt | 5 temperature monitoring, and is runtime detected. LTC2943 and LTC2944
7 for the charge counter and adds voltage, current and temperature monitoring.
|
| /Linux-v5.4/net/tipc/ |
| D | Kconfig | 40 tristate "TIPC: socket monitoring interface"
44 Support for TIPC socket monitoring interface used by ss tool.
|
| /Linux-v5.4/drivers/hwmon/occ/ |
| D | Kconfig | 12 This option enables support for monitoring sensors provided by the
27 This option enables support for monitoring sensors provided by the
|
| /Linux-v5.4/Documentation/power/ |
| D | charger-manager.rst | 8 requires temperature monitoring during suspend-to-RAM state
36 monitoring the battery health and tasks, and user processes that are
63 (in-suspend monitoring), the user should provide charger_global_desc
65 This charger_global_desc data for in-suspend monitoring is global
69 and it will manage in-suspend monitoring for all instances of Charger Manager.
72 properly in order to activate in-suspend monitoring:
107 (in-suspend monitoring) results in "normal".
|
12345678
