public inbox for linux-omap@vger.kernel.org
 help / color / mirror / Atom feed
From: Martin Margraf <m_margraf@web.de>
To: linux-omap-open-source@linux.omap.com
Subject: change cpu_freq
Date: Wed, 14 Jun 2006 14:34:25 +0200	[thread overview]
Message-ID: <44900251.3050702@web.de> (raw)

hi,

how can i change the cpu frequency of my osk5912 using the 
scale_cpu_freq feature of the 2.6.16 kernel? how is the syntax of this? 
is there a documentation available (except the ones in the documentation 
folder of my linux directory)?

my next question is, how can i read/write to the regs of the omap5912? 
during using 2.4 kernel i was able to access the regs directly with a 
module. but now with 2.6 kernel i get a segmentation fault. maybe 
someone can help me?

regards

martin

             reply	other threads:[~2006-06-14 12:34 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-06-14 12:34 Martin Margraf [this message]
2006-06-14 12:44 ` change cpu_freq Juha Yrjölä
  -- strict thread matches above, loose matches on Subject: below --
2006-06-15 18:19 Minjie Lin
2006-06-16  6:40 Martin Margraf
2006-06-16 23:35 Minjie Lin

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=44900251.3050702@web.de \
    --to=m_margraf@web.de \
    --cc=linux-omap-open-source@linux.omap.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