- 09 Nov, 2016 8 commits
-
-
Andrew Duggan authored
The rmi4 2D sensor functions report the tool type via input_mt_report_slot_state(), but the abs parameter bit has not been set so the tool type is not reported to userspace. This patch set the ABS_MT_TOOL_TYPE bit. Signed-off-by:
Andrew Duggan <aduggan@synaptics.com> Signed-off-by:
Benjamin Tissoires <benjamin.tissoires@redhat.com> Signed-off-by:
Dmitry Torokhov <dmitry.torokhov@gmail.com>
-
Andrew Duggan authored
Implements reading and setting the dribble bit in F12's control registers. Signed-off-by:
-
Andrew Duggan authored
The rmi_f11 driver currently disables dribble packets and the palm detect gesture for all devices. This patch creates a parameter in the 2d sensor platform data for controlling this functionality on a per device basis. For more information on dribble packets: Commit 05ba999f ("HID: rmi: disable dribble packets on Synaptics touchpads") For more information on the palm detect gesture: Commit f097deef ("HID: rmi: disable palm detect gesture when present") Signed-off-by:
-
Andrew Duggan authored
Commit 5b65c2a0 ("HID: rmi: check sanity of the incoming report") added support for handling incomplete HID reports do to the input data being corrupted in transit. This patch reimplements this functionality in the function drivers so they can handle getting less valid data then they expect. Signed-off-by:
-
Bjorn Andersson authored
The attn IRQ is related to the chip, rather than the transport, so move all handling of interrupts to the core driver. This also makes sure that there are no races between interrupts and availability of the resources used by the core driver. Signed-off-by:
Bjorn Andersson <bjorn.andersson@linaro.org> Signed-off-by:
-
Nick Dyer authored
Signed-off-by:
Nick Dyer <nick@shmanahar.org> Tested-by:
Chris Healy <cphealy@gmail.com> Signed-off-by:
-
Nick Dyer authored
Signed-off-by:
-
Nick Dyer authored
We have encountered some RMI4 firmwares where there are blank pages in between PDT pages which contain functions. This change makes them correctly enumerate all functions on the device. Tested on S7817 (has empty page 2). Signed-off-by:
-
- 08 Nov, 2016 1 commit
-
-
Dmitry Torokhov authored
Merge tag 'media/v4.9-3' of git://git.kernel.org/pub/scm/linux/kernel/git/mchehab/linux-media into synaptics-rmi4 Sync up with media tree to bring up latest Synaptics and Atmel changes.
-
- 17 Oct, 2016 1 commit
-
-
Mauro Carvalho Chehab authored
Remove this warning: drivers/staging/media/bcm2048/radio-bcm2048.c: In function 'bcm2048_set_rds_no_lock': drivers/staging/media/bcm2048/radio-bcm2048.c:467:6: warning: variable 'err' set but not used [-Wunused-but-set-variable] int err; ^~~ By returning the error code. Signed-off-by:Mauro Carvalho Chehab <mchehab@s-opensource.com>
-
- 14 Oct, 2016 30 commits
-
-
kbuild test robot authored
drivers/media/usb/dvb-usb/pctv452e.c:115:2-3: Unneeded semicolon Remove unneeded semicolon. Generated by: scripts/coccinelle/misc/semicolon.cocci Signed-off-by:
Fengguang Wu <fengguang.wu@intel.com> Signed-off-by:
-
Mauro Carvalho Chehab authored
The USB control messages require DMA to work. We cannot pass a stack-allocated buffer, as it is not warranted that the stack would be into a DMA enabled area. While here, remove a dead function calling usb_control_msg(). Signed-off-by: -
Mauro Carvalho Chehab authored
The USB control messages require DMA to work. We cannot pass a stack-allocated buffer, as it is not warranted that the stack would be into a DMA enabled area. Signed-off-by:
Mauro Carvalho Chehab <mchehab@osg.samsung.com> Signed-off-by:
-
Mauro Carvalho Chehab authored
The USB control messages require DMA to work. We cannot pass a stack-allocated buffer, as it is not warranted that the stack would be into a DMA enabled area. Signed-off-by:
-
Mauro Carvalho Chehab authored
The USB control messages require DMA to work. We cannot pass a stack-allocated buffer, as it is not warranted that the stack would be into a DMA enabled area. Signed-off-by:
-
Mauro Carvalho Chehab authored
There's no sense on decoding and generating a RC key code if there was an error on the URB control message. Signed-off-by: -
Mauro Carvalho Chehab authored
Instead of silently ignoring the error, return it. Signed-off-by: -
Mauro Carvalho Chehab authored
There's no sense on decoding and generating a RC key code if there was an error on the URB control message. Signed-off-by: -
Mauro Carvalho Chehab authored
The USB control messages require DMA to work. We cannot pass a stack-allocated buffer, as it is not warranted that the stack would be into a DMA enabled area. On this driver, most of the transfers are OK, but the I2C one was using stack. Reviewed-by:
Patrick Boettcher <patrick.boettcher@posteo.de> Signed-off-by:
-
Mauro Carvalho Chehab authored
There are some conditions on this driver that are tested with BUG_ON() with are not serious enough to hang a machine. So, just return an error if this happens. Signed-off-by: -
Mauro Carvalho Chehab authored
The USB control messages require DMA to work. We cannot pass a stack-allocated buffer, as it is not warranted that the stack would be into a DMA enabled area. Reviewed-by:
-
Mauro Carvalho Chehab authored
The USB control messages require DMA to work. We cannot pass a stack-allocated buffer, as it is not warranted that the stack would be into a DMA enabled area. Reviewed-by:
-
Mauro Carvalho Chehab authored
Add checks to avoid going out of the buffer. Signed-off-by: -
Mauro Carvalho Chehab authored
The USB control messages require DMA to work. We cannot pass a stack-allocated buffer, as it is not warranted that the stack would be into a DMA enabled area. Signed-off-by: -
Mauro Carvalho Chehab authored
The USB control messages require DMA to work. We cannot pass a stack-allocated buffer, as it is not warranted that the stack would be into a DMA enabled area. Signed-off-by:
-
Mauro Carvalho Chehab authored
If something bad happens while an USB control message is transfered, return an error code. Signed-off-by: -
Mauro Carvalho Chehab authored
The USB control messages require DMA to work. We cannot pass a stack-allocated buffer, as it is not warranted that the stack would be into a DMA enabled area. Reviewed-by:
-
Mauro Carvalho Chehab authored
If something goes wrong, return an error code, instead of assuming that everything went fine. Signed-off-by: -
Mauro Carvalho Chehab authored
The USB control messages require DMA to work. We cannot pass a stack-allocated buffer, as it is not warranted that the stack would be into a DMA enabled area. Signed-off-by: -
Mauro Carvalho Chehab authored
It is up to the frontend kthread to wait for lock. Signed-off-by: -
Mauro Carvalho Chehab authored
The USB control messages require DMA to work. We cannot pass a stack-allocated buffer, as it is not warranted that the stack would be into a DMA enabled area. Reviewed-by:
-
Mauro Carvalho Chehab authored
There's no sense on decoding and generating a RC key code if there was an error on the URB control message. Signed-off-by: -
Mauro Carvalho Chehab authored
The USB control messages require DMA to work. We cannot pass a stack-allocated buffer, as it is not warranted that the stack would be into a DMA enabled area. Reviewed-by:
-
Mauro Carvalho Chehab authored
Be sure that I2C reads won't use stack by passing a pointer to the state buffer, that we know it was allocated via kmalloc, instead of relying on the buffer allocated by an I2C client. Reviewed-by:
-
Mauro Carvalho Chehab authored
dib0700_ctrl_rd() takes a RX and a TX pointer. Be sure that both will point to a memory allocated via kmalloc(). Reviewed-by:
-
Mauro Carvalho Chehab authored
The USB control messages require DMA to work. We cannot pass a stack-allocated buffer, as it is not warranted that the stack would be into a DMA enabled area. Reviewed-by:
-
Mauro Carvalho Chehab authored
The USB control messages require DMA to work. We cannot pass a stack-allocated buffer, as it is not warranted that the stack would be into a DMA enabled area. Reviewed-by:
-
Mauro Carvalho Chehab authored
Instead of sending USB commands for every stats call, collect them once, when status is updated. As the frontend kthread will call it on every few seconds, the stats will still be collected. Besides reducing the amount of USB/I2C transfers, this also warrants that all stats will be collected at the same time, and makes easier to convert it to DVBv5 stats in the future. Signed-off-by: -
Mauro Carvalho Chehab authored
There's no sense on decoding and generating a RC key code if there was an error on the URB control message. Signed-off-by: -
Mauro Carvalho Chehab authored
The USB control messages require DMA to work. We cannot pass a stack-allocated buffer, as it is not warranted that the stack would be into a DMA enabled area. Reviewed-by:
-
