Hi Viresh,
On 11/25/2016 03:57 PM, Viresh Kumar wrote:
> On 25-11-16, 10:54, Joonyoung Shim wrote:
>> I found this problem during system suspend/resume of Odroid-XU3 board.
>>
>> # rtcwake -m mem -s 3
>> wakeup from "mem" at Wed Apr 4 05:54:44 2001
>> [ 15.965996] PM: Syncing filesystems ... do
On 25-11-16, 10:54, Joonyoung Shim wrote:
> I found this problem during system suspend/resume of Odroid-XU3 board.
>
> # rtcwake -m mem -s 3
> wakeup from "mem" at Wed Apr 4 05:54:44 2001
> [ 15.965996] PM: Syncing filesystems ... done.
> [ 15.976333] Freezing user space processes ... (elapse
Hi Viresh.
On 11/24/2016 05:34 PM, Viresh Kumar wrote:
> Ho Joonyoung,
>
> On 24-11-16, 16:49, Joonyoung Shim wrote:
>> The device that creates OPP table first should be removed from dev_list
>> of OPP table in last because it can be used by other resources
>> (supported_hw, prop_name, regulator)
Ho Joonyoung,
On 24-11-16, 16:49, Joonyoung Shim wrote:
> The device that creates OPP table first should be removed from dev_list
> of OPP table in last because it can be used by other resources
> (supported_hw, prop_name, regulator), but not now.
I am not sure what you are trying to do here? Why
The device that creates OPP table first should be removed from dev_list
of OPP table in last because it can be used by other resources
(supported_hw, prop_name, regulator), but not now. If OPP table is
shared by several CPUs, the CPU device that creates OPP table can be
removed earlier than other C
5 matches
Mail list logo
