From: Chuah Kim Tatt <kim.tatt.chuah@intel.com>
To: gregkh@linuxfoundation.org, vinod.koul@intel.com
Cc: heikki.krogerus@linux.intel.com,
andriy.shevchenko@linux.intel.com,
mika.westerberg@linux.intel.com, kim.tatt.chuah@intel.com,
linux-kernel@vger.kernel.org, jui.nee.tan@intel.com,
peter@hurleysoftware.com, linux-serial@vger.kernel.org
Subject: [PATCH v2 0/3] Fix DNV HSUART RX DMA timeout interrupt issue
Date: Wed, 15 Jun 2016 13:44:10 +0800 [thread overview]
Message-ID: <1465969453-16198-1-git-send-email-kim.tatt.chuah@intel.com> (raw)
From: "Chuah, Kim Tatt" <kim.tatt.chuah@intel.com>
These patches fix a DNV HSUART DMA issue with timeout interrupts, where
RX data is stuck in buffer when RX DMA is used and the number of received
bytes is less than 4096.
These patches have been tested on Intel Denverton platform.
Changes from v1:
- Added patch "serial: 8250_dma: Export serial8250_rx_dma_flush()" to solve
build error when CONFIG_SERIAL_8250_MID is set to "m".
Chuah, Kim Tatt (3):
dmaengine: hsu: Export hsu_dma_get_status()
serial: 8250_dma: Export serial8250_rx_dma_flush()
serial: 8250_mid: Read RX buffer on RX DMA timeout for DNV
drivers/dma/hsu/hsu.c | 90 +++++++++++++++++++++++++++++---------
drivers/dma/hsu/pci.c | 11 ++++-
drivers/tty/serial/8250/8250_dma.c | 1 +
drivers/tty/serial/8250/8250_mid.c | 24 +++++++---
include/linux/dma/hsu.h | 14 ++++--
5 files changed, 109 insertions(+), 31 deletions(-)
--
1.9.1
next reply other threads:[~2016-06-15 5:45 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-06-15 5:44 Chuah Kim Tatt [this message]
2016-06-15 5:44 ` [PATCH v2 1/3] dmaengine: hsu: Export hsu_dma_get_status() Chuah Kim Tatt
2016-06-30 4:34 ` Vinod Koul
2016-06-15 5:44 ` [PATCH v2 2/3] serial: 8250_dma: Export serial8250_rx_dma_flush() Chuah Kim Tatt
2016-06-15 5:44 ` [PATCH v2 3/3] serial: 8250_mid: Read RX buffer on RX DMA timeout for DNV Chuah Kim Tatt
2016-06-15 12:15 ` [PATCH v2 0/3] Fix DNV HSUART RX DMA timeout interrupt issue Andy Shevchenko
2016-06-16 9:34 ` Heikki Krogerus
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=1465969453-16198-1-git-send-email-kim.tatt.chuah@intel.com \
--to=kim.tatt.chuah@intel.com \
--cc=andriy.shevchenko@linux.intel.com \
--cc=gregkh@linuxfoundation.org \
--cc=heikki.krogerus@linux.intel.com \
--cc=jui.nee.tan@intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-serial@vger.kernel.org \
--cc=mika.westerberg@linux.intel.com \
--cc=peter@hurleysoftware.com \
--cc=vinod.koul@intel.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
all inboxes | Powered by JetHome®