cpufreq Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Dominik Brodowski <linux@brodo.de>
To: Stefan Buettcher <stefan@buettcher.org>
Cc: cpufreq ML <cpufreq@www.linux.org.uk>
Subject: Re: calling cpufreq_set
Date: Wed, 5 Nov 2003 15:29:13 +0100	[thread overview]
Message-ID: <20031105142913.GA19764@brodo.de> (raw)
In-Reply-To: <3FA839CD.3070404@buettcher.org>

Hi Stefan,

On Wed, Nov 05, 2003 at 12:44:13AM +0100, Stefan Buettcher wrote:
> Hi,
> 
> I am new to this list as well as cpufreq at all.
> 
> I have written a kernel module (2.4.19-something) on the
> ipaq 5400. This module makes direct calls to cpufreq_set.
> While the system does not break, the usb does. usbnet
> suddenly stops working and will resist my efforts to work
> afterwards.
> 
> When I do not do the calls from within the kernel but use
> the proc file interface provided by cpufreq, the system is
> stable and usb has no problems.
> 
> Has anyone experienced similar problems? Any idea why
> this happens?

I'm not aware of the details of the ipaq cpufreq driver - it's neither in
the kernel sources, nor was it ever posted on this list... so it _might_ be
a driver- or platform-specific problem. Maybe some timing calculations are
wrong after calls to cpufreq_set, maybe there needs to be some delay between
subsequent calls to cpufreq_set, ...

Other than that, cpufreq_set() is deprecated in 2.6.

	Dominik

      reply	other threads:[~2003-11-05 14:29 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-11-04 23:44 calling cpufreq_set Stefan Buettcher
2003-11-05 14:29 ` Dominik Brodowski [this message]

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=20031105142913.GA19764@brodo.de \
    --to=linux@brodo.de \
    --cc=cpufreq@www.linux.org.uk \
    --cc=stefan@buettcher.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