On Sun, Nov 23, 2014 at 06:03:23PM -0800, Greg Kroah-Hartman wrote:
The xpad wireless endpoint is not a bulk endpoint on my devices, but
rather an interrupt one, so the USB core complains when it is submitted.
I'm guessing that the author really did mean that this should be an
interrupt urb,
Hi Aniroop,
On Sat, Nov 22, 2014 at 12:18:39AM +0530, Aniroop Mathur wrote:
This patch initializes input_no by -1 in order to avoid extra subtraction
operation performed everytime for allocation of an input device.
Signed-off-by: Aniroop Mathur aniroop.mat...@gmail.com
It looks like you
On Mon, 2014-11-24 at 16:56 -0800, Benson Leung wrote:
Hi Oliver,
On Mon, Nov 24, 2014 at 1:13 AM, Oliver Neukum oneu...@suse.de wrote:
But there is very little to be gained by switching off remote wakeup.
The additional energy consumption devices with remote wakeup enabled
will be
On Thursday 20 November 2014 00:29:49 Pali Rohár wrote:
On Monday 17 November 2014 08:39:14 Pali Rohár wrote:
On Friday 14 November 2014 21:59:31 Dmitry Torokhov wrote:
Hi Pali,
On Friday, November 14, 2014 08:38:19 PM Pali Rohár wrote:
This patch series fix detection and
On Mon, 24 Nov 2014, Benjamin Tissoires wrote:
Current driver uses a common buffer for reading reports either
synchronously in i2c_hid_get_raw_report() and asynchronously in
the interrupt handler.
There is race condition if an interrupt arrives immediately after
the report is received
On Sat, 22 Nov 2014, Mathieu Magnaudet wrote:
VTL panels do not switch to the multitouch mode until the input mode
feature is read by the host. This should normally be done by
usbhid, but it looks like an other bug prevents usbhid to properly
retrieve the feature state. As a workaround, we
On Mon, 24 Nov 2014, 黄波 wrote:
From: Huang Bo huangbob...@163.com
Adds force feedback support for BETOP USB game controllers.
These devices are mass produced in China.
Thanks a lot for the patch. A few minor things below.
First, the whole driver formatting doesn't comply with our coding
On Mon, 24 Nov 2014, Benson Leung wrote:
Hi Alan,
On Sat, Nov 22, 2014 at 7:55 AM, Alan Stern st...@rowland.harvard.edu wrote:
There is no USB wrapper for pm_runtime_idle calls, but one could be
added. Still, in the meantime can you check to see what happens if you
add
On Mon, Nov 24, 2014 at 6:32 PM, Jason Gerecke killert...@gmail.com wrote:
It is not necessarily sufficient to look only at the physical and logical
usages when determining if a field is for the pen or touch. Some fields
are not contained in a sub-collection and thus only have an application
On Tue, Nov 25, 2014 at 7:24 AM, Alan Stern st...@rowland.harvard.edu wrote:
On Mon, 24 Nov 2014, Benson Leung wrote:
Hi Alan,
On Sat, Nov 22, 2014 at 7:55 AM, Alan Stern st...@rowland.harvard.edu
wrote:
There is no USB wrapper for pm_runtime_idle calls, but one could be
added. Still,
On Mon, Nov 24, 2014 at 6:32 PM, Jason Gerecke killert...@gmail.com wrote:
If a HID descriptor places HID_DG_CONTACTID before HID_DG_X and HID_DG_Y then
the ABS_X and ABS_Y will not be automatically initialized by the call to
input_mt_init_slots. Here we move the setup of those axes outside of
Hi Jason,
On Mon, Nov 24, 2014 at 6:32 PM, Jason Gerecke killert...@gmail.com wrote:
Multitouch tablets cannot work properly if wacom_wac_finger_event simply
stores the event details, since details about former fingers will be
overwritten by later ones (causing wacom_wac_finger_report to
This patch initializes input_no by -1 in order to avoid extra subtraction
operation performed everytime for allocation of an input device.
Signed-off-by: Aniroop Mathur aniroop.mat...@gmail.com
---
drivers/input/input.c | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git
Hi Jiri,
Please don't forget to merge this patch. It fixes a bad pointer issue...
Thanks,
Ping
On Thu, Nov 20, 2014 at 4:31 PM, Ping Cheng pingli...@gmail.com wrote:
PAD can be on pen interface (Intuos Pro and Cintiq series) or touch
interface (Bamboo PT and Intuos PT series) or its own
On Tue, 25 Nov 2014, Ping Cheng wrote:
Please don't forget to merge this patch. It fixes a bad pointer issue...
Hi Ping,
yes, it's in my queue for this evening or tomorrow.
I will also add Cc: stable, ok?
Thanks,
--
Jiri Kosina
SUSE Labs
--
To unsubscribe from this list: send the line
Name:.
--
To unsubscribe from this list: send the line unsubscribe linux-input in
the body of a message to majord...@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Hi,
On Wed, Nov 19, 2014 at 11:21:31PM +0100, Marcus Overhagen wrote:
Hi,
when moving a single finger [3] seems to be one of 0x21, 0x25, 0x31, 0x35
moving two fingers [3] seems to be mostly 0x22, 0x26, 0x32, 0x36 but
also sometimes it's 0x42, 0x46, 0x52, 0x56.
It seems to occationally
On Tue, Nov 25, 2014 at 11:56 AM, Jiri Kosina jkos...@suse.cz wrote:
On Tue, 25 Nov 2014, Ping Cheng wrote:
Please don't forget to merge this patch. It fixes a bad pointer issue...
Hi Ping,
yes, it's in my queue for this evening or tomorrow.
Thank you.
I will also add Cc: stable, ok?
If
On Tue, 25 Nov 2014, Ping Cheng wrote:
I will also add Cc: stable, ok?
If you Cc this one to stable, please also include my other three
patches, dated Nov. 18, 2014, under your wacom-3.19 branch. Those four
patches go together to fix a system freeze issue caused by Bamboo Pen
only device.
Hi Jaewon,
On Monday 24 November 2014 08:20 PM, Jaewon Kim wrote:
This patch adds support for haptic driver controlled by
voltage of regulator. And this driver support for
Force Feedback interface from input framework
Signed-off-by: Jaewon Kim jaewon02@samsung.com
Signed-off-by: Hyunhee
20 matches
Mail list logo
