From: Alan Cox <alan@lxorguk.ukuu.org.uk>
To: Donald <donald@asix.com.tw>
Cc: linux-serial@vger.kernel.org
Subject: Re: Questions regarding adding a patch in linux/drivers/char/8250.c
Date: Mon, 21 May 2012 10:28:48 +0100 [thread overview]
Message-ID: <20120521102848.7bfb49e0@pyramind.ukuu.org.uk> (raw)
In-Reply-To: <00a301cd3719$b3faa370$1befea50$@com.tw>
On Mon, 21 May 2012 14:19:34 +0800
"Donald" <donald@asix.com.tw> wrote:
> 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?
Sure.
The only question I would have is how do we reliably detect the presence
of the UART devices with this erratum. Can we do it from the PCI
identifier ?
Alan
next prev parent reply other threads:[~2012-05-21 9:25 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-05-21 6:19 Questions regarding adding a patch in linux/drivers/char/8250.c Donald
2012-05-21 9:28 ` Alan Cox [this message]
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=20120521102848.7bfb49e0@pyramind.ukuu.org.uk \
--to=alan@lxorguk.ukuu.org.uk \
--cc=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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox