From: "Donald" <donald@asix.com.tw>
To: linux-serial@vger.kernel.org
Subject: Questions regarding adding a patch in linux/drivers/char/8250.c
Date: Mon, 21 May 2012 14:19:34 +0800 [thread overview]
Message-ID: <00a301cd3719$b3faa370$1befea50$@com.tw> (raw)
Hi,
This is Donald from ASIX Electronics Corp. My company has three PCI to Serial controllers, including MCS9845, MCS9835, and MCS9820.
Currently those serial devices using these three chips can directly use the Linux kernel's serial driver in
linux/drivers/char/8250.c. Recently we find these three chips have a hardware bug relating to parity error count function. We have a
software workaround for this issue. Below for reference is a pseudo code for this workaround.
serial8250_do_set_termios() {
If ((PID == MCS9845 || PID == MCS935 || PID == MCS9820) && ((termios->c_cflag & PARENB))) {
port->fifosize = 1; /* Change RX FIFO size to 1 byte */
up->ier &= ~UART_IER_RLSI; /* Disable RLSI interrupt */
}
}
Is it possible to add a patch into linux/drivers/char/8250.c for our chips' hardware issue? If it's not feasible to add a patch into
linux/drivers/char/8250.c, could we submit a new driver (e.g., mcs78xx_8250.c) to Linux kernel for devices using these three chips
(i.e., those devices can use new driver mcs78xx_8250.c instead of 8250.c)
Your reply to my questions will be very appreciated.
Regards,
Donald Lee
~~~~~~~~~~~~~~~~~~~~~~~~
R&D Division
ASIX Electronics Corporation
TEL: 886-3-5799500 ext.515
http://asix.com.tw/
~~~~~~~~~~~~~~~~~~~~~~~~
next reply other threads:[~2012-05-21 6:52 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-05-21 6:19 Donald [this message]
2012-05-21 9:28 ` Questions regarding adding a patch in linux/drivers/char/8250.c Alan Cox
2012-05-29 8:37 ` Donald
2012-06-18 3:07 ` Donald
2012-06-19 9:18 ` Alan Cox
2012-06-19 12:35 ` Donald
2012-05-21 9:30 ` Alan Cox
2012-05-21 12:54 ` Donald
2012-05-21 15:07 ` Jason Smith
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='00a301cd3719$b3faa370$1befea50$@com.tw' \
--to=donald@asix.com.tw \
--cc=linux-serial@vger.kernel.org \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.