> -----Original Message----- > From: Arnd Bergmann [mailto:arnd@xxxxxxxx] > Sent: Thursday, October 29, 2015 4:49 PM > To: linux-arm-kernel@xxxxxxxxxxxxxxxxxxx > Cc: Rivera Jose-B46482; robh+dt@xxxxxxxxxx; mark.rutland@xxxxxxx; devicetree@xxxxxxxxxxxxxxx; linux- > kernel@xxxxxxxxxxxxxxx; Sharma Bhupesh-B45370; Li Yang-Leo-R58472; Yoder Stuart-B08248 > Subject: Re: [PATCH v2] arm64: dts: Added syscon-reboot node for FSL's LS2085A SoC > > On Wednesday 28 October 2015 16:09:44 J. German Rivera wrote: > > + rst_ccsr: rstccsr@1E60000 { > > + compatible = "syscon"; > > + reg = <0x0 0x1E60000 0x0 0x10000>; > > + }; > > + > > > > What does 'rstccsr' stand for? Is this by chance a reset controller? It is a region of some miscellaneous registers, some related to reset. > If so, we probably want a real driver for it rather than just a > syscon. There is not other stuff in this region that to be exposed, and so we really don't need a real driver. My suggestion is to perhaps make that more explicit in the proposed device tree node, by making the reg size "4" and naming it as per the register name rstcr: rstcr@1E60000 { compatible = "syscon"; reg = <0x0 0x1E60000 0x0 0x4>; }; The intent is really just to expose a single reset register and use syscon-reboot until PSCI is available. Thanks, Stuart -- 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
