Cliff Brake <cliff.br...@gmail.com> writes: > On Tue, Sep 1, 2009 at 6:34 AM, Mike Rapoport<m...@compulab.co.il> wrote: > >> 3) If I'm not much mistaken, board specific pin mux configuration has to deal >> with arch/arm/plat-omap/include/mach/mux.h and arch/arm/mach-omap2/mux.c. For >> instance, if my board uses ULPI pins that have not been defined already, I >> need >> to patch those file with my pin mux definitions. Am I right here, or have I >> missed something? > > It seems to me there should be a global mux configuration per CPU, but > should be configurable per board, group of boards, etc. What I would > like is a set of routines can be used to configure the mux that is > then called by the board files (similar to PXA). Especially once we > get into supporting multiple base boards with things like beagle and > overo, it would be nice to have have all this logic both places > (kernel/uboot), but maybe its needed there anyway.
There is lots of agreement around the various shortcomings of the current mux framework for OMAP. All that's missing is someone to step up and do the work. :/ I started a new wiki topic at elinux.org for linux-omap wishlist items: http://elinux.org/OMAP_wishlist here I created a pin-mux section where we could start to keep track of the important features needed in a new mux framework. Adding pointers summaries to some other platforms might be useful here as well. This will help us get a start so when someone is ready to step up and do the work, we'll have a starting point. Kevin -- To unsubscribe from this list: send the line "unsubscribe linux-omap" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
