On 02/09/16 13:34, Rob Herring wrote: > On Fri, Aug 26, 2016 at 04:37:10PM +0100, Paul Burton wrote: >> Document a binding for the MIPS Cluster Power Controller (CPC) which >> simply allows the device tree to specify where the CPC registers should >> be mapped. >> >> Signed-off-by: Paul Burton <paul.burton@xxxxxxxxxx> >> --- >> >> Documentation/devicetree/bindings/misc/mti,mips-cpc.txt | 8 ++++++++ > > This is for power domains, right? Move to bindings/power. Hi Rob, Well, sort of. The CPC controls the power domains for CPU cores & the MIPS Coherency Manager within a CPU cluster. That is, it's the block of hardware that we send commands to power up or down CPUs to. It's not something that makes use of the kernel's power domain infrastructure, it's essentially only involved in SMP startup, hotplug or cpuidle low power states. This binding is purely about assigning some address space for the CPC register interface, which can be mapped anywhere at runtime. Besides knowing where to place the registers there's currently nothing else we'd need to describe in DT. If you still think bindings/power/ is the best place for it given that, I'll move it. > >> 1 file changed, 8 insertions(+) >> create mode 100644 Documentation/devicetree/bindings/misc/mti,mips-cpc.txt >> >> diff --git a/Documentation/devicetree/bindings/misc/mti,mips-cpc.txt b/Documentation/devicetree/bindings/misc/mti,mips-cpc.txt >> new file mode 100644 >> index 0000000..92eb08f >> --- /dev/null >> +++ b/Documentation/devicetree/bindings/misc/mti,mips-cpc.txt >> @@ -0,0 +1,8 @@ >> +Binding for MIPS Cluster Power Controller (CPC). >> + >> +This binding allows a system to specify where the CPC registers should be >> +mapped using device tree. >> + >> +Required properties: >> +compatible : Should be "mti,mips-cpc". >> +regs: Should describe the address & size of the CPC register region. > > Also needs #power-domain-cells property. As above, this doesn't make use of power domain infrastructure or anything like it so I don't think that's correct. Thanks, Paul > >> -- >> 2.9.3 >>