linux-toradex.git/include/linux/hid.h, branch v6.4-rc1

HID: Recognize "Digitizer" as a valid input application

2023-03-30T15:35:42+00:00

"Digitizer" is a generic usage that may be used by various devices but
which is particularly used by non-display pen tablets. This patch adds the
usage to the list of values matched by the IS_INPUT_APPLICATION() macro
that determines if an input device should be allocated or not.

Signed-off-by: Jason Gerecke 
Reviewed-by: Ping Cheng 
Link: https://lore.kernel.org/r/20221019151832.44522-1-jason.gerecke@wacom.com
Signed-off-by: Benjamin Tissoires

HID: add KEY_CAMERA_FOCUS event in HID

2023-03-10T14:21:11+00:00

Our HID device need KEY_CAMERA_FOCUS event to control camera,
but this event is non-existent in current HID driver.
So we add this event in hid-input.c.

Signed-off-by: fengqi 
Reviewed-by: Greg Kroah-Hartman 
Signed-off-by: Jiri Kosina

HID: core: Provide new max_buffer_size attribute to over-ride the default

2023-02-23T10:51:56+00:00

Presently, when a report is processed, its proposed size, provided by
the user of the API (as Report Size * Report Count) is compared against
the subsystem default HID_MAX_BUFFER_SIZE (16k).  However, some
low-level HID drivers allocate a reduced amount of memory to their
buffers (e.g. UHID only allocates UHID_DATA_MAX (4k) buffers), rending
this check inadequate in some cases.

In these circumstances, if the received report ends up being smaller
than the proposed report size, the remainder of the buffer is zeroed.
That is, the space between sizeof(csize) (size of the current report)
and the rsize (size proposed i.e. Report Size * Report Count), which can
be handled up to HID_MAX_BUFFER_SIZE (16k).  Meaning that memset()
shoots straight past the end of the buffer boundary and starts zeroing
out in-use values, often resulting in calamity.

This patch introduces a new variable into 'struct hid_ll_driver' where
individual low-level drivers can over-ride the default maximum value of
HID_MAX_BUFFER_SIZE (16k) with something more sympathetic to the
interface.

Signed-off-by: Lee Jones 
Signed-off-by: Jiri Kosina

Merge branch 'for-6.3/hid-bpf' into for-linus

2023-02-22T09:44:31+00:00

Initial support of HID-BPF (Benjamin Tissoires)

The history is a little long for this series, as it was intended to be
sent for v6.2. However some last minute issues forced us to postpone it
to v6.3.

Conflicts:
* drivers/hid/i2c-hid/Kconfig:
  commit bf7660dab30d ("HID: stop drivers from selecting CONFIG_HID")
  conflicts with commit 2afac81dd165 ("HID: fix I2C_HID not selected
  when I2C_HID_OF_ELAN is")
  the resolution is simple enough: just drop the "default" and "select"
  lines as the new commit from Arnd is doing

Merge branch 'for-6.3/multitouch' into for-linus

2023-02-22T09:39:05+00:00

Allow to pass quirks from i2c-hid to hid-multitouch (Allen Ballway &
Dmitry Torokhov)

HID: retain initial quirks set up when creating HID devices

2023-02-09T13:24:30+00:00

In certain circumstances, such as when creating I2C-connected HID
devices, we want to pass and retain some quirks (axis inversion, etc).
The source of such quirks may be device tree, or DMI data, or something
else not readily available to the HID core itself and therefore cannot
be reconstructed easily. To allow this, introduce "initial_quirks" field
in hid_device structure and use it when determining the final set of
quirks.

This fixes the problem with i2c-hid setting up device-tree sourced
quirks too late and losing them on device rebind, and also allows to
sever the tie between hid-code and i2c-hid when applying DMI-based
quirks.

Fixes: b60d3c803d76 ("HID: i2c-hid-of: Expose the touchscreen-inverted properties")
Fixes: a2f416bf062a ("HID: multitouch: Add quirks for flipped axes")
Reviewed-by: Guenter Roeck 
Tested-by: Allen Ballway 
Signed-off-by: Dmitry Torokhov 
Reviewed-by: Alistair Francis 
Link: https://lore.kernel.org/r/Y+LYwu3Zs13hdVDy@google.com
Signed-off-by: Benjamin Tissoires

HID: use standard debug APIs

2023-02-06T14:11:45+00:00

The custom "debug" module parameter is fairly inflexible.
It can only manage debugging for all calls dbg_hid() at the same time.

Furthermore it creates a mismatch between calls to hid_dbg() which can
be managed by CONFIG_DYNAMIC_DEBUG and dbg_hid() which is managed by the
module parameter.

Furthermore the change to pr_debug() allows the debugging statements to
be completely compiled-out if desired.

Signed-off-by: Thomas Weißschuh 
Tested-by: Bastien Nocera 
Link: https://lore.kernel.org/r/20221223-hid-dbg-v1-1-5dcf8794f7f9@weissschuh.net
Signed-off-by: Benjamin Tissoires

HID: Make lowlevel driver structs const

2023-01-17T12:44:02+00:00

Nothing is nor should be modifying these structs so mark them as const.

Signed-off-by: Thomas Weißschuh 
Reviewed-by: David Rheinsberg 
Reviewed-by: Hans de Goede 
Signed-off-by: Jiri Kosina

HID: Unexport struct i2c_hid_ll_driver

2023-01-17T12:44:01+00:00

As there are no external users this implementation detail does not need
to be exported.

Signed-off-by: Thomas Weißschuh 
Reviewed-by: David Rheinsberg 
Reviewed-by: Hans de Goede 
Signed-off-by: Jiri Kosina

HID: Unexport struct hidp_hid_driver

2023-01-17T12:44:01+00:00

As there are no external users this implementation detail does not need
to be exported.

Signed-off-by: Thomas Weißschuh 
Reviewed-by: David Rheinsberg 
Reviewed-by: Hans de Goede 
Signed-off-by: Jiri Kosina