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: Windows password security audit tool. GUI, reports in PDF.
[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20180103072047.GD15166@vireshk-i7>
Date:   Wed, 3 Jan 2018 12:50:47 +0530
From:   Viresh Kumar <viresh.kumar@...aro.org>
To:     ulf.hansson@...aro.org, Kevin Hilman <khilman@...nel.org>,
        robh+dt@...nel.org, Nishanth Menon <nm@...com>,
        "Rafael J. Wysocki" <rjw@...ysocki.net>,
        Stephen Boyd <sboyd@...eaurora.org>,
        Viresh Kumar <vireshk@...nel.org>
Cc:     linux-pm@...r.kernel.org,
        Vincent Guittot <vincent.guittot@...aro.org>,
        rnayak@...eaurora.org, sudeep.holla@....com,
        devicetree@...r.kernel.org, linux-kernel@...r.kernel.org
Subject: Re: [PATCH V8 0/3] OPP: Allow OPP table to be used for power-domains

On 18-12-17, 15:51, Viresh Kumar wrote:
> Hi,
> 
> Now that the performance state of PM domains are supported by the kernel
> (merged in linux-next), I am trying once again to define the bindings
> which we dropped until the code is merged first.
> 
> Summary:
> 
> Power-domains can also have their active states and this patchset
> enhances the OPP binding to define those.
> 
> The power domains can use the OPP bindings mostly as is. Though there
> are some changes required to support special cases:
> 
> - Allow "operating-points-v2" to contain multiple phandles for power
>   domain providers providing multiple domains.
> 
> - A new property "required-opp" is added for the devices to specify the
>   minimum required OPP of the master domain or any other type of device.
> 
> - Allow some of the OPP properties to accept magic values (firmware
>   dependent) as the OS doesn't know the real freq/voltage values.
> 
> V7->V8:
> - V7 1/2 divided into two patches. 1/3 is unchanged from V7.
> - 2/3 renamed the property from "power-domain-opp" to "required-opp", as
>   suggested by Rob.
> - Added Ulf's reviewed-by for 1/3 and 3/3.
> 
> --
> viresh
> 
> Viresh Kumar (3):
>   OPP: Allow OPP table to be used for power-domains
>   OPP: Introduce "required-opp" property

>   OPP: Allow "opp-hz" and "opp-microvolt" to contain magic values

Discussions are still going on for the last commit, though the first
two are already Acked by Rob and Ulf and are quite independent of the
third one.

Any objections to getting the first two merged for 4.16-rc1 ? I will
send them to Rafael on Friday if no one objects.

-- 
viresh

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ