1*c66ec88fSEmmanuel VadotBroadcom BCM7038-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. Every BCM7xxx set-top chip 5*c66ec88fSEmmanuel Vadotsince BCM7038 has contained this hardware. 6*c66ec88fSEmmanuel Vadot 7*c66ec88fSEmmanuel VadotKey elements of the hardware design include: 8*c66ec88fSEmmanuel Vadot 9*c66ec88fSEmmanuel Vadot- 64, 96, 128, or 160 incoming level IRQ lines 10*c66ec88fSEmmanuel Vadot 11*c66ec88fSEmmanuel Vadot- Most onchip peripherals are wired directly to an L1 input 12*c66ec88fSEmmanuel Vadot 13*c66ec88fSEmmanuel Vadot- A separate instance of the register set for each CPU, allowing individual 14*c66ec88fSEmmanuel Vadot peripheral IRQs to be routed to any CPU 15*c66ec88fSEmmanuel Vadot 16*c66ec88fSEmmanuel Vadot- Atomic mask/unmask operations 17*c66ec88fSEmmanuel Vadot 18*c66ec88fSEmmanuel Vadot- No polarity/level/edge settings 19*c66ec88fSEmmanuel Vadot 20*c66ec88fSEmmanuel Vadot- No FIFO or priority encoder logic; software is expected to read all 21*c66ec88fSEmmanuel Vadot 2-5 status words to determine which IRQs are pending 22*c66ec88fSEmmanuel Vadot 23*c66ec88fSEmmanuel VadotRequired properties: 24*c66ec88fSEmmanuel Vadot 25*c66ec88fSEmmanuel Vadot- compatible: should be "brcm,bcm7038-l1-intc" 26*c66ec88fSEmmanuel Vadot- reg: specifies the base physical address and size of the registers; 27*c66ec88fSEmmanuel Vadot the number of supported IRQs is inferred from the size argument 28*c66ec88fSEmmanuel Vadot- interrupt-controller: identifies the node as an interrupt controller 29*c66ec88fSEmmanuel Vadot- #interrupt-cells: specifies the number of cells needed to encode an interrupt 30*c66ec88fSEmmanuel Vadot source, should be 1. 31*c66ec88fSEmmanuel Vadot- interrupts: specifies the interrupt line(s) in the interrupt-parent controller 32*c66ec88fSEmmanuel Vadot node; valid values depend on the type of parent interrupt controller 33*c66ec88fSEmmanuel Vadot 34*c66ec88fSEmmanuel VadotOptional properties: 35*c66ec88fSEmmanuel Vadot 36*c66ec88fSEmmanuel Vadot- brcm,irq-can-wake: If present, this means the L1 controller can be used as a 37*c66ec88fSEmmanuel Vadot wakeup source for system suspend/resume. 38*c66ec88fSEmmanuel Vadot 39*c66ec88fSEmmanuel VadotOptional properties: 40*c66ec88fSEmmanuel Vadot 41*c66ec88fSEmmanuel Vadot- brcm,int-fwd-mask: if present, a bit mask to indicate which interrupts 42*c66ec88fSEmmanuel Vadot have already been configured by the firmware and should be left unmanaged. 43*c66ec88fSEmmanuel Vadot This should have one 32-bit word per status/set/clear/mask group. 44*c66ec88fSEmmanuel Vadot 45*c66ec88fSEmmanuel VadotIf multiple reg ranges and interrupt-parent entries are present on an SMP 46*c66ec88fSEmmanuel Vadotsystem, the driver will allow IRQ SMP affinity to be set up through the 47*c66ec88fSEmmanuel Vadot/proc/irq/ interface. In the simplest possible configuration, only one 48*c66ec88fSEmmanuel Vadotreg range and one interrupt-parent is needed. 49*c66ec88fSEmmanuel Vadot 50*c66ec88fSEmmanuel VadotExample: 51*c66ec88fSEmmanuel Vadot 52*c66ec88fSEmmanuel Vadotperiph_intc: periph_intc@1041a400 { 53*c66ec88fSEmmanuel Vadot compatible = "brcm,bcm7038-l1-intc"; 54*c66ec88fSEmmanuel Vadot reg = <0x1041a400 0x30 0x1041a600 0x30>; 55*c66ec88fSEmmanuel Vadot 56*c66ec88fSEmmanuel Vadot interrupt-controller; 57*c66ec88fSEmmanuel Vadot #interrupt-cells = <1>; 58*c66ec88fSEmmanuel Vadot 59*c66ec88fSEmmanuel Vadot interrupt-parent = <&cpu_intc>; 60*c66ec88fSEmmanuel Vadot interrupts = <2>, <3>; 61*c66ec88fSEmmanuel Vadot}; 62