From: Wolfram Sang <w.sang@pengutronix.de>
To: Lauri Hintsala <lauri.hintsala@bluegiga.com>
Cc: Sascha Hauer <s.hauer@pengutronix.de>,
"linux-arm-kernel@lists.infradead.org"
<linux-arm-kernel@lists.infradead.org>,
linux-serial@vger.kernel.org
Subject: Re: mxs-auart serial driver DMA support?
Date: Thu, 12 Jan 2012 12:00:11 +0100 [thread overview]
Message-ID: <20120112110010.GF2775@pengutronix.de> (raw)
In-Reply-To: <4F0EB5BB.1060008@bluegiga.com>
[-- Attachment #1: Type: text/plain, Size: 838 bytes --]
On Thu, Jan 12, 2012 at 12:28:11PM +0200, Lauri Hintsala wrote:
> On 01/12/2012 11:42 AM, Wolfram Sang wrote:
> >
> >>Any plans to add DMA support for mxs-auart serial driver? I noticed
> >>it is impossible to archive full 3.25 Mbs speed with current one.
> >
> >No plans from our side, currently.
>
> OK, AUART works fine with 115200 bps but over that it loose data
> randomly. I have seen fifo overrun errors during receiving data with
> 1Mbs and over. So current driver is unuseful with higher baud rates.
Care to send a patch adding this information to Kconfig help text and/or
source code? Would be much more useful there, I think.
Regards,
Wolfram
--
Pengutronix e.K. | Wolfram Sang |
Industrial Linux Solutions | http://www.pengutronix.de/ |
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 198 bytes --]
WARNING: multiple messages have this Message-ID (diff)
From: w.sang@pengutronix.de (Wolfram Sang)
To: linux-arm-kernel@lists.infradead.org
Subject: mxs-auart serial driver DMA support?
Date: Thu, 12 Jan 2012 12:00:11 +0100 [thread overview]
Message-ID: <20120112110010.GF2775@pengutronix.de> (raw)
In-Reply-To: <4F0EB5BB.1060008@bluegiga.com>
On Thu, Jan 12, 2012 at 12:28:11PM +0200, Lauri Hintsala wrote:
> On 01/12/2012 11:42 AM, Wolfram Sang wrote:
> >
> >>Any plans to add DMA support for mxs-auart serial driver? I noticed
> >>it is impossible to archive full 3.25 Mbs speed with current one.
> >
> >No plans from our side, currently.
>
> OK, AUART works fine with 115200 bps but over that it loose data
> randomly. I have seen fifo overrun errors during receiving data with
> 1Mbs and over. So current driver is unuseful with higher baud rates.
Care to send a patch adding this information to Kconfig help text and/or
source code? Would be much more useful there, I think.
Regards,
Wolfram
--
Pengutronix e.K. | Wolfram Sang |
Industrial Linux Solutions | http://www.pengutronix.de/ |
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 198 bytes
Desc: Digital signature
URL: <http://lists.infradead.org/pipermail/linux-arm-kernel/attachments/20120112/a517d75b/attachment.sig>
next prev parent reply other threads:[~2012-01-12 11:00 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-01-12 6:33 mxs-auart serial driver DMA support? Lauri Hintsala
2012-01-12 6:33 ` Lauri Hintsala
2012-01-12 9:42 ` Wolfram Sang
2012-01-12 9:42 ` Wolfram Sang
2012-01-12 10:28 ` Lauri Hintsala
2012-01-12 10:28 ` Lauri Hintsala
2012-01-12 11:00 ` Wolfram Sang [this message]
2012-01-12 11:00 ` Wolfram Sang
-- strict thread matches above, loose matches on Subject: below --
2012-01-12 6:30 Lauri Hintsala
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=20120112110010.GF2775@pengutronix.de \
--to=w.sang@pengutronix.de \
--cc=lauri.hintsala@bluegiga.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-serial@vger.kernel.org \
--cc=s.hauer@pengutronix.de \
/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.