On Thu, Jul 18, 2013 at 8:25 PM, Felipe Balbi <balbi@xxxxxx> wrote: >> The Peripheral irq/dma requests are connected to one crossbar's input >> and the output of the crossbar is connected to controller's input >> line. On POR, there are some mappings which are done by default. >> Those peripherals which do not have a mapping on POR, should be configured >> to route its requests using the crossbar. (...) > why isn't this done under pinctrl ? If all it does is mux DMA and IRQ > request lines, it should be written as a pinctrl driver no ? Actually I was thinking about this at one time when designing pinctrl, "what if we face the problem of arbitrary signal multiplexing?" However pin control is named for what it does and also controls things like the electrical properties of pins, biasing and so on which is ill applicable here. I would rather say that the pin multiplexing portions of pin control could be rewritten to use a more generic component dealing with arbitrary line multiplexing, i.e. something under /lib and maybe then move over some generic concepts such as the function to group mapping. The same concept as found here is found in the muxes used by drivers/dma/amba-pl08x.c back-ends on ARM reference hardware which is also multiplexing DMA signals. In that case we have done platform-specific hooks and implemented this in the per-machine platform code. Yours, Linus Walleij -- 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
