From: One Thousand Gnomes <gnomes@lxorguk.ukuu.org.uk>
To: Michael Welling <mwelling@ieee.org>
Cc: linux-kernel@vger.kernel.org, gregkh@linuxfoundation.org, jslaby@suse.cz
Subject: Re: [PATCH 1/2] tty serial: xr17c15x driver
Date: Thu, 10 Apr 2014 11:46:48 +0100 [thread overview]
Message-ID: <20140410114648.68bfbf61@alan.etchedpixels.co.uk> (raw)
In-Reply-To: <20140410041035.GA26578@deathray>
On Wed, 9 Apr 2014 23:10:35 -0500
Michael Welling <mwelling@ieee.org> wrote:
> The 8250_core driver is supposed to support these devices but it has
> soft lockups on some hardware. This driver was ported from the vendors
> 2.6.37 driver and has been proven to work.
>
> I do not expect it to be merged, I am looking for feedback and
> possible fixes.
The thing to do is going to be to compare the various methods in the
driver with the 8250.c driver.
It appeas to be based upon an ancient 8250.c so if you want to pick up
all the changes then you need to compare with 8250.c, and if you want to
fix 8250.c instead you need to do exactly the same job so that seems a
more productive way to go about it IMHO.
There are bits of the driver you've pasted like the loop over ports for
shared IRQs you can't fix however, because they assume there is one
driver for all the ports. Not sure it matters though given your devices
are all going to be PCI bus.
Other thing to do would be to instrument serial_in/out and run the two
drivers briefly and compare the sequence of accesses and settings used.
Alan
next prev parent reply other threads:[~2014-04-10 10:47 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-04-10 4:04 Michael Welling
2014-04-10 4:04 ` [PATCH 2/2] Strip out the FSF address info Michael Welling
2014-04-10 4:10 ` [PATCH 1/2] tty serial: xr17c15x driver Michael Welling
2014-04-10 10:46 ` One Thousand Gnomes [this message]
2014-04-25 6:22 Michael Welling
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=20140410114648.68bfbf61@alan.etchedpixels.co.uk \
--to=gnomes@lxorguk.ukuu.org.uk \
--cc=gregkh@linuxfoundation.org \
--cc=jslaby@suse.cz \
--cc=linux-kernel@vger.kernel.org \
--cc=mwelling@ieee.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
all inboxes | Powered by JetHome®