On 21 August 2012 10:25, YongQin Liu wrote:
> Hi, Paul
>
> I have tried with the Shift+Reload and Ctrl+R about 10 times for each,
> but the problem still exists.
> I have reported it as a bug here:
> https://bugs.launchpad.net/linaro-android-infrastructure/+bug/1039319
I found the reason.
We need
I'm seeing the same
On Aug 20, 2012 9:25 PM, "YongQin Liu" wrote:
> Hi, Paul
>
> I have tried with the Shift+Reload and Ctrl+R about 10 times for each,
> but the problem still exists.
> I have reported it as a bug here:
> https://bugs.launchpad.net/linaro-android-infrastructure/+bug/1039319
>
>
>
Hi, Paul
I have tried with the Shift+Reload and Ctrl+R about 10 times for each,
but the problem still exists.
I have reported it as a bug here:
https://bugs.launchpad.net/linaro-android-infrastructure/+bug/1039319
Thanks,
Yongqin Liu
On 17 August 2012 19:11, Paul Sokolovsky wrote:
> Hello,
>
>
Hello there,
Last week we ran a series of open sessions as part of an
experimental Virtual Linaro Connect schedule; the blog post announcing
it is at:
http://www.linaro.org/linaro-blog/2012/08/07/linaro-announces-virtual-connect-q3-12-13-17-august-2012/
We ran all the sessions successfu
Hi Sylwester
On 20 August 2012 12:33, Sylwester Nawrocki wrote:
> Hi Sangwook,
>
[snip]
>
> registers definitions. Attached patch should correct this, sorry about
> this oversight. Let me know if there are still any issues.
> To make sure the I2C write sequences are correct it might be usefu
Hi Sangwook,
On 08/20/2012 12:43 PM, Sangwook Lee wrote:
> On 20 August 2012 09:12, Sangwook Lee wrote:
>> On 19 August 2012 22:29, Sylwester Nawrocki
>> wrote:
>>> On 08/03/2012 04:24 PM, Sangwook Lee wrote:
I was thinking about this, but this seems to be is a bit time-consuming
beca
Hi Sylwester
On 20 August 2012 09:12, Sangwook Lee wrote:
> Hi Sylwester
>
> On 19 August 2012 22:29, Sylwester Nawrocki
> wrote:
>> Hi Sangwook,
>>
>> On 08/03/2012 04:24 PM, Sangwook Lee wrote:
>>> I was thinking about this, but this seems to be is a bit time-consuming
>>> because
>>> I have
> 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.,
> 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 which device is operating. So add a callback in device
> p
Hi Sylwester
On 19 August 2012 22:29, Sylwester Nawrocki
wrote:
> Hi Sangwook,
>
> On 08/03/2012 04:24 PM, Sangwook Lee wrote:
>> I was thinking about this, but this seems to be is a bit time-consuming
>> because
>> I have to do this just due to lack of s5k4ecgx hardware information.
>> let me t
> 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 when device is back online. Present
> code continues monitoring unless device is removed from
> de
11 matches
Mail list logo
