1*c66ec88fSEmmanuel VadotBroadcom BCM6345-style Level 1 interrupt controller 2*c66ec88fSEmmanuel Vadot 3*c66ec88fSEmmanuel VadotThis block is a first level interrupt controller that is typically connected 4*c66ec88fSEmmanuel Vadotdirectly to one of the HW INT lines on each CPU. 5*c66ec88fSEmmanuel Vadot 6*c66ec88fSEmmanuel VadotKey elements of the hardware design include: 7*c66ec88fSEmmanuel Vadot 8*c66ec88fSEmmanuel Vadot- 32, 64 or 128 incoming level IRQ lines 9*c66ec88fSEmmanuel Vadot 10*c66ec88fSEmmanuel Vadot- Most onchip peripherals are wired directly to an L1 input 11*c66ec88fSEmmanuel Vadot 12*c66ec88fSEmmanuel Vadot- A separate instance of the register set for each CPU, allowing individual 13*c66ec88fSEmmanuel Vadot peripheral IRQs to be routed to any CPU 14*c66ec88fSEmmanuel Vadot 15*c66ec88fSEmmanuel Vadot- Contains one or more enable/status word pairs per CPU 16*c66ec88fSEmmanuel Vadot 17*c66ec88fSEmmanuel Vadot- No atomic set/clear operations 18*c66ec88fSEmmanuel Vadot 19*c66ec88fSEmmanuel Vadot- No polarity/level/edge settings 20*c66ec88fSEmmanuel Vadot 21*c66ec88fSEmmanuel Vadot- No FIFO or priority encoder logic; software is expected to read all 22*c66ec88fSEmmanuel Vadot 2-4 status words to determine which IRQs are pending 23*c66ec88fSEmmanuel Vadot 24*c66ec88fSEmmanuel VadotRequired properties: 25*c66ec88fSEmmanuel Vadot 26*c66ec88fSEmmanuel Vadot- compatible: should be "brcm,bcm<soc>-l1-intc", "brcm,bcm6345-l1-intc" 27*c66ec88fSEmmanuel Vadot- reg: specifies the base physical address and size of the registers; 28*c66ec88fSEmmanuel Vadot the number of supported IRQs is inferred from the size argument 29*c66ec88fSEmmanuel Vadot- interrupt-controller: identifies the node as an interrupt controller 30*c66ec88fSEmmanuel Vadot- #interrupt-cells: specifies the number of cells needed to encode an interrupt 31*c66ec88fSEmmanuel Vadot source, should be 1. 32*c66ec88fSEmmanuel Vadot- interrupts: specifies the interrupt line(s) in the interrupt-parent controller 33*c66ec88fSEmmanuel Vadot node; valid values depend on the type of parent interrupt controller 34*c66ec88fSEmmanuel Vadot 35*c66ec88fSEmmanuel VadotIf multiple reg ranges and interrupt-parent entries are present on an SMP 36*c66ec88fSEmmanuel Vadotsystem, the driver will allow IRQ SMP affinity to be set up through the 37*c66ec88fSEmmanuel Vadot/proc/irq/ interface. In the simplest possible configuration, only one 38*c66ec88fSEmmanuel Vadotreg range and one interrupt-parent is needed. 39*c66ec88fSEmmanuel Vadot 40*c66ec88fSEmmanuel VadotThe driver operates in native CPU endian by default, there is no support for 41*c66ec88fSEmmanuel Vadotspecifying an alternative endianness. 42*c66ec88fSEmmanuel Vadot 43*c66ec88fSEmmanuel VadotExample: 44*c66ec88fSEmmanuel Vadot 45*c66ec88fSEmmanuel Vadotperiph_intc: interrupt-controller@10000000 { 46*c66ec88fSEmmanuel Vadot compatible = "brcm,bcm63168-l1-intc", "brcm,bcm6345-l1-intc"; 47*c66ec88fSEmmanuel Vadot reg = <0x10000020 0x20>, 48*c66ec88fSEmmanuel Vadot <0x10000040 0x20>; 49*c66ec88fSEmmanuel Vadot 50*c66ec88fSEmmanuel Vadot interrupt-controller; 51*c66ec88fSEmmanuel Vadot #interrupt-cells = <1>; 52*c66ec88fSEmmanuel Vadot 53*c66ec88fSEmmanuel Vadot interrupt-parent = <&cpu_intc>; 54*c66ec88fSEmmanuel Vadot interrupts = <2>, <3>; 55*c66ec88fSEmmanuel Vadot}; 56