From mboxrd@z Thu Jan 1 00:00:00 1970 From: viresh.kumar@linaro.org (Viresh Kumar) Date: Tue, 25 Apr 2017 16:43:01 +0530 Subject: Touchscreen failure with CONFIG_CPU_FREQ_DEFAULT_GOV_ONDEMAND In-Reply-To: References: <20170424040709.GG26900@vireshk-i7> <20170424112906.GR26900@vireshk-i7> <20170424114343.GS26900@vireshk-i7> <20170425050633.GV26900@vireshk-i7> Message-ID: <20170425111301.GC1928@vireshk-i7> To: linux-arm-kernel@lists.infradead.org List-Id: linux-arm-kernel.lists.infradead.org On 25-04-17, 08:09, Fabio Estevam wrote: > Hi Viresh, > > On Tue, Apr 25, 2017 at 2:06 AM, Viresh Kumar wrote: > > > Honestly, I don't have a clue on how can we fix it for you now :) > > > > @Rafael: Any idea apart from running at max all the time? > > > > what touchscreen driver are you using btw? Just curious to see if there is any > > bug in there. Handling touchscreen events shouldn't require us to run at max > > freq. > > imx6q-sabresd board uses a drivers/input/touchscreen/egalax_ts.c touchscreen. > > > > > @shawn: Saw something similar ever ? > > I do not see the problem with the NXP kernel, but was not able to > identify what makes the touchscreen not to fail at 396MHz in their > kernel. @Shawn/Sascha: Can you guys help here? This looks to be some imx specific stuff now. -- viresh