[RFC V2] OPP: Redefine bindings to overcome shortcomings
From: broonie@kernel.org (Mark Brown)
Date: 2015-01-29 11:07:44
Also in:
linux-devicetree, linux-pm
Possibly related (same subject, not in this thread)
- 2015-01-30 · Re: [RFC V2] OPP: Redefine bindings to overcome shortcomings · Viresh Kumar <viresh.kumar@linaro.org>
- 2015-01-30 · Re: [RFC V2] OPP: Redefine bindings to overcome shortcomings · Viresh Kumar <hidden>
- 2015-01-29 · Re: [RFC V2] OPP: Redefine bindings to overcome shortcomings · Rob Herring <hidden>
- 2015-01-29 · Re: [RFC V2] OPP: Redefine bindings to overcome shortcomings · Viresh Kumar <hidden>
- 2015-01-28 · Re: [RFC V2] OPP: Redefine bindings to overcome shortcomings · Mark Brown <broonie@kernel.org>
On Thu, Jan 29, 2015 at 07:09:23AM +0530, Viresh Kumar wrote:
On 29 January 2015 at 01:36, Mark Brown [off-list ref] wrote:
quoted
quoted
+ Required properties: + - compatible: allow OPPs to express their compatibility. + - opp-list: phandle to opp-list defined above.
quoted
I don't understand what that compatible property is intended to mean and I expect other readers might be similarly confused - is it a standard compatbile property meaning this noe corresponds to some sort of device?
The goal is to choose the driver which we want to probe for a platform. There can be multiple DT enabled cpufreq drivers present in a build and the platform needs some way to choose one of them.
So you need to document this as a platform device then if that's what you're doing here; there's more than just specifying a compatible string involved. -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 473 bytes Desc: Digital signature URL: <http://lists.infradead.org/pipermail/linux-arm-kernel/attachments/20150129/9de5263e/attachment.sig>