* Linus Walleij <linus.walleij@xxxxxxxxxx> [131011 03:40]: > On Fri, Oct 11, 2013 at 10:56 AM, Roger Quadros <rogerq@xxxxxx> wrote: > > > The register handling is fine. But how do we deal with resource handling? > > e.g. the block that has the deep-core registers might need to be clocked or powered > > before the registers can be accessed. > > Yeah I saw this in the code there. > > In this case it seems syscon-type regmap access can be used to > read/write the registers, so maybe the pin controller also need to > get a handle on some clock etc? Uhh, let's not go there.. The resource availability needs to be handled transparently in regmap code and the reg provider hardware module driver using runtime PM. > The general idea is however that large monolitic "drivers" for a > certain IO-range such as arch/arm/mach-omap2/prm3xxx.c > doesn't scale - we saw this with the Ux500 PRCMU driver in > mfd/* to the point that our patches to extend it were NACK:ed > until we refactor it. This stuff in mach-omap2 is in the same bad > design pattern, and need to get out of it. > > The approach chosen for the Ux500 PRCMU was to distribute > out the driver into the places where it's actually used, like the > clock driver etc. The accessor functions to do some stuff over > in the PRCMU was just adding a layer of cruft. Yes I'm all in favor of having a minimal PRM core driver that manages resources and provides register access services in a controlled way to it's client drivers. As long as the emphasis is "in a controlled way". Regards, Tony -- 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
