| /Linux-v5.10/drivers/input/mouse/ |
| D | elantech.c | 624 int pres, traces; in process_packet_head_v4() local
632 traces = (packet[0] & 0xf0) >> 4; in process_packet_head_v4()
640 input_report_abs(dev, ABS_MT_TOUCH_MAJOR, traces * etd->width); in process_packet_head_v4()
642 input_report_abs(dev, ABS_TOOL_WIDTH, traces); in process_packet_head_v4()
1600 unsigned char traces; in elantech_query_info() local
1731 traces = info->capabilities[1]; in elantech_query_info()
1732 if ((traces < 2) || (traces > info->x_max)) in elantech_query_info()
1735 info->width = info->x_max / (traces - 1); in elantech_query_info()
1738 info->x_traces = traces; in elantech_query_info()
1741 traces = info->capabilities[2]; in elantech_query_info()
[all …]
|
| /Linux-v5.10/kernel/trace/ |
| D | Makefile | 84 obj-$(CONFIG_TRACEPOINTS) += power-traces.o
86 obj-$(CONFIG_TRACEPOINTS) += rpm-traces.o
|
| /Linux-v5.10/drivers/md/persistent-data/ |
| D | dm-block-manager.c | 50 struct stack_store traces[MAX_HOLDERS]; member
85 t = lock->traces + h; in __add_holder()
107 stack_trace_print(lock->traces[i].entries, in __check_holder()
108 lock->traces[i].nr_entries, 4); in __check_holder()
|
| /Linux-v5.10/drivers/misc/genwqe/ |
| D | card_utils.c | 832 int entries = 0, ring, traps, traces, trace_entries; in genwqe_ffdc_buff_size() local
872 traces = (val >> 16) & 0xff; in genwqe_ffdc_buff_size()
875 entries += traps + (traces * trace_entries); in genwqe_ffdc_buff_size()
890 int i, traps, traces, trace, trace_entries, trace_entry, ring; in genwqe_ffdc_buff_read() local
941 traces = (val >> 16) & 0xff; /* Number of Traces */ in genwqe_ffdc_buff_read()
947 for (trace = 0; trace <= traces; trace++) { in genwqe_ffdc_buff_read()
|
| /Linux-v5.10/tools/objtool/Documentation/ |
| D | stack-validation.txt | 12 that stack traces can be reliable.
33 a) More reliable stack traces for frame pointer enabled kernels
51 For stack traces based on frame pointers to be reliable, all
110 stack traces need to be reliable (or an unreliable condition needs to
142 This rule ensures that frame pointer based stack traces will work as
216 If you're 100% sure the code won't affect stack traces, or if you're
342 that it won't affect kernel stack traces, you can tell objtool to
|
| /Linux-v5.10/drivers/iommu/ |
| D | Makefile | 4 obj-$(CONFIG_IOMMU_API) += iommu-traces.o
|
| /Linux-v5.10/net/core/ |
| D | Makefile | 23 obj-$(CONFIG_TRACEPOINTS) += net-traces.o
|
| /Linux-v5.10/Documentation/hwmon/ |
| D | max31730.rst | 25 for high series resistance in circuit-board traces and the external thermal
|
| /Linux-v5.10/arch/x86/ |
| D | Kconfig.debug | 240 traces for panics, oopses, bugs, warnings, perf, /proc/<pid>/stack,
249 unwinding kernel stack traces. It uses a custom data format which is
264 stack traces.
276 traces. It scans the stack and reports every kernel text address it
|
| /Linux-v5.10/Documentation/trace/ |
| D | function-graph-fold.vim | 1 " Enable folding for ftrace function_graph traces.
|
| D | intel_th.rst | 96 # .. wait for traces to pile up ..
117 software traces to the Software Trace Hub (an stm class device). The
|
| /Linux-v5.10/arch/xtensa/ |
| D | Kconfig.debug | 40 prints in stack traces.
|
| /Linux-v5.10/drivers/isdn/capi/ |
| D | Kconfig | 21 If you say Y here, the kernelcapi driver can make verbose traces
|
| /Linux-v5.10/Documentation/admin-guide/kdump/ |
| D | gdbmacros.txt | 3 # useful information from kernel crashdump (kdump) like stack traces of
55 dump all thread stack traces on a kernel compiled with !CONFIG_FRAME_POINTER
101 dump all thread stack traces on a kernel compiled with CONFIG_FRAME_POINTER
|
| /Linux-v5.10/Documentation/usb/ |
| D | usbmon.rst | 9 used to collect traces of I/O on the USB bus. This function is analogous
12 USBMon (with uppercase letters) is used to examine raw traces produced
16 Controller Drivers (HCD). So, if HCD is buggy, the traces reported by
24 How to use usbmon to collect raw text traces
27 Unlike the packet socket, usbmon has an interface which provides traces
|
| /Linux-v5.10/Documentation/networking/device_drivers/atm/ |
| D | iphase.rst | 128 IADebugFlag, which controls the output of the traces. You can find the bit
132 traces together with loading the driver.
|
| /Linux-v5.10/Documentation/core-api/irq/ |
| D | irqflags-tracing.rst | 7 The "irq-flags tracing" feature "traces" hardirq and softirq state, in
|
| /Linux-v5.10/drivers/hwtracing/intel_th/ |
| D | Kconfig | 65 storing STP traces to system memory. It supports single
|
| /Linux-v5.10/include/linux/ |
| D | remoteproc.h | 529 struct list_head traces; member
|
| /Linux-v5.10/arch/arm/boot/dts/ |
| D | ls1021a-tsn.dts | 118 /* RGMII delays added via PCB traces */
|
| D | sun8i-a83t-allwinner-h8homlet-v2.dts | 233 * Set a 100ms delay to account for PMIC ramp time and board traces.
|
| /Linux-v5.10/Documentation/devicetree/bindings/net/dsa/ |
| D | sja1105.txt | 48 the fixed-link, or by PCB serpentine traces on the board.
|
| /Linux-v5.10/net/batman-adv/ |
| D | Kconfig | 117 say N here. Select this option to gather traces like the debug
|
| /Linux-v5.10/tools/perf/Documentation/ |
| D | perf-script.txt | 413 Show instruction stream for intel_pt traces. Combine with --xed to
428 Show call stream for intel_pt traces. The CPUs are interleaved, but
432 Show call and return stream for intel_pt traces.
|
| /Linux-v5.10/Documentation/RCU/ |
| D | stallwarn.rst | 110 To diagnose the cause of the stall, inspect the stack traces.
113 comparing the stack traces can often help determine where the stall
166 own warnings, as this often gives better-quality stack traces.
|
