On 06/22, Chunyan Zhang wrote: > Hi Stephen, > > On 20 June 2017 at 09:24, Stephen Boyd <sboyd@xxxxxxxxxxxxxx> wrote: > > On 06/18, Chunyan Zhang wrote: > > > > >> + compatible = "sprd,sc9860-ccu"; > >> + #clock-cells = <1>; > >> + reg = <0 0x20000000 0 0x400>, > >> + <0 0x20210000 0 0x3000>, > >> + <0 0x402b0000 0 0x4000>, > >> + <0 0x402d0000 0 0x400>, > >> + <0 0x402e0000 0 0x4000>, > >> + <0 0x40400000 0 0x400>, > >> + <0 0x40880000 0 0x400>, > >> + <0 0x415e0000 0 0x400>, > >> + <0 0x60200000 0 0x400>, > >> + <0 0x61000000 0 0x400>, > >> + <0 0x61100000 0 0x3000>, > >> + <0 0x62000000 0 0x4000>, > >> + <0 0x62100000 0 0x4000>, > >> + <0 0x63000000 0 0x400>, > >> + <0 0x63100000 0 0x3000>, > >> + <0 0x70b00000 0 0x3000>; > > > > There are a lot of reg properties here. Perhaps there needs to be > > different nodes for the different clock controllers in this SoC? > > > > On Spreadtrum's platform, clocks are basically located in a few > address areas due to some hardware design issue, that says there're > more than one kinds of clocks in one address range, and one kind of > clocks have more than one physical address bases, except ccu_pll and > ccu_div in this patchset. > > We're planning to map the whole device area at one time before > initializing each of them, once that has been done and upstreamed, I > will remove these lists of addressed. Ok. Does this mean we need to wait for those patches to be sent out for review? Is it more like certain clks are embedded inside other devices like display controllers, i2c controllers, etc? Is there any more information I can get on this SoC? -- Qualcomm Innovation Center, Inc. is a member of Code Aurora Forum, a Linux Foundation Collaborative Project -- To unsubscribe from this list: send the line "unsubscribe devicetree" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
