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
| ||
|
Message-ID: <20220223091012.w3flzpye6z55jnwd@vireshk-i7> Date: Wed, 23 Feb 2022 14:40:12 +0530 From: Viresh Kumar <viresh.kumar@...aro.org> To: Lukasz Luba <lukasz.luba@....com> Cc: linux-kernel@...r.kernel.org, dietmar.eggemann@....com, rafael@...nel.org, daniel.lezcano@...aro.org, nm@...com, sboyd@...nel.org, mka@...omium.org, dianders@...omium.org, robh+dt@...nel.org, devicetree@...r.kernel.org, linux-pm@...r.kernel.org Subject: Re: [[PATCH v2 2/2] OPP: Add 'opp-microwatt' parsing for advanced EM registration On 23-02-22, 08:59, Lukasz Luba wrote: > OK, so you want to have this available for the whole system. I can do > that. I would go for one value of power One value per supply, right ? > and try to fit into the > opp_parse_supplies() code. Correct. > As far as I can see in the > dev_pm_opp_get_voltage() the simple solution: supplier[0] and u_volt > is used. I would go for similar solution for u_watt. > There is even a single u_amp and no _max, _min variants, so should be > good.. Yes, I don't think we need min/max/target kind of naming here. Just a single value per supply is enough. -- viresh
Powered by blists - more mailing lists