linux-kernel - Re: [PATCH] PM / OPP: fix CPU device to be removed from OPP table in wrong order

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite for Android: free password hash cracker in your pocket

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Date:   Thu, 24 Nov 2016 14:04:03 +0530
From:   Viresh Kumar <viresh.kumar@...aro.org>
To:     Joonyoung Shim <jy0922.shim@...sung.com>
Cc:     linux-pm@...r.kernel.org, linux-kernel@...r.kernel.org,
        vireshk@...nel.org, nm@...com, sboyd@...eaurora.org,
        rjw@...ysocki.net, len.brown@...el.com, pavel@....cz,
        gregkh@...uxfoundation.org
Subject: Re: [PATCH] PM / OPP: fix CPU device to be removed from OPP table in
 wrong order

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 can't the CPU which
added the OPP should be removed last.

Can you give a real example where you see a problem ?

> If OPP table is
> shared by several CPUs, the CPU device that creates OPP table can be
> removed earlier than other CPU devices.

I don't think that's a problem, though I can be wrong for sure.

-- 
viresh