Home
last modified time | relevance | path

Searched refs:fuzz (Results 1 – 34 of 34) sorted by relevance

/linux-4.1.27/drivers/input/touchscreen/
Dof_touchscreen.c29 int max, int fuzz) in touchscreen_set_params() argument
46 absinfo->fuzz = fuzz; in touchscreen_set_params()
60 u32 maximum, fuzz; in touchscreen_parse_of_params() local
67 fuzz = of_get_optional_u32(np, "touchscreen-fuzz-x"); in touchscreen_parse_of_params()
68 if (maximum || fuzz) { in touchscreen_parse_of_params()
69 touchscreen_set_params(dev, ABS_X, maximum, fuzz); in touchscreen_parse_of_params()
70 touchscreen_set_params(dev, ABS_MT_POSITION_X, maximum, fuzz); in touchscreen_parse_of_params()
74 fuzz = of_get_optional_u32(np, "touchscreen-fuzz-y"); in touchscreen_parse_of_params()
75 if (maximum || fuzz) { in touchscreen_parse_of_params()
76 touchscreen_set_params(dev, ABS_Y, maximum, fuzz); in touchscreen_parse_of_params()
[all …]
/linux-4.1.27/Documentation/devicetree/bindings/input/touchscreen/
Dtouchscreen.txt10 - touchscreen-fuzz-x : horizontal noise value of the absolute input
12 - touchscreen-fuzz-y : vertical noise value of the absolute input
14 - touchscreen-fuzz-pressure : pressure noise value of the absolute input
26 touchscreen-fuzz-x and touchscreen-fuzz-y
27 - contact-threshold : deprecated name for touchscreen-fuzz-pressure
Dtsc2007.txt17 - ti,fuzzx: specifies the absolute input fuzz x value.
18 If set, it will permit noise in the data up to +- the value given to the fuzz
20 - ti,fuzzy: specifies the absolute input fuzz y value.
21 - ti,fuzzz: specifies the absolute input fuzz z value.
Dtsc2005.txt32 touchscreen-fuzz-x = <4>;
33 touchscreen-fuzz-y = <7>;
34 touchscreen-fuzz-pressure = <2>;
Dchipone_icn8318.txt17 - touchscreen-fuzz-x : horizontal noise value of the absolute input
19 - touchscreen-fuzz-y : vertical noise value of the absolute input
Dbrcm,iproc-touchscreen.txt49 - touchscreen-fuzz-x: horizontal noise value of the absolute input
51 - touchscreen-fuzz-y: vertical noise value of the absolute input
/linux-4.1.27/Documentation/input/
Dgameport-programming.txt88 gameport.fuzz = 8;
91 The only confusing thing here is the fuzz value. Best determined by
93 gameports can set this to zero, most common have fuzz between 8 and 32.
94 See analog.c and input.c for handling of fuzz - the fuzz value determines
137 int fuzz;
Dgpio-tilt.txt75 .fuzz = 0,
/linux-4.1.27/drivers/input/mouse/
Dappletouch.c51 int fuzz; /* fuzz touchpad generates */ member
65 .fuzz = 16,
76 .fuzz = 16,
87 .fuzz = 0,
97 .fuzz = 0,
107 .fuzz = 0,
516 dev->info->fuzz, 0); in atp_detect_size()
919 dev->info->fuzz, 0); in atp_probe()
922 dev->info->fuzz, 0); in atp_probe()
Dsynaptics.c1158 int fuzz = SYN_CAP_REDUCED_FILTERING(priv->ext_cap_0c) ? in set_abs_position_params() local
1161 input_set_abs_params(dev, x_code, x_min, x_max, fuzz, 0); in set_abs_position_params()
1162 input_set_abs_params(dev, y_code, y_min, y_max, fuzz, 0); in set_abs_position_params()
Dbcm5974.c451 int fuzz = p->snratio ? (p->max - p->min) / p->snratio : 0; in set_abs() local
452 input_set_abs_params(input, code, p->min, p->max, fuzz, 0); in set_abs()
/linux-4.1.27/include/linux/input/
Dgpio_tilt.h16 int fuzz; member
/linux-4.1.27/include/linux/
Dinput.h441 int min, int max, int fuzz, int flat);
461 INPUT_GENERATE_ABS_ACCESSORS(fuzz, fuzz)
Dgameport.h28 int fuzz; member
/linux-4.1.27/include/uapi/linux/
Dvirtio_input.h45 __u32 fuzz; member
Dinput.h71 __s32 fuzz; member
/linux-4.1.27/drivers/misc/lis3lv02d/
Dlis3lv02d.c686 int max_val, fuzz, flat; in lis3lv02d_joystick_enable() local
714 fuzz = LIS3_DEFAULT_FUZZ_12B; in lis3lv02d_joystick_enable()
717 fuzz = LIS3_DEFAULT_FUZZ_8B; in lis3lv02d_joystick_enable()
720 fuzz = (fuzz * lis3->scale) / LIS3_ACCURACY; in lis3lv02d_joystick_enable()
723 input_set_abs_params(input_dev, ABS_X, -max_val, max_val, fuzz, flat); in lis3lv02d_joystick_enable()
724 input_set_abs_params(input_dev, ABS_Y, -max_val, max_val, fuzz, flat); in lis3lv02d_joystick_enable()
725 input_set_abs_params(input_dev, ABS_Z, -max_val, max_val, fuzz, flat); in lis3lv02d_joystick_enable()
/linux-4.1.27/drivers/input/
Dinput.c59 static int input_defuzz_abs_event(int value, int old_val, int fuzz) in input_defuzz_abs_event() argument
61 if (fuzz) { in input_defuzz_abs_event()
62 if (value > old_val - fuzz / 2 && value < old_val + fuzz / 2) in input_defuzz_abs_event()
65 if (value > old_val - fuzz && value < old_val + fuzz) in input_defuzz_abs_event()
68 if (value > old_val - fuzz * 2 && value < old_val + fuzz * 2) in input_defuzz_abs_event()
249 dev->absinfo[code].fuzz); in input_handle_abs_event()
493 int min, int max, int fuzz, int flat) in input_set_abs_params() argument
504 absinfo->fuzz = fuzz; in input_set_abs_params()
Dinput-mt.c21 dev->absinfo[dst].fuzz = 0; in copy_abs()
/linux-4.1.27/drivers/input/joystick/
Danalog.c131 int fuzz; member
511 input_set_abs_params(input_dev, t, v, (x << 1) - v, port->fuzz, w); in analog_init_device()
630 port->fuzz = (port->speed * ANALOG_FUZZ_MAGIC) / port->loop / 1000 + ANALOG_FUZZ_BITS; in analog_init_port()
669 port->fuzz = gameport->fuzz; in analog_init_port()
Dsidewinder.c763 int min, max, fuzz, flat; in sw_connect() local
768 fuzz = (bits >> 1) >= 2 ? 1 << ((bits >> 1) - 2) : 0; in sw_connect()
773 min, max, fuzz, flat); in sw_connect()
Da3d.c368 adc->fuzz = 1; in a3d_connect()
/linux-4.1.27/sound/pci/au88x0/
Dau88x0_game.c116 gp->fuzz = 64; in vortex_gameport_register()
/linux-4.1.27/drivers/input/misc/
Dgpio_tilt_polled.c152 pdata->axes[i].fuzz, pdata->axes[i].flat); in gpio_tilt_polled_probe()
/linux-4.1.27/arch/arm64/
DKconfig.debug51 fuzz-test bootloaders which respect text_offset.
/linux-4.1.27/Documentation/
Dapplying-patches.txt114 it'll tell you about it by saying the patch applied with 'fuzz'.
119 When patch encounters a change that it can't fix up with fuzz it rejects it
127 never see a fuzz or reject message from patch. If you do see such messages
142 If you get "Hunk #2 succeeded at 1887 with fuzz 2 (offset 7 lines)." or a
153 fuzz its way through. This will generate a .rej file with the change that
/linux-4.1.27/arch/arm/boot/dts/
Domap3-n900.dts832 touchscreen-fuzz-x = <4>;
833 touchscreen-fuzz-y = <7>;
834 touchscreen-fuzz-pressure = <2>;
/linux-4.1.27/drivers/virtio/
Dvirtio_input.c162 virtio_cread(vi->vdev, struct virtio_input_config, u.abs.fuzz, &fu); in virtinput_cfg_abs()
/linux-4.1.27/drivers/hid/
Dhid-multitouch.c369 int fuzz = snratio ? (fmax - fmin) / snratio : 0; in set_abs() local
370 input_set_abs_params(input, code, fmin, fmax, fuzz, 0); in set_abs()
Dwacom_wac.c1342 struct hid_field *field, __u8 type, __u16 code, int fuzz) in wacom_map_usage() argument
1356 input_set_abs_params(input, code, fmin, fmax, fuzz, 0); in wacom_map_usage()
/linux-4.1.27/sound/pci/
Dazt3328.c1841 gp->fuzz = 16; /* seems ok */ in snd_azf3328_gameport()
/linux-4.1.27/Documentation/cgroups/
Dmemory.txt563 method and doesn't show 'exact' value of memory (and swap) usage, it's a fuzz
/linux-4.1.27/sound/pci/trident/
Dtrident_main.c3197 gp->fuzz = 64; in snd_trident_create_gameport()
/linux-4.1.27/
DCREDITS1751 D: 'Trinity' and similar fuzz testing work.