[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <4FC35F97.2030400@antcom.de>
Date: Mon, 28 May 2012 13:20:55 +0200
From: Roland Stigge <stigge@...com.de>
To: Russell King - ARM Linux <linux@....linux.org.uk>
CC: alan@...ux.intel.com, gregkh@...uxfoundation.org,
linux-serial@...r.kernel.org, linux-kernel@...r.kernel.org,
kevin.wells@....com, srinivas.bakki@....com,
linux-arm-kernel@...ts.infradead.org, arnd@...db.de
Subject: Re: [PATCH] serial/of-serial: Add 16654 chip to compatible string
list
On 28/05/12 12:03, Russell King - ARM Linux wrote:
> Something which occurs to me. Normally, the digit at the end indicates
> how many ports are integrated into the device (0=1port, 2=2port, 4=4port.)
> Are you sure there isn't a ST16650 which has the same characteristics?
>
> We really should stick with naming these using the single port versions if
> at all possible.
Right.
This indicates to me that maybe this is not the right solution for my
original problem, anyway. :-)
Initially, with my RFC patch, there was an #ifdef for bigger FIFO in
case of LPC32xx where we have a 16550A variant with 64 byte fifos.
Looking at the 16x50 line:
16550A 16 bytes FIFOs
16650V2 32 bytes FIFOs
16750 64 bytes FIFOs
(?)
So maybe 16750 is the better choice for me, anyway. Already supported in
of-serial. Works for now, but need more testing. Another hint is that
16750 is advertised as "IP core for Soc" which matches the case of LPC32xx.
Maybe NXP can comment on this?
Thanks in advance,
Roland
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists