Ramesh,
For scaling from userspace, you can move to the userspace governor. Kindly look into this article:
>-----Original Message-----
>From: linux-omap-owner@xxxxxxxxxxxxxxx [mailto:linux-omap-
>owner@xxxxxxxxxxxxxxx] On Behalf Of Gupta, Ramesh
>Sent: Wednesday, August 27, 2008 7:39 PM
>To: Nayak, Rajendra; linux-omap@xxxxxxxxxxxxxxx
>Subject: RE: [PATCH 00/01] CPUFreq: OMAP3 cpufreq driver
>
>Hi,
>
>
>> -----Original Message-----
>> From: linux-omap-owner@xxxxxxxxxxxxxxx
>> [mailto:linux-omap-owner@xxxxxxxxxxxxxxx] On Behalf Of Rajendra Nayak
>> Sent: Monday, August 11, 2008 6:42 PM
>> To: linux-omap@xxxxxxxxxxxxxxx
>> Subject: [PATCH 00/01] CPUFreq: OMAP3 cpufreq driver
>>
>> Hi,
>>
>> The patch which follows implements the CPUFreq driver for
>> OMAP3, tested on 3430sdp.
>> The driver uses API's defined as part of the OMAP-PM layer.
>>
>> Performance Governor is selected by default in the defconfig.
>> After bootup, to switch to ondemand or any other governor use
>> the following sysfs interface
>> /sys/devices/system/cpu/cpu0/cpufreq/scaling_governor
>
>With the ondemand Governor I am some seeing issues for DSP Bridge.
>clk_notifier_register call for iva2_ck is successful but I am seeing below messages
>on opp change request from IVA.
>
><3>clock: Could not find fieldval 0 for clock iva2_ck parent dpll2_m2_ck
>clock: Could not find fieldval 0 for clock iva2_ck parent dpll2_m2_ck
><3>clock: Could not find fieldval 0 for clock iva2_ck parent dpll2_m2_ck
>clock: Could not find fieldval 0 for clock iva2_ck parent dpll2_m2_ck
>
>Looks like access to memory stalls while opp is changing ( some times I observed
>MMU Fault messages from IVA while opp is changing). Also some times I observed
>that after the opp change IVA Power state registers are not accessible( I am getting
>BUG# soft lock up while accessing IVA Power state registers).
>
>Can you please provide your inputs on these issues?
>
>Is there any way to manually switch opp using sysfs?( useful for debugging)
>
>regards
>Ramesh Gupta G
>
>
>--
>To unsubscribe from this list: send the line "unsubscribe linux-omap" in
>the body of a message to majordomo@xxxxxxxxxxxxxxx
>More majordomo info at http://vger.kernel.org/majordomo-info.html
--
To unsubscribe from this list: send the line "unsubscribe linux-omap" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
