public inbox for linux-arm-kernel@lists.infradead.org
 help / color / mirror / Atom feed
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 17:13:43 +0530	[thread overview]
Message-ID: <20170424114343.GS26900@vireshk-i7> (raw)
In-Reply-To: <CAOMZO5BpAsJAKv-p=WPevUnx71fxbLtunJe-0ijVT7T9m7AMSQ@mail.gmail.com>

On 24-04-17, 08:37, Fabio Estevam wrote:
> On Mon, Apr 24, 2017 at 8:29 AM, Viresh Kumar <viresh.kumar@linaro.org> wrote:
> 
> > So clearly the system isn't changing the frequency a lot here and you stayed at
> > the min freq for ever. Please give output of this as well:
> >
> > grep . /sys/devices/system/cpu/cpufreq/ondemand/*
> 
> #  grep . /sys/devices/system/cpu/cpufreq/ondemand/*
> /sys/devices/system/cpu/cpufreq/ondemand/ignore_nice_load:0
> /sys/devices/system/cpu/cpufreq/ondemand/io_is_busy:0
> /sys/devices/system/cpu/cpufreq/ondemand/min_sampling_rate:10000
> /sys/devices/system/cpu/cpufreq/ondemand/powersave_bias:0
> /sys/devices/system/cpu/cpufreq/ondemand/sampling_down_factor:1
> /sys/devices/system/cpu/cpufreq/ondemand/sampling_rate:109000

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.

> /sys/devices/system/cpu/cpufreq/ondemand/up_threshold:95
> 
> > I am also worried if the interrupts from the touchscreen will be enough to boost
> > the frequency of the CPU ?
> 
> It does not seem that the interrupts from the touchscreen boost the
> frequency of the CPU.
> 
> When I keep touching the panel, the CPU frequency stays at 396 MHz.
> 
> Thanks

-- 
viresh

  reply	other threads:[~2017-04-24 11:43 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 [this message]
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=20170424114343.GS26900@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