Thread (48 messages) 48 messages, 5 authors, 2015-09-16

Re: [PATCH v4 2/2] dt: power: st: Provide bindings for ST's OPPs

From: Viresh Kumar <hidden>
Date: 2015-08-11 10:09:48
Also in: linux-arm-kernel, linux-pm, lkml

On 11-08-15, 10:30, Lee Jones wrote:
On Tue, 11 Aug 2015, Viresh Kumar wrote:
quoted
On 10-08-15, 14:22, Lee Jones wrote:
quoted
quoted
 Optional properties:
+- opp-cuts: One or more strings, describing the versions of hardware the OPPs
+  can support.
This isn't very generic.

I'm guessing some vendors my have quite a few ways to differentiate
between board versions/revisions/cuts etc.

How about another array where a vendor can choose to identify a piece
of hardware however they see fit.

Example 1 (simple version):

/* Version 1 */
opp-version = <1>;

Example 2 (using the kernel's versioning):

/* 2.6.32-rc1 */
opp-version = <2 6 32 1>;

Example 3 (using ST's versioning):

/* Major 2, Minor 0, Cut 2, All substrates */
opp-version = <2 0 2 0xff>;
But how will we parse this with generic code ?
Why would you want to?
So that individual platforms don't need to reinvent the wheel ?

-- 
viresh
--
To unsubscribe from this list: send the line "unsubscribe devicetree" in
the body of a message to majordomo-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Keyboard shortcuts
hback out one level
jnext message in thread
kprevious message in thread
ldrill in
Escclose help / fold thread tree
?toggle this help