Messages in this thread | | | Date | Fri, 30 Jun 2023 16:29:09 +0200 | Subject | Re: [PATCH] irq-bcm6345-l1: do not assume a fixed block to cpu mapping | From | Florian Fainelli <> |
| |
On 6/29/2023 8:26 AM, Jonas Gorski wrote: > The irq to block mapping is fixed, and interrupts from the first block > will always be routed to the first parent IRQ. But the parent interrupts > themselves can be routed to any available CPU. > > This is used by the bootloader to map the first parent interrupt to the > boot CPU, regardless wether the boot CPU is the first one or the second > one. > > When booting from the second CPU, the assumption that the first block's > IRQ is mapped to the first CPU breaks, and the system hangs because > interrupts do not get routed correctly. > > Fix this by passing the appropriate bcm6434_l1_cpu to the interrupt > handler instead of the chip itself, so the handler always has the right > block. > > Fixes: c7c42ec2baa1 ("irqchips/bmips: Add bcm6345-l1 interrupt controller") > Signed-off-by: Jonas Gorski <jonas.gorski@gmail.com>
Reviewed-by: Florian Fainelli <florian.fainelli@broadcom.com> -- Florian [unhandled content-type:application/pkcs7-signature]
| |