* Linus Walleij <linus.walleij@xxxxxxxxxx> [131011 09:05]: > On Fri, Oct 11, 2013 at 5:43 PM, Tony Lindgren <tony@xxxxxxxxxxx> wrote: > > * 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. > > OK we can surely discuss this with broonie, it makes sense to > have regmap be able to do its deed transparently. Yes I think so too. Sounds like we need callbacks for the runtime PM checks to the "register provider" driver. Hwo knows, maybe those features are there already :) Tony -- To unsubscribe from this list: send the line "unsubscribe linux-omap" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
