PXA/8250 UART Conflicts
maz at misterjones.org
Tue May 11 12:29:43 EDT 2010
On Tue, 11 May 2010 11:00:36 -0400, Michael Cashwell
<mboards at prograde.net>
> I'm using a PXA270-based Gumstix and a provisional 184.108.40.206 kernel to
> explore supporting a dual 8250-like UART chip over i2c for one of our
> hardware guys. But enabling both the 8250 and pxa2xx-uart drivers
> at the ttySn level. Both seem to do the following:
> serial_core: uart_register_driver() ->
> tty_io: tty_register_driver() ->
> char_dev: register_chrdev_region()
> using the same starting minor number. Thus the first driver gets
> /dev/ttyS0 and up and the rest fail with -EBUSY.
> Am I missing something? Are these drivers just incompatible and Kconfig
> shouldn't let me turn both on? (In fact, doing so kills the console if
> on an internal PXA uart because the 8250 driver loads first. That was
> with JTAG".)
Both Viper and Zeus platforms faced the exact same problem. On the Viper,
either we let the 8250 driver manage all the serial ports (including the
PXA ports), or we only have the 3 PXA UARTs. On the Zeus, the PXA driver is
simply out of the picture as the console lives on one of the 8250 UARTs.
> I'd like the tty layer to just assign the minor numbers in sequence,
> come first served. But I don't see how to get that. Or is there some
> platform way to influence the tty range requested?
I remember a SPARC hack in drivers/serial/8250.c (grep for CONFIG_SPARC)
for the exact same purpose. Not that I would recommend doing so for PXA or
any other platform...
Who you jivin' with that Cosmik Debris?
More information about the linux-arm-kernel