linux-riscv.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: Carlos Eduardo de Paula <me@carlosedp.com>
To: Paul Walmsley <paul.walmsley@sifive.com>
Cc: linux-riscv@lists.infradead.org
Subject: Re: Changing SiFive Unleashed core clock rate on 5.x kernel
Date: Fri, 16 Aug 2019 15:59:03 -0300	[thread overview]
Message-ID: <CADnnUqeUwjhmFp5moem4Cx-ux1kAmhpdyeerTqZ2cNhyvrT_hw@mail.gmail.com> (raw)
In-Reply-To: <alpine.DEB.2.21.9999.1908131908000.19217@viisi.sifive.com>

Got it, just to be clear, the sysfs changes only work on this 5.3 tree
and patches right? Not on my current 5.2-rc7.

Thanks!

On Tue, Aug 13, 2019 at 11:09 PM Paul Walmsley <paul.walmsley@sifive.com> wrote:
>
> On Tue, 13 Aug 2019, Paul Walmsley wrote:
>
> > On Mon, 12 Aug 2019, Carlos Eduardo de Paula wrote:
> >
> > > Now with Kernel 5.x and with the board DTB, what's the correct way to
> > > set this clock rate?
> >
> > There are some experimental patches here:
> >
> > https://github.com/sifive/riscv-linux/tree/dev/paulw/cpufreq-dt-aloe-v5.3-rc4
> >
> > Only the userspace governor is enabled - for one-off, manual frequency
> > changes, like the one you mentioned above.
>
> By the way, the command lines to change this would be the usual CPUFreq
> sysfs changes.  Something like this:
>
> echo userspace > /sys/devices/system/cpu/cpufreq/policy0/scaling_governor
> echo 1400000 > /sys/devices/system/cpu/cpufreq/policy0/scaling_setspeed
>
>
> - Paul



-- 
________________________________________
Carlos Eduardo de Paula
me@carlosedp.com
http://carlosedp.com
http://twitter.com/carlosedp
Linkedin
________________________________________

_______________________________________________
linux-riscv mailing list
linux-riscv@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-riscv

  reply	other threads:[~2019-08-16 18:59 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-08-12 20:32 Changing SiFive Unleashed core clock rate on 5.x kernel Carlos Eduardo de Paula
2019-08-13 21:22 ` Paul Walmsley
2019-08-14  2:09   ` Paul Walmsley
2019-08-16 18:59     ` Carlos Eduardo de Paula [this message]
2019-08-16 19:50       ` Paul Walmsley
2019-08-16 20:50         ` Carlos Eduardo de Paula
2019-08-16 20:57           ` Paul Walmsley
2019-08-16 21:17             ` Carlos Eduardo de Paula
2019-08-16 21:44               ` Carlos Eduardo de Paula

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=CADnnUqeUwjhmFp5moem4Cx-ux1kAmhpdyeerTqZ2cNhyvrT_hw@mail.gmail.com \
    --to=me@carlosedp.com \
    --cc=linux-riscv@lists.infradead.org \
    --cc=paul.walmsley@sifive.com \
    /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).