Hello,
I'm experiencing the following issue which I'd like to help resolve.
Please let me know if there's any other information or action that I
can provide.
I'll send additional information in subsequent mails to avoid the
majordomo length block.
Many thanks,
Daniel
[1] Summary:
Samsung
On 07/19/2014 02:02 AM, Chen Gang wrote:
2014-07-18 18:51 GMT+08:00 Richard Weinberger rich...@nod.at:
Am 18.07.2014 12:44, schrieb Chen Gang:
On 07/18/2014 03:35 PM, Richard Weinberger wrote:
Am 18.07.2014 02:36, schrieb Chen Gang:
On 07/18/2014 02:09 AM, Richard Weinberger wrote:
Am
On 07/20/2014 04:38 PM, Chen Gang wrote:
On 07/19/2014 02:02 AM, Chen Gang wrote:
2014-07-18 18:51 GMT+08:00 Richard Weinberger rich...@nod.at:
Am 18.07.2014 12:44, schrieb Chen Gang:
On 07/18/2014 03:35 PM, Richard Weinberger wrote:
Am 18.07.2014 02:36, schrieb Chen Gang:
On 07/18/2014
Am 20.07.2014 10:38, schrieb Chen Gang:
On 07/19/2014 02:02 AM, Chen Gang wrote:
2014-07-18 18:51 GMT+08:00 Richard Weinberger rich...@nod.at:
Am 18.07.2014 12:44, schrieb Chen Gang:
On 07/18/2014 03:35 PM, Richard Weinberger wrote:
Am 18.07.2014 02:36, schrieb Chen Gang:
On 07/18/2014
Hi
On Sun, Jul 20, 2014 at 1:49 AM, Dmitry Torokhov
dmitry.torok...@gmail.com wrote:
We attempt to remove noise from coordinates reported by devices in
input_handle_abs_event(), unfortunately, unless we were dropping the
event altogether, we were ignoring the adjusted value and were passing
On 07/20/2014 05:45 PM, Richard Weinberger wrote:
Am 20.07.2014 10:38, schrieb Chen Gang:
On 07/19/2014 02:02 AM, Chen Gang wrote:
2014-07-18 18:51 GMT+08:00 Richard Weinberger rich...@nod.at:
Am 18.07.2014 12:44, schrieb Chen Gang:
On 07/18/2014 03:35 PM, Richard Weinberger wrote:
Am
On 07/20/2014 05:51 PM, Chen Gang wrote:
On 07/20/2014 05:45 PM, Richard Weinberger wrote:
Am 20.07.2014 10:38, schrieb Chen Gang:
On 07/19/2014 02:02 AM, Chen Gang wrote:
2014-07-18 18:51 GMT+08:00 Richard Weinberger rich...@nod.at:
Am 18.07.2014 12:44, schrieb Chen Gang:
On 07/18/2014
Fix coding style with regard to missing spaces after , and the column limit
that was violated after the first change.
Signed-off-by: Bivolaru Catalin bivolaru.cata...@gmail.com
---
The change was tested only by compilation.
diff --git a/drivers/input/keyboard/sunkbd.c
Recent version of xf86-input-wacom no longer support directly accessing
serial tablets. Instead xf86-input-wacom now expects all wacom tablets to
be driven by the kernel and to show up as evdev devices.
This has caused old serial Wacom tablets to stop working for people who still
have such
On Sun, 2014-07-20 at 15:01 +0300, Bivolaru Catalin wrote:
Fix coding style with regard to missing spaces after , and the column limit
that was violated after the first change.
Some checkpatch errors should be ignored.
These are some of them.
This change doesn't make it easier to read
or to
Hi Dmitry,
We attempt to remove noise from coordinates reported by devices in
input_handle_abs_event(), unfortunately, unless we were dropping the
event altogether, we were ignoring the adjusted value and were passing
on the original value instead.
Reviewed-by: Andrew de los Reyes
evdev-client_list is rcu-protected. There is no need to have a
separate spinlock just for the list. Either one is good enough, so lets
drop the spinlock.
Signed-off-by: David Herrmann dh.herrm...@gmail.com
---
Hi
I stumbled across this one when doing some evdev reviews. Maybe I'm missing
On Sun, Jul 20, 2014 at 08:48:12PM +0200, David Herrmann wrote:
evdev-client_list is rcu-protected. There is no need to have a
separate spinlock just for the list. Either one is good enough, so lets
drop the spinlock.
Signed-off-by: David Herrmann dh.herrm...@gmail.com
---
Hi
I stumbled
On Sun, Jul 20, 2014 at 09:00:02PM +0200, David Herrmann wrote:
Hi
On Sun, Jul 20, 2014 at 8:54 PM, Dmitry Torokhov
dmitry.torok...@gmail.com wrote:
On Sun, Jul 20, 2014 at 08:48:12PM +0200, David Herrmann wrote:
evdev-client_list is rcu-protected. There is no need to have a
separate
evdev-client_list is rcu-protected. We need the client_lock only to
protect against concurrent writes. However, all paths that access
client_list already lock evdev-mutex. Therefore, drop client_lock and use
evdev-mutex as list-protection.
This also drops several helper functions that are called
On Sun, Jul 20, 2014 at 08:52:54AM -0700, Joe Perches wrote:
On Sun, 2014-07-20 at 15:01 +0300, Bivolaru Catalin wrote:
Fix coding style with regard to missing spaces after , and the column limit
that was violated after the first change.
Some checkpatch errors should be ignored.
These
On Sun, Jul 20, 2014 at 02:51:37PM +0100, Jonathan Cameron wrote:
On 20/07/14 14:49, Jonathan Cameron wrote:
On 18/07/14 20:29, Arnd Bergmann wrote:
This adds support for the touchscreen on Samsung s3c64xx.
The driver is completely untested but shows roughly how
it could be done, following
On Tue, Jul 15, 2014 at 01:30:59PM +0200, Daniel Mack wrote:
This patch adds a driver for Microchips CAP1106, an I2C driven, 6-channel
capacitive touch sensor.
For now, only the capacitive buttons are supported, and no specific
settings that can be tweaked for individual channels, except for
On Tue, Jul 08, 2014 at 06:37:36PM +0200, Fabian Frederick wrote:
Cc: Dmitry Torokhov dmitry.torok...@gmail.com
Cc: Paul Gortmaker paul.gortma...@windriver.com
Cc: linux-input@vger.kernel.org
Signed-off-by: Fabian Frederick f...@skynet.be
Applied, thank you.
---
On Tue, Jul 08, 2014 at 10:47:58AM +0200, Tobias Klauser wrote:
Add #ifdef CONFIG_PM_SLEEP around keyscan_supend() and keyscan_resume() to fix
the following compiler warnings occuring if CONFIG_PM_SLEEP is unset:
+ /scratch/kisskb/src/drivers/input/keyboard/st-keyscan.c: warning:
On Sat, Jul 19, 2014 at 03:10:43PM +0200, David Herrmann wrote:
This ioctl is the counterpart to EVIOCGVERSION and returns the
uinput-version the kernel was compiled with.
Reviewed-by: Peter Hutterer peter.hutte...@who-t.net
Signed-off-by: David Herrmann dh.herrm...@gmail.com
Applied, thank
Hi David,
On Sat, Jul 19, 2014 at 03:10:40PM +0200, David Herrmann wrote:
Hi Dmitry
I posted all these ~2 months ago, but haven't seen any comments from you.
Seeing
that you switched jobs (congratulations, btw!),
Thanks :)
I guess you were quite busy the
last few weeks. Hence, here's a
Hi David,
On Sat, Jul 19, 2014 at 03:10:44PM +0200, David Herrmann wrote:
This adds a new ioctl UINPUT_DEV_SETUP that replaces the old device setup
method (by write()'ing struct uinput_user_dev to the node). The old
method is not easily extendable and requires huge payloads. Furthermore,
Wire up support for EVIOC{G|S}KEYCODE to allow users change key mappings
from userspace.
Signed-off-by: Dmitry Torokhov dmitry.torok...@gmail.com
---
Just compiled, not tested.
drivers/input/keyboard/cap1106.c | 8 +++-
1 file changed, 7 insertions(+), 1 deletion(-)
diff --git
24 matches
Mail list logo
