Searched full:monitoring (Results 1 – 25 of 677) sorted by relevance
12345678910>>...28
| /Linux-v5.10/drivers/hwmon/pmbus/ |
| D | Kconfig | 21 If you say yes here you get hardware monitoring support for generic
34 If you say yes here you get hardware monitoring support for Analog
43 If you say yes here you get hardware monitoring support for Analog
53 If you say yes here you get hardware monitoring support for BEL
63 If you say yes here you get hardware monitoring support for the IBM
72 If you say yes here you get hardware monitoring support for the INSPUR
81 If you say yes here you get hardware monitoring support for the
90 If you say yes here you get hardware monitoring support for Infineon
99 If you say yes here you get hardware monitoring support for the
108 If you say yes here you get hardware monitoring support for Renesas
[all …]
|
| /Linux-v5.10/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 modes requires to be ordered and secured properly.
46 So, perf_events performance monitoring and observability operations are
57 monitoring is fully available to privileged processes without access,
71 monitoring and observability operations, thus, bypass *scope* permissions
73 privilege [13]_ (POSIX 1003.1e: 2.2.2.39) for performance monitoring and
75 perfomance monitoring and observability in the system.
77 For backward compatibility reasons the access to perf_events monitoring and
[all …]
|
| /Linux-v5.10/Documentation/hwmon/ |
| D | hwmon-kernel-api.rst | 1 The Linux Hardware Monitoring kernel API
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
[all …]
|
| 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 | 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
66 Fan Monitoring
123 Temperature Monitoring
149 Voltage Monitoring
185 Monitoring of in9 isn't enabled at lower init levels (<3) because that
197 shouldn't be changed once the monitoring has started, but we ignore that
|
| 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 | 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 | 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 | gsc-hwmon.rst | 13 This driver supports hardware monitoring for the temperature sensor,
18 Voltage Monitoring
29 Temperature Monitoring
|
| D | pc87427.rst | 24 monitoring capabilities. It can monitor up to 18 voltages, 8 fans and
35 Fan Monitoring
55 Temperature Monitoring
|
| D | ucd9000.rst | 32 ADC with a 2.5V internal reference for monitoring up to 13 power supply voltage,
36 system-health monitor. The device integrates a 12-bit ADC for monitoring up to
44 monitor. The device integrates a 12-bit ADC for monitoring up to 16 power-supply
57 monitor. The device integrates a 12-bit ADC for monitoring up to 10 power-supply
64 system-health monitor. The device integrates a 12-bit ADC for monitoring up to
|
| /Linux-v5.10/drivers/hwmon/ |
| D | Kconfig | 3 # Hardware monitoring chip drivers configuration
7 tristate "Hardware Monitoring support"
11 Hardware monitoring devices let you monitor the hardware health
32 bool "Hardware Monitoring Chip debugging messages"
42 tristate "AB8500 thermal monitoring"
98 AD7414 temperature monitoring chip.
108 AD7416, AD7417 and AD7418 temperature monitoring chips.
192 ADT7410/ADT7420 temperature monitoring chip drivers.
202 ADT7310 and ADT7320 temperature monitoring chips.
213 ADT7410 and ADT7420 temperature monitoring chips.
[all …]
|
| /Linux-v5.10/drivers/perf/ |
| D | Kconfig | 14 Support for PMU events monitoring on the ARM CCI (Cache Coherent
48 Support for PMU events monitoring on the Arm CMN-600 Coherent Mesh
68 Groups (PMCG), which provide monitoring of transactions passing
97 monitoring L2 cache events.
107 monitoring L3 cache events.
|
| /Linux-v5.10/sound/pci/mixart/ |
| D | mixart.h | 148 int monitoring; /* pipe used for monitoring issue */ member
182 int monitoring_active[2]; /* Mixer : Monitoring Active */
183 int monitoring_volume[2]; /* Mixer : Monitoring Volume */
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.10/arch/x86/events/ |
| D | Kconfig | 2 menu "Performance monitoring"
18 monitoring on modern processors.
26 monitoring on modern processors.
|
| /Linux-v5.10/sound/usb/line6/ |
| D | pcm.h | 46 *) software monitoring (for devices without hardware monitoring)
57 LINE6_STREAM_MONITOR = software monitoring
153 /* Previously captured frame (for software monitoring) */
156 /* Size of previously captured frame (for software monitoring/sync) */
|
| /Linux-v5.10/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".
|
| /Linux-v5.10/Documentation/ABI/testing/ |
| D | sysfs-bus-event_source-devices-dfl_fme | 22 0x06 local event id for overall monitoring (portid=0xff).
29 for access to all fme pmu performance monitoring events.
35 Description: Read-only. Attribute group to describe performance monitoring
37 a single performance monitoring event supported by this fme pmu.
41 All supported performance monitoring events are listed below.
|
| 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.10/Documentation/input/devices/ |
| D | atarikbd.rst | 146 Joystick Monitoring
155 Fire Button Monitoring
158 A mode is provided to permit monitoring a single input bit at a high rate. In
300 Set mouse monitoring routines to return cursor motion keycodes instead of
418 disabled). Any valid mouse mode command resumes mouse motion monitoring. (The
448 When the ikbd is in either the JOYSTICK MONITORING mode or the FIRE BUTTON
449 MONITORING mode, the PAUSE OUTPUT command also temporarily stops the
450 monitoring process (i.e. the samples are not enqueued for transmission).
483 SET JOYSTICK MONITORING
502 SET FIRE BUTTON MONITORING
[all …]
|
| /Linux-v5.10/drivers/gpu/drm/nouveau/nvkm/subdev/therm/ |
| D | ic.c | 101 nvkm_i2c_bus_probe(bus, "monitoring device", board, in nvkm_therm_ic_ctor()
113 nvkm_i2c_bus_probe(bus, "monitoring device", board, in nvkm_therm_ic_ctor()
122 /* The vbios doesn't provide the address of an exisiting monitoring in nvkm_therm_ic_ctor()
125 nvkm_i2c_bus_probe(bus, "monitoring device", nv_board_infos, in nvkm_therm_ic_ctor()
|
| /Linux-v5.10/drivers/nvme/host/ |
| D | Kconfig | 28 bool "NVMe hardware monitoring"
31 This provides support for NVMe hardware monitoring. If enabled,
32 a hardware monitoring device will be created for each NVMe drive
|
| /Linux-v5.10/net/netlink/ |
| D | Kconfig | 7 tristate "NETLINK: socket monitoring interface"
10 Support for NETLINK socket monitoring interface used by the ss tool.
|
| /Linux-v5.10/arch/x86/include/asm/ |
| D | resctrl.h | 14 * @cur_rmid: The cached Resource Monitoring ID
16 * @default_rmid: The user assigned Resource Monitoring ID
46 * which supports resource control or monitoring and we enable by
|
| /Linux-v5.10/net/xdp/ |
| D | Kconfig | 11 tristate "XDP sockets: monitoring interface"
15 Support for PF_XDP sockets monitoring interface used by the ss tool.
|
12345678910>>...28
