Home
last modified time | relevance | path

Searched refs:monitored (Results 1 – 25 of 58) sorted by relevance

123

/kernel/linux/linux-5.10/drivers/usb/mon/
Dmon_main.c47 m1->u_bus->monitored = 1; in mon_reader_add()
50 mbus->u_bus->monitored = 1; in mon_reader_add()
177 ubus->monitored = 0; in mon_stop()
185 ubus->monitored = 0; in mon_stop()
202 ubus->monitored = 1; in mon_bus_add()
257 if (ubus->monitored) { in mon_dissolve()
258 ubus->monitored = 0; in mon_dissolve()
/kernel/linux/linux-5.10/Documentation/hwmon/
Dab8500.rst25 temperature are monitored. Other GPADC channels can also be monitored if needed
Dda9055.rst51 are monitored by the ADC channels.
Dda9052.rst64 are monitored by the ADC channels.
Dlochnagar.rst18 map interface to the Lochnagar board controller, and can therefore be monitored
Dadm1025.rst42 ambient temperature to be monitored.
Dmax16065.rst71 Each monitored channel has its own low and high critical limits. MAX16065,
/kernel/linux/linux-5.10/Documentation/devicetree/bindings/power/supply/
Dsc2731_charger.txt9 - monitored-battery: phandle of battery characteristics devicetree node.
38 monitored-battery = <&bat>;
Dsc27xx-fg.txt18 - monitored-battery: Phandle of battery characteristics devicetree node.
56 monitored-battery = <&bat>;
Dbq24190.txt13 - monitored-battery: phandle of battery characteristics devicetree node
48 monitored-battery = <&bat>;
/kernel/linux/linux-5.10/Documentation/admin-guide/
Dperf-security.rst11 monitored processes. The data leakage is possible both in scenarios of
32 execution metrics for various monitored parts of the system (e.g.,
95 performance analysis of monitored processes or a system. For example,
177 monitored *scope* is maximized and no perf_events specific limits
184 user or in kernel space can be monitored and captured for later
193 monitored and captured for later analysis. Per-user per-cpu
200 monitored and captured for later analysis. Per-user per-cpu
219 file descriptors that is not less than the number of monitored events
220 multiplied by the number of monitored CPUs.
231 specifically for capturing monitored performance events and related data.
/kernel/linux/linux-5.10/Documentation/devicetree/bindings/hwmon/
Dvexpress.txt16 - label : string describing the monitored value
/kernel/linux/linux-5.10/arch/arm64/boot/dts/sprd/
Dsc2731.dtsi23 monitored-battery = <&bat>;
104 monitored-battery = <&bat>;
/kernel/linux/linux-5.10/Documentation/devicetree/bindings/arm/tegra/
Dnvidia,tegra30-actmon.txt6 from the monitored clients.
/kernel/linux/linux-5.10/include/linux/usb/
Dhcd.h702 if (bus->monitored) in usbmon_urb_submit()
709 if (bus->monitored) in usbmon_urb_submit_error()
716 if (bus->monitored) in usbmon_urb_complete()
/kernel/linux/linux-5.10/Documentation/ABI/testing/
Dsysfs-devices-mapping7 for PCIe root port, which can be monitored by that IIO PMON
Dsysfs-devices-edac53 field should be monitored for non-zero values and report
64 field should be also be monitored for non-zero values.
148 to fail. This count field should be monitored for non-zero values
Dsysfs-bus-event_source-devices-events18 supported by many/most CPUs. These events can be monitored
/kernel/linux/linux-5.10/Documentation/accounting/
Dpsi.rst79 /proc/pressure/ representing the resource to be monitored and write the
98 Monitors activate only when system enters stall state for the monitored
100 in the stall state psi signal growth is monitored at a rate of 10 times per
/kernel/linux/linux-5.10/drivers/powercap/
DKconfig29 and monitored on modern Intel processors (Sandy Bridge and later).
/kernel/linux/linux-5.10/Documentation/sparc/oradax/
Doracle-dax.rst47 coprocessor. This is done using the monitored load and mwait
168 First, a "monitored load" is achieved via a Load from Alternate Space
170 "monitored wait" is achieved via the mwait instruction (a write to
174 block of data containing the monitored location is modified, then the
188 - go into a loop executing monitored load + monitored wait and
/kernel/linux/linux-5.10/Documentation/powerpc/
Dimc.rst100 to be monitored and the sampling duration. On each overflow in the CPMCxSEL,
152 *Currently the event monitored for trace-mode is fixed as cycle.*
/kernel/linux/linux-5.10/tools/perf/Documentation/
Dperf-stat.txt123 Do not aggregate counts across all monitored CPUs.
158 container "name" are monitored when they run on the monitored CPUs. Multiple cgroups
281 Aggregate counts per monitored threads, when monitoring threads (-t option)
353 Do not aggregate counts across all monitored CPUs.
/kernel/linux/linux-5.10/Documentation/devicetree/bindings/iio/dac/
Dad5592r.txt29 but can be monitored by an ADC, since
/kernel/linux/linux-5.10/Documentation/admin-guide/mm/
Duserfaultfd.rst229 When the ``userfaultfd`` is monitored by an external manager, the manager
264 removed, but the area is not, the area remains monitored by the
281 return ``-ENOSPC`` when the monitored process exits at the time of

123