approaching (full) in projects: Linux-v6.1

Project(s)

Full Search
Definition
Symbol
File Path
History
Type

Searched full:approaching (Results 1 – 25 of 35) sorted by relevance

/Linux-v6.1/Documentation/input/
D	multi-touch-protocol.rst	174 of the contact area and approaching tool, respectively. 181 ABS_MT_POSITION_X/Y and the center of the approaching finger (b) is 244 The length, in surface units, of the major axis of the approaching 246 orientation of the contact and the approaching tool are assumed to be the 250 The length, in surface units, of the minor axis of the approaching 300 The surface X coordinate of the center of the approaching tool. Omit if 305 The surface Y coordinate of the center of the approaching tool. Omit if the 315 The type of approaching tool. A lot of kernel drivers cannot distinguish
/Linux-v6.1/Documentation/devicetree/bindings/regulator/
D	regulator.yaml	`135 is assumed still to be functional but approaching limit where it gets 156 is assumed still to be functional but approaching limit where it gets 178 hardware is assumed still to be functional but approaching limit where 198 hardware is assumed still to be functional but approaching limit where it`
/Linux-v6.1/drivers/misc/echo/
D	fir.h	`29 reduced. A drop in MIPs and memory approaching 50% should be`
/Linux-v6.1/include/linux/
D	firmware.h	`29 * @FW_UPLOAD_ERR_WEAROUT: FLASH device is approaching wear-out, wait & retry`
/Linux-v6.1/Documentation/process/
D	code-of-conduct-interpretation.rst	`53 uncertain about approaching the TAB or any other maintainers, please`
D	2.Process.rst	`41 this time, at a rate approaching 1,000 changes ("patches," or "changesets")`
/Linux-v6.1/tools/perf/pmu-events/arch/x86/sandybridge/
D	snb-metrics.json	`131 …fraction of cycles where the core's performance was likely hurt due to approaching bandwidth limit… 135 …fraction of cycles where the core's performance was likely hurt due to approaching bandwidth limit…`
/Linux-v6.1/tools/perf/pmu-events/arch/x86/jaketown/
D	jkt-metrics.json	`131 …fraction of cycles where the core's performance was likely hurt due to approaching bandwidth limit… 135 …fraction of cycles where the core's performance was likely hurt due to approaching bandwidth limit…`
/Linux-v6.1/tools/perf/pmu-events/arch/x86/haswell/
D	hsw-metrics.json	`182 …ses are satisfied from (metric values >1 are valid). Often it hints on approaching bandwidth limit… 242 …fraction of cycles where the core's performance was likely hurt due to approaching bandwidth limit… 246 …fraction of cycles where the core's performance was likely hurt due to approaching bandwidth limit…`
/Linux-v6.1/tools/perf/pmu-events/arch/x86/ivybridge/
D	ivb-metrics.json	`182 …ses are satisfied from (metric values >1 are valid). Often it hints on approaching bandwidth limit… 242 …fraction of cycles where the core's performance was likely hurt due to approaching bandwidth limit… 246 …fraction of cycles where the core's performance was likely hurt due to approaching bandwidth limit…`
/Linux-v6.1/arch/sparc/kernel/
D	wof.S	`132 * are approaching the infamous register window trap handling`
/Linux-v6.1/tools/perf/pmu-events/arch/x86/ivytown/
D	ivt-metrics.json	`182 …ses are satisfied from (metric values >1 are valid). Often it hints on approaching bandwidth limit… 242 …fraction of cycles where the core's performance was likely hurt due to approaching bandwidth limit… 246 …fraction of cycles where the core's performance was likely hurt due to approaching bandwidth limit…`
/Linux-v6.1/tools/perf/pmu-events/arch/x86/broadwell/
D	bdw-metrics.json	`204 …ses are satisfied from (metric values >1 are valid). Often it hints on approaching bandwidth limit… 264 …fraction of cycles where the core's performance was likely hurt due to approaching bandwidth limit… 268 …fraction of cycles where the core's performance was likely hurt due to approaching bandwidth limit…`
/Linux-v6.1/tools/perf/pmu-events/arch/x86/broadwellde/
D	bdwde-metrics.json	`207 …ses are satisfied from (metric values >1 are valid). Often it hints on approaching bandwidth limit… 267 …fraction of cycles where the core's performance was likely hurt due to approaching bandwidth limit… 271 …fraction of cycles where the core's performance was likely hurt due to approaching bandwidth limit…`
/Linux-v6.1/fs/ceph/
D	quota.c	`307 limit is approaching */`
/Linux-v6.1/tools/perf/pmu-events/arch/x86/haswellx/
D	hsx-metrics.json	`182 …ses are satisfied from (metric values >1 are valid). Often it hints on approaching bandwidth limit… 242 …fraction of cycles where the core's performance was likely hurt due to approaching bandwidth limit… 246 …fraction of cycles where the core's performance was likely hurt due to approaching bandwidth limit…`
/Linux-v6.1/drivers/iio/cdc/
D	ad7150.c	`72 * 7:4 are for timeout approaching - applies if above upper threshold`
/Linux-v6.1/tools/perf/pmu-events/arch/x86/broadwellx/
D	bdx-metrics.json	`204 …ses are satisfied from (metric values >1 are valid). Often it hints on approaching bandwidth limit… 264 …fraction of cycles where the core's performance was likely hurt due to approaching bandwidth limit… 268 …fraction of cycles where the core's performance was likely hurt due to approaching bandwidth limit…`
/Linux-v6.1/tools/perf/pmu-events/arch/x86/skylake/
D	skl-metrics.json	`228 …ses are satisfied from (metric values >1 are valid). Often it hints on approaching bandwidth limit… 288 …fraction of cycles where the core's performance was likely hurt due to approaching bandwidth limit… 292 …fraction of cycles where the core's performance was likely hurt due to approaching bandwidth limit…`
/Linux-v6.1/arch/x86/math-emu/
D	README	`77 even for arguments approaching 2^63. This is far superior to an`
/Linux-v6.1/tools/perf/pmu-events/arch/x86/icelake/
D	icl-metrics.json	`243 …ses are satisfied from (metric values >1 are valid). Often it hints on approaching bandwidth limit… 303 …fraction of cycles where the core's performance was likely hurt due to approaching bandwidth limit… 307 …fraction of cycles where the core's performance was likely hurt due to approaching bandwidth limit…`
/Linux-v6.1/tools/perf/pmu-events/arch/x86/tigerlake/
D	tgl-metrics.json	`243 …ses are satisfied from (metric values >1 are valid). Often it hints on approaching bandwidth limit… 303 …fraction of cycles where the core's performance was likely hurt due to approaching bandwidth limit… 307 …fraction of cycles where the core's performance was likely hurt due to approaching bandwidth limit…`
/Linux-v6.1/tools/perf/pmu-events/arch/x86/icelakex/
D	icx-metrics.json	`235 …ses are satisfied from (metric values >1 are valid). Often it hints on approaching bandwidth limit… 295 …fraction of cycles where the core's performance was likely hurt due to approaching bandwidth limit… 299 …fraction of cycles where the core's performance was likely hurt due to approaching bandwidth limit…`
/Linux-v6.1/tools/perf/pmu-events/arch/x86/cascadelakex/
D	clx-metrics.json	`228 …ses are satisfied from (metric values >1 are valid). Often it hints on approaching bandwidth limit… 288 …fraction of cycles where the core's performance was likely hurt due to approaching bandwidth limit… 292 …fraction of cycles where the core's performance was likely hurt due to approaching bandwidth limit…`
/Linux-v6.1/tools/perf/pmu-events/arch/x86/skylakex/
D	skx-metrics.json	`228 …ses are satisfied from (metric values >1 are valid). Often it hints on approaching bandwidth limit… 288 …fraction of cycles where the core's performance was likely hurt due to approaching bandwidth limit… 292 …fraction of cycles where the core's performance was likely hurt due to approaching bandwidth limit…`