All of lore.kernel.org
 help / color / mirror / Atom feed
From: Harry van Haaren <harryhaaren@gmail.com>
To: Viresh Kumar <viresh.kumar@linaro.org>
Cc: linux-rt-users@vger.kernel.org,
	Thomas Gleixner <tglx@linutronix.de>,
	Steven Rostedt <rostedt@goodmis.org>,
	"Rafael J. Wysocki" <rjw@rjwysocki.net>
Subject: Re: CpuFreq Laptop Scaling broken?
Date: Wed, 27 Aug 2014 15:53:52 +0100	[thread overview]
Message-ID: <CAKudYbPyN0GZ1pMPLQMd_Ks0hELBhE35SN8A1hi3_v8MMPVAjg@mail.gmail.com> (raw)
In-Reply-To: <CAKudYbOMKp437Sqq-A8m4A-d-rLHCGLXM5cH3ep13vp11ocJyg@mail.gmail.com>

On Tue, Aug 26, 2014 at 11:44 PM, Harry van Haaren
<harryhaaren@gmail.com> wrote:
> On Tue, Aug 26, 2014 at 5:34 AM, Viresh Kumar <viresh.kumar@linaro.org> wrote:
>> The functions  of interest would be, drivers/cpufreq/cpufreq.c:
>> - static ssize_t show(struct kobject *kobj, struct attribute *attr, char *buf)
>> - static ssize_t store_scaling_governor(struct cpufreq_policy *policy,
>> const char *buf, size_t count)
>>
>> Try to add some prints there while returning errors and then try to change
>> governor from userspace and things might get somewhat better then..
>
> Thanks for the suggestion, I'll update once I have more info

Found a little time to check this: the cpufreq_get_policy() call
returns non-zero:

static ssize_t store_scaling_governor(struct cpufreq_policy *policy,
                    const char *buf, size_t count)
{
    int ret;
    char    str_governor[16];
    struct cpufreq_policy new_policy;

  printk( "RT debug: store_scaling_governor() with %s\n", buf );

    ret = cpufreq_get_policy(&new_policy, policy->cpu);
    if (ret)
  {
    printk( "RT debug: ERROR: get policy() returned \n" );
        return ret;
  }


dmesg:
[   43.186804] RT debug: store_scaling_governor() with performance
[   43.186811] RT debug: ERROR: get policy() returned


This output is from a fresh boot: so it seems that the getting the
current policy after
a boot isn't functioning right here.

  reply	other threads:[~2014-08-27 14:53 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-08-25 12:28 CpuFreq Laptop Scaling broken? Harry van Haaren
2014-08-25 13:55 ` Viresh Kumar
2014-08-25 13:56   ` Viresh Kumar
2014-08-25 16:58     ` Joakim Hernberg
2014-08-25 14:02   ` Harry van Haaren
2014-08-25 17:18     ` Fernando Lopez-Lezcano
2014-08-25 17:36       ` Harry van Haaren
2014-08-26  4:34     ` Viresh Kumar
2014-08-26 22:44       ` Harry van Haaren
2014-08-27 14:53         ` Harry van Haaren [this message]
     [not found]           ` <CAKohpokeUufzx7so6FcEd8rAg-MPw+2c9Aug9L_vXdu_4MvNOA@mail.gmail.com>
2014-09-05 12:06             ` Harry van Haaren
2014-09-05 12:50               ` Viresh Kumar
2014-09-05 22:47                 ` Thomas Gleixner
2014-09-25 12:44                   ` Harry van Haaren
2014-08-25 14:10   ` Steven Rostedt
     [not found]     ` <53FB4EEF.3060809@pavlinux.ru>
2014-08-25 15:03       ` Harry van Haaren

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=CAKudYbPyN0GZ1pMPLQMd_Ks0hELBhE35SN8A1hi3_v8MMPVAjg@mail.gmail.com \
    --to=harryhaaren@gmail.com \
    --cc=linux-rt-users@vger.kernel.org \
    --cc=rjw@rjwysocki.net \
    --cc=rostedt@goodmis.org \
    --cc=tglx@linutronix.de \
    --cc=viresh.kumar@linaro.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.