OPP: Introduce OPP bindings V2 and supporting code
Get series with b4
b4 am [email protected]Versions newest first
- v1 Latest0 of 7 patches 0 repliesNew
Patches in v1 No applies recorded yet
None of the 7 patches the cover letter announces are in this archive.
Reviews trailers per patch
No Reviewed-by, Acked-by or Tested-by trailers for v1 yet.
Cover letter [PATCH 0/7] OPP: Introduce OPP bindings V2 and supporting code
Quoted 9 lines · Viresh Kumar
Quoted 3 lines · Stephen Boyd
voltages. I suppose something like opp-microvolt-names would work though but I don't know how software would correlate that to the regulator it uses because that information is elsewhere in the
I hope the CPU node will have an array of supplies to support multiple regulators, right? If yes, then we can just keep the array of <t/min/max> in the same order. And software should be able to correlate then?
It's probably not *too* bad for small numbers of supplies but bindings that require that indexes into two different arrays match up (particularly with different step sizes as here) do have legibility issues - it's easy to miscount when reading things.
Quoted 5 lines
Quoted 2 lines
device's node. Why not put the information about which clock and regulator is used into the opp node?
Don't know. I have been asked specifically to keem them out of the OPPs, as they belong to the CPU or device instead.
The DT should describe the hardware and how it's connected. No power
supplies or clocks are connected to an OPP, an OPP is a property of
something else.
-------------- 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/20150322/dac50316/attachment.sig>