Hi, On Thu, Feb 19, 2015 at 8:18 AM, Steven Saunderson <[email protected]> wrote: > Hi, > > I'm running 3.19 on my CT and can't get the internal UARTs to work. The two > UARTs I'm testing are /dev/ttyS0 (debug port) and /dev/ttyS2 (connects to BT > half of AP6210). > > With the 3.4 kernel, ttyS0 uses irq 33 and the BT UART uses irq 35. But > with the 3.19 kernel, according to /proc/tty/driver/serial, ttyS0 uses irq > 41 and ttyS2 uses irq 42. The CT dtb specifies interrupts 1 and 3 for these > devices and given the convention of adding 32 these irq numbers become 33 > and 35 which sounds right to me. But for some strange reason these devices > end up with irqs 41 and 42. > > I would think that any device inside the SoC would be hard-wired to a > certain interrupt line and the irqs here should always be 33 and 35. > > Does anybody know whether using irqs 41 and 42 here could be correct ? Or > has anybody got the UARTs working with 3.19 ?
Mine is working fine. Mine is also using irqs 41 and 42. You should look at /proc/interrupts. You'll see that 41 and 42 are the interrupt numbers used in the kernel. The real IRQ is between "GIC" and the last column, which says which device or driver is using it. The software and hardware interrupt numbers aren't always in the same order. It previously was with GIC. Recently hierarchy irq domain support was added. This might have changed the behavior. ChenYu -- You received this message because you are subscribed to the Google Groups "linux-sunxi" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/d/optout.
