Home
last modified time | relevance | path

Searched full:monitoring (Results 1 – 25 of 935) sorted by relevance

12345678910>>...38

/OK3568_Linux_fs/kernel/drivers/hwmon/pmbus/
H A DKconfig21 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 …]
/OK3568_Linux_fs/kernel/include/linux/
H A Ddamon.h38 * struct damon_region - Represents a monitoring target region.
62 * struct damon_target - Represents a monitoring target.
64 * @nr_regions: Number of monitoring target regions of this target.
65 * @regions_list: Head of the monitoring target regions of this target.
68 * Each monitoring context could have multiple targets. For example, a context
71 * example, in the virtual address monitoring context, it could be a pidfd or
82 * enum damos_action - Represents an action of a Data Access Monitoring-based
126 * &weight_nr_accesses, and &weight_age, because monitoring primitives are
176 * means DAMON does monitoring and applying the action of the scheme to
212 * struct damos - Represents a Data Access Monitoring-based Operation Scheme.
[all …]
/OK3568_Linux_fs/kernel/Documentation/admin-guide/
H A Dperf-security.rst14 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 …]
/OK3568_Linux_fs/buildroot/dl/qt5location/git/src/positioning/
H A Dqgeoareamonitorsource.cpp61 the class with the same \l sourceName() shares the same area monitoring backend.
92 \value AccessError The connection setup to the remote area monitoring backend failed because the
94 \value InsufficientPositionInfo The area monitoring source could not retrieve a location fix or
95 the accuracy of the fix is not high enough to provide an effective area monitoring.
102 Defines the types of area monitoring capabilities.
107 \value AnyAreaMonitorFeature Matches all possible area monitoring features.
113 Returns the area monitoring features available to this source.
144 Returns 0 if the system has no support for position monitoring.
240 The area monitoring backend becomes the new QObject parent for \a newSource.
246 used by the area monitoring engine.
[all …]
H A Dqgeoareamonitorinfo.cpp61 The purpose of area monitoring is to inform a user when he/she comes close to an area of
68 monitoring process. Note that extensive monitoring can be very resource consuming
74 to-be-monitored area from the monitoring source once the expiry date has been reached.
77 the current applications lifetime. If an area is entered while the monitoring
237 an expiry date. This implies an indefinite monitoring period if the object is persistent or
277 monitoring. \l QGeoAreaMonitorSource::supportedAreaMonitorFeatures() can be used to
329 Reads a area monitoring data from the specified \a stream into the given
/OK3568_Linux_fs/kernel/drivers/hwmon/
H A DKconfig3 # 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 …]
/OK3568_Linux_fs/kernel/Documentation/hwmon/
H A Dhwmon-kernel-api.rst1 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 …]
H A Dpc87360.rst44 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
H A Dlm63.rst47 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;
H A Dsmsc47m1.rst57 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
H A Dsch5627.rst20 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
H A Demc6w201.rst22 "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,
/OK3568_Linux_fs/kernel/mm/damon/
H A Dreclaim.c26 * do no real monitoring and reclamation due to the watermarks-based activation
103 * the low watermark, DAMON_RECLAIM becomes active, so starts the monitoring
121 * Sampling interval for the monitoring in microseconds.
123 * The sampling interval of DAMON for the cold memory monitoring. Please refer
130 * Aggregation interval for the monitoring in microseconds.
132 * The aggregation interval of DAMON for the cold memory monitoring. Please
139 * Minimum number of monitoring regions.
141 * The minimal number of monitoring regions of DAMON for the cold memory
142 * monitoring. This can be used to set lower-bound of the monitoring quality.
143 * But, setting this too high could result in increased monitoring overhead.
[all …]
H A DKconfig3 menu "Data Access Monitoring"
6 bool "DAMON: Data Access Monitoring Framework"
28 bool "Data access monitoring primitives for virtual address spaces"
32 This builds the default data access monitoring primitives for DAMON
36 bool "Data access monitoring primitives for the physical address space"
40 This builds the default data access monitoring primitives for DAMON
60 can use the interface for arbitrary data access monitoring.
H A Dcore.c250 * damon_set_targets() - Set monitoring targets.
251 * @ctx: monitoring context
282 * damon_set_attrs() - Set attributes for the monitoring.
283 * @ctx: monitoring context
286 * @primitive_upd_int: time interval between monitoring primitive updates
314 * damon_set_schemes() - Set data access monitoring based operation schemes.
315 * @ctx: monitoring context
351 /* Returns the size upper limit for each monitoring region */
374 * __damon_start() - Starts monitoring with given context.
375 * @ctx: monitoring context
[all …]
/OK3568_Linux_fs/yocto/meta-openembedded/meta-oe/recipes-kernel/libpfm/
H A Dlibpfm4_4.11.0.bb1 SUMMARY = "Monitoring tools exploiting the performance monitoring events"
3 monitoring tools exploiting the performance monitoring events such as those \
4 provided by the Performance Monitoring Unit (PMU) of modern processors."
/OK3568_Linux_fs/kernel/drivers/perf/
H A DKconfig14 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.
/OK3568_Linux_fs/kernel/sound/pci/mixart/
H A Dmixart.h148 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);
/OK3568_Linux_fs/external/xserver/os/
H A Dospoll.h77 * @param fd File descriptor to stop monitoring
85 * @param ospoll ospoll monitoring fd
95 * @param ospoll ospoll monitoring fd
119 * @param ospoll ospoll monitoring fd
133 * @param ospoll ospoll monitoring fd
/OK3568_Linux_fs/kernel/Documentation/power/
H A Dcharger-manager.rst8 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".
/OK3568_Linux_fs/kernel/sound/usb/line6/
H A Dpcm.h46 *) 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) */
/OK3568_Linux_fs/kernel/Documentation/ABI/testing/
H A Dsysfs-bus-event_source-devices-dfl_fme22 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.
H A Dsysfs-bus-event_source-devices-events15 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
/OK3568_Linux_fs/kernel/Documentation/input/devices/
H A Datarikbd.rst146 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 …]
/OK3568_Linux_fs/kernel/arch/x86/events/
H A DKconfig2 menu "Performance monitoring"
18 monitoring on modern processors.
26 monitoring on modern processors.

12345678910>>...38