From: Adam Ford <aford173@gmail.com>
To: Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
Jiri Slaby <jslaby@suse.com>, Vignesh R <vigneshr@ti.com>,
Andy Shevchenko <andriy.shevchenko@linux.intel.com>,
Douglas Anderson <dianders@chromium.org>,
Adam Ford <aford173@gmail.com>, Tony Lindgren <tony@atomide.com>,
Yegor Yefremov <yegorslists@googlemail.com>,
linux-serial@vger.kernel.org,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Serial 8250 DMA Broken on OMAP3630
Date: Sun, 6 Oct 2019 12:04:47 -0500 [thread overview]
Message-ID: <CAHCN7x+oXNA6WRiq1OnDdcgDTJrm-QyazyYLw-ow0vPMMmrVbQ@mail.gmail.com> (raw)
Has anyone else had any issues using the CONFIG_SERIAL_8250_DMA on the OMAP?
I can use the DMA on the legacy, omap-serial driver, but when I enable
the DMA on the 8250-omap driver, I get missing frames in Bluetooth.
The older driver seems to have an ISR that seems to address a variety
of items compared to the very tiny ISR for 8250-omap.c.
I am not exactly sure where to start, but if someone has any
suggestions on how I can troubleshoot, please let me know. As of now,
I have to disable CONFIG_SERIAL_8250_DMA to get the Bluetooth
connected to UART2 operational on a DM3730 at 3,000,000 baud, but it
appears to work just fine after some patches I just submitted for
handling RTS/CTS. The legacy omap-serial driver works fine with DMA.
adam
next reply other threads:[~2019-10-06 17:05 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-10-06 17:04 Adam Ford [this message]
2019-10-07 8:17 ` Serial 8250 DMA Broken on OMAP3630 Andy Shevchenko
2019-10-09 13:43 ` Vignesh Raghavendra
2019-10-09 14:08 ` Adam Ford
2019-10-09 17:34 ` Tony Lindgren
2019-10-09 19:27 ` Adam Ford
2019-10-09 20:16 ` Tony Lindgren
2019-10-10 14:11 ` Adam Ford
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=CAHCN7x+oXNA6WRiq1OnDdcgDTJrm-QyazyYLw-ow0vPMMmrVbQ@mail.gmail.com \
--to=aford173@gmail.com \
--cc=andriy.shevchenko@linux.intel.com \
--cc=dianders@chromium.org \
--cc=gregkh@linuxfoundation.org \
--cc=jslaby@suse.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-serial@vger.kernel.org \
--cc=tony@atomide.com \
--cc=vigneshr@ti.com \
--cc=yegorslists@googlemail.com \
/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).