54a19b4d3f
There are some ABI documents that, while they don't generate any warnings, they have issues when parsed by get_abi.pl script on its output result. Address them, in order to provide a clean output. Reviewed-by: Tom Rix <trix@redhat.com> # for fpga-manager Reviewed-By: Kajol Jain<kjain@linux.ibm.com> # for sysfs-bus-event_source-devices-hv_gpci and sysfs-bus-event_source-devices-hv_24x7 Acked-by: Jonathan Cameron <Jonathan.Cameron@huawei.com> #for IIO Acked-by: Oded Gabbay <oded.gabbay@gmail.com> # for Habanalabs Acked-by: Vaibhav Jain <vaibhav@linux.ibm.com> # for sysfs-bus-papr-pmem Acked-by: Cezary Rojewski <cezary.rojewski@intel.com> # for catpt Acked-by: Suzuki K Poulose <suzuki.poulose@arm.com> Acked-by: Ilya Dryomov <idryomov@gmail.com> # for rbd Acked-by: Jonathan Corbet <corbet@lwn.net> Signed-off-by: Mauro Carvalho Chehab <mchehab+huawei@kernel.org> Link: https://lore.kernel.org/r/5bc78e5b68ed1e9e39135173857cb2e753be868f.1604042072.git.mchehab+huawei@kernel.org Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
2.4 KiB
What: /sys/bus/hid/drivers/ntrig//activate_slack Date: May, 2010 KernelVersion: 2.6.35 Contact: linux-input@vger.kernel.org Description: (RW) Number of contact frames ignored before acknowledging the start of activity (activating touch).
What: /sys/bus/hid/drivers/ntrig//decativate_slack Date: May, 2010 KernelVersion: 2.6.35 Contact: linux-input@vger.kernel.org Description: (RW) Number of empty (no contact) frames ignored before acknowledging the end of activity (deactivating touch).
When the last finger is removed from the device, it sends a
number of empty frames. By holding off on deactivation for a few
frames false erroneous disconnects can be tolerated, where the
sensor may mistakenly not detect a finger that is still present.
What: /sys/bus/hid/drivers/ntrig//activation_width What: /sys/bus/hid/drivers/ntrig//activation_height Date: May, 2010 KernelVersion: 2.6.35 Contact: linux-input@vger.kernel.org Description: Threholds to override activation slack.
================= =====================================
activation_width (RW) Width threshold to immediately
start processing touch events.
activation_height (RW) Height threshold to immediately
start processing touch events.
================= =====================================
What: /sys/bus/hid/drivers/ntrig//min_width What: /sys/bus/hid/drivers/ntrig//min_height Date: May, 2010 KernelVersion: 2.6.35 Contact: linux-input@vger.kernel.org Description: Minimum size contact accepted.
========== ===========================================
min_width (RW) Minimum touch contact width to decide
activation and activity.
min_height (RW) Minimum touch contact height to decide
activation and activity.
========== ===========================================
What: /sys/bus/hid/drivers/ntrig//sensor_physical_width What: /sys/bus/hid/drivers/ntrig//sensor_physical_height Date: May, 2010 KernelVersion: 2.6.35 Contact: linux-input@vger.kernel.org Description: (RO) These are internal ranges not used for normal events but useful for tuning.
What: /sys/bus/hid/drivers/ntrig//sensor_logical_width What: /sys/bus/hid/drivers/ntrig//sensor_logical_height Date: May, 2010 KernelVersion: 2.6.35 Contact: linux-input@vger.kernel.org Description: (RO) The range for positions reported during activity.