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]
Date:	Thu, 10 Dec 2015 22:45:33 +0100
From:	"Rafael J. Wysocki" <rjw@...ysocki.net>
To:	Lee Jones <lee.jones@...aro.org>
Cc:	Viresh Kumar <viresh.kumar@...aro.org>, Nishanth Menon <nm@...com>,
	Len Brown <len.brown@...el.com>,
	Linaro Kernel Mailman List <linaro-kernel@...ts.linaro.org>,
	"linux-pm@...r.kernel.org" <linux-pm@...r.kernel.org>,
	Stephen Boyd <sboyd@...eaurora.org>,
	open list <linux-kernel@...r.kernel.org>,
	Pavel Machek <pavel@....cz>,
	Greg Kroah-Hartman <gregkh@...uxfoundation.org>,
	Viresh Kumar <vireshk@...nel.org>
Subject: Re: [PATCH V3 2/2] PM / OPP: Parse 'opp-<prop>-<name>' bindings

On Thursday, December 10, 2015 09:54:45 AM Lee Jones wrote:
> On 9 December 2015 at 02:31, Viresh Kumar <viresh.kumar@...aro.org> wrote:
> > OPP bindings (for few properties) allow a platform to choose a
> > value/range among a set of available options. The options are present as
> > opp-<prop>-<name>, where the platform needs to supply the <name> string.
> >
> > The OPP properties which allow such an option are: opp-microvolt and
> > opp-microamp.
> >
> > Add support to the OPP-core to parse these bindings, by introducing
> > dev_pm_opp_{set|put}_prop_name() APIs.
> >
> > Signed-off-by: Viresh Kumar <viresh.kumar@...aro.org>
> > ---
> >  drivers/base/power/opp/core.c | 165 ++++++++++++++++++++++++++++++++++++++----
> >  drivers/base/power/opp/opp.h  |   2 +
> >  include/linux/pm_opp.h        |   9 +++
> >  3 files changed, 161 insertions(+), 15 deletions(-)
> 
> Tested-by: Lee Jones <lee.jones@...aro.org>

OK, so tentatively I can take these two.

What exectly does depend on them and how that thing is intended to be handled?

Thanks,
Rafael

--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ