Re: [PATCH v4 0/6] Touchscreen performance related fixes
On Tue, Dec 16, 2014 at 10:31:47AM +0200, Catalin Crenguta wrote: > > It seems that because the ribbon cable has both the analog and digital > signals, the analog signals are affected by the digital ones (hence > the touchscreen was working OK when the display was disabled). Putting > decoupling capacitors on X+, X-, Y+, Y- reduces the noise and the > false events disappear. IOW, the root cause is a design flaw in the BB-View 4.3 Cape? Thanks, Richard -- To unsubscribe from this list: send the line "unsubscribe linux-omap" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
Re: [PATCH v4 0/6] Touchscreen performance related fixes
On Fri, Dec 12, 2014 at 4:16 PM, Griffis, Brad wrote: > How are you configuring ti,charge-delay in your dts? I've seen this behavior > on some custom boards where we were using a smaller charge delay (0x400) to > begin with, and by upping it to 0xb000 we resolved the issue. These patches > however already specified ti,charge-delay = 0xb000 by default so this would > surprise me that it's still seeing that issue. Was the touchscreen working > as expected before these new patches, or does it have issues both ways? It seems that because the ribbon cable has both the analog and digital signals, the analog signals are affected by the digital ones (hence the touchscreen was working OK when the display was disabled). Putting decoupling capacitors on X+, X-, Y+, Y- reduces the noise and the false events disappear. I'm sorry for all the noise I have generated. Best regards, -- To unsubscribe from this list: send the line "unsubscribe linux-omap" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
Re: [PATCH v4 0/6] Touchscreen performance related fixes
On Fri, Dec 12, 2014 at 4:16 PM, Griffis, Brad wrote: > How are you configuring ti,charge-delay in your dts? I've seen this behavior > on some custom boards where we were using a smaller charge delay (0x400) to > begin with, and by upping it to 0xb000 we resolved the issue. These patches > however already specified ti,charge-delay = 0xb000 by default so this would > surprise me that it's still seeing that issue. Was the touchscreen working > as expected before these new patches, or does it have issues both ways? I have created a DTS for Beaglebone Black with 4 wire touchscreen and display which works on 3.18 stable and tsc-devel, omap2plus_defconfig with tsc and tilcdc support. It seems that with lcdc disabled, I am not getting false reports but when I'm activating the lcdc, I get a lot of false pen-downs/pen-ups. Even with tilcdc enabled, after it prints "timeout waiting for framedone" and the screen get blanked (white), the noise is gone. Regards, Catalin. -- To unsubscribe from this list: send the line "unsubscribe linux-omap" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
Re: [PATCH v4 0/6] Touchscreen performance related fixes
On Fri, Dec 12, 2014 at 4:16 PM, Griffis, Brad wrote: > How are you configuring ti,charge-delay in your dts? I've seen this behavior > on some custom boards where we were using a smaller charge delay (0x400) to > begin with, and by upping it to 0xb000 we resolved the issue. These patches > however already specified ti,charge-delay = 0xb000 by default so this would > surprise me that it's still seeing that issue. Was the touchscreen working > as expected before these new patches, or does it have issues both ways? Initially I had set the charge-delay to 0x400 and I was seeing many false pen-down/pen-up events With 0xb000, I was still getting many of them but less than with 0x400. -- To unsubscribe from this list: send the line "unsubscribe linux-omap" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
RE: [PATCH v4 0/6] Touchscreen performance related fixes
> -Original Message-
> From: Catalin Crenguta [mailto:catalin.creng...@gmail.com]
> I have tried your patches by cloning [1] and copying the relevant files over
> the kernel I've cloned from [2].
> It compiles & runs, but I'm seeing lots of pen-down/pen-up events when I'm
> not touching the screen.
> Any suggestions?
How are you configuring ti,charge-delay in your dts? I've seen this behavior
on some custom boards where we were using a smaller charge delay (0x400) to
begin with, and by upping it to 0xb000 we resolved the issue. These patches
however already specified ti,charge-delay = 0xb000 by default so this would
surprise me that it's still seeing that issue. Was the touchscreen working as
expected before these new patches, or does it have issues both ways?
N�r��yb�X��ǧv�^�){.n�+{��f��{ay� ʇڙ�,j��f���h���z� �w���
���j:+v���w�j�mzZ+�ݢj"��!�i
Re: [PATCH v4 0/6] Touchscreen performance related fixes
On Friday 12 December 2014 02:10 AM, Sebastian Andrzej Siewior wrote: > On 12/11/2014 09:34 PM, Nicolae Rosia wrote: >> Hello, > > Hi, > >> Any updates on this series? I don't see it applied in [1] or [2]. > > I manage to freeze am335x-evm with those patches and I think Vignesh > is looking into this. I was not able to reproduce this issue with my kernel configurations. I am yet to try with Sebastian's ".config" file. Not been able work on this. > >> Regards, >> Nicolae Rosia > > Sebastian > Regards, Vignesh -- To unsubscribe from this list: send the line "unsubscribe linux-omap" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
Re: [PATCH v4 0/6] Touchscreen performance related fixes
Hello, I have tried your patches by cloning [1] and copying the relevant files over the kernel I've cloned from [2]. It compiles & runs, but I'm seeing lots of pen-down/pen-up events when I'm not touching the screen. Any suggestions? Hardware: Beaglebone Black with BB-View 4.3 Cape from Farnell [1] git clone -b tsc-devel git://git.ti.com/kernel/tsc-adc.git (tsc-devel branch) [2] https://github.com/beagleboard/linux/tree/3.14 -- To unsubscribe from this list: send the line "unsubscribe linux-omap" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
Re: [PATCH v4 0/6] Touchscreen performance related fixes
On 12/11/2014 09:34 PM, Nicolae Rosia wrote: > Hello, Hi, > Any updates on this series? I don't see it applied in [1] or [2]. I manage to freeze am335x-evm with those patches and I think Vignesh is looking into this. > Regards, > Nicolae Rosia Sebastian -- To unsubscribe from this list: send the line "unsubscribe linux-omap" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
Re: [PATCH v4 0/6] Touchscreen performance related fixes
Hello, Any updates on this series? I don't see it applied in [1] or [2]. [1] https://github.com/RobertCNelson/ti-linux-kernel/commits/ti-linux-3.14.y/drivers/input/touchscreen/ti_am335x_tsc.c [2] https://github.com/RobertCNelson/ti-linux-kernel/commits/ti-linux-3.14.y-exp/drivers/input/touchscreen/ti_am335x_tsc.c Regards, Nicolae Rosia On Mon, Dec 1, 2014 at 12:29 PM, Vignesh R wrote: > > Hi, > > On Monday 01 December 2014 03:29 PM, Sebastian Andrzej Siewior wrote: >> On 12/01/2014 10:53 AM, Vignesh R wrote: >>> Hi Sebastian, >> >> Hi Vignesh, >> >>> I fixed the issue that was triggering the WARN_ON(). I think it would be >>> better if you tested these patches, before I posted them on the >>> mainline. I don't want to clutter the list with too main versions. Here >>> is the link to the tree with latest changes: >> >> awesome, thank you. >> >>> >>> git clone -b tsc-devel git://git.ti.com/kernel/tsc-adc.git >>> (tsc-devel branch) >> >> I will and let you know. >> >>> Please test the above tree and let me know the results. >>> I will post new version(v5) if there are no issues wrt IIO and TSC >>> working at the same time. >> >> Cool. Were you able to get in touch with someone who has a 5-wire touch? > > I have asked Jeff Lance to verify 5-wire touch. > > Regards > Vignesh > -- > To unsubscribe from this list: send the line "unsubscribe devicetree" in > the body of a message to majord...@vger.kernel.org > More majordomo info at http://vger.kernel.org/majordomo-info.html -- To unsubscribe from this list: send the line "unsubscribe linux-omap" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
Re: [PATCH v4 0/6] Touchscreen performance related fixes
Hi, On Monday 01 December 2014 03:29 PM, Sebastian Andrzej Siewior wrote: > On 12/01/2014 10:53 AM, Vignesh R wrote: >> Hi Sebastian, > > Hi Vignesh, > >> I fixed the issue that was triggering the WARN_ON(). I think it would be >> better if you tested these patches, before I posted them on the >> mainline. I don't want to clutter the list with too main versions. Here >> is the link to the tree with latest changes: > > awesome, thank you. > >> >> git clone -b tsc-devel git://git.ti.com/kernel/tsc-adc.git >> (tsc-devel branch) > > I will and let you know. > >> Please test the above tree and let me know the results. >> I will post new version(v5) if there are no issues wrt IIO and TSC >> working at the same time. > > Cool. Were you able to get in touch with someone who has a 5-wire touch? I have asked Jeff Lance to verify 5-wire touch. Regards Vignesh -- To unsubscribe from this list: send the line "unsubscribe linux-omap" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
Re: [PATCH v4 0/6] Touchscreen performance related fixes
On 12/01/2014 10:53 AM, Vignesh R wrote: > Hi Sebastian, Hi Vignesh, > I fixed the issue that was triggering the WARN_ON(). I think it would be > better if you tested these patches, before I posted them on the > mainline. I don't want to clutter the list with too main versions. Here > is the link to the tree with latest changes: awesome, thank you. > > git clone -b tsc-devel git://git.ti.com/kernel/tsc-adc.git > (tsc-devel branch) I will and let you know. > Please test the above tree and let me know the results. > I will post new version(v5) if there are no issues wrt IIO and TSC > working at the same time. Cool. Were you able to get in touch with someone who has a 5-wire touch? > Regards > Vignesh > Sebastian -- To unsubscribe from this list: send the line "unsubscribe linux-omap" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
Re: [PATCH v4 0/6] Touchscreen performance related fixes
Hi Sebastian, On Monday 24 November 2014 05:21 PM, Sebastian Andrzej Siewior wrote: > * Vignesh R | 2014-11-14 10:37:25 [+0530]: > >> This series of patches fix TSC defects related to lag in touchscreen >> performance and cursor jump at touch release. The lag was result of >> udelay in TSC interrupt handler. Cursor jump due to false pen-up event. >> The patches implement Advisory 1.0.31 in silicon errata of am335x-evm > am335x not -evm. The am335x-evm is a board (with its own advisory > document) built around the SoC. > > Just testing the v4. I can use now IIO and touchscren at the same time. > back at v1 I reported that it does not work, this has been fixed now. > I had it running for a few minutes, now I see one of WARN_ON() beeing > triggered (I've cut a few numbers so don't wonder about PID 2 and so on): > I fixed the issue that was triggering the WARN_ON(). I think it would be better if you tested these patches, before I posted them on the mainline. I don't want to clutter the list with too main versions. Here is the link to the tree with latest changes: git clone -b tsc-devel git://git.ti.com/kernel/tsc-adc.git (tsc-devel branch) Please test the above tree and let me know the results. I will post new version(v5) if there are no issues wrt IIO and TSC working at the same time. The cursor jump at touch release has been fixed. But I do see random cursor movement when dragging on the screen. This is not due to false pen-up events. My patches do not aim at fixing them. (the aim is to remove udelay in irq handler and fix false pen-ups). With these changes, false pen-ups have been eliminated and there is a significant improvement in the performance of TSC. I feel these patches can go in, if there are no other serious issues. I will work on random cursor jump in a separate patch series. Regards Vignesh -- To unsubscribe from this list: send the line "unsubscribe linux-omap" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
Re: [PATCH v4 0/6] Touchscreen performance related fixes
On Monday 24 November 2014 06:05 PM, Sebastian Andrzej Siewior wrote: > On 11/24/2014 01:16 PM, Vignesh R wrote: > >> I have tried running both IIO and TSC at the same time. But I have never >> seen WARN_ON() even after running for close to 30 min. Can you send me >> the exact script, so that it will be easy to reproduce? > > Sure thing. > - one shell > evtest /dev/input/event2 > - second shell > ./iio-test.sh > with: > > |#!/bin/sh > | > |while [ 1 = 1 ] > |do > |cat /sys/bus/iio/devices/iio\:device0/in_voltage4_raw > |done > > > the kernel config: https://breakpoint.cc/am335x-config > I was able to reproduce this issue. When ADC hits WARN_ON(), the TSC steps should be disabled. But, in this case, TSC is sampling the first Y co-ordinate and all TSC steps are enabled. REG_SE: 0x1ffc1 ADC_STAT: 0x24 Any idea why this may be happening? Regards Vignesh -- To unsubscribe from this list: send the line "unsubscribe linux-omap" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
Re: [PATCH v4 0/6] Touchscreen performance related fixes
On 11/24/2014 01:16 PM, Vignesh R wrote: > I have tried running both IIO and TSC at the same time. But I have never > seen WARN_ON() even after running for close to 30 min. Can you send me > the exact script, so that it will be easy to reproduce? Sure thing. - one shell evtest /dev/input/event2 - second shell ./iio-test.sh with: |#!/bin/sh | |while [ 1 = 1 ] |do |cat /sys/bus/iio/devices/iio\:device0/in_voltage4_raw |done the kernel config: https://breakpoint.cc/am335x-config > > Regards > Vignesh Sebastian -- To unsubscribe from this list: send the line "unsubscribe linux-omap" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
Re: [PATCH v4 0/6] Touchscreen performance related fixes
On Monday 24 November 2014 05:21 PM, Sebastian Andrzej Siewior wrote: > * Vignesh R | 2014-11-14 10:37:25 [+0530]: > >> This series of patches fix TSC defects related to lag in touchscreen >> performance and cursor jump at touch release. The lag was result of >> udelay in TSC interrupt handler. Cursor jump due to false pen-up event. >> The patches implement Advisory 1.0.31 in silicon errata of am335x-evm > am335x not -evm. The am335x-evm is a board (with its own advisory > document) built around the SoC. > > Just testing the v4. I can use now IIO and touchscren at the same time. > back at v1 I reported that it does not work, this has been fixed now. > I had it running for a few minutes, now I see one of WARN_ON() beeing > triggered (I've cut a few numbers so don't wonder about PID 2 and so on): > > |dmesg |grep WARNING | wc -l > |10 > | dmesg |grep WARNING > |[306.257995] WARNING: CPU: 0 PID: 97 at mfd/ti_am335x_tscadc.c:94 > am335x_tsc_se_set_once+0xf8/0x104 > |[365.469591] WARNING: CPU: 0 PID: 58 at mfd/ti_am335x_tscadc.c:94 > am335x_tsc_se_set_once+0xf8/0x104 > |[379.255904] WARNING: CPU: 0 PID: 24 at mfd/ti_am335x_tscadc.c:94 > am335x_tsc_se_set_once+0xf8/0x104 > |[426.230505] WARNING: CPU: 0 PID: 35 at mfd/ti_am335x_tscadc.c:94 > am335x_tsc_se_set_once+0xf8/0x104 > |[435.654091] WARNING: CPU: 0 PID: 28 at mfd/ti_am335x_tscadc.c:94 > am335x_tsc_se_set_once+0xf8/0x104 > |[438.897519] WARNING: CPU: 0 PID: 91 at mfd/ti_am335x_tscadc.c:94 > am335x_tsc_se_set_once+0xf8/0x104 > |[525.720193] WARNING: CPU: 0 PID: 88 at mfd/ti_am335x_tscadc.c:94 > am335x_tsc_se_set_once+0xf8/0x104 > |[527.644770] WARNING: CPU: 0 PID: 38 at mfd/ti_am335x_tscadc.c:94 > am335x_tsc_se_set_once+0xf8/0x104 > |[557.218349] WARNING: CPU: 0 PID: 56 at mfd/ti_am335x_tscadc.c:94 > am335x_tsc_se_set_once+0xf8/0x104 > |[610.077274] WARNING: CPU: 0 PID: 2 at mfd/ti_am335x_tscadc.c:94 > am335x_tsc_se_set_once+0xf8/0x104 > > The complete trace: > > |[610.110692] CPU: 0 PID: 4422 Comm: cat Tainted: GW 3.18.0-rc6+ > #1745 > |[610.118577] [] (unwind_backtrace) from [] > (show_stack+0x10/0x14) > |[610.126772] [] (show_stack) from [] > (warn_slowpath_common+0x68/0x88) > |[610.135313] [] (warn_slowpath_common) from [] > (warn_slowpath_null+0x1c/0x24) > |[610.144586] [] (warn_slowpath_null) from [] > (am335x_tsc_se_set_once+0xf8/0x104 [ti_am335x_tscadc]) > |[610.155886] [] (am335x_tsc_se_set_once [ti_am335x_tscadc]) from > [] (tiadc_read_raw+0xbc/0x190 [ti_am335x_adc]) > |[610.168326] [] (tiadc_read_raw [ti_am335x_adc]) from [] > (iio_read_channel_info+0x9c/0xa4 [industrialio]) > |[610.180191] [] (iio_read_channel_info [industrialio]) from > [] (dev_attr_show+0x1c/0x48) > |[610.190477] [] (dev_attr_show) from [] > (sysfs_kf_seq_show+0x8c/0x110) > |[610.199108] [] (sysfs_kf_seq_show) from [] > (kernfs_seq_show+0x24/0x28) > |[610.207833] [] (kernfs_seq_show) from [] > (seq_read+0x1b4/0x47c) > |[610.215922] [] (seq_read) from [] (vfs_read+0x8c/0x148) > |[610.223269] [] (vfs_read) from [] (SyS_read+0x40/0x8c) > |[610.230525] [] (SyS_read) from [] > (ret_fast_syscall+0x0/0x30) > > Could you please look at that one? (I tested it on am335x-evm btw). I have tried running both IIO and TSC at the same time. But I have never seen WARN_ON() even after running for close to 30 min. Can you send me the exact script, so that it will be easy to reproduce? Regards Vignesh > > Sebastian > -- To unsubscribe from this list: send the line "unsubscribe linux-omap" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
Re: [PATCH v4 0/6] Touchscreen performance related fixes
* Vignesh R | 2014-11-14 10:37:25 [+0530]: >This series of patches fix TSC defects related to lag in touchscreen >performance and cursor jump at touch release. The lag was result of >udelay in TSC interrupt handler. Cursor jump due to false pen-up event. >The patches implement Advisory 1.0.31 in silicon errata of am335x-evm am335x not -evm. The am335x-evm is a board (with its own advisory document) built around the SoC. Just testing the v4. I can use now IIO and touchscren at the same time. back at v1 I reported that it does not work, this has been fixed now. I had it running for a few minutes, now I see one of WARN_ON() beeing triggered (I've cut a few numbers so don't wonder about PID 2 and so on): |dmesg |grep WARNING | wc -l |10 | dmesg |grep WARNING |[306.257995] WARNING: CPU: 0 PID: 97 at mfd/ti_am335x_tscadc.c:94 am335x_tsc_se_set_once+0xf8/0x104 |[365.469591] WARNING: CPU: 0 PID: 58 at mfd/ti_am335x_tscadc.c:94 am335x_tsc_se_set_once+0xf8/0x104 |[379.255904] WARNING: CPU: 0 PID: 24 at mfd/ti_am335x_tscadc.c:94 am335x_tsc_se_set_once+0xf8/0x104 |[426.230505] WARNING: CPU: 0 PID: 35 at mfd/ti_am335x_tscadc.c:94 am335x_tsc_se_set_once+0xf8/0x104 |[435.654091] WARNING: CPU: 0 PID: 28 at mfd/ti_am335x_tscadc.c:94 am335x_tsc_se_set_once+0xf8/0x104 |[438.897519] WARNING: CPU: 0 PID: 91 at mfd/ti_am335x_tscadc.c:94 am335x_tsc_se_set_once+0xf8/0x104 |[525.720193] WARNING: CPU: 0 PID: 88 at mfd/ti_am335x_tscadc.c:94 am335x_tsc_se_set_once+0xf8/0x104 |[527.644770] WARNING: CPU: 0 PID: 38 at mfd/ti_am335x_tscadc.c:94 am335x_tsc_se_set_once+0xf8/0x104 |[557.218349] WARNING: CPU: 0 PID: 56 at mfd/ti_am335x_tscadc.c:94 am335x_tsc_se_set_once+0xf8/0x104 |[610.077274] WARNING: CPU: 0 PID: 2 at mfd/ti_am335x_tscadc.c:94 am335x_tsc_se_set_once+0xf8/0x104 The complete trace: |[610.110692] CPU: 0 PID: 4422 Comm: cat Tainted: GW 3.18.0-rc6+ #1745 |[610.118577] [] (unwind_backtrace) from [] (show_stack+0x10/0x14) |[610.126772] [] (show_stack) from [] (warn_slowpath_common+0x68/0x88) |[610.135313] [] (warn_slowpath_common) from [] (warn_slowpath_null+0x1c/0x24) |[610.144586] [] (warn_slowpath_null) from [] (am335x_tsc_se_set_once+0xf8/0x104 [ti_am335x_tscadc]) |[610.155886] [] (am335x_tsc_se_set_once [ti_am335x_tscadc]) from [] (tiadc_read_raw+0xbc/0x190 [ti_am335x_adc]) |[610.168326] [] (tiadc_read_raw [ti_am335x_adc]) from [] (iio_read_channel_info+0x9c/0xa4 [industrialio]) |[610.180191] [] (iio_read_channel_info [industrialio]) from [] (dev_attr_show+0x1c/0x48) |[610.190477] [] (dev_attr_show) from [] (sysfs_kf_seq_show+0x8c/0x110) |[610.199108] [] (sysfs_kf_seq_show) from [] (kernfs_seq_show+0x24/0x28) |[610.207833] [] (kernfs_seq_show) from [] (seq_read+0x1b4/0x47c) |[610.215922] [] (seq_read) from [] (vfs_read+0x8c/0x148) |[610.223269] [] (vfs_read) from [] (SyS_read+0x40/0x8c) |[610.230525] [] (SyS_read) from [] (ret_fast_syscall+0x0/0x30) Could you please look at that one? (I tested it on am335x-evm btw). Sebastian -- To unsubscribe from this list: send the line "unsubscribe linux-omap" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
[PATCH v4 0/6] Touchscreen performance related fixes
This series of patches fix TSC defects related to lag in touchscreen performance and cursor jump at touch release. The lag was result of udelay in TSC interrupt handler. Cursor jump due to false pen-up event. The patches implement Advisory 1.0.31 in silicon errata of am335x-evm to avoid false pen-up events and remove udelay. The advisory says to use steps 1 to 4 for ADC and 5 to 16 for TSC (assuming 4 wire TSC and 4 channel ADC). Further the X co-ordinate must be the last one to be sampled just before charge step. The first two patches implement the required changes. A DT parameter to configure the duration of tsc charge step. It represents number of ADC clock cycles to wait between applying the step configuration registers and going back to the IDLE state. The charge delay value can vary across boards. Configuring correct value of charge delay is important to avoid false pen-up events. Hence it is necessary to expose charge-delay value as DT parameter. The pen-up detection happens immediately after the charge step so this does in fact function as a hardware knob for adjusting the amount of settling time. After applying these changes false pen-up events have not be observed and smooth circles can be drawn on touch screen. The performance is much better in recognizing quick movement across the screen. No lag or cursor jump is observed. Change log: v3: - Replace delta filtering logic in TSC driver with median filtering as suggested by Richard. - Addressed Lee Jones comments. v2: - Addressed comments by Hartmut Knaack - patch 2 was split into two as per Lee Jones comment Brad Griffis (2): input: touchscreen: ti_am335x_tsc Interchange touchscreen and ADC steps input: touchscreen: ti_am335x_tsc: Remove udelay in interrupt handler Vignesh R (4): mfd: ti_am335x_tscadc: Remove unwanted reg_se_cache save ARM: dts: AM335x: Make charge delay a DT parameter for TSC input: touchscreen: ti_am335x_tsc: Use charge delay DT parameter input: touchscreen: ti_am335x_tsc: Replace delta filtering with median filtering .../bindings/input/touchscreen/ti-tsc-adc.txt | 15 ++ arch/arm/boot/dts/am335x-evm.dts | 1 + drivers/iio/adc/ti_am335x_adc.c| 5 +- drivers/input/touchscreen/ti_am335x_tsc.c | 186 +++-- drivers/mfd/ti_am335x_tscadc.c | 7 +- include/linux/mfd/ti_am335x_tscadc.h | 4 +- 6 files changed, 127 insertions(+), 91 deletions(-) -- 1.9.1 -- To unsubscribe from this list: send the line "unsubscribe linux-omap" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
