From: "Lennart Sorensen" <lsorense@csclub.uwaterloo.ca>
To: Sebastian Andrzej Siewior <bigeasy@linutronix.de>
Cc: linux-serial@vger.kernel.org, linux-kernel@vger.kernel.org,
Felipe Balbi <balbi@ti.com>
Subject: Re: [RFC PATCH] tty: serial: Add 8250-core based omap driver
Date: Fri, 4 Jul 2014 14:13:17 -0400 [thread overview]
Message-ID: <20140704181317.GE17769@csclub.uwaterloo.ca> (raw)
In-Reply-To: <20140703184808.GD17769@csclub.uwaterloo.ca>
On Thu, Jul 03, 2014 at 02:48:08PM -0400, Lennart Sorensen wrote:
> On Wed, Jul 02, 2014 at 06:00:09PM +0200, Sebastian Andrzej Siewior wrote:
> > This patch provides a 8250-core based UART driver for the internal OMAP
> > UART. The longterm goal is to provide the same functionality as the
> > current OMAP uart driver and hopefully DMA support which could borrowed
> > from the 8250-core.
>
> This sounds interesting. We are currently finding the omap serial driver
> awefully slow at handling serial traffic with ti's 3.12.y kernel branch,
> while the 3.8.y was seemingly a bit better (on the dra7xx eval board).
> Haven't had time to really investigate that yet though.
>
> > The whole PM-Runtime part is currently missing.
> > It has been only tested as console UART.
> > The tty name is ttyS based instead of ttyO. How big is the pain here,
> > what could be the easiest way to provide compatibility?
>
> I would certainly love to see ttyS instead of ttyO. But of course I am
> working on a new system that isn't released yet so changing things is
> a complete non issue for me. :)
>
> I should give this driver a try and see how it compares so far.
I get a segfault at this line:
mvr = uart_read(up, UART_OMAP_MVER);
I added it to ti's 3.12.y kernel and ran it on uart7 and uart8 on
a dra7xx-evm as a module (built in the kernel never booted due to
the crash).
--
Len Sorensen
next prev parent reply other threads:[~2014-07-04 18:13 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-07-02 16:00 [RFC PATCH] tty: serial: Add 8250-core based omap driver Sebastian Andrzej Siewior
2014-07-02 16:09 ` Felipe Balbi
2014-07-02 19:09 ` Aaro Koskinen
2014-07-02 19:25 ` Robert Nelson
2014-07-03 7:34 ` Tony Lindgren
2014-07-03 13:25 ` Felipe Balbi
2014-07-03 13:34 ` Robert Nelson
2014-07-03 14:07 ` Felipe Balbi
2014-07-03 15:44 ` Sebastian Reichel
2014-07-03 15:52 ` Felipe Balbi
2014-07-03 16:06 ` Sebastian Reichel
2014-07-03 16:19 ` Javier Martinez Canillas
2014-07-03 17:08 ` Felipe Balbi
2014-07-04 6:30 ` Tony Lindgren
2014-07-04 16:51 ` Sebastian Andrzej Siewior
2014-07-04 16:57 ` Robert Nelson
2014-07-07 7:26 ` Tony Lindgren
2014-07-07 13:26 ` One Thousand Gnomes
2014-07-04 16:59 ` Peter Maydell
2014-07-03 18:48 ` Lennart Sorensen
2014-07-04 18:13 ` Lennart Sorensen [this message]
2014-07-08 16:46 ` Sebastian Andrzej Siewior
2014-07-08 17:24 ` Lennart Sorensen
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=20140704181317.GE17769@csclub.uwaterloo.ca \
--to=lsorense@csclub.uwaterloo.ca \
--cc=balbi@ti.com \
--cc=bigeasy@linutronix.de \
--cc=linux-kernel@vger.kernel.org \
--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;
as well as URLs for NNTP newsgroup(s).