average\-on (full) in projects: Linux-v6.1

Project(s)

Full Search
Definition
Symbol
File Path
History
Type

Searched +full:average +full:- +full:on (Results 1 – 25 of 627) sorted by relevance

12 3 4 5 6 7 8 9 10 >>...26

/Linux-v6.1/Documentation/devicetree/bindings/input/
D	microchip,qt1050.txt	1 Microchip AT42QT1050 Five-channel Touch Sensor IC 4 one to five keys, dependent on mode. The QT1050 includes all signal processing 11 - compatible: Must be "microchip,qt1050" 12 - reg: The I2C address of the device 13 - interrupts: The sink for the touchpad's IRQ output, 14 see ../interrupt-controller/interrupts.txt 17 - wakeup-source: touch keys can be used as a wakeup source 19 Each button (key) is represented as a sub-node: 25 - linux,code: Keycode to emit. 26 - reg: The key number. Valid values: 0, 1, 2, 3, 4. [all …]
/Linux-v6.1/Documentation/hwmon/
D	lochnagar.rst	10 ----------- 12 Lochnagar 2 features built-in Current Monitor circuitry that allows for the 13 measurement of both voltage and current on up to eight of the supply voltage 22 ---------------- 30 power1_average Measured average power for DBVDD1 (microWatts) 37 power2_average Measured average power for 1V8 DSP (microWatts) 44 power3_average Measured average power for 1V8 CDC (microWatts) 51 power4_average Measured average power for VDDCORE DSP (microWatts) 58 power5_average Measured average power for AVDD 1V8 (microWatts) 63 power6_average Measured average power for SYSVDD (microWatts) [all …]
D	lm25066.rst	`10 Addresses scanned: - 22 Addresses scanned: - 34 Addresses scanned: - 44 Addresses scanned: - 54 Addresses scanned: - 61 Author: Guenter Roeck <linux@roeck-us.net> 65 ----------- 72 Documentation/hwmon/pmbus.rst for details on PMBus client drivers. 76 ----------- 78 This driver does not auto-detect devices. You will have to instantiate the [all …]`
D	fam15h_power.rst	16 - BIOS and Kernel Developer's Guide (BKDG) For AMD Family 15h Processors 17 - BIOS and Kernel Developer's Guide (BKDG) For AMD Family 16h Processors 18 - AMD64 Architecture Programmer's Manual Volume 2: System Programming 23 ----------- 28 processor varies based on the workload being executed. Derated power 55 On multi-node processors the calculated value is for the entire 57 attributes only for internal node0 of a multi-node processor. 62 calculate the average power consumed by a processor during a 91 CPU average power 110 v. Calculate the average power consumption for a compute unit over [all …]
D	sysfs-interface.rst	5 through the sysfs interface. Since lm-sensors 3.0.0, libsensors is 6 completely chip-independent. It assumes that all the kernel drivers 10 This is a major improvement compared to lm-sensors 2. 14 temperature sensor is connected to the CPU, or that the second fan is on 22 For this reason, even if we aim at a chip-independent libsensors, it will 37 Up to lm-sensors 3.0.0, libsensors looks for hardware monitoring attributes 38 in the "physical" device directory. Since lm-sensors 3.0.1, attributes found 53 than once, even if there is a single element of the given type on the 61 to cause an alarm) is chip-dependent. 65 are interpreted as 0! For more on how written strings are interpreted see the [all …]
/Linux-v6.1/Documentation/devicetree/bindings/hwmon/
D	adi,adm1275.yaml	`1 # SPDX-License-Identifier: (GPL-2.0 OR BSD-2-Clause) 3 --- 6 $schema: http://devicetree.org/meta-schemas/core.yaml# 11 - Krzysztof Kozlowski <krzk@kernel.org> 15 that offer digital current, voltage, and power monitoring using an on-chip, 16 12-bit analog-to-digital converter (ADC), communicated through a PMBus 25 - adi,adm1075 26 - adi,adm1272 27 - adi,adm1275 28 - adi,adm1276 [all …]`
/Linux-v6.1/Documentation/accounting/
D	delay-accounting.rst	7 runnable task may wait for a free CPU to run on. 9 The per-task delay accounting functionality measures 18 g) write-protect copy 34 statistics of a task are available both during its lifetime as well as on its 39 --------- 43 generic data structure to userspace corresponding to per-pid and per-tgid 52 cache, direct compact, write-protect copy etc. 59 When a task exits, records containing the per-task statistics 61 task of a thread group, the per-tgid statistics are also sent. More details 69 ----- [all …]
/Linux-v6.1/drivers/gpu/drm/amd/include/
D	kgd_pp_interface.h	`212 * APU power is managed to system-level requirements through the PPT 222 * enum pp_power_limit_level - Used to query the power limits 231 PP_PWR_LIMIT_MIN = -1, 238 * enum pp_power_type - Used to specify the type of the requested power 241 * moving average of APU power (default ~5000 ms). 242 * @PP_PWR_TYPE_FAST: manages the ~10 ms moving average of APU power, 306 /* export for dpm on ci and si / 448 / Average clocks / 500 / Average clocks / 559 / Average clocks */ [all …]`
/Linux-v6.1/Documentation/translations/zh_CN/accounting/
D	delay-accounting.rst	`1 .. include:: ../disclaimer-zh_CN.rst 3 :Original: Documentation/accounting/delay-accounting.rst 36 ---- 57 ---- 77 getdelays [-dilv] [-t tgid] [-p pid] 81 # ./getdelays -d -p 10 86 # ./getdelays -d -t 5 87 print delayacct stats ON 91 CPU count real total virtual total delay total delay average 93 IO count delay total delay average [all …]`
/Linux-v6.1/tools/perf/bench/
D	synthesize.c	1 // SPDX-License-Identifier: GPL-2.0 4 * record'. Synthesis is done on the current process and the 'dummy' event 14 #include "../util/synthetic-events.h" 22 #include <subcmd/parse-options.h> 33 OPT_BOOLEAN('t', "mt", &run_mt, "Run multi-threaded benchmark"), 34 OPT_UINTEGER('m', "min-threads", &min_threads, 36 OPT_UINTEGER('M', "max-threads", &max_threads, 38 OPT_UINTEGER('i', "single-iterations", &single_iterations, 39 "Number of iterations used to compute single-threaded average"), 40 OPT_UINTEGER('I', "multi-iterations", &multi_iterations, [all …]
/Linux-v6.1/tools/perf/pmu-events/arch/x86/ivytown/
D	uncore-interconnect.json	22 "BriefDescription": "Direct 2 Core Spawning; Spawn Failure - Egress Credits", 27 …on": "Counts the number of DRS packets that we attempted to do direct2core on. There are 4 mutual… 32 "BriefDescription": "Direct 2 Core Spawning; Spawn Failure - Egress and RBT Miss", 37 …on": "Counts the number of DRS packets that we attempted to do direct2core on. There are 4 mutual… 42 "BriefDescription": "Direct 2 Core Spawning; Spawn Failure - Egress and RBT Invalid", 47 …on": "Counts the number of DRS packets that we attempted to do direct2core on. There are 4 mutual… 52 "BriefDescription": "Direct 2 Core Spawning; Spawn Failure - Egress and RBT Miss, Invalid", 57 …on": "Counts the number of DRS packets that we attempted to do direct2core on. There are 4 mutual… 62 "BriefDescription": "Direct 2 Core Spawning; Spawn Failure - RBT Miss", 67 …on": "Counts the number of DRS packets that we attempted to do direct2core on. There are 4 mutual… [all …]
D	uncore-other.json	48 …cle. This can be used with the write transaction count to calculate the average write latency in … 58 …cle. This can be used with the write transaction count to calculate the average write latency in … 68 …ycle. This can be used with the read transaction count to calculate the average read latency in t… 78 …ycle. This can be used with the read transaction count to calculate the average read latency in t… 108 …cle. This can be used with the transaction count event to calculate the average latency in the un… 118 …cle. This can be used with the transaction count event to calculate the average latency in the un… 164 "BriefDescription": "BL Ingress Occupancy - DRS", 189 "BriefDescription": "BL Ingress Occupancy - NCB", 214 "BriefDescription": "BL Ingress Occupancy - NCS", 236 …ny requests behind it in the switch queue will lose ownership and have to re-acquire it later when… [all …]
/Linux-v6.1/tools/perf/pmu-events/arch/x86/jaketown/
D	uncore-other.json	48 …cle. This can be used with the write transaction count to calculate the average write latency in … 58 …cle. This can be used with the write transaction count to calculate the average write latency in … 68 …ycle. This can be used with the read transaction count to calculate the average read latency in t… 78 …ycle. This can be used with the read transaction count to calculate the average read latency in t… 108 …cle. This can be used with the transaction count event to calculate the average latency in the un… 118 …cle. This can be used with the transaction count event to calculate the average latency in the un… 164 "BriefDescription": "BL Ingress Occupancy - DRS", 189 "BriefDescription": "BL Ingress Occupancy - NCB", 214 "BriefDescription": "BL Ingress Occupancy - NCS", 256 …on request type in addition to the source queue. Note the special filtering equation. We do OR-r… [all …]
D	uncore-memory.json	8 … the number of DRAM Activate commands sent on this channel. Activate commands are issued to open … 12 … "BriefDescription": "DRAM RD_CAS and WR_CAS Commands.; All DRAM WR_CAS (w/ and w/out auto-pre)", 32 … "BriefDescription": "DRAM RD_CAS and WR_CAS Commands.; All DRAM RD_CAS (w/ and w/out auto-pre)", 62 …"BriefDescription": "DRAM RD_CAS and WR_CAS Commands.; DRAM WR_CAS (w/ and w/out auto-pre) in Read… 72 …"BriefDescription": "DRAM RD_CAS and WR_CAS Commands.; DRAM WR_CAS (w/ and w/out auto-pre) in Writ… 86 "PublicDescription": "Uncore Fixed Counter - uclks", 124 …"PublicDescription": "Counts the number of ECC errors detected and corrected by the iMC on this ch… 133 …nt in a major mode (selected by a filter) on the given channel. Major modea are channel-wide, an… 143 …nt in a major mode (selected by a filter) on the given channel. Major modea are channel-wide, an… 153 …nt in a major mode (selected by a filter) on the given channel. Major modea are channel-wide, an… [all …]
/Linux-v6.1/drivers/staging/greybus/tools/
D	README.loopback	`3 1 - LOOPBACK DRIVER 15 # modprobe gb-loopback 18 When the module is probed, New files are available on the sysfs 25 async - Use asynchronous operations. 26 iteration_max - Number of tests iterations to perform. 27 size - payload size of the transfer. 28 timeout - The number of microseconds to give an individual 30 us_wait - Time to wait between 2 messages 31 type - By writing the test type to this file, the test starts. 34 2 - ping [all …]`
/Linux-v6.1/tools/perf/pmu-events/arch/powerpc/power10/
D	metrics.json	10 "BriefDescription": "Average cycles per completed instruction", 16 …"BriefDescription": "Average cycles per completed instruction when dispatch was stalled for any re… 22 …"BriefDescription": "Average cycles per completed instruction when dispatch was stalled because th… 28 …"BriefDescription": "Average cycles per completed instruction when dispatch was stalled because th… 34 …"BriefDescription": "Average cycles per completed instruction when dispatch was stalled waiting to… 40 …"BriefDescription": "Average cycles per completed instruction when dispatch was stalled waiting to… 46 …"BriefDescription": "Average cycles per completed instruction when dispatch was stalled due to an … 52 …"BriefDescription": "Average cycles per completed instruction when dispatch was stalled while the … 58 …"BriefDescription": "Average cycles per completed instruction when dispatch was stalled while the … 64 …"BriefDescription": "Average cycles per completed instruction when dispatch was stalled while the … [all …]
/Linux-v6.1/tools/perf/pmu-events/arch/powerpc/power8/
D	metrics.json	46 "MetricExpr": "(PM_BR_MPRED_TA - PM_BR_MPRED_CCACHE) / PM_RUN_INST_CMPL * 100", 52 …"MetricExpr": "(PM_BR_MPRED_TA - PM_BR_MPRED_CCACHE) / (PM_BR_PRED_LSTACK_BR0 + PM_BR_PRED_LSTACK_… 124 "MetricExpr": "(PM_CMPLU_STALL_BRU_CRU - PM_CMPLU_STALL_BRU) / PM_RUN_INST_CMPL", 135 "BriefDescription": "Cycles stalled by FXU Multi-Cycle Instructions", 148 …"MetricExpr": "(PM_CMPLU_STALL_FXU / PM_RUN_INST_CMPL) - (PM_CMPLU_STALL_FXLONG / PM_RUN_INST_CMPL… 208 "MetricExpr": "(PM_GCT_NOSLOT_IC_MISS - PM_GCT_NOSLOT_IC_L3MISS) / PM_RUN_INST_CMPL", 213 … "BriefDescription": "Cycles stalled by GCT empty due to Icache misses that resolve off-chip", 220 …L) - (PM_GCT_NOSLOT_IC_MISS / PM_RUN_INST_CMPL) - (PM_GCT_NOSLOT_BR_MPRED / PM_RUN_INST_CMPL) - (… 237 "BriefDescription": "Cycles stalled by D-Cache Misses", 243 …"BriefDescription": "Cycles stalled by D-Cache Misses that resolved in distant interventions and m… [all …]
/Linux-v6.1/drivers/cpuidle/governors/
D	menu.c	1 // SPDX-License-Identifier: GPL-2.0-only 3 * menu.c - the menu idle governor 5 * Copyright (C) 2006-2007 Adam Belay <abelay@novell.com> 40 * ----------------------- 42 * the C state is required to actually break even on this cost. CPUIDLE 50 * that is based on historic behavior. For example, if in the past the actual 54 * menu uses a running average for this correction factor, however it uses a 56 * that the ratio is dependent on the order of magnitude of the expected 59 * seconds of idle time. A second independent factor that has big impact on 65 * indexed based on the magnitude of the expected duration as well as the [all …]
/Linux-v6.1/tools/perf/pmu-events/arch/x86/icelakex/
D	icx-metrics.json	4 …"MetricExpr": "topdown\\-fe\\-bound / (topdown\\-fe\\-bound + topdown\\-bad\\-spec + topdown\\-ret… 7 …on by the Backend part. Within the Frontend; a branch predictor predicts the next address to fetch… 12 …"MetricExpr": "(5 * IDQ_UOPS_NOT_DELIVERED.CYCLES_0_UOPS_DELIV.CORE - INT_MISC.UOP_DROPPING) / SLO… 15 …he CPU was stalled due to Frontend latency issues. For example; instruction-cache misses; iTLB mi… 39 … corrected path; following all sorts of miss-predicted branches. For example; branchy code with lo… 52 …"MetricExpr": "(1 - (BR_MISP_RETIRED.ALL_BRANCHES / (BR_MISP_RETIRED.ALL_BRANCHES + MACHINE_CLEARS… 71 …o switches from DSB to MITE pipelines. The DSB (decoded i-cache) is a Uop Cache where the front-en… 87 … Commonly used instructions are optimized for delivery by the DSB (decoded i-cache) or MITE (legac… 92 "MetricExpr": "max(0, tma_frontend_bound - tma_fetch_latency)", 100 "MetricExpr": "(IDQ.MITE_CYCLES_ANY - IDQ.MITE_CYCLES_OK) / CORE_CLKS / 2", [all …]
/Linux-v6.1/tools/perf/pmu-events/arch/x86/haswell/
D	hsw-metrics.json	7 …on by the Backend part. Within the Frontend; a branch predictor predicts the next address to fetch… 15 …he CPU was stalled due to Frontend latency issues. For example; instruction-cache misses; iTLB mi… 38 … corrected path; following all sorts of miss-predicted branches. For example; branchy code with lo… 46 …o switches from DSB to MITE pipelines. The DSB (decoded i-cache) is a Uop Cache where the front-en… 62 … Commonly used instructions are optimized for delivery by the DSB (decoded i-cache) or MITE (legac… 67 "MetricExpr": "tma_frontend_bound - tma_fetch_latency", 75 "MetricExpr": "(IDQ.ALL_MITE_CYCLES_ANY_UOPS - IDQ.ALL_MITE_CYCLES_4_UOPS) / CORE_CLKS / 2", 78 …the legacy decode pipeline). This pipeline is used for code that was not pre-cached in the DSB or … 83 "MetricExpr": "(IDQ.ALL_DSB_CYCLES_ANY_UOPS - IDQ.ALL_DSB_CYCLES_4_UOPS) / CORE_CLKS / 2", 91 …"MetricExpr": "(UOPS_ISSUED.ANY - UOPS_RETIRED.RETIRE_SLOTS + 4 * ((INT_MISC.RECOVERY_CYCLES_ANY /… [all …]
/Linux-v6.1/tools/perf/pmu-events/arch/x86/ivybridge/
D	ivb-metrics.json	7 …on by the Backend part. Within the Frontend; a branch predictor predicts the next address to fetch… 15 …he CPU was stalled due to Frontend latency issues. For example; instruction-cache misses; iTLB mi… 20 "MetricExpr": "ICACHE.IFETCH_STALL / CLKS - tma_itlb_misses", 38 … corrected path; following all sorts of miss-predicted branches. For example; branchy code with lo… 46 …o switches from DSB to MITE pipelines. The DSB (decoded i-cache) is a Uop Cache where the front-en… 62 … Commonly used instructions are optimized for delivery by the DSB (decoded i-cache) or MITE (legac… 67 "MetricExpr": "tma_frontend_bound - tma_fetch_latency", 75 "MetricExpr": "(IDQ.ALL_MITE_CYCLES_ANY_UOPS - IDQ.ALL_MITE_CYCLES_4_UOPS) / CORE_CLKS / 2", 78 …the legacy decode pipeline). This pipeline is used for code that was not pre-cached in the DSB or … 83 "MetricExpr": "(IDQ.ALL_DSB_CYCLES_ANY_UOPS - IDQ.ALL_DSB_CYCLES_4_UOPS) / CORE_CLKS / 2", [all …]
/Linux-v6.1/drivers/net/wireless/ti/wlcore/
D	conf.h	`1 /* SPDX-License-Identifier: GPL-2.0-only / 117 Range: 0 - 0xFFFFFFFF 130 * after a PS-poll has been transmitted. 132 * Range: 0 - 200000 139 * Range: 0 - 200000 147 * Range: 0 - 4096 161 * Occupied Rx mem-blocks number which requires interrupting the host 177 * Max time in msec the FW may delay RX-Complete interrupt. 179 * Range: 1 - 100 203 * of the 22Mbps rate. There is a FW limitation on 12 rates so we must drop [all …]`
/Linux-v6.1/tools/perf/pmu-events/arch/x86/cascadelakex/
D	clx-metrics.json	7 …on by the Backend part. Within the Frontend; a branch predictor predicts the next address to fetch… 15 …he CPU was stalled due to Frontend latency issues. For example; instruction-cache misses; iTLB mi… 39 … corrected path; following all sorts of miss-predicted branches. For example; branchy code with lo… 52 …"MetricExpr": "(1 - (BR_MISP_RETIRED.ALL_BRANCHES / (BR_MISP_RETIRED.ALL_BRANCHES + MACHINE_CLEARS… 71 …o switches from DSB to MITE pipelines. The DSB (decoded i-cache) is a Uop Cache where the front-en… 87 … Commonly used instructions are optimized for delivery by the DSB (decoded i-cache) or MITE (legac… 92 "MetricExpr": "tma_frontend_bound - tma_fetch_latency", 100 "MetricExpr": "(IDQ.ALL_MITE_CYCLES_ANY_UOPS - IDQ.ALL_MITE_CYCLES_4_UOPS) / CORE_CLKS / 2", 103 …the legacy decode pipeline). This pipeline is used for code that was not pre-cached in the DSB or … 107 …"BriefDescription": "This metric represents fraction of cycles where decoder-0 was the only active… [all …]
/Linux-v6.1/Documentation/userspace-api/media/drivers/
D	imx-uapi.rst	`1 .. SPDX-License-Identifier: GPL-2.0 13 --------- 18 - V4L2_EVENT_IMX_FRAME_INTERVAL_ERROR 22 (see below for more on the FIM). 30 ----------------------------------- 33 NTSC/PAL signal re-sync (too little or too many video lines). When 34 this happens, the IPU triggers a mechanism to re-establish vertical 52 the FIM event notification on the ipuX_csiY subdev device node. 60 - V4L2_CID_IMX_FIM_ENABLE 64 - V4L2_CID_IMX_FIM_NUM [all …]`
/Linux-v6.1/Documentation/admin-guide/pm/
D	cpufreq_drivers.rst	1 .. SPDX-License-Identifier: GPL-2.0 21 there is a different cpu-freq driver for each generation. 23 Note that the driver's will not load on the "wrong" hardware, 29 to load on processors without this capability. The capability 37 6th Generation: powernow-k6 39 7th Generation: powernow-k7: Athlon, Duron, Geode. 41 8th Generation: powernow-k8: Athlon, Athlon 64, Opteron, Sempron. 42 Documentation on this functionality in 8th generation processors 46 BIOS supplied data, for powernow-k7 and for powernow-k8, may be 49 The powernow-k8 driver will attempt to use ACPI if so configured, [all …]

12 3 4 5 6 7 8 9 10 >>...26