On Mon, Sep 22, 2014 at 4:39 PM, Thierry Reding
wrote:
>
> On Tue, Sep 02, 2014 at 10:56:46AM +0800, Daniel Kurtz wrote:
> > There are several different models of N116BGE. According to the commit
> > that added innolux_n116bge_mode [0], this N116BGE is for the eDP variety.
On Mon, Sep 22, 2014 at 4:39 PM, Thierry Reding
thierry.red...@gmail.com wrote:
On Tue, Sep 02, 2014 at 10:56:46AM +0800, Daniel Kurtz wrote:
There are several different models of N116BGE. According to the commit
that added innolux_n116bge_mode [0], this N116BGE is for the eDP variety
Hi Thierry,
Congratulations! I saw in one thread that you said you are out on
paternity leave.
You mentioned that you would be back around v3.17-rc6, which should be
soonish, so just a gentle ping on this patch for when you return.
Thanks,
-Daniel
--
To unsubscribe from this list: send the
Hi Thierry,
Congratulations! I saw in one thread that you said you are out on
paternity leave.
You mentioned that you would be back around v3.17-rc6, which should be
soonish, so just a gentle ping on this patch for when you return.
Thanks,
-Daniel
--
To unsubscribe from this list: send the
N116BGE panel support
The clock and htotal values from add by that patch are out of spec according to
the datasheets I have seen for the eDP N116BGE (-EA2 and -EB2).
This patch changes the values to the "Typ" values on the datasheet.
Signed-off-by: Daniel Kurtz
---
Thierry,
It i
: simple: Add Innolux N116BGE panel support
The clock and htotal values from add by that patch are out of spec according to
the datasheets I have seen for the eDP N116BGE (-EA2 and -EB2).
This patch changes the values to the Typ values on the datasheet.
Signed-off-by: Daniel Kurtz djku
-by: Günther Noack
Signed-off-by: Daniel Kurtz
---
I am able to compile test this change, but would appreciate help testing it
on a system that uses xf86-video-fbdev.
Thanks!
drivers/gpu/drm/exynos/exynos_drm_fbdev.c | 1 +
1 file changed, 1 insertion(+)
diff --git a/drivers/gpu/drm/exynos
siarhei.siamas...@gmail.com
Reported-by: Günther Noack m...@guenthernoack.de
Signed-off-by: Daniel Kurtz djku...@chromium.org
---
I am able to compile test this change, but would appreciate help testing it
on a system that uses xf86-video-fbdev.
Thanks!
drivers/gpu/drm/exynos/exynos_drm_fbdev.c | 1 +
1
On Fri, Jun 20, 2014 at 7:59 AM, Siarhei Siamashka
wrote:
>
> On Fri, 4 Apr 2014 17:22:01 +0800
> Daniel Kurtz wrote:
>
> > Kernel access to the eyxnos fbdev framebuffer is via its gem object's
> > kernel mapping (kvaddr, stored in info->screen_base).
> >
On Fri, Jun 20, 2014 at 7:59 AM, Siarhei Siamashka
siarhei.siamas...@gmail.com wrote:
On Fri, 4 Apr 2014 17:22:01 +0800
Daniel Kurtz djku...@chromium.org wrote:
Kernel access to the eyxnos fbdev framebuffer is via its gem object's
kernel mapping (kvaddr, stored in info-screen_base
On Thu, May 8, 2014 at 12:33 PM, Seung-Woo Kim wrote:
>
> Hello Daniel,
>
> On 2014년 05월 07일 23:14, Daniel Kurtz wrote:
> > On Wed, May 7, 2014 at 1:14 PM, Seung-Woo Kim
> > wrote:
> >> Hi Daniel,
> >>
> >> On 2014년 05월 05일 00:26, Daniel Kurtz
On Thu, May 8, 2014 at 12:33 PM, Seung-Woo Kim sw0312@samsung.com wrote:
Hello Daniel,
On 2014년 05월 07일 23:14, Daniel Kurtz wrote:
On Wed, May 7, 2014 at 1:14 PM, Seung-Woo Kim sw0312@samsung.com
wrote:
Hi Daniel,
On 2014년 05월 05일 00:26, Daniel Kurtz wrote:
Mixer hardware
On Wed, May 7, 2014 at 1:14 PM, Seung-Woo Kim wrote:
> Hi Daniel,
>
> On 2014년 05월 05일 00:26, Daniel Kurtz wrote:
>> Mixer hardware supports offsetting dma from start of source buffer using
>> the MXR_GRP_SXY register.
>>
>> Signed-off-by: Daniel Kurtz
On Wed, May 7, 2014 at 1:14 PM, Seung-Woo Kim sw0312@samsung.com wrote:
Hi Daniel,
On 2014년 05월 05일 00:26, Daniel Kurtz wrote:
Mixer hardware supports offsetting dma from start of source buffer using
the MXR_GRP_SXY register.
Signed-off-by: Daniel Kurtz djku...@chromium.org
These constants directly define register values, so move them to the
register definition header.
Also, the logic used for setting fmt from bpp is either/or, so just use
if/else.
** No functional change
Signed-off-by: Daniel Kurtz
---
drivers/gpu/drm/exynos/exynos_mixer.c | 19
nce the driver does not actually supported single-buffer formats,
buf_num will always be 2, and we drop the broken 1-buffer case.
Signed-off-by: Daniel Kurtz
---
drivers/gpu/drm/exynos/exynos_mixer.c | 17 +++--
1 file changed, 3 insertions(+), 14 deletions(-)
diff --git a/drivers/gpu/
AFAICT, the only difference between NV12 and NV21 is Cr:Cb vs Cb:Cr.
Since the video processor can handle either order, it should be able to
handle both formats.
Signed-off-by: Daniel Kurtz
---
drivers/gpu/drm/exynos/exynos_drm_plane.c | 1 +
drivers/gpu/drm/exynos/exynos_mixer.c | 12
I don't actually have a way of testing the video processor changes, but they
seem correct from looking at the code. Hopefully someone has a way of testing
them.
Daniel Kurtz (4):
drm/exynos/mixer: move format definitions to regs-mixer
drm/exynos/mixer: use MXR_GRP_SXY_SY
drm/exynos/mixer
Mixer hardware supports offsetting dma from start of source buffer using
the MXR_GRP_SXY register.
Signed-off-by: Daniel Kurtz
---
drivers/gpu/drm/exynos/exynos_mixer.c | 8 +++-
1 file changed, 3 insertions(+), 5 deletions(-)
diff --git a/drivers/gpu/drm/exynos/exynos_mixer.c
b/drivers
AFAICT, the only difference between NV12 and NV21 is Cr:Cb vs Cb:Cr.
Since the video processor can handle either order, it should be able to
handle both formats.
Signed-off-by: Daniel Kurtz djku...@chromium.org
---
drivers/gpu/drm/exynos/exynos_drm_plane.c | 1 +
drivers/gpu/drm/exynos
I don't actually have a way of testing the video processor changes, but they
seem correct from looking at the code. Hopefully someone has a way of testing
them.
Daniel Kurtz (4):
drm/exynos/mixer: move format definitions to regs-mixer
drm/exynos/mixer: use MXR_GRP_SXY_SY
drm/exynos/mixer
Mixer hardware supports offsetting dma from start of source buffer using
the MXR_GRP_SXY register.
Signed-off-by: Daniel Kurtz djku...@chromium.org
---
drivers/gpu/drm/exynos/exynos_mixer.c | 8 +++-
1 file changed, 3 insertions(+), 5 deletions(-)
diff --git a/drivers/gpu/drm/exynos
the driver does not actually supported single-buffer formats,
buf_num will always be 2, and we drop the broken 1-buffer case.
Signed-off-by: Daniel Kurtz djku...@chromium.org
---
drivers/gpu/drm/exynos/exynos_mixer.c | 17 +++--
1 file changed, 3 insertions(+), 14 deletions(-)
diff --git
These constants directly define register values, so move them to the
register definition header.
Also, the logic used for setting fmt from bpp is either/or, so just use
if/else.
** No functional change
Signed-off-by: Daniel Kurtz djku...@chromium.org
---
drivers/gpu/drm/exynos/exynos_mixer.c
.
Signed-off-by: Daniel Kurtz
---
drivers/gpu/drm/exynos/exynos_drm_fbdev.c | 1 -
1 file changed, 1 deletion(-)
diff --git a/drivers/gpu/drm/exynos/exynos_drm_fbdev.c
b/drivers/gpu/drm/exynos/exynos_drm_fbdev.c
index 2dcc589..3270a36 100644
--- a/drivers/gpu/drm/exynos/exynos_drm_fbdev.c
+++ b
set fix->smem_{start,len} or
fix->mmio_{start,len} fields.
This avoids leaking kernel, physical and dma mapped addresses to user
space via the ioctls FBIOGET_VSCREENINFO and FBIOGET_FSCREENINFO.
Signed-off-by: Daniel Kurtz
---
drivers/gpu/drm/exynos/exynos_drm_fbdev.c | 7 ---
1 file c
fix-smem_{start,len} or
fix-mmio_{start,len} fields.
This avoids leaking kernel, physical and dma mapped addresses to user
space via the ioctls FBIOGET_VSCREENINFO and FBIOGET_FSCREENINFO.
Signed-off-by: Daniel Kurtz djku...@chromium.org
---
drivers/gpu/drm/exynos/exynos_drm_fbdev.c | 7 ---
1
.
Signed-off-by: Daniel Kurtz djku...@chromium.org
---
drivers/gpu/drm/exynos/exynos_drm_fbdev.c | 1 -
1 file changed, 1 deletion(-)
diff --git a/drivers/gpu/drm/exynos/exynos_drm_fbdev.c
b/drivers/gpu/drm/exynos/exynos_drm_fbdev.c
index 2dcc589..3270a36 100644
--- a/drivers/gpu/drm/exynos
On Tue, Mar 18, 2014 at 2:08 PM, Inki Dae wrote:
> 2014-03-18 14:45 GMT+09:00 Kukjin Kim :
>> Inki Dae wrote:
>>>
>>> Applied.
>>>
>>> Thanks,
>>> Inki Dae
>>>
>>> 2014-03-17 12:28 GMT+09:00 Daniel Kurtz :
>>>
On Tue, Mar 18, 2014 at 2:08 PM, Inki Dae inki@samsung.com wrote:
2014-03-18 14:45 GMT+09:00 Kukjin Kim kgene@samsung.com:
Inki Dae wrote:
Applied.
Thanks,
Inki Dae
2014-03-17 12:28 GMT+09:00 Daniel Kurtz djku...@chromium.org:
The following commit [0] fixed a use-after-free
The following commit [0] fixed a use-after-free, but left the subdrv open
in the error path.
[0] commit 6ca605f7c70895a35737435f17ae9cc5e36f1466
drm/exynos: Fix freeing issues in exynos_drm_drv.c
Signed-off-by: Daniel Kurtz
---
Hi, I noticed this when reviewing some recent patches.
I am only
The following commit [0] fixed a use-after-free, but left the subdrv open
in the error path.
[0] commit 6ca605f7c70895a35737435f17ae9cc5e36f1466
drm/exynos: Fix freeing issues in exynos_drm_drv.c
Change-Id: I452e944bf090fb11434d9e34213c890c41c15d73
Signed-off-by: Daniel Kurtz
---
drivers/gpu
The following commit [0] fixed a use-after-free, but left the subdrv open
in the error path.
[0] commit 6ca605f7c70895a35737435f17ae9cc5e36f1466
drm/exynos: Fix freeing issues in exynos_drm_drv.c
Change-Id: I452e944bf090fb11434d9e34213c890c41c15d73
Signed-off-by: Daniel Kurtz djku
The following commit [0] fixed a use-after-free, but left the subdrv open
in the error path.
[0] commit 6ca605f7c70895a35737435f17ae9cc5e36f1466
drm/exynos: Fix freeing issues in exynos_drm_drv.c
Signed-off-by: Daniel Kurtz djku...@chromium.org
---
Hi, I noticed this when reviewing some recent
Hi Tomasz,
Thank you for the reviews.
On Dec 9, 2013 5:15 AM, "Tomasz Figa" wrote:
>
> Hi Daniel,
>
> On Thursday 21 of November 2013 02:21:24 Daniel Kurtz wrote:
> > These tables are all immutable, make them const to save 4416 bytes of RAM.
> >
> > siz
Hi Tomasz,
Thank you for the reviews.
On Dec 9, 2013 5:15 AM, Tomasz Figa t.f...@samsung.com wrote:
Hi Daniel,
On Thursday 21 of November 2013 02:21:24 Daniel Kurtz wrote:
These tables are all immutable, make them const to save 4416 bytes of RAM.
size arch/arm/mach-exynos/pmu.o
These tables are all immutable, make them const to save 4416 bytes of RAM.
size arch/arm/mach-exynos/pmu.o
textdata bss
8484420 4 // before
5264 4 4 // after
Signed-off-by: Daniel Kurtz
---
arch/arm/mach-exynos/pmu.c | 14
The restore functions do not modify the passed in struct sleep_save,
so that parameter can be const.
This allows us to pass in const struct. This allows us to use const
structs sleep_save to define system registers that will always be
restored to a constant value.
Signed-off-by: Daniel Kurtz
The restore functions do not modify the passed in struct sleep_save,
so that parameter can be const.
This allows us to pass in const struct. This allows us to use const
structs sleep_save to define system registers that will always be
restored to a constant value.
Signed-off-by: Daniel Kurtz
These tables are all immutable, make them const to save 4416 bytes of RAM.
size arch/arm/mach-exynos/pmu.o
textdata bss
8484420 4 // before
5264 4 4 // after
Signed-off-by: Daniel Kurtz djku...@chromium.org
---
arch/arm/mach-exynos/pmu.c
On Fri, May 17, 2013 at 4:36 PM, Jean Delvare wrote:
> Hi Robert,
>
> On Thu, 16 May 2013 13:44:55 +1000, Robert Norris wrote:
>> On Wed, May 15, 2013 at 09:49:23PM +0200, Jean Delvare wrote:
>> > > Interrupt: pin B routed to IRQ 0
>> >
>> > Hmm, this "IRQ 0" is quite odd. I'm wondering if
On Fri, May 17, 2013 at 4:36 PM, Jean Delvare kh...@linux-fr.org wrote:
Hi Robert,
On Thu, 16 May 2013 13:44:55 +1000, Robert Norris wrote:
On Wed, May 15, 2013 at 09:49:23PM +0200, Jean Delvare wrote:
Interrupt: pin B routed to IRQ 0
Hmm, this IRQ 0 is quite odd. I'm wondering if
issue of doubly filtered pointer
> events.
>
> Reported-by: Daniel Kurtz
> Signed-off-by: Henrik Rydberg
> ---
> Hi Daniel,
>
> This patch has only been compile tested, but chances are that it will
> work for you, together with the previous patch.
>
> Cheers,
&
On Fri, Feb 15, 2013 at 11:36 AM, Henrik Rydberg wrote:
> The pointer emulation events are derived from contact values that
> have already been filtered, so send the emulated events as is.
>
> Reported-by: Daniel Kurtz
> Signed-off-by: Henrik Rydberg
Hi Henrik,
Brilliant! Gl
EIO.
Signed-off-by: Daniel Kurtz
---
Changes from V1:
- simplified implied logic (thanks Henrik!)
- error print the partial number of bytes received, not -EIO
drivers/input/touchscreen/atmel_mxt_ts.c | 83 +---
1 file changed, 45 insertions(+), 38 deletions(-)
diff --
On Wed, Dec 26, 2012 at 5:01 PM, Daniel Kurtz wrote:
>
> It is a bit more precise to compute the total number of pixels first and
> then divide, rather than multiplying the line pixel count by the
> already-rounded line duration.
>
> Signed-off-by: Daniel Kurtz
Ping?
> -
On Wed, Dec 26, 2012 at 5:01 PM, Daniel Kurtz djku...@chromium.org wrote:
It is a bit more precise to compute the total number of pixels first and
then divide, rather than multiplying the line pixel count by the
already-rounded line duration.
Signed-off-by: Daniel Kurtz djku...@chromium.org
.
Signed-off-by: Daniel Kurtz djku...@chromium.org
---
Changes from V1:
- simplified implied logic (thanks Henrik!)
- error print the partial number of bytes received, not -EIO
drivers/input/touchscreen/atmel_mxt_ts.c | 83 +---
1 file changed, 45 insertions(+), 38
On Fri, Feb 15, 2013 at 11:36 AM, Henrik Rydberg rydb...@euromail.se wrote:
The pointer emulation events are derived from contact values that
have already been filtered, so send the emulated events as is.
Reported-by: Daniel Kurtz djku...@chromium.org
Signed-off-by: Henrik Rydberg rydb
the issue of doubly filtered pointer
events.
Reported-by: Daniel Kurtz djku...@chromium.org
Signed-off-by: Henrik Rydberg rydb...@euromail.se
---
Hi Daniel,
This patch has only been compile tested, but chances are that it will
work for you, together with the previous patch.
Cheers,
Henrik
On Wed, Feb 13, 2013 at 1:52 PM, Dmitry Torokhov
wrote:
> On Fri, Feb 01, 2013 at 04:28:32PM +0800, Daniel Kurtz wrote:
>> The input fuzz algorithm does a pretty good job filtering out small
>> jitter on input samples.
>>
>> However, there is a subtle problem when f
On Wed, Feb 13, 2013 at 1:52 PM, Dmitry Torokhov
dmitry.torok...@gmail.com wrote:
On Fri, Feb 01, 2013 at 04:28:32PM +0800, Daniel Kurtz wrote:
The input fuzz algorithm does a pretty good job filtering out small
jitter on input samples.
However, there is a subtle problem when fuzz is used
ew
tracking ID.
Signed-off-by: Daniel Kurtz
---
drivers/input/mouse/synaptics.c | 30 +++---
1 file changed, 27 insertions(+), 3 deletions(-)
diff --git a/drivers/input/mouse/synaptics.c b/drivers/input/mouse/synaptics.c
index b6c6838..47159d8 100644
--- a/drive
this in the mt layer/input core,
so, for now, just disable fuzz for the synaptics IMAGE_SENSOR path that
uses input_mt_report_pointer_emulation().
Signed-off-by: Daniel Kurtz
---
drivers/input/mouse/synaptics.c | 3 ++-
1 file changed, 2 insertions(+), 1 deletion(-)
diff --git a/drivers/input/mouse
rom the object table.
3) Spurious or bootloader induced interrupts
Signed-off-by: Benson Leung
Signed-off-by: Daniel Kurtz
---
drivers/input/touchscreen/atmel_mxt_ts.c | 51 +---
1 file changed, 40 insertions(+), 11 deletions(-)
diff --git a/drivers/input/touchscr
Signed-off-by: Daniel Kurtz
---
drivers/input/touchscreen/atmel_mxt_ts.c | 17 +++--
1 file changed, 11 insertions(+), 6 deletions(-)
diff --git a/drivers/input/touchscreen/atmel_mxt_ts.c
b/drivers/input/touchscreen/atmel_mxt_ts.c
index 6c2c712..76a25d3 100644
--- a/drivers/input
before enabling the irq (or handling
messages).
Signed-off-by: Daniel Kurtz
---
drivers/input/touchscreen/atmel_mxt_ts.c | 32
1 file changed, 20 insertions(+), 12 deletions(-)
diff --git a/drivers/input/touchscreen/atmel_mxt_ts.c
b/drivers/input/touchscreen
i2c addr and reloads object table and creates
a new input device.
Signed-off-by: Benson Leung
Signed-off-by: Daniel Kurtz
Signed-off-by: Yufeng Shen
---
drivers/input/touchscreen/atmel_mxt_ts.c | 128 +--
1 file changed, 87 insertions(+), 41 deletions(-)
diff
From: Benson Leung
175ms is not enough time to update the firmware. Set to
500ms.
Signed-off-by: Benson Leung
---
drivers/input/touchscreen/atmel_mxt_ts.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/drivers/input/touchscreen/atmel_mxt_ts.c
From: Benson Leung
Rather than msleep for MXT_RESET_TIME and MXT_FWRESET_TIME
during the transition to bootloader mode and the transition
back from app, wait for the CHG assert to indicate that the
transition is done.
This change replaces the msleep with a wait for completion that
the
device during fw update, no need to worry
about device open/close events.
2) If firmware update fails, the device and driver will still be in
bootloader mode and an improperly configured input device will not exist.
Signed-off-by: Daniel Kurtz
---
drivers/input/touchscreen/atmel_mxt_ts.c | 10
Move input device initialization to its own helper function.
This is in preparation of a future patch that makes input device
conditional on the device not being in its bootloader.
Signed-off-by: Daniel Kurtz
---
drivers/input/touchscreen/atmel_mxt_ts.c | 91 ++--
1
From: Benson Leung
The driver should not immediately read bootloader status when
in Application Update Mode. The CHG line will assert when the device
has made a state transition and is ready to report a new status
via i2c.
This change adds a wait for completion in mxt_check_bootloader,
and
ive, this is an IO error, so we use
some helper functions to convert these partial transfers to -EIO in a
uniform way. Other error codes might still be useful, though, so we pass
them up unmodified.
Signed-off-by: Daniel Kurtz
---
drivers/input/touchscreen/atmel_mxt_ts.c |
bootloader resets
Input: atmel_mxt_ts - increase FWRESET_TIME
Daniel Kurtz (6):
Input: atmel_mxt_ts - refactor i2c error handling
Input: atmel_mxt_ts - register input device before request_irq
Input: atmel_mxt_ts - refactor input device creation
Input: atmel_mxt_ts - handle bootloader mode
bootloader resets
Input: atmel_mxt_ts - increase FWRESET_TIME
Daniel Kurtz (6):
Input: atmel_mxt_ts - refactor i2c error handling
Input: atmel_mxt_ts - register input device before request_irq
Input: atmel_mxt_ts - refactor input device creation
Input: atmel_mxt_ts - handle bootloader mode
, this is an IO error, so we use
some helper functions to convert these partial transfers to -EIO in a
uniform way. Other error codes might still be useful, though, so we pass
them up unmodified.
Signed-off-by: Daniel Kurtz djku...@chromium.org
---
drivers/input/touchscreen/atmel_mxt_ts.c | 92
From: Benson Leung ble...@chromium.org
The driver should not immediately read bootloader status when
in Application Update Mode. The CHG line will assert when the device
has made a state transition and is ready to report a new status
via i2c.
This change adds a wait for completion in
Move input device initialization to its own helper function.
This is in preparation of a future patch that makes input device
conditional on the device not being in its bootloader.
Signed-off-by: Daniel Kurtz djku...@chromium.org
---
drivers/input/touchscreen/atmel_mxt_ts.c | 91
device during fw update, no need to worry
about device open/close events.
2) If firmware update fails, the device and driver will still be in
bootloader mode and an improperly configured input device will not exist.
Signed-off-by: Daniel Kurtz djku...@chromium.org
---
drivers/input/touchscreen
From: Benson Leung ble...@chromium.org
175ms is not enough time to update the firmware. Set to
500ms.
Signed-off-by: Benson Leung ble...@chromium.org
---
drivers/input/touchscreen/atmel_mxt_ts.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git
From: Benson Leung ble...@chromium.org
Rather than msleep for MXT_RESET_TIME and MXT_FWRESET_TIME
during the transition to bootloader mode and the transition
back from app, wait for the CHG assert to indicate that the
transition is done.
This change replaces the msleep with a wait for completion
exit switches to APP i2c addr and reloads object table and creates
a new input device.
Signed-off-by: Benson Leung ble...@chromium.org
Signed-off-by: Daniel Kurtz djku...@chromium.org
Signed-off-by: Yufeng Shen mile...@chromium.org
---
drivers/input/touchscreen/atmel_mxt_ts.c | 128
before enabling the irq (or handling
messages).
Signed-off-by: Daniel Kurtz djku...@chromium.org
---
drivers/input/touchscreen/atmel_mxt_ts.c | 32
1 file changed, 20 insertions(+), 12 deletions(-)
diff --git a/drivers/input/touchscreen/atmel_mxt_ts.c
b/drivers
...@chromium.org
Signed-off-by: Daniel Kurtz djku...@chromium.org
---
drivers/input/touchscreen/atmel_mxt_ts.c | 17 +++--
1 file changed, 11 insertions(+), 6 deletions(-)
diff --git a/drivers/input/touchscreen/atmel_mxt_ts.c
b/drivers/input/touchscreen/atmel_mxt_ts.c
index 6c2c712
the object table.
3) Spurious or bootloader induced interrupts
Signed-off-by: Benson Leung ble...@chromium.org
Signed-off-by: Daniel Kurtz djku...@chromium.org
---
drivers/input/touchscreen/atmel_mxt_ts.c | 51 +---
1 file changed, 40 insertions(+), 11 deletions(-)
diff
this in the mt layer/input core,
so, for now, just disable fuzz for the synaptics IMAGE_SENSOR path that
uses input_mt_report_pointer_emulation().
Signed-off-by: Daniel Kurtz djku...@chromium.org
---
drivers/input/mouse/synaptics.c | 3 ++-
1 file changed, 2 insertions(+), 1 deletion(-)
diff --git
.
Signed-off-by: Daniel Kurtz djku...@chromium.org
---
drivers/input/mouse/synaptics.c | 30 +++---
1 file changed, 27 insertions(+), 3 deletions(-)
diff --git a/drivers/input/mouse/synaptics.c b/drivers/input/mouse/synaptics.c
index b6c6838..47159d8 100644
--- a/drivers/input
It is a bit more precise to compute the total number of pixels first and
then divide, rather than multiplying the line pixel count by the
already-rounded line duration.
Signed-off-by: Daniel Kurtz
---
drivers/gpu/drm/drm_irq.c |6 +-
1 files changed, 5 insertions(+), 1 deletions
It is a bit more precise to compute the total number of pixels first and
then divide, rather than multiplying the line pixel count by the
already-rounded line duration.
Signed-off-by: Daniel Kurtz djku...@chromium.org
---
drivers/gpu/drm/drm_irq.c |6 +-
1 files changed, 5 insertions
chained_irq_enter/exit() already mask/unmask the chained interrupt.
There is no need to also explicitly do it in the handler.
Signed-off-by: Daniel Kurtz
---
arch/arm/mach-exynos/common.c |7 ---
1 files changed, 0 insertions(+), 7 deletions(-)
diff --git a/arch/arm/mach-exynos
chained_irq_enter/exit() already maskack/unmask the chained interrupt.
There is no need to also explicitly do it in the handler.
Signed-off-by: Daniel Kurtz djku...@chromium.org
---
arch/arm/mach-exynos/common.c |7 ---
1 files changed, 0 insertions(+), 7 deletions(-)
diff --git a/arch
On Mon, Aug 13, 2012 at 5:42 AM, Henrik Rydberg wrote:
> By sending a full frame of events at the same time, the irqsoff
> latency at heavy load is brought down from 200 us to 100 us.
>
> Signed-off-by: Henrik Rydberg
> ---
> drivers/input/evdev.c | 68
>
On Mon, Aug 13, 2012 at 5:42 AM, Henrik Rydberg wrote:
> On heavy event loads, such as a multitouch driver, the irqsoff latency
> can be as high as 250 us. By accumulating a frame worth of data
> before passing it on, the latency can be dramatically reduced. As a
> side effect, the special
On Mon, Aug 13, 2012 at 5:42 AM, Henrik Rydberg rydb...@euromail.se wrote:
On heavy event loads, such as a multitouch driver, the irqsoff latency
can be as high as 250 us. By accumulating a frame worth of data
before passing it on, the latency can be dramatically reduced. As a
side effect,
On Mon, Aug 13, 2012 at 5:42 AM, Henrik Rydberg rydb...@euromail.se wrote:
By sending a full frame of events at the same time, the irqsoff
latency at heavy load is brought down from 200 us to 100 us.
Signed-off-by: Henrik Rydberg rydb...@euromail.se
---
drivers/input/evdev.c | 68
On Sat, Jul 21, 2012 at 2:31 AM, Chase Douglas
wrote:
>
> On 07/20/2012 02:03 AM, Daniel Kurtz wrote:
>>>>>>
>>>>>> * Leave the device as SEMI_MT, but provide the real locations, and
>>>>>> allow userspace to determine the device vendor
On Sat, Jul 21, 2012 at 2:31 AM, Chase Douglas
chase.doug...@canonical.com wrote:
On 07/20/2012 02:03 AM, Daniel Kurtz wrote:
* Leave the device as SEMI_MT, but provide the real locations, and
allow userspace to determine the device vendor/model/etc. If
userspace knows that a specific device
On Fri, Jul 20, 2012 at 3:25 PM, Henrik Rydberg wrote:
> On Fri, Jul 20, 2012 at 11:14:25AM +0800, Chung-Yih Wang (王崇懿) wrote:
>> From our experiments, the assumption of "the slowest corner is the
>> stationary finger" is not always true. That is the major reason we want to
>> report the firmware
On Fri, Jul 20, 2012 at 3:25 PM, Henrik Rydberg rydb...@euromail.se wrote:
On Fri, Jul 20, 2012 at 11:14:25AM +0800, Chung-Yih Wang (王崇懿) wrote:
From our experiments, the assumption of the slowest corner is the
stationary finger is not always true. That is the major reason we want to
report
On Fri, Jul 20, 2012 at 12:16 AM, Chase Douglas
wrote:
>
> On 07/18/2012 08:02 PM, Chung-Yih Wang (王崇懿) wrote:
>>
>> Hi Chase,
>>
>> Thanks for your great comments. You are right, it is impossible to
>> get correct finger tracking if both fingers are moving. However, we
>> think it still
On Fri, Jul 20, 2012 at 12:16 AM, Chase Douglas
chase.doug...@canonical.com wrote:
On 07/18/2012 08:02 PM, Chung-Yih Wang (王崇懿) wrote:
Hi Chase,
Thanks for your great comments. You are right, it is impossible to
get correct finger tracking if both fingers are moving. However, we
think
On Fri, Jul 6, 2012 at 3:15 AM, Henrik Rydberg wrote:
> On Thu, Jul 05, 2012 at 10:22:30AM -0700, Dmitry Torokhov wrote:
>> Hi Daniel, Henrik,
>>
>> On Thu, Jun 28, 2012 at 09:08:05PM +0800, Daniel Kurtz wrote:
>> > If sysfs entry creation fails, the driver is st
On Fri, Jul 6, 2012 at 3:15 AM, Henrik Rydberg rydb...@euromail.se wrote:
On Thu, Jul 05, 2012 at 10:22:30AM -0700, Dmitry Torokhov wrote:
Hi Daniel, Henrik,
On Thu, Jun 28, 2012 at 09:08:05PM +0800, Daniel Kurtz wrote:
If sysfs entry creation fails, the driver is still usable, so don't
801 - 894 of 894 matches
Mail list logo
