On Tue, Jan 15, 2013 at 8:21 PM, Rajagopal Venkat
wrote:
> On 14 January 2013 20:06, MyungJoo Ham wrote:
>> On Tue, Jan 8, 2013 at 2:50 PM, Rajagopal Venkat
>> wrote:
>>> Set devfreq device min and max frequency limits when device
>>> is added to devfreq, pro
On Tue, Jan 15, 2013 at 8:46 PM, Rajagopal Venkat
wrote:
> On 14 January 2013 20:18, MyungJoo Ham wrote:
>> On Tue, Jan 8, 2013 at 2:50 PM, Rajagopal Venkat
>> wrote:
>>> devfreq stats is not taking device suspend and resume into
>>> account. Fix it.
>&g
err = devfreq_update_status(devfreq, devfreq->previous_freq);
> - if (err)
> + if (!devfreq->stop_polling &&
> + devfreq_update_status(devfreq,
> devfreq->previous_freq))
> return 0;
>
> len = sprintf(buf, "
> --
> 1.7.10.4
>
> --
> To unsubscribe from this list: send the line "unsubscribe linux-pm" in
> the body of a message to majord...@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
--
MyungJoo Ham, Ph.D.
Mobile Software Platform Lab, DMC Business, Samsung Electronics
___
linaro-dev mailing list
linaro-dev@lists.linaro.org
http://lists.linaro.org/mailman/listinfo/linaro-dev
GFP_KERNEL);
> devfreq->last_stat_updated = jiffies;
> + devfreq_set_freq_limits(devfreq);
>
> dev_set_name(&devfreq->dev, dev_name(dev));
> err = device_register(&devfreq->dev);
> --
> 1.7.10.4
>
> --
>
> On Monday 08 of October 2012 10:48:24 MyungJoo Ham wrote:
> > > On 8 October 2012 03:31, Rafael J. Wysocki wrote:
> > > > On Thursday 04 of October 2012 14:58:33 Rajagopal Venkat wrote:
> > > >> Add devfreq suspend/resume apis for devfreq users. This pat
2012. 10. 10. 오후 4:19에 "Rajagopal Venkat" 님이
작성:
>
> On 8 October 2012 13:44, MyungJoo Ham wrote:
> >> Prepare devfreq core framework to support devices which
> >> can idle. When device idleness is detected perhaps through
> >> runtime-pm,
>> for devices which can idle.
> >>
> >> Signed-off-by: Rajagopal Venkat
> >> Acked-by: MyungJoo Ham
> >
> > Well, I wonder if this may be tied in to the runtime PM framework, so that,
> > for example, pm_runtime_suspend() will automatically suspend
vents to perform
> specific actions. These events include start/stop devfreq.
> This sets ground for adding suspend/resume events.
>
> The devfreq apis are not modified and are kept intact.
>
> Signed-off-by: Rajagopal Venkat
Thank you!
Reviewed and Tested (at Exynos421
> On 4 October 2012 18:06, MyungJoo Ham wrote:
> >> This patchset updates devfreq core to add support for devices
> >> which can idle. When device idleness is detected perhaps
> >> through runtime-pm, need some mechanism to suspend devfreq
> >> load mo
> This patchset updates devfreq core to add support for devices
> which can idle. When device idleness is detected perhaps
> through runtime-pm, need some mechanism to suspend devfreq
> load monitoring and resume when device is back online.
>
> patch 1 introduce core design changes - per device wo
Title: Samsung Enterprise Portal mySingle
> Add devfreq suspend/resume apis for devfreq users. This patch> supports suspend and resume of devfreq load monitoring, required> for devices which can idle.> > Signed-off-by: Rajagopal Venkat <rajagopal.ven...@linaro.org>
A
> On 27 September 2012 13:50, MyungJoo Ham wrote:
> >> Prepare devfreq core framework to support devices which
> >> can idle. When device idleness is detected perhaps through
> >> runtime-pm, need some mechanism to suspend devfreq load
> >> monitorin
onding devfreq object.
>
> -What:/sys/class/devfreq/.../central_polling
> -Date:September 2011
> -Contact: MyungJoo Ham
> -Description:
> - The /sys/class/devfreq/.../central_polling shows whether
> - the devfre
> Sender : Rajagopal Venkat
> Date : 2012-09-18 14:20 (GMT+09:00)
> Title : Re: Re: [PATCH 1/3] devfreq: core updates to support devices which
> can idle
> On 17 September 2012 17:46, MyungJoo Ham wrote:
> >> On 10 September 2012 14:43, 함명주 wrote:
> >> >> Pr
> On 10 September 2012 14:43, 함명주 wrote:
> >> Prepare devfreq core framework to support devices which
> >> can idle. When device idleness is detected perhaps through
> >> runtime-pm, need some mechanism to suspend devfreq load
> >> monitoring and resume back when device is online. Present
> >> cod
sfs node to expose
> governor predicted next target frequency.
>
> Signed-off-by: Rajagopal Venkat
Signed-off-by: MyungJoo Ham
> ---
> Documentation/ABI/testing/sysfs-class-devfreq | 11 ++-
> drivers/devfreq/devfreq.c | 14 +
> Add devfreq suspend/resume apis for devfreq users. This patch
> supports suspend and resume of devfreq load monitoring, required
> for devices which can idle.
>
> Signed-off-by: Rajagopal Venkat
Rather than letting device driver be responsible to call
devfreq_suspend_device() or devfreq_dev_s
> On 23 August 2012 09:57, MyungJoo Ham wrote:
> >> > On 20 August 2012 12:50, 함명주 wrote:
> >> >
> >> > > Prepare devfreq core framework to support devices which
> >> > > can idle. When device idleness is detected perhaps through
> &g
> On 20 August 2012 15:15, 함명주 wrote:
> >> Devfreq returns governor predicted frequency as current
> >> frequency via sysfs interface. But device may not support
> >> all frequencies that governor predicts. As per the design
> >> its driver responsibility to maintain current frequency
> >> at whic
e can,
it's better to remove device specific information from governors
and cores as long as it does not significantly increase the
complexity of drivers.
UINT_MAX means "I recommend to run as fast as possible." Then, the
driver only needs to provide the fastest frequency. The core and
go
> This patch adds suspend and resume apis needed
> for devices which can idle. Suspend/resume apis
> are called from driver to suspend/resume devfreq
> load monitoring of that device.
>
> Signed-off-by: Rajagopal Venkat
1. Some devfreq devices may need their own code to do suspend/resume; e.g.,
On Tue, Nov 29, 2011 at 2:33 PM, Haojian Zhuang
wrote:
> On Tue, Nov 29, 2011 at 1:00 PM, MyungJoo Ham
> wrote:
>> On Tue, Nov 29, 2011 at 1:41 PM, Haojian Zhuang
>> wrote:
>>> On Thu, Nov 17, 2011 at 6:13 PM, Donggeun Kim wrote:
>>>> Because battery hea
= cm_setup_timer();
>> + }
>> +
>> + return 0;
>> +}
>> +
>> +static void cm_suspend_complete(struct device *dev)
>> +{
>> + struct platform_device *pdev = container_of(dev, struct
>> platform_device,
>> + dev);
>> + struct charger_manager *cm = platform_get_drvdata(pdev);
>> +
>> + if (cm_suspended) {
>> + if (rtc_dev) {
>> + struct rtc_wkalrm tmp;
>> +
>> + rtc_read_alarm(rtc_dev, &tmp);
>> + rtc_wkalarm_save.pending = tmp.pending;
>> + rtc_set_alarm(rtc_dev, &rtc_wkalarm_save);
>> + }
>> + cm_suspended = false;
>> + cm_rtc_set = false;
>> + }
>> +
>> + uevent_notify(cm, NULL);
>> +}
>> +
>> +static const struct dev_pm_ops charger_manager_pm = {
>> + .prepare = cm_suspend_prepare,
>> + .complete = cm_suspend_complete,
>> +};
>> +
[]
--
MyungJoo Ham, Ph.D.
Mobile Software Platform Lab, DMC Business, Samsung Electronics
___
linaro-dev mailing list
linaro-dev@lists.linaro.org
http://lists.linaro.org/mailman/listinfo/linaro-dev
On Thu, Nov 17, 2011 at 8:22 PM, Amit Kachhap wrote:
> On 11 November 2011 13:03, MyungJoo Ham wrote:
>> On Sat, Nov 5, 2011 at 2:03 AM, wrote:
>>> From: Amit Daniel Kachhap
>>>
>>> This patch adds support for AFTR(ARM OFF TOP RUNNING) mode in
>>>
location, which is the
method we have been using.
Besides, the Exynos4210 chipmaker (S.LSI) has told that INFORM6 and 7
registers are used by in-chip code (iROM or iRAM).
Cheers!
MyungJoo
--
MyungJoo Ham, Ph.D.
Mobile Software Platform Lab, DMC Business, Samsung Electronics
26 matches
Mail list logo
