Skip to contentSkip to conversation

calling cpufreq_set

DISCUSSION Stefan Buettcher 2 participants 2 messages Nov 4, 2003 – Nov 5, 2003

lore
Share & tools
lore
#0 lore raw

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?

Stefan

#1 lore raw

Hi Stefan,

Quoted 10 lines · Stefan Buettcher

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.

Quoted 6 lines

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