Re: [PATCH 0/7] OPP: Introduce OPP bindings V2 and supporting code

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 




On Tue, Feb 17, 2015 at 01:16:25PM +0530, Viresh Kumar wrote:
> On 12 February 2015 at 16:20, Stephen Boyd <sboyd@xxxxxxxxxxxxxx> wrote:

> > 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.

> > 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.

Attachment: signature.asc
Description: Digital signature


[Index of Archives]     [Device Tree Compilter]     [Device Tree Spec]     [Linux Driver Backports]     [Video for Linux]     [Linux USB Devel]     [Linux PCI Devel]     [Linux Audio Users]     [Linux Kernel]     [Linux SCSI]     [XFree86]     [Yosemite Backpacking]
  Powered by Linux