| /linux-4.1.27/Documentation/input/ |
| D | multi-touch-protocol.txt | 11 objects in direct contact with the device surface, is needed. This
26 events. Only the ABS_MT events are recognized as part of a contact
31 Drivers for type A devices separate contact packets by calling
34 contact and prepare to receive another.
36 Drivers for type B devices separate contact packets by calling
58 identified contact, and use that slot to propagate changes for the contact.
61 is interpreted as a contact, and the value -1 denotes an unused slot. A
64 the full state of each initiated contact has to reside in the receiving
70 contact that is reported by the hardware. Whenever the identity of the
71 contact associated with a slot changes, the driver should invalidate that
[all …]
|
| D | ntrig.txt | 33 deactivate_slack the number of "no contact" frames to ignore before
67 seeing both inappropriately dropped contact and ghosts, contacts reported
70 Deactivation slack helps prevent dropped contact for single touch use, but does
78 of events the more likely those events are from a real contact, and that the
79 larger the size of each contact the more likely it is real. Balancing the
90 contact immediately overrides the waiting period and leads to activation.
108 The calibration of these devices does drift over time. If ghosts or contact
|
| D | event-codes.txt | 115 BTN_TOUCH is used for touch contact. While an input tool is determined to be
116 within meaningful physical contact, the value of this property must be set
117 to 1. Meaningful physical contact may mean any contact, or it may mean
118 contact conditioned by an implementation defined property. For example, a
321 contact. BTN_TOOL_<name> events should be reported where possible.
341 should be used to report when the tool is in contact with the tablet.
|
| D | alps.txt | 179 occasionally it's seen with only a single contact).
223 3) There doesn't seem to be a count of the contact points anywhere in the v4
224 protocol packets. Deriving a count of contact points must be done by
229 the count of contact points can only be updated every third packet as
|
| D | iforce-protocol.txt | 6 This is not a reference. Comments and corrections are welcome. To contact me,
|
| D | ff.txt | 218 a really good reason to use this, please contact
|
| D | joystick.txt | 22 Should you need to contact me, the author, you can do so either by e-mail
342 If you have one of these, contact me.
|
| D | input.txt | 22 Should you need to contact me, the author, you can do so either by e-mail
|
| /linux-4.1.27/Documentation/ABI/testing/ |
| D | sysfs-devices-soc | 3 contact: Lee Jones <lee.jones@linaro.org>
17 contact: Lee Jones <lee.jones@linaro.org>
24 contact: Lee Jones <lee.jones@linaro.org>
31 contact: Lee Jones <lee.jones@linaro.org>
38 contact: Lee Jones <lee.jones@linaro.org>
45 contact: Lee Jones <lee.jones@linaro.org>
52 contact: Lee Jones <lee.jones@linaro.org>
|
| D | sysfs-cfq-target-latency | 3 contact: Tao Ma <boyu.mt@taobao.com>
|
| D | sysfs-bus-iio | 138 between ambient (reference) and distant temperature for contact-
|
| /linux-4.1.27/Documentation/misc-devices/mei/ |
| D | mei-client-bus.txt | 61 As a theoretical example let's pretend the ME comes with a "contact" NFC IP.
64 #define CONTACT_DRIVER_NAME "contact"
107 struct contact_driver *contact;
112 mei_cl_register_event_cb(dev, contact_event_cb, contact);
128 struct contact_driver *contact = context;
139 nfc_hci_recv_frame(contact->hdev, payload, payload_size);
|
| /linux-4.1.27/Documentation/devicetree/bindings/input/touchscreen/ |
| D | mms114.txt | 11 - contact-threshold:
27 contact-threshold = <10>;
|
| D | touchscreen.txt | 27 - contact-threshold : deprecated name for touchscreen-fuzz-pressure
|
| /linux-4.1.27/drivers/iio/temperature/ |
| D | Kconfig | 7 tristate "MLX90614 contact-less infrared sensor"
11 MLX90614 contact-less infrared sensor connected with I2C.
|
| /linux-4.1.27/drivers/input/mouse/ |
| D | cypress_ps2.c | 524 struct cytp_contact *contact; in cypress_process_packet() local
536 contact = &report_data.contacts[i]; in cypress_process_packet()
537 pos[i].x = contact->x; in cypress_process_packet()
538 pos[i].y = contact->y; in cypress_process_packet()
544 contact = &report_data.contacts[i]; in cypress_process_packet()
547 input_report_abs(input, ABS_MT_POSITION_X, contact->x); in cypress_process_packet()
548 input_report_abs(input, ABS_MT_POSITION_Y, contact->y); in cypress_process_packet()
549 input_report_abs(input, ABS_MT_PRESSURE, contact->z); in cypress_process_packet()
|
| /linux-4.1.27/Documentation/usb/ |
| D | usb-serial.txt | 44 For any questions or problems with this driver, please contact
88 For any questions or problems with this driver, please contact Greg
139 For any questions or problems with the driver, please contact Ganesh
167 For any questions or problems with this driver, please contact Brian
189 For any questions or problems with this driver, please contact Hugh
201 For any questions or problems with this driver, please contact Bill Ryder.
261 contact me here via email:
282 Please contact Peter Berger (pberger@brimson.com) or Al Borchers
319 For any questions or problems with this driver, please contact William
333 For any questions or problems with this driver, please contact Gary
[all …]
|
| D | acm.txt | 22 Should you need to contact me, the author, you can do so either by e-mail
|
| D | gadget_serial.txt | 28 please contact Al Borchers at alborchers@steinerpoint.com.
|
| /linux-4.1.27/Documentation/devicetree/bindings/input/ |
| D | imx-keypad.txt | 3 The KPP is designed to interface with a keypad matrix with 2-point contact
4 or 3-point contact keys. The KPP is designed to simplify the software task
|
| /linux-4.1.27/Documentation/arm/SA1100/ |
| D | Victor | 14 For any comments, please feel free to contact me through the above
|
| D | ADSBitsy | 4 For more details, contact Applied Data Systems or see
|
| D | GraphicsMaster | 3 For more details, contact Applied Data Systems or see
|
| D | GraphicsClient | 3 For more details, contact Applied Data Systems or see
|
| /linux-4.1.27/Documentation/zh_CN/ |
| D | SecurityBugs | 3 If you have any comment or update to the content, please contact the
|
| D | stable_kernel_rules.txt | 3 If you have any comment or update to the content, please contact the
|
| D | IRQ.txt | 3 If you have any comment or update to the content, please contact the
|
| D | stable_api_nonsense.txt | 3 If you have any comment or update to the content, please contact the
|
| D | io_ordering.txt | 3 If you have any comment or update to the content, please contact the
|
| D | sparse.txt | 3 If you have any comment or update to the content, please contact the
|
| D | volatile-considered-harmful.txt | 3 If you have any comment or update to the content, please contact the
|
| D | SubmittingDrivers | 3 If you have any comment or update to the content, please contact the
|
| D | email-clients.txt | 3 If you have any comment or update to the content, please contact the
|
| D | oops-tracing.txt | 3 If you have any comment or update to the content, please contact the
|
| D | SubmittingPatches | 3 If you have any comment or update to the content, please contact the
|
| D | HOWTO | 3 If you have any comment or update to the content, please contact the
|
| D | gpio.txt | 3 If you have any comment or update to the content, please contact the
|
| /linux-4.1.27/Documentation/hwmon/ |
| D | mcp3021 | 28 available. The default I2C device address is 0x4d (contact the Microchip
|
| D | lm83 | 34 contact us. Note that the LM90 can easily be misdetected as a LM83.
|
| D | w83792d | 112 contact us.
|
| D | it87 | 96 to fix this. Please contact your BIOS manufacturer and ask him for fix.
|
| D | w83781d | 395 Please contact us if you can figure out how it is supposed to work. As
|
| /linux-4.1.27/Documentation/zh_CN/arm64/ |
| D | tagged-pointers.txt | 3 If you have any comment or update to the content, please contact the
|
| D | legacy_instructions.txt | 3 If you have any comment or update to the content, please contact the
|
| D | memory.txt | 3 If you have any comment or update to the content, please contact the
|
| D | booting.txt | 3 If you have any comment or update to the content, please contact the
|
| /linux-4.1.27/arch/powerpc/boot/dts/ |
| D | sbc8548-pre.dtsi | 6 * Paul Gortmaker (see MAINTAINERS for contact information)
|
| D | sbc8548.dts | 6 * Paul Gortmaker (see MAINTAINERS for contact information)
|
| D | sbc8548-altflash.dts | 9 * Paul Gortmaker (see MAINTAINERS for contact information)
|
| D | sbc8349.dts | 6 * Paul Gortmaker (see MAINTAINERS for contact information)
|
| D | sbc8548-post.dtsi | 6 * Paul Gortmaker (see MAINTAINERS for contact information)
|
| D | sbc8641d.dts | 6 * Paul Gortmaker (see MAINTAINERS for contact information)
|
| /linux-4.1.27/Documentation/ko_KR/ |
| D | stable_api_nonsense.txt | 6 a problem with the translation, please contact the maintainer of this file.
|
| D | HOWTO | 5 a problem with the translation, please contact the maintainer of this file.
|
| /linux-4.1.27/Documentation/ |
| D | SubmittingDrivers | 39 maintainer then please contact Willy Tarreau <w@1wt.eu>.
43 to track changes in API's. The final contact point for Linux 2.6
107 If you want to be the contact and update point for the
|
| D | CodeOfConflict | 17 please contact the Linux Foundation's Technical Advisory Board at
|
| D | unicode.txt | 93 For more information, contact them at:
|
| D | HOWTO | 62 contact a lawyer, and do not ask on the Linux kernel mailing list. The
|
| D | devices.txt | 46 where that applies (e.g. busmice), please contact me with the
1203 This is a commercial driver; contact James Howes
|
| /linux-4.1.27/Documentation/zh_CN/arm/ |
| D | Booting | 3 If you have any comment or update to the content, please contact the
|
| D | kernel_user_helpers.txt | 3 If you have any comment or update to the content, please contact the
|
| /linux-4.1.27/Documentation/ja_JP/ |
| D | stable_kernel_rules.txt | 6 please contact maintainer of this file or JF project.
|
| D | stable_api_nonsense.txt | 7 please contact the maintainer of this file or JF project.
|
| D | SubmitChecklist | 7 please contact the maintainer of this file or JF project.
|
| D | HOWTO | 7 please contact the maintainer of this file or JF project.
|
| D | SubmittingPatches | 7 please contact the maintainer of this file or JF project.
|
| /linux-4.1.27/Documentation/networking/ |
| D | sctp.txt | 34 Or contact the lksctp developers through the mailing list:
|
| D | ipddp.txt | 70 You can contact me (Jay Schulist <jschlst@samba.org>) with any
|
| D | s2io.txt | 140 For further support please contact either your 10GbE Xframe NIC vendor (IBM,
|
| D | dns_resolver.txt | 27 (*) Implements the dns_resolver key_type to contact userspace.
|
| D | ray_cs.txt | 62 different parameters, contact the network administrator for the
|
| D | skfp.txt | 108 If your problem is not listed here, please contact our
|
| D | batman-adv.txt | 199 You can also contact the Authors:
|
| D | cxgb.txt | 326 If you have problems with the software or hardware, please contact our
|
| D | ixgbe.txt | 284 http://www.open-fcoe.org/ for FCoE project information and contact
|
| D | README.ipw2200 | 439 For direct support of the 1.0.0 version, you can contact
|
| D | cs89x0.txt | 603 Web site. You can also contact Cirrus Logic's Technical Support (email:
|
| D | arcnet-hardware.txt | 303 contact on the board: it's the fourth contact from the left on the
|
| /linux-4.1.27/drivers/media/radio/ |
| D | Kconfig | 299 of hardware. If you have this hardware, then please contact the
414 of hardware. If you have this hardware, then please contact the
429 of hardware. If you have this hardware, then please contact the
452 of hardware. If you have this hardware, then please contact the
486 of hardware. If you have this hardware, then please contact the
|
| /linux-4.1.27/drivers/staging/speakup/ |
| D | TODO | 41 We prefer that you contact us on the mailing list; however, if you do
|
| D | spkguide.txt | 1347 It is requested, but not required, that you contact the authors of the
|
| /linux-4.1.27/Documentation/i2c/busses/ |
| D | i2c-sis96x | 44 in the name of progress... please contact me at <mhoffman@lightlink.com> or
|
| D | i2c-ali15x3 | 64 contact the ALI office in San Jose they may give you the password.
|
| /linux-4.1.27/Documentation/filesystems/ |
| D | bfs.txt | 55 implementation please contact the author:
|
| D | romfs.txt | 145 please contact me. However, think twice before wanting me to add
|
| D | proc.txt | 78 contact Bodo Bauer at bb@ricochet.net. We'll be happy to add them to this
|
| /linux-4.1.27/drivers/staging/ |
| D | Kconfig | 20 see what needs to be worked on, and who to contact.
|
| /linux-4.1.27/Documentation/video4linux/ |
| D | README.ir | 22 Feel free to contact me in case of trouble. Note that the ir-kbd-*
|
| D | Zoran | 468 at high verbosity. See 'Contacting' on how to contact the developers.
476 reports or questions, please contact the mailinglist instead of the developers
|
| /linux-4.1.27/arch/openrisc/ |
| D | README.openrisc | 11 For more information about Linux on OpenRISC, please contact South Pole AB.
|
| /linux-4.1.27/Documentation/zh_CN/video4linux/ |
| D | omap3isp.txt | 3 If you have any comment or update to the content, please contact the
|
| D | v4l2-framework.txt | 3 If you have any comment or update to the content, please contact the
|
| /linux-4.1.27/Documentation/arm/Samsung-S3C24XX/ |
| D | Suspend.txt | 53 saving the resume address, if your board requires it, then contact
|
| /linux-4.1.27/Documentation/ABI/ |
| D | README | 49 Contact: Primary contact for this interface (may be a mailing list)
|
| /linux-4.1.27/Documentation/zh_CN/filesystems/ |
| D | sysfs.txt | 3 If you have any comment or update to the content, please contact the
|
| /linux-4.1.27/Documentation/x86/ |
| D | earlyprintk.txt | 136 mailing list or contact the x86 maintainers.
|
| D | boot.txt | 395 Please contact <hpa@zytor.com> if you need a bootloader ID
|
| /linux-4.1.27/Documentation/scsi/ |
| D | aha152x.txt | 57 operation. If you think that you need other values: contact me.
|
| D | aic79xx.txt | 391 Linux kernel. Please contact SuSE for an updated Linux
407 of the OS. Please contact your Linux vendor for instructions on
|
| D | tmscsim.txt | 86 contact me to get the appropriate patches.
388 Try to disable DsCn, if you meet this problem. Please contact me for
|
| D | BusLogic.txt | 75 Unlike some other vendors, if you contact Mylex Technical Support with a
203 Host Adapter not in the following table contact the author beforehand to verify
|
| /linux-4.1.27/drivers/net/ppp/ |
| D | Kconfig | 159 a modem (not a synchronous or ISDN modem) to contact your ISP, you
|
| /linux-4.1.27/Documentation/fb/ |
| D | sstfb.txt | 151 contact me.
|
| /linux-4.1.27/Documentation/isdn/ |
| D | README.hysdn | 177 If you have any problems concerning the driver or configuration contact
|
| D | README.gigaset | 386 distribution, ... feel free to contact us (using one of the places
|
| /linux-4.1.27/ |
| D | REPORTING-BUGS | 13 contact your Linux distribution or embedded vendor for support.
|
| D | COPYING | 327 Also add information on how to contact you by electronic and paper mail.
|
| D | CREDITS | 763 D: Former security contact point (please use vendor-sec@lst.de)
|
| /linux-4.1.27/Documentation/serial/ |
| D | moxa-smartio | 63 occurs, please contact Moxa at support@moxa.com.tw.
483 possible. If all the possible solutions fail, please contact our technical
|
| /linux-4.1.27/Documentation/blockdev/ |
| D | README.DAC960 | 43 problems with disks being marked offline, for example, please contact Mylex
97 contact the author beforehand to verify that it is or will be supported.
196 If in doubt, contact Mylex RAID Technical Support (mylexsup@us.ibm.com) to
|
| /linux-4.1.27/Documentation/wimax/ |
| D | README.i2400m | 60 For more information, please contact linux-wimax@intel.com.
|
| /linux-4.1.27/Documentation/powerpc/ |
| D | qe_firmware.txt | 38 http://opensource.freescale.com. For other firmware files, please contact
|
| /linux-4.1.27/Documentation/sound/oss/ |
| D | README.OSS | 10 you have problems with it, please contact him or the current device-specific
11 driver maintainer (e.g. for aedsp16 specific problems contact me). If you have
96 First of all it's highly recommended to contact me before sending anything
561 some FTP sites). You should contact Voice Crystal (www.voicecrystal.com)
1420 (http://www.opensound.com/ossfree). Then please contact
1447 If you have any corrections and/or comments, please contact me.
|
| /linux-4.1.27/Documentation/development-process/ |
| D | 3.Early-stage | 134 that role currently. So, when there is doubt about who to contact, a
|
| /linux-4.1.27/scripts/ |
| D | spelling.txt | 259 contant||contact
|
| /linux-4.1.27/tools/usb/usbip/ |
| D | COPYING | 311 Also add information on how to contact you by electronic and paper mail.
|
| /linux-4.1.27/drivers/staging/rtl8192e/ |
| D | license | 310 Also add information on how to contact you by electronic and paper mail.
|
| /linux-4.1.27/drivers/staging/rtl8192u/ |
| D | copying | 311 Also add information on how to contact you by electronic and paper mail.
|
| /linux-4.1.27/Documentation/filesystems/cifs/ |
| D | README | 15 For questions or bug reports please contact:
316 port attempt to contact the server on this tcp port, before
|
| /linux-4.1.27/drivers/usb/serial/ |
| D | Kconfig | 601 reader. This is an interface to ISO 7816 compatible contact-based
|
| /linux-4.1.27/Documentation/laptops/ |
| D | thinkpad-acpi.txt | 1428 not, please contact ibm-acpi-devel@lists.sourceforge.net with a report.
|
| /linux-4.1.27/drivers/scsi/ |
| D | Kconfig | 820 without modification please contact the author by email at
|