On Fri, Aug 7, 2009 at 2:55 AM, Tony Lindgren<tony@xxxxxxxxxxx> wrote: > Well we need to mux all the pins that can potentially conflict only in the > board-*.c files. > > For naming, I think we should use the default mode0 name in the mux register as the > key, and then link package specific pin names to that key. The pin names are > very handy to see for debugging at least. I like that approach - it matches the method in the documentation tables (i.e. unique pin name is the mode 0 function). > Another thing to consider is if we want to support dynamic muxing. That means > we need to keep the mux tables in the memory. Dynamic muxing would be very nice. It is required if we ever want to do card detect with microSD cards. > Or do init time muxing in board-*.c files, then re-register the pins needed for > dynamic muxing in board-*.c files. That way most of the mux data can be __initdata, > and only the pins that have been registered for dynamic muxing need to be kept > in the memory. This sounds good too. Reagrds, Steve -- 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
