From: Roland Stigge <stigge@antcom.de>
To: alan@linux.intel.com, gregkh@linuxfoundation.org,
linux-serial@vger.kernel.org, linux-kernel@vger.kernel.org,
arnd@arndb.de, kevin.wells@nxp.com, srinivas.bakki@nxp.com,
linux-arm-kernel@lists.infradead.org
Cc: Roland Stigge <stigge@antcom.de>
Subject: [PATCH RFC] serial/8250: Adjusting FIFO parameters for LPC32xx
Date: Sat, 26 May 2012 18:11:18 +0200 [thread overview]
Message-ID: <1338048678-23991-1-git-send-email-stigge@antcom.de> (raw)
Hi,
this is how the modified FIFO is handled in the repositories at
git.lpclinux.com. Is there a better way for doing this (without ifdef)? Looks
like registering additional types (like PORT_16550A) isn't encouraged. Maybe
extending of_serial.c? The latter currently doesn't handle .fifosize and
.tx_loadsz, though.
Any suggestions appreciated.
Thanks in advance,
Roland
---
drivers/tty/serial/8250/8250.c | 7 +++++++
1 file changed, 7 insertions(+)
--- linux-2.6.orig/drivers/tty/serial/8250/8250.c
+++ linux-2.6/drivers/tty/serial/8250/8250.c
@@ -158,9 +158,16 @@ static const struct serial8250_config ua
},
[PORT_16550A] = {
.name = "16550A",
+#ifdef CONFIG_ARCH_LPC32XX
+ .fifo_size = 64,
+ .tx_loadsz = 32,
+ .fcr = UART_FCR_DMA_SELECT | UART_FCR_ENABLE_FIFO |
+ UART_FCR_R_TRIG_00 | UART_FCR_T_TRIG_00,
+#else
.fifo_size = 16,
.tx_loadsz = 16,
.fcr = UART_FCR_ENABLE_FIFO | UART_FCR_R_TRIG_10,
+#endif
.flags = UART_CAP_FIFO,
},
[PORT_CIRRUS] = {
next reply other threads:[~2012-05-26 16:12 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-05-26 16:11 Roland Stigge [this message]
2012-05-27 2:32 ` Arnd Bergmann
2012-05-27 9:06 ` Roland Stigge
2012-05-27 10:23 ` Arnd Bergmann
2012-05-27 11:37 ` Roland Stigge
2012-05-27 12:07 ` Arnd Bergmann
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1338048678-23991-1-git-send-email-stigge@antcom.de \
--to=stigge@antcom.de \
--cc=alan@linux.intel.com \
--cc=arnd@arndb.de \
--cc=gregkh@linuxfoundation.org \
--cc=kevin.wells@nxp.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-serial@vger.kernel.org \
--cc=srinivas.bakki@nxp.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®