On Thu, 21 May 2009, Mike Chan wrote: > On Thu, May 21, 2009 at 3:37 PM, Paul Walmsley <paul@xxxxxxxxx> wrote: > > > > would suggest keeping pin remuxing in board-*.c or maybe chip-*.c files; > > ideally this file would only pertain to the SDRC IP block itself. > > Is there a reason why any board-*.c would not want this? It seems a > little silly for everyone to be doing the same repetitive pin muxing > if they want to suspend properly for a reasonable amount of time. I suspect you are asking a slightly different question, which is, "why shouldn't this pin muxing go in sdrc.c". The reason is because the pin muxing API we have is chip- and package-specific. This sdrc.c file shouldn't contain any chip- or package-specific information. Whether it goes into board-*.c or into a chip- or package-specific file is another question. Richard's earlier E-mail covered the answer to your literal question. It seems wisest for boards that don't use SDRC_CKE1 to keep it in safe mode. - Paul -- 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
