On Fri, 13 Jun 2014, Antonio Ospite wrote:
> > Previously the tpkbd driver had various functions marked "_tp" to indicate
> > that it's for the "mouse" half of the keyboard as the kernel sees it,
> > however it does nothing special with the keyboard half. I was intending
> > (somewhat sloppily)
Hi Benjamin,
On Fri, Jun 13, 2014 at 1:29 PM, Benjamin Tissoires
wrote:
> This solves a bug with the wireless receiver:
Your patch does get rid of the crash. But, it does not fix it at the
root cause.
> - at plug, the wireless receiver does not know which Wacom device it is
> connected to, so
Hi,
Here's another patch which has been pending for months.
On Mon, Nov 18, 2013 at 09:29:01AM -0600, Felipe Balbi wrote:
> In the hopes that people run new kernels on
> their devices, let's add a warning message
> asking users to have their DTS file fixed.
>
> The goal is that by Linux 4.0 we w
On Thu, 12 Jun 2014 09:56:41 +0100 (BST)
Jamie Lentin wrote:
> On Wed, 11 Jun 2014, Antonio Ospite wrote:
>
[...]
> >> +static int tpcompactkbd_input_mapping(struct hid_device *hdev,
> >
> > Maybe name these functions like tpkbd_input_mapping_compact()?
> >
> > This way the namespace is more c
Signed-off-by: Ulrik De Bie
---
drivers/input/mouse/elantech.c | 1 +
1 file changed, 1 insertion(+)
diff --git a/drivers/input/mouse/elantech.c b/drivers/input/mouse/elantech.c
index 0eb185b..fa150d9 100644
--- a/drivers/input/mouse/elantech.c
+++ b/drivers/input/mouse/elantech.c
@@ -1617,6 +16
Some elantech v3 touchpad equipped laptops also have a trackpoint, before
this commit, these give sync errors. With this patch, the trackpoint is
provided as another input device: 'Elantech PS/2 TrackPoint'
The patch will also output messages that do not follow the expected pattern.
In the mean ti
Patch 1 adds support for trackpoint on elantech driver for v3 models.
Patch 2 adds a psmouse_reset when the elantech probes fails. Patch 2 depends on
Patch 1.
Changes since v2:
* psmouse_reset change is now moved to a separate patch
* comments/white spaces/newlines cleanup
* Unexpected trackpoi
On Jun 13 2014 or thereabouts, Benjamin Tissoires wrote:
> On Jun 13 2014 or thereabouts, Dmitry Torokhov wrote:
> > On Fri, Jun 13, 2014 at 04:29:04PM -0400, Benjamin Tissoires wrote:
> > > This field is not used, remove it.
> >
> > We must have lost the assignment, but it should be assigned to p
On Fri, Jun 13, 2014 at 04:32:18PM -0400, Benjamin Tissoires wrote:
> This reverts commit 1b2faaf7e219fc2905d75afcd4c815e5d39eda80.
>
> The Intuos4 series presents a bug in which it hangs if it receives
> a set feature command while switching to the enhanced mode.
> This bug is triggered when plug
On Jun 13 2014 or thereabouts, Dmitry Torokhov wrote:
> On Fri, Jun 13, 2014 at 04:29:04PM -0400, Benjamin Tissoires wrote:
> > This field is not used, remove it.
>
> We must have lost the assignment, but it should be assigned to phys of
> corresponding input device.
hehe. Even in 2007, when the
On Fri, Jun 13, 2014 at 04:29:04PM -0400, Benjamin Tissoires wrote:
> This field is not used, remove it.
We must have lost the assignment, but it should be assigned to phys of
corresponding input device.
>
> Signed-off-by: Benjamin Tissoires
> ---
> drivers/input/tablet/wacom.h | 1 -
> d
This reverts commit 1b2faaf7e219fc2905d75afcd4c815e5d39eda80.
The Intuos4 series presents a bug in which it hangs if it receives
a set feature command while switching to the enhanced mode.
This bug is triggered when plugging an Intuos 4 while having
a gnome user session up and running.
Signed-off
This solves a bug with the wireless receiver:
- at plug, the wireless receiver does not know which Wacom device it is
connected to, so it does not actually creates all the LEDs
- when the tablet connects, wacom->wacom_wac.features.type is set to the
proper device so that wacom_wac can understan
This field is not used, remove it.
Signed-off-by: Benjamin Tissoires
---
drivers/input/tablet/wacom.h | 1 -
drivers/input/tablet/wacom_sys.c | 2 --
2 files changed, 3 deletions(-)
diff --git a/drivers/input/tablet/wacom.h b/drivers/input/tablet/wacom.h
index 9ebf0ed..70b1e71 100644
--- a/
> This is a conversion queue driver for the mx25 SoC. It uses the central
> ADC which is used by two seperate independent queues. This driver
> prepares different conversion configurations for each possible input.
> For a conversion it creates a conversionqueue of one item with the
> correct confi
> Ok, so you decided to continue setting mode on every LED brightness
> update. That should be fine, but you never answered my question about
> whether it is necessary?
I decided to do it that way because official driver did it as well. I
can check if it is necessary.
> You're almost done. One la
Hi Denis,
On Fri, Jun 13, 2014 at 12:21 PM, Denis Carikli wrote:
> Signed-off-by: Denis Carikli
> ---
> .../imx25-eukrea-mbimxsd25-baseboard-cmo-qvga.dts | 13 +
> 1 file changed, 13 insertions(+)
>
> diff --git a/arch/arm/boot/dts/imx25-eukrea-mbimxsd25-baseboard-cmo-qvga.dts
>
From: Markus Pargmann
This is the core driver for imx25 touchscreen/adc driver. The module
has one shared ADC and two different conversion queues which use the
ADC. The two queues are identical. Both can be used for general purpose
ADC but one is meant to be used for touchscreens.
This driver is
Hi,
I haven't seen any new comments on that serie since february,
so I picked it again and I tried to address all remaining comments.
To be able to test that patch, the following patch will need to be
cherry-picked.
http://lists.infradead.org/pipermail/linux-arm-kernel/2014-June/263494.html
De
From: Markus Pargmann
This is a driver for the imx25 ADC/TSC module. It controls the
touchscreen conversion queue and creates a touchscreen input device.
The driver currently only supports 4 wire touchscreens. The driver uses
a simple conversion queue of precharge, touch detection, X measurement,
Signed-off-by: Denis Carikli
---
arch/arm/boot/dts/imx25.dtsi | 11 ---
1 file changed, 8 insertions(+), 3 deletions(-)
diff --git a/arch/arm/boot/dts/imx25.dtsi b/arch/arm/boot/dts/imx25.dtsi
index 98783f5..5564167 100644
--- a/arch/arm/boot/dts/imx25.dtsi
+++ b/arch/arm/boot/dts/imx2
Signed-off-by: Denis Carikli
---
arch/arm/configs/imx_v4_v5_defconfig |2 ++
1 file changed, 2 insertions(+)
diff --git a/arch/arm/configs/imx_v4_v5_defconfig
b/arch/arm/configs/imx_v4_v5_defconfig
index 397f43c..b6b3674 100644
--- a/arch/arm/configs/imx_v4_v5_defconfig
+++ b/arch/arm/confi
From: Markus Pargmann
This is a conversion queue driver for the mx25 SoC. It uses the central
ADC which is used by two seperate independent queues. This driver
prepares different conversion configurations for each possible input.
For a conversion it creates a conversionqueue of one item with the
Signed-off-by: Denis Carikli
---
.../imx25-eukrea-mbimxsd25-baseboard-cmo-qvga.dts | 13 +
1 file changed, 13 insertions(+)
diff --git a/arch/arm/boot/dts/imx25-eukrea-mbimxsd25-baseboard-cmo-qvga.dts
b/arch/arm/boot/dts/imx25-eukrea-mbimxsd25-baseboard-cmo-qvga.dts
index 9797280
On Thu, Jun 12, 2014 at 11:34:12PM +0300, Janne Kanniainen wrote:
> This driver adds support for USB controlled led panels that exists in
> MSI GT683R laptop
>
> Signed-off-by: Janne Kanniainen
> ---
> Changes in v2:
> - sorted headers to alphabetic order
> - using devm_kzalloc
>
Hi
On Fri, Jun 13, 2014 at 9:24 AM, Hans de Goede wrote:
>> You rely on external data here, so please check for truncation. If
>> anyone changes psmouse->ps2dev.serio->phys, they would not notice that
>> you rely on it here. So I'd do sth like:
>>
>> size_t n = snprintf(etd->tp_phys, sizeof(etd->
26 matches
Mail list logo
