Re: [PATCH v4 0/6] Touchscreen performance related fixes
On Fri, Dec 12, 2014 at 4:16 PM, Griffis, Brad bgrif...@ti.com 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 bgrif...@ti.com 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 bgrif...@ti.com 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
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
TLV320AIC3104 Sample rate problem
Hello, I'm using an Audio Cape Rev. B connected to BeagleBone Black (MCLK=12MHz) and I'm trying to record audio at sample rate 8KHz. Recording and playback using ALSA is OK, but when playing the recorded samples on PC you can hear that the actual sample rate is lower (the pitch shifted to a lower tone). I have added debug messages throughout the alsa driver tlv320aic3x.c, and I found out that the PLL parameters are computed correctly as in TLV320AIC3104 Datasheet Table found at page 27. (p: 1 j: 8 d: 1920 r: 1). Has anyone else encountered a problem like this? Can someone with more experience check the driver? Kernel: https://github.com/beagleboard/linux , commit 2bcc89c, 3.14.19+. Best regards, Catalin Crenguta -- 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
