From: viresh.kumar@linaro.org (Viresh Kumar)
To: linux-arm-kernel@lists.infradead.org
Subject: Touchscreen failure with CONFIG_CPU_FREQ_DEFAULT_GOV_ONDEMAND
Date: Mon, 24 Apr 2017 09:37:09 +0530 [thread overview]
Message-ID: <20170424040709.GG26900@vireshk-i7> (raw)
In-Reply-To: <CAOMZO5BZ8Z8dfwsfuiunNQ_q39_k4QJg7jLPQfaxn+YBsmz2jw@mail.gmail.com>
On 21-04-17, 13:11, Fabio Estevam wrote:
> Hi,
>
> Running 4.11-rc7 on a imx6q-sabresd board I notice that egalax
> touchscreen stops generating evtest events after a random period of
> time.
>
> This problem can be avoided if I unselect CONFIG_CPU_FREQ_DEFAULT_GOV_ONDEMAND:
>
> --- a/arch/arm/configs/imx_v6_v7_defconfig
> +++ b/arch/arm/configs/imx_v6_v7_defconfig
> @@ -54,7 +54,6 @@ CONFIG_CMA=y
> CONFIG_CMDLINE="noinitrd console=ttymxc0,115200"
> CONFIG_KEXEC=y
> CONFIG_CPU_FREQ=y
> -CONFIG_CPU_FREQ_DEFAULT_GOV_ONDEMAND=y
> CONFIG_ARM_IMX6Q_CPUFREQ=y
> CONFIG_CPU_IDLE=y
> CONFIG_VFP=y
>
> With this change evtest always capture all touchscreen events. No
> single failure is seen.
>
> I could see the same behavior with all mainline kernels I tested (4.9 and 4.10).
>
> Any ideas as to how fix this bug when CONFIG_CPU_FREQ_DEFAULT_GOV_ONDEMAND=y?
So as Rafael pointed out the problem doesn't happen if you stay at the max
frequencies, but otherwise.
You need to investigate on why that is the case. You can go to the cpufreq sysfs
directory and see what frequencies are getting selected, etc..
Give me output of this for now:
grep . /sys/devices/system/cpu/cpufreq/policy0/*
grep . /sys/devices/system/cpu/cpufreq/policy0/stats/*
--
viresh
next prev parent reply other threads:[~2017-04-24 4:07 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-04-21 16:11 Touchscreen failure with CONFIG_CPU_FREQ_DEFAULT_GOV_ONDEMAND Fabio Estevam
2017-04-21 21:28 ` Rafael J. Wysocki
2017-04-21 21:37 ` Fabio Estevam
2017-04-21 21:33 ` Rafael J. Wysocki
2017-04-24 4:07 ` Viresh Kumar [this message]
2017-04-24 11:20 ` Fabio Estevam
2017-04-24 11:29 ` Viresh Kumar
2017-04-24 11:37 ` Fabio Estevam
2017-04-24 11:43 ` Viresh Kumar
2017-04-24 11:51 ` Fabio Estevam
2017-04-25 5:06 ` Viresh Kumar
2017-04-25 11:09 ` Fabio Estevam
2017-04-25 11:13 ` Viresh Kumar
[not found] ` <CAHCN7xJVicKuAc0dDbzBg4h2d1UUP66iKkSsWN_f=rPd4mOZSw@mail.gmail.com>
2017-04-25 13:43 ` Fabio Estevam
2017-04-25 14:35 ` Adam Ford
2017-04-25 15:24 ` Fabio Estevam
2017-04-26 4:18 ` Viresh Kumar
2017-04-27 0:57 ` Adam Ford
2017-04-27 1:50 ` Fabio Estevam
2017-04-27 2:01 ` Adam Ford
2017-04-27 2:20 ` Fabio Estevam
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20170424040709.GG26900@vireshk-i7 \
--to=viresh.kumar@linaro.org \
--cc=linux-arm-kernel@lists.infradead.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).