The accelerometer node used the generic compatible property only.
Add the device-specific one, to make it future proof.
Signed-off-by: Geert Uytterhoeven geert+rene...@glider.be
---
Depends on commit 3a38958d2477b718 (Input: adxl34x - add OF match
support), which is in v4.2-rc1.
---
Hi Geert,
Thank you for the patch.
On Monday 06 July 2015 11:59:06 Geert Uytterhoeven wrote:
The accelerometer node used the generic compatible property only.
Add the device-specific one, to make it future proof.
Signed-off-by: Geert Uytterhoeven geert+rene...@glider.be
---
Depends on
Hi,
I recently noticed that there's a minor issue with hid-rmi.c. After a
suspend/resume cycle the f11 control register is set to the default
configuration, thus undoing the changes performed on init.
I made some changes to the driver to prevent this from happening: the
configuration is saved on
On Mon, Jul 6, 2015 at 12:17 PM, Laurent Pinchart
laurent.pinch...@ideasonboard.com wrote:
--- a/arch/arm/boot/dts/sh73a0-kzm9g.dts
+++ b/arch/arm/boot/dts/sh73a0-kzm9g.dts
@@ -206,7 +206,7 @@
};
accelerometer@1d {
- compatible = adi,adxl34x;
+
Replace the deprecated generic adi,adxl34x compatible value by the
adxl345-specific adi,adxl345 value, cfr. commit e465bf6fc55d5ce2 (DT:
i2c: Deprecate adi,adxl34x compatible string).
Signed-off-by: Geert Uytterhoeven geert+rene...@glider.be
---
Depends on commit 3a38958d2477b718 (Input: adxl34x
Hi Geert,
Thank you for the patch.
On Monday 06 July 2015 12:55:32 Geert Uytterhoeven wrote:
Replace the deprecated generic adi,adxl34x compatible value by the
adxl345-specific adi,adxl345 value, cfr. commit e465bf6fc55d5ce2 (DT:
i2c: Deprecate adi,adxl34x compatible string).
Using managed input device (via devm_input_allocate_device) simplifies
error handling and driver removal paths and also silences CID# 712569.
Signed-off-by: Dmitry Torokhov dmitry.torok...@gmail.com
---
drivers/input/misc/arizona-haptics.c | 52
1 file
On Monday, 6 July 2015, at 9:44 pm, Henrik Rydberg wrote:
I think your patch is a good reduction, all in accord with what we talked
about,
but I have doubts that it will not create regressions. From what I have
seen so
far, patch-wise, the best solution is to leave the code as it is.
Hi,
It seems to me that swapping error for ret buries the functional changes in
the patch...
would it be better to split them into a second cleanup patch?
On Monday, July 06, 2015 10:38:41 AM Dmitry Torokhov wrote:
Using managed input device (via devm_input_allocate_device) simplifies
error
It's been four weeks, and I haven't heard back on this patch. I believe I've
implemented what was requested. Is there a problem with it?
On Monday, 8 June 2015, at 9:07 pm, Matt Whitlock wrote:
Now that input_mt_report_pointer_emulation() can synthesize ABS_TOOL_WIDTH
from ABS_MT_WIDTH_MAJOR,
Hi Matt,
It's been four weeks, and I haven't heard back on this patch. I believe I've
implemented what was requested. Is there a problem with it?
I thought you did get response on this patch set, concerning the fabrication of
force data? I seem to remember a mail from Dmitry about this,
From: Anshul Garg aksgarg1...@gmail.com
As per current implementation input driver can only
send ktime converted to timeval which user space again
have to convert.
In some cases input drivers need 64bit timestamp value
from driver only so that same value can be used by upper
layer without any
I think your patch is a good reduction, all in accord with what we talked
about,
but I have doubts that it will not create regressions. From what I have seen
so
far, patch-wise, the best solution is to leave the code as it is.
So you believe that the current (in-tree) behavior is
On Monday, 6 July 2015, at 9:11 pm, Henrik Rydberg wrote:
It's been four weeks, and I haven't heard back on this patch. I believe I've
implemented what was requested. Is there a problem with it?
I thought you did get response on this patch set, concerning the fabrication
of
force data? I
Hi Anshul,
On Mon, Jul 06, 2015 at 12:33:44PM -0700, Anshul Garg wrote:
From: Anshul Garg aksgarg1...@gmail.com
As per current implementation input driver can only
send ktime converted to timeval which user space again
have to convert.
Why? ktime is kernel construct and thus userspace has
Hi Gabriele,
On 07/06/2015 03:20 AM, Gabriele Mazzotta wrote:
Hi,
I recently noticed that there's a minor issue with hid-rmi.c. After a
suspend/resume cycle the f11 control register is set to the default
configuration, thus undoing the changes performed on init.
This is because i2c_hid does
On Fri, Jul 03, 2015 at 01:13:01AM +0200, Martin Kepplinger wrote:
Despite it's name, sign_extend32() is used for 16 bit values aswell.
Signed-off-by: Martin Kepplinger mart...@posteo.de
Applied, thank you.
---
drivers/input/misc/bma150.c | 7 +++
1 file changed, 3 insertions(+), 4
On Sat, 4 Jul 2015, linuxsea wrote:
Use real names this is :
From: Yang Bo linux...@163.com
Signed-off-by: Yang Bo linux...@163.com
Please resubmit the whole patch with your real name updated.
--
Jiri Kosina
SUSE Labs
--
To unsubscribe from this list: send the line unsubscribe
Hi Dirk,
On Fri, Jul 03, 2015 at 11:07:49AM +0200, Dirk Behme wrote:
diff --git a/include/linux/platform_data/zforce_ts.h
b/include/linux/platform_data/zforce_ts.h
index 44cd90f..1794268 100644
--- a/include/linux/platform_data/zforce_ts.h
+++ b/include/linux/platform_data/zforce_ts.h
@@
Some touchpads are configured with firmware which continues to scan for
fingers at a minimal scan rate even after receiving the HID power sleep
command. This allows a finger touching the touchpad to genrate a wake
event. This patch ensures that scanning is disabled if the touchpad is
not a wake
On Mon, Jul 06, 2015 at 12:33:06PM -0700, Joshua Clayton wrote:
Hi,
It seems to me that swapping error for ret buries the functional changes in
the patch...
would it be better to split them into a second cleanup patch?
Fair enough, although I am not sure if I ever get to the renaming again
From: Roger Quadros rog...@ti.com
The controller has a RESET pin which is usually controlled over
a GPIO line. If such a GPIO is provided, perform a RESET
during probe.
Signed-off-by: Roger Quadros rog...@ti.com
Signed-off-by: Dmitry Torokhov dmitry.torok...@gmail.com
---
Let's switch to using standard touchscreen device properties parsing module
instead of doing it by hand in the driver.
Signed-off-by: Dmitry Torokhov dmitry.torok...@gmail.com
---
drivers/input/touchscreen/pixcir_i2c_ts.c | 95 ++-
1 file changed, 44 insertions(+), 51
We are using threaded interrupt handler and thus are allowed to sleep.
Let's switch over to gpiod_get_value_cansleep() so that we do not get
ugly warnings in case GPIO controller might sleep when accessing GPIO.
Signed-off-by: Dmitry Torokhov dmitry.torok...@gmail.com
---
This allows uniform parsing on legacy, DT and ACPI systems.
Signed-off-by: Dmitry Torokhov dmitry.torok...@gmail.com
---
drivers/input/touchscreen/pixcir_i2c_ts.c | 26 +-
include/linux/platform_data/pixcir_i2c_ts.h | 1 -
2 files changed, 9 insertions(+), 18
input_mt_init_slots() will perform necessary settings for performing
multi-touch to single-touch emulation, we do not need to do that ourselves.
Signed-off-by: Dmitry Torokhov dmitry.torok...@gmail.com
---
drivers/input/touchscreen/pixcir_i2c_ts.c | 5 -
1 file changed, 5 deletions(-)
diff
These reg_default tables are not modified after initialized, so make them
const.
Signed-off-by: Axel Lin axel@ingics.com
---
drivers/input/misc/drv260x.c | 2 +-
drivers/input/misc/drv2665.c | 2 +-
drivers/input/misc/drv2667.c | 2 +-
3 files changed, 3 insertions(+), 3 deletions(-)
diff
Let's move driver's platform data definitions from include/linux/input/
into include/linux/platform_data/ so that it stays with the rest of
platform data definitions.
Signed-off-by: Dmitry Torokhov dmitry.torok...@gmail.com
---
drivers/input/touchscreen/pixcir_i2c_ts.c | 2 +-
On pm8xxx PMICs, shutdown and restart are signaled to the PMIC
via a pin called PS_HOLD. When this pin goes low, the PMIC
performs a configurable power sequence. Add a .shutdown hook so
that we can properly configure this power sequence for shutdown
or restart depending on the system state.
Hi, This patch is to add support for SiS i2c touch panel.
Thanks a lot.
Signed-off-by: Yuger yuger...@sis.com
---
drivers/input/touchscreen/Kconfig | 11 +
drivers/input/touchscreen/Makefile | 1 +
drivers/input/touchscreen/sis_i2c.c | 627
We want the hover event like BTN_LEFT, even no contract object,
it still can be reported to upper OS system.
Signed-off by: Duson Lin duson...@emc.com.tw
---
drivers/input/mouse/elan_i2c_core.c | 12 +---
1 file changed, 5 insertions(+), 7 deletions(-)
diff --git
31 matches
Mail list logo
