- Original Message -
> From: "Dmitry Torokhov"
> Sent: Tuesday, March 31, 2015 4:35:18 PM
>
> Hi Aaron,
>
> On Tue, Mar 31, 2015 at 10:06:05AM -0500, Aaron Sierra wrote:
> > When an IRQ isn't available, poll the device based on poll_period.
>
> What is the point in using such mode? Why
On Tue, Mar 31, 2015 at 10:05:59AM -0500, Aaron Sierra wrote:
> Eliminate redundant calculations by performing millisecond to jiffy
> calculations once during driver initialization.
>
> Signed-off-by: Aaron Sierra
Applied, thank you.
> ---
> drivers/input/touchscreen/tsc2007.c | 11 ++-
On Tue, Mar 31, 2015 at 03:55:59PM +0200, Rasmus Villemoes wrote:
> tty_name no longer uses the buf parameter, so remove it along with all
> the 64 byte stack buffers that used to be passed in.
>
> Mostly generated by the coccinelle script
>
> @depends on patch@
> identifier buf;
> constant C;
>
ELAN0600 seems to work just fine in mouse emulation mode through i2c-hid,
but to have full raw touch support we need to register it in elan_i2c.ko
Found on a Lenovo Yoga 3 11".
Reported-and-tested-by: Alessio Treglia
Signed-off-by: Benjamin Tissoires
---
Hi,
Alessio reported this touchpad on
Hi Aaron,
On Tue, Mar 31, 2015 at 10:06:05AM -0500, Aaron Sierra wrote:
> When an IRQ isn't available, poll the device based on poll_period.
What is the point in using such mode? Why would not IRQ be available?
If this is for device bringup I'd say just carry this locally.
Thanks.
--
Dmitry
--
On 03/31/2015 03:17 PM, Dmitry Torokhov wrote:
On Tue, Mar 31, 2015 at 02:57:35PM -0500, Thor Thayer wrote:
Hi,
I have a SPI gpio expander chip that is using the regmap framework.
There are some pushbuttons that I'd like to use the gpio_keys
framework for but only the first button press creat
On Tue, Mar 31, 2015 at 06:14:49PM +0200, Tomeu Vizoso wrote:
> So ancestor devices can remain runtime-suspended when the system goes
> into a sleep state, they and all of their descendant devices need to
> have runtime PM enabled.
I am confused. Input devices are not runtime-PM-enabled, so what
e
Hi,
I have a SPI gpio expander chip that is using the regmap framework.
There are some pushbuttons that I'd like to use the gpio_keys framework
for but only the first button press creates an input event.
It seems like my problem occurs because I'm only getting events on a
button press. The
On Tue, Mar 31, 2015 at 02:57:35PM -0500, Thor Thayer wrote:
> Hi,
>
> I have a SPI gpio expander chip that is using the regmap framework.
> There are some pushbuttons that I'd like to use the gpio_keys
> framework for but only the first button press creates an input
> event.
>
> It seems like my
On Tue, Mar 31, 2015 at 02:57:35PM -0500, Thor Thayer wrote:
> Which brings up my next question. Can the gpio_keys framework be used with a
> regmapped gpio? I haven't been able to find any examples of gpio_keys with
> an external gpio expander and maybe this isn't valid usage.
Why would there be
On Tue, 2015-03-31 at 22:00 +0200, Jiri Slaby wrote:
> On 03/31/2015, 02:36 PM, Oliver Neukum wrote:
> > There is a typo in a device ID
>
> Hi, this should have gone to jikos instead ;).
It has. Unless I am very mistaken. I made a version
against your tree driven by embarasment.
Regards
On 03/31/2015, 02:36 PM, Oliver Neukum wrote:
> There is a typo in a device ID
Hi, this should have gone to jikos instead ;).
> Signed-off-by: Oliver Neukum
> CC: sta...@vger.kernel.org
> ---
> drivers/hid/hid-ids.h | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/drive
Have it return 1 in both input_dev_type and input_class (for evdev
handlers) so that input devices that are runtime-suspended won't be
suspended when the system goes to a sleep state. This can make resume
times considerably shorter because these devices don't need to be
resumed when the system is a
So ancestor devices can remain runtime-suspended when the system goes
into a sleep state, they and all of their descendant devices need to
have runtime PM enabled.
Signed-off-by: Tomeu Vizoso
---
drivers/input/evdev.c | 3 +++
1 file changed, 3 insertions(+)
diff --git a/drivers/input/evdev.c b
Hi,
this series contain what I needed to do in order to have my USB webcam to not
be resumed when the system resumes, reducing considerably the total time that
resuming takes.
It makes use of the facility that Rafael Wysocki added in aae4518b3 ("PM /
sleep: Mechanism to avoid resuming runtime-
Eliminate redundant calculations by performing millisecond to jiffy
calculations once during driver initialization.
Signed-off-by: Aaron Sierra
---
drivers/input/touchscreen/tsc2007.c | 11 ++-
1 file changed, 6 insertions(+), 5 deletions(-)
diff --git a/drivers/input/touchscreen/tsc200
When an IRQ isn't available, poll the device based on poll_period.
Signed-off-by: Aaron Sierra
---
drivers/input/touchscreen/tsc2007.c | 43 +++--
1 file changed, 36 insertions(+), 7 deletions(-)
diff --git a/drivers/input/touchscreen/tsc2007.c
b/drivers/input/t
On 03/31/2015 05:07 PM, Benjamin Tissoires wrote:
> Hi,
>
> so this is the v2 with Hans' ack and Henrik's respin of the first patch.
The whole series looks good, thank you Benjamin.
Acked-by: Henrik Rydberg
Henrik
--
To unsubscribe from this list: send the line "unsubscribe linux-input" in
th
When slowly dropping 1, 2 and then 3 fingers on an image sensor touchpad,
we can see that the first finger gets reassigned a new slot while it did
not move. This is due to the kernel tracking algorithm which can not
assign correctly the 3 touches, being out of slots.
Declaring that we support 3 sl
Hi,
so this is the v2 with Hans' ack and Henrik's respin of the first patch.
Cheers,
Benjamin
Benjamin Tissoires (3):
Input: MT - make slot assignment work for overcovered solutions
Revert "Revert "Input: synaptics - use dmax in input_mt_assign_slots""
Input: synaptics - allocate 3 slots
The recent inclusion of a deassignment cost in the slot assignment
algorithm did not properly account for the corner cases where the
solutions are overcovered. This patch makes sure the resulting assignment
is unique, allocating new slots when necessary.
Signed-off-by: Henrik Rydberg
Signed-off-b
This reverts commit 09d042a2eb90 ("Revert "Input: synaptics - use dmax in
input_mt_assign_slots"")
Now that balanced slots assignments seem to be fixed, let's
reenable the use in synaptics.c and wait for users to complain
if there are still problems.
Signed-off-by: Benjamin Tissoires
Acked-by:
Hi Henrik,
On Mar 31 2015 or thereabouts, Henrik Rydberg wrote:
> Hi Benjamin,
>
> > If two touches are under the dmax distance, it looks like they can now
> > be assigned to the same slot. Add a band aid to prevent such situation
> > and be able to use the balanced slot assignment.
>
> Yes, gre
On Sat, 21 Mar 2015, Michal Malý wrote:
> Since all functions that need to send some data to the device they
> manage share the same HID report some synchronization is needed to
> prevent sending bogus data to the device.
This patch is doing much more than just adding a mutual exclusion
mechanis
On Sat, 21 Mar 2015, Michal Malý wrote:
> The original warning message was highly misleading. This warning can be
> triggered only if a device is flagged to be handled by hid-lg4ff in
> hid-lg but hid-lg4ff lacks support for such device.
>
> Signed-off-by: Michal Malý
> ---
> drivers/hid/hid-lg
All users of tty_name pass the return value directly to a printf
function, so we might as well use tty->name directly instead of
copying it to a user-supplied (stack) buffer.
allmodconfig compile-tested only.
Rasmus Villemoes (3):
tty: constify return type of tty_name
tty: return tty->name di
tty_name no longer uses the buf parameter, so remove it along with all
the 64 byte stack buffers that used to be passed in.
Mostly generated by the coccinelle script
@depends on patch@
identifier buf;
constant C;
expression tty;
@@
- char buf[C];
<+...
- tty_name(tty, buf)
+ tty_name(tty)
...
There is a typo in a device ID
Signed-off-by: Oliver Neukum
CC: sta...@vger.kernel.org
---
drivers/hid/hid-ids.h | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/drivers/hid/hid-ids.h b/drivers/hid/hid-ids.h
index 56a4ed6..4ee0fb0 100644
--- a/drivers/hid/hid-ids.h
+++ b/drive
This patch fixes a kernel panic which occurs when buf_list is empty. This can
happen occasionally when user space is under heavy load (e.g. due to image
processing on the CPU) and new buffers aren't re-queued fast enough. In that
case, vb2_start_streaming_called can return true, but when the spin
Hi Benjamin,
> If two touches are under the dmax distance, it looks like they can now
> be assigned to the same slot. Add a band aid to prevent such situation
> and be able to use the balanced slot assignment.
Yes, great find. You patch is correct, but it is not a band aid, but a
result stemming
Hi,
On 31-03-15 00:09, Benjamin Tissoires wrote:
Hi,
So, it occurs that the balanced slots assignment introduced in v4.0 had some
troubles and the Synaptics part was reverted.
I tried to spend some time today to figure out a solution, and the only way
I can get something from it is to add a ban
31 matches
Mail list logo
