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: Tue, 25 Apr 2017 10:36:33 +0530 [thread overview]
Message-ID: <20170425050633.GV26900@vireshk-i7> (raw)
In-Reply-To: <CAOMZO5AkTKjU5kw0gszLVdVOc_Sb_sWhr65heE==kyw=5rcN-g@mail.gmail.com>
On 24-04-17, 08:51, Fabio Estevam wrote:
> On Mon, Apr 24, 2017 at 8:43 AM, Viresh Kumar <viresh.kumar@linaro.org> wrote:
>
> > 110 ms is your sampling rate right now. Looks too high.
> >
> > Try doing this:
> >
> > echo 10000 > /sys/devices/system/cpu/cpufreq/ondemand/sampling_rate
> >
> > and retry your tests.
>
> Tried 10ms and also 1ms, but touchscreen also failed in both cases.
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.
@shawn: Saw something similar ever ?
--
viresh
next prev parent reply other threads:[~2017-04-25 5:06 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
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 [this message]
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=20170425050633.GV26900@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