Hi, On Thu, Jul 18, 2013 at 10:13:48PM +0530, Sricharan R wrote: > Some socs have a large number of interrupts/dma requests to service > the needs of its many peripherals and subsystems. All of the > requests lines from the subsystems are not needed at the same > time, so they have to be muxed to the controllers appropriately. > In such places a interrupt/dma controllers are preceded by an > IRQ/DMA CROSSBAR that provides flexibility in muxing the device > requests to the controller inputs. > > 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. > > The drivers identifies every controller's crossbar as individual devices. > The mappings can be specified from the DT crossbar nodes and those gets mapped > during the crossbar device's probe. The mappings can also be specified by adding > the crossbar lines to the peripheral device nodes and map it with > crossbar_map/unmap apis. > > Signed-off-by: Sricharan R <r.sricharan@xxxxxx> 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 ? -- balbi
Attachment:
signature.asc
Description: Digital signature
